The Havannah project: a Scrum Case Study
Do you want to understand SCRUM methodology properly? Then I can recommend in-depth reading of chapter 23rd of the book Agile Estimating and Planning, by Mike Cohn, Prentice Hall, 2005. This book is among the 12 reference books recommended by PMI to prepare PMI-ACP® exam. Besides planning and estimating techniques, what I liked the most was that practical case study, novel style, so easy to follow. I liked it so much that I could not help translating it into Spanish.
In this article I would like make the reading easier with 4 summary videos (Spanish audio). To get even more practical, in these videos I try to explain how I would use Asana to manage this agile project.
The Kick-off Meeting
You can read here (in Spanish) how the project Havannah is started and why a new agile management model is needed. It is remarkable when the Scrum Master requires everyone involved in collecting requirements.
Planning the Product Backlog
You can read here (in Spanish) how is a brainstorming session to collect requirements in a user story workshop, and a planning poker session to get the project sizing. The end result: a product backlog with 32 user stories as big as 146 story points.
Planning the First Sprint
Read here (in Spanish) how is a sprint planning session, resulting in a team firmly committed to deliver 4 user stories measuring 18 story points, needing to get over 30 tasks done, with an estimated effort of 198 hours. Progress can be measured by means of a sprint burn down chart.
Click here to download the Excel file I use as a template to draw release and sprint burn down charts.
That initial velocity of 18 story points per iteration is valid to get a rough estimation: 7 iterations are needed to get 132 points done. However, the Scrum Master does not publish a deadline of 14 weeks, that would be quite uncertain. Management is told between 12 and 20 weeks. A more accurate estimation will be provided at the end of the 3rd iteration.
Read here (in Spanish) how scope is changed (more value) thanks to the prioritization facilitated by a survey conducted following the Kano Model. Release performance would be better represented with an alternative release burndown chart. Read here (in Spanish) how the project ends.