Execution & Delivery
Discovery decides what is worth building. Delivery is whether it actually ships, at the quality you promised, without the team resenting you by the end of it.
Write for the builder
A story is a placeholder for a conversation, not a specification in a smaller box. The acceptance criteria are the contract; the card is the invitation.
Protect refinement
Nearly every painful sprint planning is a refinement problem in disguise. Ten well-refined items beat forty written alone at your desk.
Own your share of the mess
Late decisions, shifting priorities and vague criteria are product-side impediments. Naming them yourself in a retro is worth more than any process change.
Guides in this track
Common questions
Am I the product owner or the product manager?
In Scrum, Product Owner is an accountability rather than a job title, and at most companies the product manager holds it. The friction appears when someone else holds the title while you hold the strategy — then nobody can decide anything, and that is worth resolving explicitly rather than living with.
How involved should I be in estimation?
Present, contributing context, not estimating. You own priority order; the team owns how much fits. Pushing back on estimates is the fastest way to get padded numbers and lose your early warning signal.
Engineering says my requirements keep changing. Is that avoidable?
Some change is healthy — that is what iteration means. What is not healthy is changing acceptance criteria mid-sprint on work already in progress. If that happens often, it is usually a sign the item entered the sprint before it was understood, which is a refinement problem rather than a discipline problem.