13. Questions we are interested in…
• Did this deliver value to the customer?
• What impact did it have on their business?
• Are they actually using the software?
• Are we building the right thing?
• Are we on track?
• How are we doing in terms of budget?
• Will we be able to finish in time?
14. EPIC
Features
Mr. Product Owner
The Team
The conversations should include:
• How do we assess the impact on
the business?
• How do we judge whether this was
the right thing to build?
17. Tim
e
# stories
Stories when created
Stories when developed/done
• The PO knows what ought to
be developed up front.
• The dev team works on
hardest/riskiest items first,
leaving the easier ones for
later (so they are faster at the
end)
• Predicted end date converges
to the left has time passes.
18. Tim
e
# stories
Stories when created
Stories when developed/done
• The dev team works on the
easier first, leaving the
hardest/riskiest for later…
• Culture where team is
desperate to appear busy?
• End date every hard to predict
19. Backlog with stories of different size
and level of refinement
Priority
• Useful for the dev team to have
the highest priority items as the
smallest, and most refined items
• BUT, the fact that a story is
unclear does not mean is has low
value or is not important!
• Those stories should perhaps be
the ones to be worked on sooner
rather than later!
• The criteria for priority should be
value/risk, not “known”
20. Tim
e
# stories That’s the ideal curve, when
the Product Owner knows
what he/she is doing
When you’re constantly
learning from feedback (i.e.
when you are agile)
21. Tim
e
# stories
Stories when they are created
Stories when are developed/done
• You need something else to
measure progress – Cannot
tell when you’ll be finished
• You need to become value-
driven, with different kind of
metrics