back to notes

Learning Plan for Agile Scaling Organizations

Learning Plan for Agile Scaling Organizations

1 Goal
The goal of the Learning Plan for organizations that are scaling to ensure that everyone understand the fundamentals of the processes and roles of Agile, Scrum, SAFe and Kanban. Secondarily it is to provide a forum to discuss unique situations, circumstances and environments that the organization and teams encounter and have to deal with. The items below are meant to be self-contained and don’t require other items in order for the attendee to understand and use the concepts and techniques. However, in order for someone to thoroughly understand the concepts and processes it is recommended that they participate in all presentations that are appropriate for their role. As such, in section 3 we present the recommended modules for the following organizational roles, Scrum Master, Product Owner, Team member, Leadership and Project Management. Additionally, there is a matrix by role for easier reference. Section 4 specifies the most important modules for people to take.
Most of these learning modules are expected to be short in length and also include a fair amount of time for questions. Some are much longer, e.g. “Leading SAFe” for leadership. Also, with a few exceptions most are expected to be presented in real time in a virtual mode.

Note that Leadership includes anyone involved in guiding the organization either as a manager of others or as individual contributors.
Some of the modules below have no description in this documents because it is expected that the reader would understand what the subject matter is at a high level. Some do have descriptions to better set expectations. It is expected that all modules would have extensive descriptions when sent or presented to potential attendees.

2 Learning Modules

2.1 Event based workshops
The goal of modules in this section is to provide to the attendee the fundamental description of each Scrum event so that they can participate in the event and help others with the facilitation. There are certain aspects of these events at the team level that are different for teams in an organization that is scaling their efforts. While the changes are not significant in activity, teams need to better understand the effect they have on other teams and how other teams affect them. Additionally, the plans are more widely tied together. This module will describe all the normal processes as well as the changes for scaling.
For each of the ceremonies below the following content will be defined:
• What the purpose of the event is and is not
• Who attends and their roles in the event
• Useful and not so useful variations
• Additional information required for scaling organizations

2.1.1 Daily Scrum – 30 minutes

2.1.2 Sprint Planning – 1 hour

2.1.3 Backlog Refinement – 30 minutes

2.1.4 Sprint Retrospective – 30 minutes

2.1.5 Sprint Review – 30 minutes

2.2 Roles
The goal of modules in this section is to provide to the attendee the fundamental description of each role used in the scaling organization so that they understand the responsibilities of each role. Some of the roles are traditional organizational roles and the content is to explain how those roles are adapted to work in an Agile/Lean environment. The Scrum roles, Scrum Master, Product Owner and Team Member workshops are explained in detail. Some roles (QA) include a discussion of using tools and techniques when working with teams. Some roles will require a more in-depth instruction on how to use certain tools (e.g. Jira) and therefore people are encouraged to take the additional modules in section 2.7.

2.2.1 Scrum Master - 2 hours

2.2.2 Product Owner and Product Management- 2 hours

2.2.3 Project Management – 1 day

2.2.4 Quality Assurance – 2 Hours (Includes role definition and tools and techniques instruction)

2.2.5 Team member – 1 hour

2.2.6 Business Analyst – 1 - hour

2.2.7 Release Train Engineer – 2 hours

2.3 Portfolio, Program & Team Work Items
The goal of the modules in this section is to provide the attendee with a complete understanding of how work items for the organization and teams are identified, created, maintained and used within the organization.

2.3.1 Initiatives, Epics & Features – 2 hours

2.3.2 User Stories – Five 2 hour sessions

2.4 Scaling for Leadership
The goal of this section is for the attendees to understand Agile/Lean and how a large organization can deliver products.

2.4.1 Leading SAFe – 2 days
This workshop/class is designed for those who want to get the initial certification in SAFe called “Certified SAFe Agilist” or the SA certification and will be taking the certification test. It is not designed to be customized for an organization. It is a 2 day course that requires the attendees to fully participate.

2.4.2 SAFe for Execs – 4 hours

2.4.3 Agile for Practice Managers – 2 hours
This workshop is for managers and leaders that have been part of an Agile practice for a while and now have questions that are beyond the normal foundation questions. It is meant to be run as a Lean Coffee with the attendees deciding on the issues/problems/questions to be addressed with multiple coaches providing a variety of guidance. Time is allotted for in-depth discussions. This may also be done periodically with audience requested themes.

2.4.4 Scrum of Scrums – 30 minutes
In order for a large program to deliver products there needs to be coordination. The Scrum of Scrums event facilitates the coordination of addressing risks, dependencies and deliveries. While the name implies a simple scaling up of the Scrum event, this event is different in process, focus, and attendees.

2.5 What do I do when…?" – A Series of Lean Coffees - 1 hour each
The goal of this module is for attendees to understand and deal with common scenarios, situations, and anti-patterns that come up in the course of a Sprint or delivering product. This session is meant to discuss the following statements.
• Work is inserted into Sprint – Often or occasionally
• Priorities change mid-sprint
• No one participates in the retro
• The daily Scrum lasts an hour
• "Fine, but we're different!"
• Additional topics to be defined by attendees

