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.
Scaling agile
Lessons learned of an agile transformation in a
large SW platform project
2015-03-30 | Page 2
› How to create an efficient WoW
in a SW platform project
consisting of more than 20 teams
divided ove...
2015-03-30 | Page 3
background
x4
2015-03-30 | Page 4
› RBS 6000 Gen 2.
› WRAT project assignment is to deploy the SW of WCDMA
traffic part on Baseband boar...
2015-03-30 | Page 5
› Personnel divided into XFT (cross functional teams) 2012
(Sys-Design-Test competence)
› Ambition for...
2015-03-30 | Page 6
Backlog breakdown
EPIC Sub-Epic User Story Task
# Epic pts
1 xxxxxxxx 18
2 xxxxxxxx 15
3 xxxxxxxx 33
#...
2015-03-30 | Page 7
WRAT People
› Staffing of WRAT project.
› 4 different sites involved.
› Both Ericsson and partner team...
2015-03-30 | Page 8
Continuous integration
(CI) definition
› Continuous integration is a software development practice whe...
2015-03-30 | Page 9
Lessons learned during
agile transformation
CI
2015-03-30 | Page 10
Lessons learned during
agile transformation cont’
Scaling Agile | Johnny Kemi | LTG-27
Upcoming SlideShare
Loading in …5
×

Scaling Agile | Johnny Kemi | LTG-27

770 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

Scaling Agile | Johnny Kemi | LTG-27

  1. 1. Scaling agile Lessons learned of an agile transformation in a large SW platform project
  2. 2. 2015-03-30 | Page 2 › How to create an efficient WoW in a SW platform project consisting of more than 20 teams divided over 4 different sites. › What have the challenges been and what have we learned during the agile transformation Topic
  3. 3. 2015-03-30 | Page 3 background x4
  4. 4. 2015-03-30 | Page 4 › RBS 6000 Gen 2. › WRAT project assignment is to deploy the SW of WCDMA traffic part on Baseband board 5212/16 which is the digital unit in the RBS. Our Product
  5. 5. 2015-03-30 | Page 5 › Personnel divided into XFT (cross functional teams) 2012 (Sys-Design-Test competence) › Ambition for XFTs to work in all development domains and disciplines (i.e. end2end) › Only a few domain expert teams kept › OPOs working as a team creating a huge anatomy and backlog of project scope › Discussions how to spread competence and align development started Start of agile journey
  6. 6. 2015-03-30 | Page 6 Backlog breakdown EPIC Sub-Epic User Story Task # Epic pts 1 xxxxxxxx 18 2 xxxxxxxx 15 3 xxxxxxxx 33 # Sub-Epic pts 1 xxxxxxxx 2 8 xxxxxxxx 0 OPO OPO Team Team member(s) # User Story pts 1 xxxxxxxx 12 9 xxxxxxxx 7 # User Story hours 1 xxxxxxxx 6 7 xxxxxxxx 12 EPIC burndown 1,2 points / sprint & team 1,2 points / sprint & team 7,2 points / sprint Sub- Epic burndown Story burndown EPIC Velocity is WRAT specific Sub-Epic velocity is WRAT specific Story velocity is team specific Task velocity is employee specific
  7. 7. 2015-03-30 | Page 7 WRAT People › Staffing of WRAT project. › 4 different sites involved. › Both Ericsson and partner teams. › 1/3 part of the teams are not XFTs. These serve in a sort of service layer function to the XFTs
  8. 8. 2015-03-30 | Page 8 Continuous integration (CI) definition › Continuous integration is a software development practice where – All product development teams integrate their work to GIT master branch (uplift and merge) as frequently as possible maintaining legacy – each integration is tested in various loops of automated tests on all test cycles – each integration to master is tested by an automated test suit (delivery check) to detect errors as quickly as possible before integrating into master branch Continuous Integration Product Development Hourly cycle Daily cycle weekly cycle XFT Various loops of automated tests Delivery Check release cycle Frequent commits of SW
  9. 9. 2015-03-30 | Page 9 Lessons learned during agile transformation CI
  10. 10. 2015-03-30 | Page 10 Lessons learned during agile transformation cont’

×