• Elements of a service • Service blueprints AGILE ESTIMATION WITH PLANNING POKER Why estimate? ➔ To prioritize product backlog ➔ To make longer-term predictions
player = 1 deck of cards ➔ ScrumMaster moderates the meeting ➔ Moderator provides quick task overview ➔ Opportunity to clarify assumptions and assess risks ➔ Product owner answers any questions
estimator privately picks a card and don’t show ➔ All cards are simultaneously shown ➔ People with high or low estimates justify their estimation ➔ Use the egg timer to limit this discussion ➔ Repeat until a consensus
Story Points are about effort ➔ Story points are for stories ➔ Could involve multiple roles/persons ➔ Not every 3-point story will take exactly the same amount of time ? ?
to be delivered for features per iteration ➔ Gets more accurate with time TWO APPROACHES 1. Commitment-driven sprint planning 2. Velocity-driven sprint planning
POKER ➔ Discussions lead to accurate estimations ➔ Not just the opinion of principals ➔ Greater understanding of work ➔ Leverages collective knowledge and teamwork ➔ High level architecture and design discussion ➔ Ownership of estimate
actually do the work ➔ Avoid long technical discussions ➔ Time the session ➔ Use the “I need a break” & “question” cards ➔ Use PlanningWith.Cards for distributed teams