Do you know the 8 Steps to Scrum?
24/05/2018 2:36 PM by
Scrum is easier than it seems, we'll explain how in these 8 simple steps.
- Figure: This Scrum image includes all the important steps from the initial meeting to the Review and Retro. Print this
SSW 8 Steps to Scrum PDF and put it on your "
War Room" wall
The Product Owner explains the product vision, scope is agreed, and the number of days needed for the 'Backlog Construction' is proposed.
A 'Backlog Construction' is performed, listing the features, technologies and a ball park of the number of sprints. Together with a rate, this becomes the estimate.
Features are ordered by the Product Owner. The Development Team estimates and forecasts which features will be delivered in the Sprint.
The Development Team works on features in priority order, having done a Daily Scrum and sending 'Done' emails once the
'Definition of Done' is met. A task board is often used. During this process, the team also refines items in the Product Backlog to ensure they conform to the
'Definition of Ready'.
The Development Team demos all the features they've completed. Feedback is gathered. This is the real measure of the success of the Sprint.
Work accepted by the Product Owner can be deployed to production. Each Sprint is a potentially shippable increment of software.
Bugs and small changes are added to the current Sprint. Other requests are added to the Product Backlog if approved by the Product Owner.
This is the best part: Inspecting and adapting. Upon finishing the Sprint, the Scrum Team discusses what went well, what didn't and what to improve.
- Figure: If you like this, retweet twitter.com/AdamCogan/status/375010501693960192
Do you feel this rule needs an update?