Acceptance criteria have one job: describe what changes. Not what stays the same. Not what was already working before the sprint started. In my previous role, I caught this mistake twice in a single story-writing session. The second time, I…
Senior stakeholders do not need real-time updates on normal release turbulence. They need to know about unplanned impact. Those are different things, and confusing them is expensive for everyone involved. In my previous role, I was the person deciding whether…
A fixed product requirement and an open design question look very similar on paper, until you are two days into a debate you did not intend to start. In my previous role, a single line in a requirement document turned…
When a team discusses a change to a release date, the date has not changed. When they agree it should change, it still has not changed. It changes when the right person — the one who owns the consequences —…
The trigger for introducing a Change Advisory Board wasn’t a single incident. It was a pattern that became impossible to ignore. Feature requests were arriving from multiple directions — some with clear context and ownership, others more informal. A pain…
Backlog prioritisation breaks down when urgency is used as a proxy for importance. The solution isn’t a better framework — it’s a system that separates time-sensitivity from business impact, makes trade-offs explicit in the room, and protects capacity for work…
ICE scoring is a prioritisation framework that ranks backlog items by multiplying three factors: Impact, Confidence, and Ease. Each is scored on a 1–10 scale. Multiply them together and you get a number out of 1,000. The highest scores rise…
A backlog isn’t just a to-do list. Story mapping helps Product Owners see the user journey, find the MVP, and align stakeholders on what to build next.
Every request feels urgent, but some delays cost more than others. Cost of Delay and WSJF help Product Owners decide what really can’t wait.
Not all features make customers happy. The Kano Model helps you distinguish between basics, performance boosters, and delighters, and balance them in the roadmap.
