Now I need a place to hide away?
Well it's not quite that bad. Scrum has come a long way since Jeff Sutherland and Ken Schwaber decided to shake up the software development world by creating a framework for making products faster, better, smarter and for lower cost, even if it was named after a bunch of sweaty men huddled together with ill intent for the other side.
The Scrum framework as we know it today kicked off in the mid 1990's when they both presented their paper at the OOPSLA conference. But it may interest you to know that it was almost a decade earlier when Hirotaka Takeuchi and Ikujiro Nonaka first coined the term "Scrum" in relation to product development. This revelation came after their study of successful manufacturing firms where they noticed that the winning formula was cross-functional teams iterating during overlapping phases.
Scrum made its way into many organizations over the next 15 years, but it wasn't until 2010 that Jeff Sutherland and Jeff Schwaber finally laid down the framework in a semi-official form we know today as The Scrum Guide. There have been five versions of the guide released since 2010, with the latest being in November 2017.
Scrum has since evolved into a powerhouse for delivering successful Agile projects. But is there any quantifiable data to support its widespread adoption? There certainly is. The "State of Scrum 2017-2018 - Scaling and Agile Transformation" produced by the Scrum Alliance gives us some great insights into the game of Scrum and how it is played today.
Before we look at this data, it's important to know that the information was captured through 91 countries, 27 industries, and over 2000 respondents. 78% of the respondents were in the USA and Europe, while only 10% were located in Asia. Given that Asia represents 58% of the world's population, and is the fastest growing economic region and will be for at least the next decade or so, the Scrum Alliance may want to increase their respondent representation in this region for future reports.
How many use Scrum?
94% of respondents use Scrum in their Agile practices. This is broken down into two main areas. While only 16% use Scrum exclusively, 78% use a mixture of Scrum with other approaches such as XP and Kanban.
What about Team Size?
We all know that a good Scrum Team should be small and flexible. Most people believe that aside from the Product Owner and Scrum Master, the development team should consist of between 5-9 members. The report confirms this, and the average Scrum team size was 7.4. Of the 2000 respondents, 8% had team sizes between 1-4 members. 78% had 5-9 members, while 13% had 10+ members.
Sprint number and length
The average length of a Sprint was 2.4 weeks which sounds about right. An interesting thing I noticed was that the average number of Sprints per project was only 5. This could be that a lot of projects were feature updates or a small list of features regarded as a single project, rather than a huge release. This could also be disguised as a Release or Product Roadmap broken down into small "projects". If we multiply the average Sprint length (2.4) by the average number of Sprints per project (5.0), we get a 12-week average duration for Sprint projects. This was indeed confirmed in the 11.6 weeks reported in the State of Scrum.
81% of respondents held a Retrospective after the Sprint. This seems high at first glance, but when you really think about it, it's really not acceptable that almost 20% of Scrum teams don't even hold a Retrospective. The whole idea of Agile and Scrum is to Inspect and Adapt, and particularly with processes and team performance, this is hard to do if the team isn't meeting for a Retrospective.
87% have a daily Scrum. Now this is where I start to grind my teeth. Is this a Scrum Master issue, or a team just not committed to Scrum? Similarly, only 86% hold a Sprint Planning meeting before a Sprint. I wonder what these teams were thinking when they head into a Sprint with no formal plan for the next iteration. We respect adaptive planning in Scrum, but progressive elaboration does not mean we can enter the current iteration without knowing what we will do and how we will do it. The Definition of Done and our Sprint Goal is a form of planning, so what the heck was going on in their minds?
* * *
If your Scrum projects are not half the Scrum they use to be, it is time to buckle down and look at the processes you are deploying and if they follow the Scrum Guide's framework, all the way down to the roles, rules, events and artifacts that deliver value to the stakeholders. Make sure your Scrum projects are implemented in the best way possible now and tomorrow. Don't long for yesterday!
1. Schwaber, K. and Sutherland, J. (2017) The Scrum Guide. Available from: www.scrumguides.org
2. Scrum Alliance (2017) State of Scrum 2017-2018 - Scaling and Agile Transformation.
3. Wikipedia (2018) Scrum (Software Development). Available from:
Thank you for your interest in the Scrumptious blog. If you have any ideas for Scrum topics, please message me here. Until next time, remember, projects can be Scrumptious!