Your SlideShare is downloading. ×
0
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Release planning in scaled agile environments | Ola Morin | LTG-20
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Release planning in scaled agile environments | Ola Morin | LTG-20

233

Published on

Presentation held at Lean Tribe Gathering in Malmö may 6th 2014.

Presentation held at Lean Tribe Gathering in Malmö may 6th 2014.

Published in: Engineering
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
233
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Release planning in scaled agile environments Ola Morin 2014-05-06 @ LTG-20 www.softhouse.se
  • 2. Scaled agile framework (SAFe)
  • 3. Agile Release Train (ART) Long-lived virtual organization of teams Operates under architectural and UX guidance Common cadence and normalized estimating
  • 4. Potentially Shippable Increment (PSI) / Release Develop on cadence PSI PSI PSI PSI Customer preview Major release New feature Customer upgrade Minor release Deliver on demand
  • 5. Input PSI / Release planning Output … … … … … … … … … …
  • 6. PSI / Release planning event - 2 days Context • Business state • Upcoming objectives Vision • Vision and release dates • Top 10 features Guidelines • Architecture and frameworks • UI design rules Team breakout 1 • Develop plans • Identifying risks and impediments Team plan review • Presentation of team breakout 1 Program plan review • Adjustments based on team breakouts Planning adjustments • Presenting any adjustments based on Program plan review Team breakout 2 • Develop final plans • Refine risks and impediments Final plan review • Presentation of team breakout 2 Program risks • Remaining program risks are handled Confidence vote • Fist of five (Plan re- work) • If no confidence was achieved Summary • Retrospective • Going forward
  • 7. Hierarchic release planning W Goals Commitment Alignment PSI n PSI n+1 t Program Scrum masters teams
  • 8. A program board
  • 9. Areas for discussion  Reasons for not gather everybody in a 2 day event?  What is more important than a common program vision?  Is normalized estimation points beneficial?  How does this effect the different teams?  Is team sprint lengths important as long as they have a common PSI cadence?
  • 10. Thank You! ola.morin@softhouse.se

×