Bookmark and Share

Rolling out Scrum in an organisation

There is no one solution to rolling out Scrum in an organisation; every organisation has their own challenges when it comes to change. However, the wonderful thing about Scrum is that it is a simple framework, it is easily transferable to others and positive effects can be quickly felt by everyone involved.

The keys to success lie in good planning, good information, getting people involved and helping the people grow into filling the required roles so they can become self sufficient. At CoreWorks we run a campaign in which we inform, involve, lead, coach, track and grow people so they can succeed with Scrum.


When an organisation takes a decision to implement any form of change it is critical that an clear and simple information is pushed out into the organisation. This needs to be at all levels of the organisation 


The most effective way to ensure success in rolling out Scrum in an organisation is to get people from the organisation involved and give them ownership of the roll out process. While it is not always possible to take everyone on board during the planning stage CoreWorks ensures that everyone that is touched by Scrum has a chance to attend an introduction to Scrum and to participate in fun workshops designed to re-enforce Scrum principles and practices discussed in the introduction to Scrum.


CoreWorks' experience with Scrum allow us to take the lead when rolling out Scrum which gives the opportunity for the people in the organisation to adjust to working with Scrum and to get comfortable with the process. However, the goal is always to transfer the lead to the organistaion its self.


Through coaching and tracking the Scrum Team's progress CoreWorks helps the organisation to become self sufficient in running Scrum projects.


CoreWorks tracks the progress of the Scrum Team during the first few Sprints in order to determine how well the Scrum Team is working with key areas of the Scrum process. This is done during the Sprint Retrospective where each Scrum Team member is asked to complete a short survey originally by Bas Vodde at Nokia Siemens Networks in Finland - funnily enough called the Nokia Test.


Using both input from the Sprint Retrospectives and Nokia Test, CoreWorks helps the Scrum Team grow towards becoming a hyperproduct team.

A typical roadmap to Scrum

In our experience a typical roll out looks like this:

  1. Introduce Scrum to and get the backing of senior management
  2. Introduce Scrum to and get the backing of managers and project leaders
  3. Introduce Scrum to and get the backing of the people who will form the Scrum Team
  4. Run Scrum workshops that model the Scrum process e.g. play the XpGame
  5. Choose the projects that will be run under Scrum
  6. Introduce Scrum to the selected customers
  7. Inform the rest of the organisation about the Scrum rollout
  8. Collect and organise the Product Backlog for the selected projects
  9. Run Sprint 1 - with 100% involvement from a certified Scrum Master
  10. Run Sprint 2 - with 50% involvement from a certified Scrum Master
  11. Run Sprint 3 - with possibly 25% with a certified Scrum Master but most can run solo by this point
  12. There after it is a good idea to have a certified Scrum Master come in for the first couple of months just to check the Scrum Team progress.

One last thing to be prepared for, is the interest from other areas/departments. Don't be surprised if people want to come by and ask about Scrum and see it in action so it is always a good idea to have a 5 minuet introduction to Scrum on hand.



Latest articles