Mar 3rd, 2014
By: Jeff Patton
I spend a lot of time in a wide variety of companies with product managers and teams who work hard to keep delivery promises made in a roadmap months or years ago. Often when I ask why teams are working on this big feature: “because it’s promised in the roadmap.” is the only answer I get. No one seems to know exactly why.
This short article describes how we use an opportunity canvas to drive first discussions about what we’re building and why.
Adopting new process language bothers me. I was introduced to the Extreme Programming term “story” in 2000 and it wasn’t until 2005 that I stopped rolling my eyes when I heard the term and could actually begin to use it in sentences myself.
“Backlog grooming” isn’t a new term in the Scrum community, but it’s a term that still drives me up the wall. Let me explain why.
Backlog grooming meeting as team torture
Years ago, I sat in on a painful meeting with a software development team I was just beginning to coach. It was important that I learn the way they were working today, and respect the process choices they’d made so far. It was my goal to observe and understand.
- Ben Linders on Evaluate Process Qualities, not Process Compliance
- Der perfekte Product Design Sprint - die besten Methoden für kompakte 5 Tage | produktbezogen.de on Describing Agile Product Discovery
- Colin Claverie (@Coclav) on Evaluate Process Qualities, not Process Compliance
- Aaron Sanders on Consequences of Thinking, Fast and Slow – Blog Series
- Jean Tabaka on Consequences of Thinking, Fast and Slow – Blog Series