This document provides an overview of techniques for product management tasks like estimation, prioritization, and backlog management. It discusses 10 estimation techniques like planning poker, affinity mapping, and three-point estimation. It also covers 10 prioritization techniques including MoSCoW, Kano model, and value vs cost. Finally, it outlines different backlog item types and approaches to maintain an effective product backlog through refinement and funneling ideas.
3. At the end of this session, you will…
Know 10 different estimation techniques
Know 10 different prioritization techniques
Have new ideas for product backlogs
5. Why are you estimating?
Forecasting – what we think will happen
The estimate provides insights into expected cash flows,
financial capacity, and dependencies.
Targeting – what we want to happen
The estimate works as a target for production, marketing,
sometimes coupled with rewards.
Budgeting – what it takes to make it happen
The estimate is used to reserve money, schedule people,
and allocate resources.
6. Beyond Budgeting
Photo by Ehud Neuhaus on Unsplash
Decouple the
estimations
Forecasting
(Time)
Targeting
(Scope)
Budgeting
(Cost)
32. Product Backlog Items
Features (User Stories)
Minimum Marketable Features (MMFs)
Changes
Lean Experiments (Experiment Stories)
Research Spikes (Technical Spikes)
Technical Debt (Refactoring)
Improvements (Team Requests)
Defects (Bugs)
Business Requirements
33. Backlog Refinement is
Backlog Maintenance
Photo by Alex Motoc on Unsplash
Keeping the backlog up-to-date
is a neverending job.
34. “Scrum is a framework for developing, delivering,
and sustaining complex products.”
Product Owner
Scrum Master
Development Team
Sprint
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Product Backlog
Sprint Backlog
Increment
https://scrumguides.org
35. Scrum is a framework for delivering complex products,
not discovering them.
Scrum
36. Visualize
Limit work in progress
Manage flow
Make policies explicit
Implement feedback loops
Improve and evolve
Service Request Manager
(recommended)
Service Delivery Manager
(recommended)
“Kanban is a method for defining, managing, and
improving services that deliver knowledge work.”
https://www.kanban.university/
37. Kanban is a method for delivering knowledge work,
not discovering it.
Kanban
39. Some work is pure
discovery. Other
work is pure
development.
Most work is a bit
of both.
Contextualize (Frame)
Empathize
(Discover)
Synthesize
(Define)
Hypothesize
(Ideate)Externalize (Build)
Sensitize
(Test)
Systematize
(Learn)
40. Discovery Kanban is yet another Innovation Funnel
Discovery
Development
https://kanbanize.com/blog/patrick-steyaert-customer-kanban/
41. Amount of Entrance
Amount of Exit
Conversion Rate per stage
Duration per stage
Overall Conversion Rate
Overall Duration
Funnel Metrics
42. Turn your
Product Backlog
into a Backlog
Funnel
Unsorted
ideas
Tests and Lean
Experiments
Validated Features and
User Stories
Prioritization
Prioritization
Prioritization
Estimation
Estimation
Estimation