20 yrs ago using Scrum to identify problems & let the team figure out how to solve them made sense. It doesn't today.

May 30, 2018 — Posted by Al Shalloway
Some people have alluded that the reason for so much bad Scrum these days is that Scrum has crossed the chasm & now mostly mid to late adopters are adopting it. But I disagree. Besides it being a self-serving explanation for why Scrum adoption is not as good as it should be, it isn't true. I've been using, teaching & coaching Scrum for almost 20 years. I find that those picking up Scrum now to be just as smart &committed as those I worked with in 2000.
 
I think the reason for bad Scrum now is that:
  1. the pace of software dev is much faster
  2. there's a lot more legacy code to deal with but Scrum ignores tech practices other than say "learn them later"
  3. there's much less emphasis on actually how to do the work & much more emphasis on frameworks
 
The reality is that today it is easy to spot where teams are having problems. And the solutions to them are readily available. We know more than we did 20 yrs ago. Instead of starting by teaching a simple framework & leaving people to figure out the tough stuff, we need to start teaching the tough stuff up front, & just enough Scrum to support that work. 
 
Let's focus on the work, not the framework.
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