Software Engineering, Project Management, and Effectiveness
When I analyze process flows, I like to see them at a glance, in terms of activities and artifacts. This helps me compare it with other approaches to find similarities and differences. This is my view of Scrum at a glance:
The Talk-Through Version … From the product backlog, you identify a product increment to execute. For Sprint planning, you identify the goal, the sprint duration, the relevant stories, and the tasks. To do so, you break the stories into tasks. You estimate the tasks.
As part of daily work, you have a daily standup meeting, identify what got done, what will get done, and any impediments. You update the Sprint backlog and Sprint burndown charts.
At part of the Sprint review, you demo the product increment to stakeholders and you update the product burndown chart.
After release, you perform a retrospective, to identify what went well, and what to improve.
If you have any feedback or suggestions on how to improve my scannable view, please share.
Many thanks to James Waletzky for review and feedback.
Thanks for such a wonderful post. I have also tried to write about Scrum: An Introduction to this simple-powerful agile methodology. I would really appreciate if you can provide your valuable feedback on the post at http://www.rohitprabhakar.com/2010/05/08/scrum-an-introduction-to-this-simple-powerful-agile-methodology/