Going Beyond Scrum to Scrum as Example

January 8, 2018 — Posted by Al Shalloway

If you are having troubles with Agile at the team level you should read this - Scrum as Example. It is designed both for those using Scrum and those about to start. It is an extension of Scrum in that you can start with Scrum (the practices in the example are Scrum practices), but by realizing that these practices represent decisions that Scrum has been made for you, it gives you the opportunity to make better decisions when your context warrants it.

Continue reading here if you are interested in why Scrum often gets teams into trouble by its design, training method and promotion approach.

The Challenge of Scrum

Everyone acknowledges that there is a lot of bad Scrum out there. People often do some of Scrum's practices but not all. This has derisively been called "Scrum but." Unfortunately, the cause of this is inherent in the way Scrum has been designed, the way it is taught and the way it is promoted.

The Design of Scrum Is Flawed

Scrum is designed to discover impediments to development in a couple of weeks (for the purpose of this article we are assuming 2-week sprints are being used) and then to remove them. For example, interruptions, not having cross-functional teams, and doing daily standups. The idea is that by removing impediments you will be able to do Scrum properly. While Scrum can lead to success if can follow all of Scrum's prescribed practices, they are not always the best practices for a team to be doing. This leads people to stick with Scrum even when it is not appropriate and they do not know alternatives that will meet the same objectives.

The Challenge of How Scrum Is Taught

This situation is exacerbated by how Scrum is taught - "use the Scrum practices until you understand them and can go beyond them." The challenge here is that using them as defined may not get a team to effectiveness. So teams struggle with the Scrum practices. Unfortunately, they've been taught to follow Scrum as is. Their understanding on why they are doing the practices is not deep. This leaves them to try things on their own when they can't get the practices to work. Without understanding this often leads to just different bad practices.

The Promotion of Scrum Makes Things Worse

This situation is exacerbated again by how Scrum has been promoted. Many Scrum proponents have equated Agile to Scrum, ignoring the fact that Scrum is just one way to achieve Agile. But the impression for people who have decided to do Agile is that they should start with Scrum. Furthermore, Ken Schwaber, one of the creators of Scrum, says "Scrum is simple, just use it as is." The challenge here is two fold. First, consultants who only know Scrum and make their living off of it succumb to what Upton Sinclair referred to by saying "It is difficult to get a man to understand something, when his salary depends upon his not understanding it!". The second is it sets up the notion that Scrum is providing an answer to the teams and it'd work if they'd only follow it. This is why, if you want to use Scrum, it is better to use someone who also knows Kanban. S/he won't be attached to either.

The bottom line is that these three things combine to have people learn Scrum, try to follow it, and then not know what to do when it doesn't work.

Getting Out of the Trap

I am not suggesting that Scrum should not be used nor should people abandon their investment in it. Just the opposite. I created Scrum as Example so that one can still use Scrum while getting out of the above traps. Being aware of these traps is important, however, as it is easy to fall into them.

Another way out of the trap is to consider Scrum as a tool in your toolbox and not the entire tool box. Scrum has many brilliant ideas. It is where I learned the value of teams. But as a toolbox, Scrum may be a trap.

Subscribe to our blog Net Objectives Thoughts Blog

Share this:

About the author | Al Shalloway

Al Shalloway is the founder and CEO of Net Objectives. With over 40 years of experience, Alan is an industry thought leader in Lean, Kanban, product portfolio management, SAFe, Scrum and agile design.



        

Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Guy Beaver
Business and Strategy Development, Executive Management, Management, Operations, DevOps, Planning/Estimation, Change Management, Lean Implementation, Transitioning to Agile, Lean-Agile, Lean, SAFe, Kanban, Scrum
Israel Gat
Business and Strategy Development, DevOps, Lean Implementation, Agile, Lean, Kanban, Scrum
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, SAFe, Kanban
Ken Pugh
Agile Design and Patterns, Software Design, Design Patterns, C++, C#, Java, Technical Writing, TDD, ATDD, Certifications, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Max Guernsey
Analysis and Design Methods, Planning/Estimation, Database Agility, Design Patterns, TDD, TDD Databases, ATDD, Lean-Agile, Scrum
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile
Steve Thomas
Business and Strategy Development, Change Management, Lean Implementation, Team Agility, Transitioning to Agile
Tom Grant
Business and Strategy Development, Executive Management, Management, DevOps, Analyst, Analysis and Design Methods, Planning/Estimation, Innovation Games, Lean Implementation, Agile, Lean-Agile, Lean, Kanban