3 years ago I had to deal with all kind of processes: The no-process strategy (my favorite .. sight), heavy waterfall (I’m still soaked by that one …), home grown iterative process etc. Scrum was definitely only discussed during a good Rugby game.
This is where it gets interesting (I realize this was a long introduction but I wanted to give you a bit of a background). A lot of developers and testers from other part of the world are engaged in delivering the new softwares but, for now, stayed on their own development process. There were good reasons for this but my organization ended up testing a software developed in multiple location, which is fine, but with different development processes in each location, which is definitely not fine ! If the development teams are independent, working on different products, I’m fine having to deal with different processes. But distributed development with different processes is a big no-no !
You’d think that we might have been better off standardizing on scrum right at the beginning of the project. Maybe, maybe not (we’ll never know). I actually see some benefits which could prove useful in the near future. For development and test teams working on non-agile processes, scrum might be a BIG cultural change which you probably have to introduce with care. You might want them to realize the benefit of scrum on real projects to get their mind ready. I see these few months where we’ve been on different processes as a first step to transition for a large development organization.
So you’ve got buy-in from executives management. You’ve got your developers, testers, product managers, a bit more comfortable with scrum. How do you ensure they don’t go wild and actually embrace and apply it properly?
If you already have people trained and experienced in scrum within the different groups, you might want to use them for internal trainings. They really need a first experience as a ScrumMaster so they can work with the team, the stakeholders, the product owner etc. Explaining the concepts is not the big challenge here. It can be done fairly easily. The whole challenge (and fun) is the implementation of the various principles and the proper use of all scrum artifacts. The person needs to set the dynamics, the pace. Ensures that everyone understand their new responsibilities and role and how they fit within the new process. The person doesn’t necessarily need to be the scrum master but need to be working daily with the team until stability is reached.
When transitioning your organization to scrum, you need to realize the management and hierarchical implication. A scrum team is not managed but manages itself and that’s the beauty of it. You don’t have development leads, test leads within a scrum team. You have developers and testers all working in the same direction to deliver what they have committed to deliver to their stakeholders. The ScrumMaster is not the manager of this team. He is a facilitator, helping the team focusing on what they do best (hopefully developing great softwares !), helping the team organizes itself, dealing with external issues, giving visibility on progress to stakeholders, setting the pace etc.
In a sense, introducing scrum shift the lines and makes the hierarchy a bit flatter which might be disrupting at first. This is why, having external training might be a good idea if your development organization hierarchy is deep or if politics might get in the way. The term “ScrumMaster” gives a sense of rank which doesn’t exist but could be perceived as such.I’ve always found the term poorly chosen. Having a third-party helping you during your transition might ease the friction and put everyone at the same level.
So you can have internal training, getting help from certified scrum master to help you training your team. What else? Well, I’m a firm believer in self-training and we need to take advantage of all the resources around us. It’s not like we’re in the 60′s trying to learn something about a new subject. This is 2009, I can order whatever book I need on any given subject and have it delivered the next day, I can find tons of information on the Internet: White papers, ebooks, articles, training video etc. I can participate in specialized forums to engage in discussions, get answers etc. We have NO excuse. You just need to be careful and really scope your research for information as it is endless. You might want to give pointers to your organization to get them started.
I find this video quite useful as an overview of scrum. It can be given to everyone in your organization from your developers, testers, product owner, executives and also stakeholders. I would say especially stakeholders as they might not understand what the fuss is all about and how it’s going to help them get better softwares. They also have a role to play in the process and they need to understand it properly. Executives are also key people to “train” as you definitely want their buy-in and full support. Be careful, this is not a comprehensive training of course and miss quite important point but it’s still a good high level overview.
I will probably come back regularly on this subject as we’re right in the middle of the transition and I’m pretty sure this is going an interesting roller-coaster ride !