This post begins my series on Getting Back to the Original Scrum.
I understand why people think I don’t like Scrum. I have been struggling with this myself. I have used Scrum for almost 2 decades with great results. But I teach it differently and base it on a different model than the Scrum Guide.
I’ve been realizing what I love about Scrum comes from The New New Product Development Game and what I don’t comes from its redefinition.
Scrum was not created by Ken and Jeff. It was created by Hirotaka Takeuchi and Ikujiro Nonaka in 1986 and formalized later for software development (while leaving all aspects of actual development out of the definition – another challenge in my mind).
I am going to start writing a series of blogs about this:
- what is great about Scrum and how it incorporates the essence of Agile
- why basing Scrum on empiricism instead of Nonaka’s learning model makes Scrum less effective in general and in IT environments in particular.
- the New Scrum Game – recreating Team-Agile based on what we’ve learned after more than 2 decades of Scrum’s initial appearance.
- what I’d add to Scrum given our current knowledge of Flow, Lean and technical practices today
- why I’d change the Product owner roles to be more consistent with TNNPDG
- why I’d change the Product owner roles to be more consistent with TNNPDG
- why these additions are critical more than 2 decades later
- how to incorporate Nonaka’s Middle-Up-Down Management into Scrum
- A summary of New Scrum Game