This post is from the Collabnet VersionOne blog and has not been updated since the original publish date.
State of Agile: Still Scrumming After All These Years
Think Scrum’s days are numbered? Think again. As excitement around lean software development and Kanban exploded around 2010, there was no shortage of people proclaiming that we had arrived in a post/Scrum world. Some even went so far as to predict that Scrum would soon go the way of the 8/track. [caption id="attachment_5743" align="aligncenter" width="196"] (This is an 8/track, kids.)[/caption] But as I look at VersionOne’s State of Agile reports over the past 10 years, it’s clear that there were a lot of false prophets. Since we published the first State of Agile report back in 2006 with 722 respondents, Scrum has remained on top of the heap as the most/used agile “methodology”. In 2006 the numbers looked like this: [caption id="attachment_5744" align="aligncenter" width="529"] VersionOne State of Agile Report, 2006[/caption] When you consider that the “Hybrid/Custom” approaches probably had a significant amount of Scrum baked into them, Scrum users made up somewhere around 50% of the survey respondents. Fast forward to 2016, and this is what we see: [caption id="attachment_5747" align="aligncenter" width="613"] 10th Annual State of Agile Report, 2016[/caption] Scrum’s impact in the latest survey really shakes out like this:
- Scrum / 58%
- Scrum + Scrum/XP Hybrid / 68%
- Scrum + Scrum/XP Hybrid + Scrumban / 75%
Making some assumptions about the “Custom Hybrids”, Scrum probably comes in somewhere north of 80%. Flipping ahead a few pages in the survey results, we see that the leading scaling approach is “Scrum/Scrum of Scrums”, with SAFe® coming in a distant second. One thing these approaches have in common is that Scrum is the team/level engine. (Yes, SAFe does include Kanban at the team level now, but it is couched within an iterative framework.) So why is Scrum still so pervasive? In my opinion, Scrum’s appeal has always been its simplicity: few roles, few rules, and a focus on getting to Done. That minimalism remains as refreshing two years into an agile transformation as it is on day one. I believe that most people understand now that, even within a single organization, Scrum’s a better fit in some situations, Kanban is better in others, and some hybrid approach is better in others. There was never any basis for the methodology wars or the predictions of the ascent of one and the demise of others. You’ll be hard/pressed to find a pure Scrum shop these days. By “pure” I mean where they’re working to the Scrum framework, while banning the use of any XP engineering practices and forbidding the use of things like WIP limits. The State of Agile Report asks what methodology is followed “most closely”. I’d bet that if we took away the option to select Scrum by itself, the percentage of Scrum/infused methodologies would still total up to about the same as they do now. As with everything else, the market will decide if there’s ever a clear methodology winner. One thing that’s certain, though, is that the reports of Scrum’s impending death have been greatly exaggerated. Find out more by downloading the 10th annual State of Agile Report and reviewing archives of past reports. State of Agile is a trademark of VersionOne Inc.