Scribd
Upload
166 views1 page

Product Increment: Pre-Game 4a. Daily Scrum 4b. Development

The 8 steps to Scrum + DevOps are: 1. The Product Owner explains the product vision and scope to estimate the number of days needed for backlog construction. 2. A backlog is constructed listing features, technologies, and estimated sprints to give the customer a cost estimate. 3. The Product Owner orders features by priority. The team estimates which can be delivered in the sprint. 4. The team works on the highest priority items in the sprint backlog using daily scrums and completes them to the definition of done. 5. Each sprint is a potentially shippable product increment with a focus on continuous deployment, delivery, and automation to increase agility.

Uploaded by

efrainbss
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
166 views1 page

Product Increment: Pre-Game 4a. Daily Scrum 4b. Development

The 8 steps to Scrum + DevOps are: 1. The Product Owner explains the product vision and scope to estimate the number of days needed for backlog construction. 2. A backlog is constructed listing features, technologies, and estimated sprints to give the customer a cost estimate. 3. The Product Owner orders features by priority. The team estimates which can be delivered in the sprint. 4. The team works on the highest priority items in the sprint backlog using daily scrums and completes them to the definition of done. 5. Each sprint is a potentially shippable product increment with a focus on continuous deployment, delivery, and automation to increase agility.

Uploaded by

efrainbss
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

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

You might also like