2.6 Metrics
The goal of this section is to introduce the attendees to various kinds of metrics that are used to track both team and product progress.

2.6.1 Scrum Team Metrics – 90 minutes
There are certain metrics that individual teams use to help improve their efficiency. This module is meant for team members to help them understand the importance of tracking certain information and how it affects their decisions on planning.

2.6.2 Program/Portfolio/SAFe Metrics – 1 hour
Just as there are specific metrics for individual teams to use, there are metrics that a program can use that are different from the team metrics.

2.6.3 Advanced Metrics – 90 minutes
This module describes more advanced metrics that can be used at a team but mostly at a program level and how to get the information from Jira.

2.6.4 Kanban Team Metrics – 90 minutes
Kanban teams, because of how they work will focus on different metrics than a scrum team. This module will also focus on how to use Jira for Kanban teams and techniques for providing information on progress.

2.7 Tools and Techniques
The goal for this section is give some detail on how to use corporate tools and Agile techniques.

2.7.1 Jira – 90 minutes

2.7.2 TDD & BDD – 90 minutes

2.7.3 Kanban for teams – 2 hours - See Agile Coach for recommendations

3 Learning Goals by Role
This section provides guidance on which module should be taken based on the role of the person in the organization. However, any person should feel free to take any learning module.

3.1 Scrum Master
A Scrum Master should take the following modules:
• All modules in section 2.1, 2.2, 2.3, 2.5
• Modules 2.4.1 and 2.4.4
• Module 2.5 is optional
• If they have a Scrum team, sections 2.6.1 and 2.6.2
• If they have a Kanban team, sections 2.6.2 and 2.6.4
• Module 2.7.1
• Module 2.7.3 if they have a Kanban team

3.2 Product Owner
A Product Owner should take the following modules:
• All modules assigned to the Scrum Master

3.3 Leader
Leaders and stakeholders should take the modules in 2.4

3.4 Team Member
Team members on a Scrum Team should take modules:
• All modules in 2.1
• Modules 2.2.1, 2.2.2, 2.2.4, 2.2.5
• Module 2.3.2
• Either module 2.6.1 or 2.6.4 depending on their team

3.5 Project Management
Project Management should take modules:
• Module 2.2.3
• Either module 2.4.1 or 2.4.2
• Module 2.6
 
3.6 Learning Plan by Role Matrix
Learning Plan by Role - Scrum Master (SM) - Product Owner (PO) - Team Member (TM) - Leader (L) - Project Mgmt (PM)
2.1 Event Based Workshops
2.1.1 Daily Scrum SM PO TM
2.1.2 Sprint Planning SM PO TM
2.1.3 Backlog Refinement SM PO TM
2.1.4 Sprint Retrospective SM PO TM
2.1.5 Sprint Review SM PO TM

2.2 Roles
2.2.1 Scrum Master SM PO TM
2.2.2 Product Owner & Product Mgmt SM PO TM
2.2.3 Project Management SM PO PM
2.2.4 Quality Assurance SM PO TM
2.2.5 Team Member SM PO TM
2.2.6 Business Analyst SM PO
2.2.7 Release Train Engineer SM PO

2.3 Portfolio, Program & Team Work Items
2.3.1 Initiatives, Epics & Features SM PO
2.3.2 User Stories SM PO TM

2.4 Scaling for Leadership
2.4.1 Leading SAFe L
2.4.2 SAFe for Execs L
2.4.3 Agile for Practice Managers L
2.4.4 Scrum of Scrums SM PO L PM

2.5 Lean Coffee SM PO

2.6 Metrics
2.6.1 Scrum Team Metrics SM PO TM PM
2.6.2 Program/Portfolio/SAFe Metrics SM PO PM
2.6.3 Advanced Metrics PM
2.6.4 Kanban Team Metrics SM PO PM

2.7 Tools & Techniques
2.7.1 Jira SM PO TM
2.7.2 TDD & BDD SM PO TM
2.7.3 Kanban for teams SM PO TM

4 Prioritized Learning Plan
This section lists the modules in priority order.
1. Module 2.1.2 - “Sprint Planning”
2. Module 2.5 - “What Do I Do When…” Lean Coffee – This should be started immediately focused on the primary issues uncovered by the SMs. Also, use this to prioritize addition Lean Coffee topics or separate modules.
3. Module 2.4.1 - “Leading SAFe” – Ideally leadership should take this course prior to launching the first Program Increment so they are better able to lead the organization.
4. Module 2.2.1 – “Scrum Master” – Describe the role of the SM to all since there seems to be some confusion between the SM and Project Manager roles.
5. Module 2.2.2 – “Product Owner” – Describe the role of the PO and contrasted to the SM.