Product Ownership Practices and Techniques
Practices and techniques test whether you can select and apply product ownership tools to real decisions: vision, roadmaps, backlogs, prioritization, and validation. Questions often present a messy situation and ask which technique fits the decision.
Core rules and concepts
- A vision states target customer, need, product, and value. A roadmap expresses outcomes or themes over time, not a feature Gantt chart.
- The backlog is ordered by value, risk, and learning needs. Refinement is continuous, not a one-off meeting.
- Story mapping organizes work by user activity to expose gaps and thin slices. Impact mapping links a goal to actors, impacts, and deliverables.
- Prioritization: WSJF equals cost of delay divided by job size. MoSCoW is a categorization aid, not a fixed contract. Kano separates basic, performance, and delighter needs.
- An MVP is a learning vehicle for validated learning; a minimum marketable feature is the smallest slice that delivers value.
- Acceptance criteria define a specific story. Definition of Done is the team-level quality bar for every increment.
- Use leading and outcome metrics, not only shipped-feature counts.
Worked example
Two features compete. Feature A has cost of delay 8 and job size 2, so WSJF is 4. Feature B has cost of delay 6 and job size 1, so WSJF is 6. B goes first, unless dependencies or risk change the comparison. Reasoning: WSJF compares relative economics, so the estimate scale must be consistent and the cost of delay must include time-criticality, risk reduction, and value.
Traps
- Applying WSJF with absolute, mixed-scale estimates.
- Treating MoSCoW categories as permanent.
- Defining MVP as the smallest possible feature set rather than a learning instrument.
- Using a story map as a flat backlog.
- Confusing acceptance criteria with Definition of Done.