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.
Upcoming SlideShare
Challenges of an Offshore Agile Coach in a Large Scale Agile Transformation
Next

3

Share

Agile Eastern Europe 2011 Large Scale Agile Transformation

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Agile Eastern Europe 2011 Large Scale Agile Transformation

  1. 1. Large Scale Agile Transformation Agile Eastern Europe: Season 3 Kiev, Ukraine Sept 23 & 24 2011
  2. 2. The Story of A Large Scale Agile Transformation Agile Transformation Petra Skapa
  3. 3. Questions… <ul><li>How many of you are or have been part of an Agile team? </li></ul><ul><li>How many of you have been part of an organization transitioning to Agile? </li></ul><ul><li>How many of you have had the job of helping organization transition? </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  4. 4. Once upon a time... <ul><li>..in an Agile Transformation far far away… </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Transformation Petra Skapa
  5. 5. Chapter 1 <ul><li>...there lived a prince who wanted his castle to be grander, his land to produce more crops and for all the people to be happy. </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  6. 6. Chapter 2 <ul><li>The prince decided to go on a long long long journey to seek the answers to his dreams. </li></ul><ul><li>He attended gatherings (like AgileEE ), met new cultures and discovered a magic chest called Agile that might provide the riches he dreamed of. </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com AGILE
  7. 7. Chapter 3 <ul><li>The prince opened the chest and out popped an Agile coach </li></ul><ul><li>The coach and the prince </li></ul><ul><li>worked together for many </li></ul><ul><li>moons, and this is their story.. </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  8. 8. Interlude <ul><li>4 x 4 teaser </li></ul><ul><ul><li>4 companies 4 questions </li></ul></ul><ul><li>1 deep dive </li></ul><ul><li>Why did they want to ? </li></ul><ul><li>How was it done? </li></ul><ul><li>Are they Agile now? </li></ul><ul><li>Was it worth it ? </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Transformation
  9. 9. Why did they want to transform to Agile? <ul><li>Long time to market </li></ul><ul><li>Delivering the wrong thing to customers </li></ul><ul><li>Desire to scale </li></ul><ul><li>Low quality = high maintenance costs </li></ul><ul><li>Losing market share </li></ul><ul><li>Brain drain </li></ul><ul><li>They used to be innovative, less now </li></ul><ul><li>It’s cooool, it’s in style </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  10. 10. 2003 © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Question Answer 2. How? <ul><li>Hired experts </li></ul><ul><li>Pilot project </li></ul><ul><li>Right people on the bus </li></ul><ul><li>Continuous integration on legacy code </li></ul><ul><li>Strong sponsor, leader of department </li></ul><ul><li>Took risks, willing to fail </li></ul>3. Agile now? B, they did a second wave, tried again and continue to move forward 4. Worth it? <ul><li>Significantly reduced time to market </li></ul><ul><li>Continued expansion of Agile </li></ul>
  11. 11. 2009 © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Question Answer 2. How? <ul><li>Centralized support </li></ul><ul><li>Just do Scrum at scale (by the book) </li></ul><ul><li>Local leaders with some control </li></ul><ul><li>Agile partner consultants </li></ul>3. Agile now? in progress, pockets of agility 4. Worth it? <ul><li>Visibility increased </li></ul><ul><li>R&D and Product Mgmt as partners </li></ul><ul><li>Increased focus on value </li></ul><ul><li>First ever “0 bug release” </li></ul>
  12. 12. Scrum at Scale Model © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Just do Scrum.. ..at scale
  13. 13. Feature Team © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Source: http://www.featureteamprimer.org/ Larman, Vodde
  14. 14. Feature versus Component Team © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Source: http://www.featureteamprimer.org/ Larman, Vodde
  15. 15. Sometimes they have no reason at all… © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com not
  16. 16. 2010 © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Question Answer 2. How? <ul><li>2 consultants </li></ul><ul><li>Create documents </li></ul><ul><li>Check and enforce adherence </li></ul><ul><li>No team contact, training only </li></ul>3. Agile now? No 4. Worth it? <ul><li>No change </li></ul><ul><li>But still rich </li></ul>
  17. 17. Lets’ zoom in on Global Retailer 2005 © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  18. 18. We asked, why change? <ul><li>Unsustainable pace </li></ul><ul><li>Scaling challenges </li></ul><ul><ul><li>Couldn’t meet demand </li></ul></ul><ul><li>Big future vision </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  19. 19. We asked, what was wrong? © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Phase 1 - Assessment and Recommendations
  20. 20. We listened to people <ul><li>Imposed Deadlines </li></ul><ul><li>Lack of clear requirements </li></ul><ul><li>Waiting on other teams </li></ul><ul><li>Integration with other systems </li></ul><ul><li>Testing is an afterthought </li></ul><ul><li>Poor communication </li></ul><ul><li>Context switching, multi tasking, re-prioritizing </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  21. 21. We looked at the code <ul><li>It wasn’t pretty </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  22. 22. We looked at the code <ul><li>15 manual steps to prepare a build </li></ul><ul><li>Deployment failure 50% </li></ul><ul><li>25% test coverage </li></ul><ul><li>0% of tests run automatically </li></ul><ul><li>30% code duplication </li></ul><ul><li>100s of methods over 150 lines </li></ul><ul><li>Files over 2000 lines </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  23. 23. We identified themes for improvement <ul><li>Lack of Communication and Collaboration </li></ul><ul><li>Lack of Disciplined Testing Practices </li></ul><ul><li>Lack of Clearly Defined Roles & Responsibilities </li></ul><ul><li>Too Many Manual Processes </li></ul><ul><li>Undisciplined Project Initiation </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  24. 24. We made recommendations <ul><li>Pilot Project </li></ul><ul><li>Put in iterations </li></ul><ul><li>Teach coding best practices (XP) </li></ul><ul><li>Metrics </li></ul><ul><li>Communication </li></ul><ul><li>Roles clarity </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  25. 25. We created an Agile Roadmap © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  26. 26. The roadmap changed over time © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  27. 27. We developed a change model © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Guidance Team Chief Agilist Backlog Owner Strategic Direction Employee Employee Organizational Owners Employee 1 Employee 2 Employee 2 Agile Training 101 Agile Cookbook & Inception Toolbox Agile Health Check & Assessment Project & Story Sizing Iteration Management Employee External Expert External Expert
  28. 28. We ended with continuous improvement <ul><li>..and all the riches that brings </li></ul><ul><li>Based on Lean thinking </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  29. 29. Was it worth it? <ul><li>“ I would never go back to how we worked before” </li></ul><ul><li>Major brand expansion </li></ul><ul><li>Destination employer </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  30. 30. Epilogue – Know Why! <ul><li>Don’t embark on an Agile transformation because you want to ‘be Agile’, </li></ul><ul><li>do it because you want to… </li></ul><ul><li>Make more money </li></ul><ul><li>Beat your competitors </li></ul><ul><li>Delight your customers </li></ul><ul><li>Retain your people </li></ul><ul><li>Innovate </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  31. 31. And once you know why, then.. <ul><li>Accept their will be a learning curve </li></ul><ul><ul><li>Change is hard </li></ul></ul><ul><li>Have a holistic approach </li></ul><ul><ul><li>System thinking </li></ul></ul><ul><li>Find out what is most important to do first </li></ul><ul><ul><li>Find the biggest pains and wastes </li></ul></ul><ul><li>Invest time, experts and potentially tools </li></ul><ul><ul><li>People need support to change </li></ul></ul><ul><li>Think continuous improvement </li></ul>© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com
  32. 32. Thank You! спасибі
  • venkatasundaram

    May. 31, 2018
  • govindk76

    Nov. 7, 2016
  • chesternace

    Jul. 9, 2013

Views

Total views

2,268

On Slideshare

0

From embeds

0

Number of embeds

252

Actions

Downloads

0

Shares

0

Comments

0

Likes

3

×