Scaled agile framework 04 apr2014

850 views

Published on

large-scale agile / scaled agile framework

Published in: Software, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
850
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
42
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Scaled agile framework 04 apr2014

  1. 1. 
 SCALED AGILE FRAMEWORK" Maarit Laanti, 4.4.2014!
  2. 2. Maarit Laanti" •  20 years in various product development roles at Nokia,
 6 years in agile & lean transformation / organizational development! –  Coached and trained hundreds of practitioners
 in agile methods deployment! •  Scaled Agile Framework (SAFe) Program Consultant at Nitor Delta! •  PhD — “Agile Methods in Large-Scale Software Development Organizations – Applicability and Model for Adoption” (2013)! •  Author or editor of agile and lean textbooks: ! –  376 vuotta ketteriä kokemuksia / Sytyke (2013)! –  LESS!, Essays on Business Transformation (2012)! –  Ohjelmistoliiketoiminta (2003)!
  3. 3. Storyline" 1.  AGILE IS GREAT! 2.  SO WHY DO WE HAVE PROBLEMS STILL?! 3.  SCALED AGILE IS THE ANSWER! 4.  BENEFITS!
  4. 4. AGILE IS GREAT!"
  5. 5. Agile is Great!" Source:  Version  One  2013    State  of  Agile  Survey  
  6. 6. Forrester (2012)
 Agile Software Development And The Factors That Drive Success " Key Findings:" •  Agile tenets and techniques help the best firms to be better. ! •  But there is more to “success” than implementing a few Agile tenets and techniques ! •  Most firms still have a long way to go to become more agile. ! •  The successful group (21%)" –  Significantly involve business sponsors 46% more often ! –  Maximized The Flow Of Their Agile Projects ! –  Used Automated Deployment and Incremental Deployment ! Source:     h;ps://www.pronq.com/community/sites/hp_community/files/learn/4aa4-­‐3679enw.pdf    
  7. 7. …and we all love agile!" Scientific sources" •  70% would not go back (Source: Laanti, 2008)! •  People feel less stress (Source: Laanti, HICSS 2013)! •  Main benefits:! –  Improved team communication! –  Enhanced ability to adapt to changes! –  Increased productivity (Source: Survey on Agile and Lean usage in Finnish software Industry, 2012)! Non-scientific sources" (via Scaled Agile Framework case Studies)! •  Mitchell International, http://www.mitchell.com/ ! –  “greatest thing Mitchell has done in my 14 years here”! •  SEI, https://www.seic.com/enUS/ about.htm ! –  20-25% increase in customer satisfaction! Agile  
  8. 8. "SO WHY DO WE HAVE PROBLEMS STILL?"
  9. 9. Mismatch in steering" CEO   MarkeNng   Finance   HR                       Agile  
  10. 10. Water-scrum-fall is a reality in many organizations
 (Forrester 2011)" Water   Scrum   Fall   Read  more:   h;p://www.cohaa.org/content/sites/default/files/water-­‐scrum-­‐fall_0.pdf    
  11. 11. Or you have converted this typical situation in traditional settings…." Project 1! Project 2! Project 3! Project 4! People" Project" Allocation" Joe! 1! 0.1! 2! 0.4! 3! 0.3! 4! 0.2!
  12. 12. …into this new version where many tasks are still filling the pipeline and everything delays" People" Project" Allocation" team! 1! 0.1! 2! 0.4! 3! 0.3! 4! 0.2! Project 1! Project 2! Project 3! Project 4! Product owner! Backlog!
  13. 13. SCALED AGILE IS THE ANSWER 
 "
  14. 14. Scales Agile…" 1.  Organizes along value chain, away from silos! –  Communication is improved! –  More time in doing, less in meetings! 2.  Automation of work! –  Continuous integration, continuous testing, continuous deployment! 3.  Systematic removal of waiting times! –  Organize work according to pull-principle! –  Understanding and using queuing theory to create optimal flow! 4.  Use smaller batch sizes! –  Reduction of complexity! 5.  Using fast feedback in all levels of the organization! "
  15. 15. Is this what your requirements management is like?" Gather all the requirements! ! ! ! ! End up with ! not-so-usable ! code! ! •  Requirements pile up in storage and get outdated before implemented! •  Guidance on agreed intervals (milestones); not on-time and continuous! •  Limited visibility on what is under development (visibility only on milestones)!
  16. 16. Agile Portfolio Management" Field  studies   Rela,ve  target  se0ng   (compe,tor  comparison)   Fast  customer   feedback   Crowdsourcing  /   ideas   Por$olio   management   Implementa0on   Fast     feedback   Gradual   specifica,ons   Priori,es  and  goals   Transparency   Quick  releasing   Taming uncertainty with:" •  Adaptive decision making" •  Gradual commitments" •  Fast feedback"
  17. 17. Organizing along the value chain" UX   Dev   Arch   Customer   Value  Chain  
  18. 18. Because the whole is more than the sum of its parts! " Aristotle   Co-­‐evoluNon   UX             Focus-­‐ group   Feedback   Arch   •  SynergisNc!     •  Feedback  is  immediate  and  accurate!  
  19. 19. What makes large-scale agile transformation hard?" UX   Dev   Arch   Value  Chain   Management  must  drive,   because  they  have  the   common  interest  
  20. 20. What makes large-scale agile transformation hard?" UX   Dev   Arch   Value  Chain   This  is  true  in  all  lean   transformaNons  
  21. 21. What makes large-scale agile transformation hard?" UX   Dev   Arch   Value  Chain   And  like  in  lean  transiNons,   the  benefits  are  huge!  
  22. 22. What makes large-scale agile transformation hard?" UX   Dev   Arch   Cust omer   Value  Chain   …more  than  what  team   level  brings  you.  
  23. 23. Leaders should lead the way " ! Best practices learned the hard way how to succeed in agile transformation:! 1.  Keep regular! –  Change team meetings,! –  Guiding team meetings! 2.  Train leadership: leaders as teachers ! –  Leaders will be change agents and spokespersons for the change! –  Commit to change, and engage others!! 3.  Listen and react of problems surfaced! –  No politics, no closed groups!! 4.  Keep the change alive!!
  24. 24. Large-­‐scale  agile  is     for  soware  and  services     what  lean  thinking  is  for  manufacturing  
  25. 25. Adaptive Organization" Field  studies   Metrics   Market  info   Crowdsourcing   Release  trials   Adap,ve  loop   Teams   Projects   Por-olio   Rela,ve  metrics  CDF  Adap,ve  planning   Goals  /  rela,ve  target  se0ng   Balancing  investment   Progress  velocity  cycle  ,me   Reward  /     investment   How  to  do/   What  to  do   Double-­‐loop  learning   Con,nuous   improvement   Streaming  problem   solving  
  26. 26. BENEFITS"
  27. 27. 27 SAFe Delivers Business Results 27
  28. 28. 28 Makes Money Faster 28
  29. 29. 29 Delivers Better Fit for Purpose 29
  30. 30. Benefits of Agile Portfolio Management" 1.  “Lean” portfolio – more standard solutions, less “half-baked” solutions with the help of joined backlog! –  Simple but working solutions that meet the need! 2.  Alignment! –  Backlog structure creates better alignment and supports fast decision-making! 3.  Options thinking: systematically nurture successes! –  Visibility enables more nimble steering! –  Start easier; prove concept to get more funding! 4.  Better control on spends! –  Control spends from first cent!
  31. 31. Agile strategy: Leverage with better service" •  All goods have two components: ! –  The actual good! –  Service component! •  Service can be:! –  Make buying decisions easy! –  Ease customer effort! –  Predict when service is needed next time! Old  manual  service   Digitaliza0on   Combine  with   addi0onal  data  to   create  be=er  service  
  32. 32. Be the top dog!"
  33. 33. Net Promoter score predicts success" Are you recommended?" Key drivers:! 1.  Quality! 2.  Usability! 3.  Cost!
  34. 34. Great usability can only be created with iterations" •  IteraNons  are  needed  to  create  great  usability!   •  Scaled agile gives strategic advantage"
  35. 35. What is the best you can dream of?"
  36. 36. Thank You!" www.nitordelta.fi    
  37. 37. KETTERÄ
 MUUTOS   ! ! ! ASIAKAS-" KOKEMUKSEN" SUUNNITTELU" " ! ! Nitor" nitordelta KETTERÄ" TOIMITUS" 
 JATKUVAT" PALVELUT"

×