SCRUM On RailsScrum and Continuous Delivery

Tho

rste

n K

aman

n -

item

is A

G -

© 2

013

Thorsten Kamann Agile Coach !

itemis AG @thorque thorsten-kamann.de

Certified ScrumMaster

Certified Product Owner

Continuous Delivery Expert@itemis

Author

Speaker On Conferences

Maid-Of-All-Work

3 roles

3 artifacts

3+1+1 meetings

1 product

Product Owner ScrumMaster Development Team+ + = Scrum Team

Product Backlog

Sprint BacklogImpediment Backlog

Backlog Refinement +1 (once per sprint)

Sprint Planing (once per sprint) Sprint Review (once per sprint)

Retrospective (once per sprint)

Daily Scrum +1 (daily)

1 potentially shippable product increment

Daily Scrum

24h

Sprint

1, 2 or 4 weeks

Sprint Goal Sprint Planning Sprint Review

Sprint Retrospective

Product Owner Scrum MasterDevelopment Team

Backlog Refinement

Potentially shippable

product increment

From Code to ProductionAutomated Repeatable

Tested

Approved

Deployed

Stages

Time to Market

0

12,5

25

37,5

50

Sprint 1 Sprint 2 Sprint 3 Sprint n

Effort and Quality

Continuous Build

commit-driven

After resolving

a story

Integration Build After everysprint

Acceptance Build

Delivered package

Continuous Delivery in a Scrum context

Development Integration Acceptance Production

Development

Integration

Acceptance

Production

Development

Integration

Acceptance

Production

Commits

Story

Sprint Result

Product

All Builds must be

GREEN (see Definition of Done)

After resolving a story deliver to the next stage

(eg. Integration)

Potentially shippable product increment have to delivered to

the next stage

(eg. Acceptance).

Results of Retrospective

Build Env

Reporting

Monitoring/Notification

...

Burndown Chart

Taskboard

Build Dashboard

Looks good?but...

Many pieces need to fit together

Automation is hard!Manual tasks are valid

You need a DevOps team!

You need a HIGH test coverage!

But it is possibleand very valuable

Thank you!