Why You Should be Directly Taught What Scrum Tries to Force You To Do

May 20, 2018 — Posted by Al Shalloway
As I write more & more I am getting a deeper understanding of why there are so many challenges that teams are having adopting Scrum. It's not so much Scrum itself as the way it is taught.
 
The purpose of adopting Scrum is not to adopt Scrum in & of itself. It is to make a team &its organization more effective. The best way to do this is to learn how to do Agile & then use the Scrum framework to support these practices. This the opposite of learning the Scrum framework first & leaving teams to figure out how to do Agile.
 
Scrum is usually taught as a forcing framework. That is, use Scrum’s immutable roles, event, artifacts &rules to both uncover impediments to a team’s ability to deliver value as well as force the team to adopt solid Agile methods that will overcome these challenges (e.g., small stories are needed so they can be completed in a sprint).
 
Another way to adopt Scrum, however, is to directly learn what doing Scrum would have you do while learning enough of Scrum to support these efforts.
 
We must remember the distinction between Scrum as a framework for developing software in an Agile manner & what Agile software development actually is.  They are not the same. 
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 45 years of experience, Al is an industry thought leader in Lean, Kanban, product portfolio management, Scrum and agile design. He helps companies transition to Lean and Agile methods enterprise-wide as well teaches courses in these areas.



        

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