Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
OUR APPROACH TO MULTI
SPEED RELEASE CYCLES
Lean Tribe Gathering #27 Göteborg
Anders Sixtensson, 150421
IT Factory
 WHAT - The future (existing) line organization
for service management of the deliveries from
the eCommerce Pr...
(One of )The Big Picture
3
Feature
Template
…..
Business
Need
Initial
Screening
Assess-
ment
Prioritiz
e
Routing
Programme...
www.scaledagileframework.com/
SAFe mapping to Big Picture
Feature
Template
…..
Business
Need
Initial
Screenin
g
Assess-
ment
Prioritiz
e
Routing
Program...
Connection to
gates
SOLUTIONING
DEVELOPMENT
END2END TEST PGLS RUN
0
2 4
6 7
STQ1
STQ2 STQ3
STQ4 STQ5
FEATURE x
Feature Lea...
7
Multi speed release cycles
Publication
- no IT
involved
Front End
new platforms
- HTML, GUI
Legacy and
Integration
– ISE...
The Delivery Engine = 2 week
sprint cycles
A Factory Release Train
 A number of 2 week sprint
cycles for a number of
teams
 Cross skilled teams
C
S
D
T
DB
Server
C...
Factory – a number of Release
trains
 Example 4 +8 +12
week Release Trains
4w 4w 4w 4w 4w 4w 4w 4w 4w 4w 4w 4w
8w 8w 8w 8...
Release Planning, level 0, 1 and 2
A,10,4w
B,40,8w
C,5,4w
D,70,12w
E,10,8w
F, 20
G, 100+
H, 50
I, 50++
J, 10
K, 30
Epics t...
Challenges and (hopefully) open
space discussions
 Find quick decision flow for small & highly
prioritized features
 Fea...
Upcoming SlideShare
Loading in …5
×

Our approach to multi speed release cycles | Anders Sixtensson | LTG-27

745 views

Published on

Presentation held at Lean Tribe Gathering 27 in Gothenburg apr 21 2015.

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Our approach to multi speed release cycles | Anders Sixtensson | LTG-27

  1. 1. OUR APPROACH TO MULTI SPEED RELEASE CYCLES Lean Tribe Gathering #27 Göteborg Anders Sixtensson, 150421
  2. 2. IT Factory  WHAT - The future (existing) line organization for service management of the deliveries from the eCommerce Program  WHY – to reduce time-to-market – Agile – Multi speed release cycles – Industry standard => SAFe, ….,…. ,
  3. 3. (One of )The Big Picture 3 Feature Template ….. Business Need Initial Screening Assess- ment Prioritiz e Routing Programme Priority Group Feature Routing Group eCOM Programme Development Log Quality Control SOM NEW WEB OTHER eCom PROJECTS RUN 3 4.1 2a 2b 3 Incidents Fixes 4.2 4.3 RUNLEGACY Multichannel Factory X Feature TeamsFactory Backlog Legacy Backlog Project Backlog Project Backlog Project Backlog Code Control Tools Process Management Master Planning FACTORY XXX Programme Development Log Business Need FEATURE x Feature Lead SA/ITSA
  4. 4. www.scaledagileframework.com/
  5. 5. SAFe mapping to Big Picture Feature Template ….. Business Need Initial Screenin g Assess- ment Prioritiz e Routing Programme Priority Group Feature Routing Group eCOM Programme Development Log SOM NEW WEB OTHER eCom PROJECTS RUN W2b W3 3 4.1 2a 2b 3 Incidents Fixes 4.2 4.3 RUNLEGACY Multichannel Factory X Feature TeamsFactory Backlog Legacy Backlog Project Backlog Project Backlog Project Backlog FACTORY XXX Programme Development Log Business Need FEATURE x Feature Lead SA/ITSA Business Need Portfolio mgmt Program mgmt = Factory = ART Team mgmt = Vendor
  6. 6. Connection to gates SOLUTIONING DEVELOPMENT END2END TEST PGLS RUN 0 2 4 6 7 STQ1 STQ2 STQ3 STQ4 STQ5 FEATURE x Feature Lead SA/ITSA DEVELOPMENT END2END TEST PGLS Feature Build E2E- Testing Device Testing NFT, ORT SAT/BAT Support Release & PGLS Dev ST EIT Low Leve l Desi gn Run RUN LEGACY LEGACY Low Leve l Desi gn 3 64+ SOLUTIONING Pl an ni ng SolutionBacklog Solu tion Defi nitio n Teams 1 20 Assess ment Prioritised Feature Log Solu tion Desi gn Teams 75 iteratio nsYYY Dev iteratio nsDev iteratio ns Dev iteratio ns
  7. 7. 7 Multi speed release cycles Publication - no IT involved Front End new platforms - HTML, GUI Legacy and Integration – ISELL, MHS 8w-12w Solutioning Develop and run Back End new platforms - XXX, YYY Daily Weekly-4w 4w-8w There will be a range of cycles; daily (e.g. editorial changes), weekly, monthly and up to several months for more complex changes.
  8. 8. The Delivery Engine = 2 week sprint cycles
  9. 9. A Factory Release Train  A number of 2 week sprint cycles for a number of teams  Cross skilled teams C S D T DB Server Client/UX User Test S D C S D T S D T S Plan&Commit Stabilize&Demo
  10. 10. Factory – a number of Release trains  Example 4 +8 +12 week Release Trains 4w 4w 4w 4w 4w 4w 4w 4w 4w 4w 4w 4w 8w 8w 8w 8w 8w 8w 12 w 12 w 12 w 12 w Ex – 8 week train
  11. 11. Release Planning, level 0, 1 and 2 A,10,4w B,40,8w C,5,4w D,70,12w E,10,8w F, 20 G, 100+ H, 50 I, 50++ J, 10 K, 30 Epics to Features + allocated to Release trains to be Release Planned next coming 3 months To be Release Planned next 3-6 months + 6 months away Feature B, 40 Story points, 8 week train 3 month cycle Program Backlog Level 0 for Factory 4/8/12 week cycle Features to Stories + allocated to teams and sprints Level 1 per train 8 week 2w cycle Sprint goal + Stories to Tasks for next 2 weeks Level 2 per team
  12. 12. Challenges and (hopefully) open space discussions  Find quick decision flow for small & highly prioritized features  Features requires Legacy parts with own Release cycles, run by vendors, having SLAs  Get stable velocity to base forecasting on  Governance and funding  Truly XFTs co-located with vendors and sourcing

×