Discover more from Maarten’s Newsletter
Why Did the Chicken Cross the Road?
The Agile and Product Management Edition
Why did the chicken cross the road?
Here are some answers from various perspectives.
Scrum Master: "The chicken crossed the road because they did not want to conflict with the Scrum Guide."
Release Train Engineer: "The Release Train compelled them to cross the road during Big Room Planning to realize more value for their Value Streams."
Agile Coach: "The chicken crossed the road to discover better ways of working while responding to changes over following a plan."
Kanban Master: "WIP was too high on the road so the chicken had to pull out."
Lean Master: "Staying in the same place was a non-value adding activity and the chicken wanted to reduce waste."
Product Owner: "The chicken crossed the road because the Product Manager told them to."
Product Manager: "Why would a chicken need to cross the road? What's the problem they are trying to solve? What progress are they looking for in their lives?"
Developer: "The other side of the road was riddled with technical debt and the chicken applied the Boy Scout rule."
Project Manager: "You're asking the wrong question. Was it part of the project plan or not?"
Marketing Manager: "It doesn't matter whether why the chicken crossed the road. What's the story we want to tell about it?"
CEO: "How can we better monetize the chicken crossing the road?"
Sales Manager: “The chicken crossed the road to get a bigger sales commission.”
Any better suggestions? Feel free to drop 🐔 in the comments.
Thanks for reading Maarten’s Newsletter! Subscribe for free to receive new posts and support my work.