8 Steps to Scrum + DevOps

(endorsed by Ken Schwaber, Scrum.org)

4a. Daily
Scrum
Pre-Game
5. PRODUCT
4b. Development INCREMENT
In
Progress

z 4c. Groom Rene

To Do zz Product Backlog 5a. Continuous
1 8 Deployment to
UAT/Staging
1. INITIAL 2. BACKLOG
MEETING CONSTRUCTION 3. SPRINT
PLANNING
4. SPRINT 5b. Automated
Deployment to
Production

Done

7. SPRINT
Product
REVIEW
Backlog

5c. Live
8. SPRINT
RETROSPECTIVE
5d. Gather Metrics:
Errors, Performance,
Scrum Product Programmer Tester Sys Admin Usage and User
6. PRODUCT
Master Owner Feedback
FEEDBACK

The Product Owner explains the Features are ordered by the Product Each Sprint is a potentially shippable The Development Team demos all the

1 product vision and scope, and the

number of days needed for the Backlog
Construction is proposed.
3 Owner. The Development Team estimates
and forecasts which features will be
delivered in the Sprint.
5 increment of software. A focus on
DevOps reduces risk and increases agility. 7 features theyve completed. Feedback
is gathered. This is the real measure of
the success of the Sprint.

A Backlog Construction is performed The Development Team works away Bugs & small changes are added to the This is the best part: inspecting and

2 listing the features, technologies and an

estimated number of Sprints. A cost per
Sprint gives the customer a ballpark.
4 ordered by priority, having Daily Scrums
and completing the PBIs to the Denition
of Done. Tip 1: Use an electronic Task
6 current Sprint. Other requests are added
to the Product Backlog if approved by
the Product Owner.
8 adapting. Upon nishing the Sprint, the
Scrum Team discusses what went well,
what didnt and what to improve.
Board. Tip 2: Send done emails.

www.ssw.com.au/8Steps @AdamCogan - retweet https://bitly.com/ovuYRm version 4.5