Scrum on rails
Upcoming SlideShare
Loading in...5
×
 

Scrum on rails

on

  • 492 views

Continuous Delivery describes a process by which you can fully automatically test and deliver your software product. However Scrum is management framework to enable agility to your project. Both fit ...

Continuous Delivery describes a process by which you can fully automatically test and deliver your software product. However Scrum is management framework to enable agility to your project. Both fit together. This presentation shows how thy fit and where are the pitfalls.

Statistics

Views

Total Views
492
Views on SlideShare
492
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum on rails Scrum on rails Presentation Transcript

    • Thorsten Kamann - itemis AG - © 2013 SCRUM On Rails Scrum and Continuous Delivery
    • Thorsten Kamann Agile Coach ! itemis AG @thorque thorsten-kamann.de Continuous Delivery Expert@itemis Certified ScrumMaster Speaker On Conferences Author Certified Product Owner Maid-Of-All-Work
    • 3 roles 3 artifacts 3 +1+1 meetings 1 product
    • Product Owner + ScrumMaster + Development T eam = Scrum T eam
    • l og ck a Impe dimen tB c t Bac du l og ro klog Back P t prin S
    • ent finem og Re Backl Sprint Revie w rint) e per sp +1 (onc Sprint P la ning (once p er sprin t) (once per sprin t) Scrum aily D Retrospective (once per sprint) ) +1 (daily
    • 1 potentially shippable product increment
    • Product Owner Daily Scrum Development Team Scrum Master 24h Sprint 1, 2 or 4 weeks Sprint Goal Sprint Planning Backlog Refinement Sprint Review Sprint Retrospective Potentially shippable product increment
    • T ested Stages From Code to Product ion Autom ated Repeatable Approved me Ti et rk Ma to ed oy pl De
    • Effort and Quality 50 37,5 25 12,5 0 Sprint 1 Sprint 2 Sprint 3 Sprint n
    • Continuous Delivery in a Scrum context Acceptance Build Integration Build Continuous Build After every sprint After resolving a story commit-driven Delivered package Development Integration Acceptance Production
    • Production Acceptance Integration Development
    • Production Product Acceptance Sprint Result Integration Story Development Commits
    • 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 B hb as dD uil rd oa
    • 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 possible and very valuable
    • Thank you!