When we talk about adopting any new framework or methodology, we think about how we can incorporate these changes into our organization. We simply cannot impose any change in our organization and get started with it, there has to be some process or ways to incorporate that. Also, there are some ways to incorporate Scrum changes within our organization. There include five activities in adopting the Scrum successfully:
So to remember, we call it by the acronym ADAPT.
Let’s now talk about the Patterns of Adopting and Spreading a Scrum:
Patterns for Adopting Scrum
Start Small or Go All In
Organizations go ahead with it like a Pilot project, like selecting few team members and implementing Scrum with them, It's a ‘Start Small’ pattern. The other approach can be Go All In, which is like the executives are convinced and want the whole organization to implement in one go.
Reasons to prefer starting small
- It’s less expensive
- Early success guaranteed
- Avoids risks of going all in
- Less stressful
- Can be done without much change
Reasons to prefer going all in
- Reduces resistance
- Avoids problems within different teams
- The All-in transition is Quick!
Choosing between the two
As recommended by Mike Cohn, one should always Start Small! It involves less cost, and guaranteed early success. Going all in should be in limited cases, only when it’s a quick need. Also, it involves more cost/money as there are a lot of changes in different departments if required.
Public Display of Agility or Stealth
The next pattern that comes into the picture is whether to Publicize it or not. We can do the Public Display of Agility. In this approach, the organization announces that it is adopting Scrum. This can vary from announcing it in a meeting room to announcing it through the press release.
The other approach is Stealth transition. In this, only team members know they are using Scrum until the project is complete.
Reasons for Public Display of Agility
- Everyone knows that team is doing it and they are more likely to be focussed
- Operating publicly is a firm statement of commitment
- You can solicit organizational support
- It sends a powerful message
Reasons for Stealth Transition
- A chance to make progress before resistance starts
- It keeps pressure off
- No one knows until you tell them
- If no one knows, no one can tell you to stop
Choosing between the two
As recommended by Mike Cohn, always choose to make a public display of Agility when you are confident and committed to the transition and when you expect a lot of resistance but want to overcome it quickly.
In contrast, choose a quiet approach, when you want to do an experiment using Scrum.
Patterns for Spreading Scrum
Getting started with Scrum is one thing, spreading it across the organization is another. Unless you choose an all-in transition, you will need to build upon the successes of the first few teams as you move Scrum to other teams.
There are 3 general patterns given by Mike Cohn that talks about spreading Scrum.
Split and Seed
This talks about taking a team that has begun to be successful with Scrum and using its team members to seed new teams.
It’s typically put to use after the first few teams have successfully implemented and adopted Scrum. By this time, each team member understands how Sprint work and how the ready software is delivered at the end of the sprint.
In Split and Seed pattern, we split one functioning Scrum team into each half of the original team forming the basis of the new team. New people are then added to these split teams to form new Scrum teams.
A large initial team is used to seed as many as four new teams. Collated below are the reasons to prefer Split and Seed pattern.
- Add teams more quickly
- Each team has someone with Scrum experience to guide them
Grow and Split
The Grow and Split pattern involve adding team members until the team is large enough that it can be comfortably split in two. Immediately after splitting, each of the new teams will probably be on the small end of the desirable size ranging five to nine members. After allowing the new teams one sprint at this reduced size, new members are added until each team becomes a large enough that it can also be split. This pattern repeats until the entire organization has transitioned.
In following cases, you can prefer Grow and Split pattern.
- Don’t have to destroy any existing teams
- Team members feel more continuity from sprint to sprint
The Third pattern of Spreading Scrum is Internal Coaching. In the organizations, there include types of teams. Some teams excel with the new agile approach, while others struggles. On each team, there exists one identified person who understands and implement Scrum successfully. That person is assigned as a Coach for other teams.
Coaches were given responsibilities to attend sprint meetings, daily scrum each week and coach other teams.
Reasons to prefer Internal Coaching
- Well running teams do not need to be Split
- Coaches can be selected for new teams
- Coaches can move from team to team
Choosing your Pattern!
In general, consider going with Split and Seed pattern, when in a hurry. It is the fastest way of spreading Scrum. However, if the technology doesn’t support moving people among teams, changing the team members can affect the productivity.
The Grow and Split pattern is simply more natural and direct approach. Consider using this approach if there is no sense of urgency as it is less risky.
Internal Coaching can be used on its own, mostly when the group is large enough and when splitting teams are not possible for the projects.