Implementing SCRUM in a team is a nice challenge. Based on the amounts of discussion on SCRUMButt and SINO (SCRUM In Name Only), it is not really easy to get the process, the artefacts and the mind-set right within each team. But when it works, the organisation often wants more. Scaling the agile implementation brings along many more challenges, among which the definition of scaling. I found a nice nice interview with Steve Spearman on infoq site, where he states:
” To some people scaling agile means going from a few agile teams to multiple, or even hundreds of, agile development teams. There are some unique challenges that come up whenever you have an organization where more than 3 or 4 agile teams need to work together in a coordinated fashion. Other definitions of scaling may be to spread agile beyond IT, seeking agility in business operations or other areas of the organization.”
The good news is, that there are some frameworks that can help you out. The bad news is they each have their accents, their own strong and weak point. But how do the various frameworks differ? Which do you use in your organisation?
In the interview Steve refers to the ASK matrix he made that compares the scaling frameworks. The site provides links to the frameworks itself, compares them and shares some comment by framework authors of DAD, LeSS and Spotify authors. It seems a nice read for the summer-months. Check it out on www.agilescaling.org