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.

Less in-action

1,181 views

Published on

Session presented at Regional Scrum Gathering South Asia 2015

Published in: Leadership & Management
  • Be the first to comment

  • Be the first to like this

Less in-action

  1. 1. © GOSEI LeSS in Action Ran Nyman Scrum Gathering BLR 5.6.2015
  2. 2. Gosei  Oy  all  rights  reserved. Session Product development started in 2007 Two teams and management cultures Waterfall Agile The product High capacity GGSN and SAE Gateway What did we learn about LeSS 2
  3. 3. Gosei  Oy  all  rights  reserved. Who am I 3 Ran Nyman Worked with LeSS in 2005 Worked with many large SAFe implementations for several years between 2008 and 2011 MSc in Computer Science Since in 1995 professional SW development
  4. 4. Starting Development 4
  5. 5. Gosei  Oy  all  rights  reserved. Starting Phase Two teams Mixing teams Component or Feature teams? No legacy code How often can you start from scratch? First steps Build initial architecture Create Producut Backlog Decide tooling and development practices 5
  6. 6. Gosei  Oy  all  rights  reserved. Setting up Teams Where to get ScrumMasters? What do with managers? Mixing teams a good approach? 6
  7. 7. Gosei  Oy  all  rights  reserved. Deciding Development Practices Programming Language Continuous Integration Automated Acceptance Testing Tools Robotframwork.org with Catapult driver Unit testing Fast feedback! Even with prototype Hardware is essential 7
  8. 8. Initial LeSS with 2 Teams 8
  9. 9. Gosei  Oy  all  rights  reserved. LeSS with 2 Teams Initial Product Backlog Creation Initial Architecture Common Sprint Planning 1 & 2 Scrum of Scrum coordination during Sprint Joint Sprint Review Team Retrospectives Overall Sprint Retrospective 9
  10. 10. Gosei  Oy  all  rights  reserved. 10 Initial Product Backlog Creation
  11. 11. Gosei  Oy  all  rights  reserved. 11 Initial Architecture
  12. 12. Gosei  Oy  all  rights  reserved. Common Sprint Planning 1 and 2 12
  13. 13. Gosei  Oy  all  rights  reserved. 13 Initial Team Room
  14. 14. Gosei  Oy  all  rights  reserved. Better Team Rooms 14
  15. 15. Gosei  Oy  all  rights  reserved. Common Sprint Review 15
  16. 16. Gosei  Oy  all  rights  reserved. Common Sprint Retrospective 16
  17. 17. Gosei  Oy  all  rights  reserved. Remarks Arguments between teams Do not separate teams in opposite end of building Common planning and workshops are not enough Create shared space with teams that create initial architecture Technical challenges Planning vs Doing balance was hard to find Improvements! 17
  18. 18. Gosei  Oy  all  rights  reserved. Analysis Managers as ScrumMaster does not work 18
  19. 19. Growing Phase 1 19
  20. 20. Gosei  Oy  all  rights  reserved. Growing Phase 1 Adding 4 more teams to existing site Non agile background Resistance to new ways of Coaching helped 20
  21. 21. Gosei  Oy  all  rights  reserved. LeSS with up to 6 Teams Common Sprint Planning 1 and 2 did not work anymore Common Product Backlog Refinement did not work Sprint Planning 1 and Product Backlog Refinement with Team Representatives 21
  22. 22. Less.Works - Ran Nyman Sprint  Planning TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Team PO Team PO  +  Teams More  than  few  teams
  23. 23. Less.Works - Ran Nyman Sprint  Planning Team TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Team PO Team PO  +  Teams More  than  few  teams
  24. 24. Less.Works - Ran Nyman Sprint  Planning Team SM TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Team PO Team PO  +  Teams More  than  few  teams
  25. 25. Less.Works - Ran Nyman Sprint  Planning Team SM TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Team PO Team PO  +  Teams More  than  few  teams
  26. 26. Less.Works - Ran Nyman Sprint  Planning Team SM TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Team PO Team PO  +  Teams More  than  few  teams
  27. 27. Less.Works - Ran Nyman Sprint  Planning Team SM TR SM PO TR TR TR TR TR TR TR 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Sprint  backlog Team PO Team PO  +  Teams More  than  few  teams
  28. 28. Less.Works - Ran Nyman Sprint  Planning Team SMSM TR SM PO TR TR TR TR TR TR TR Team Team Team SM Team Team 1 2 Time-­‐box  2h Sprint  planning  PO  +  Team  representatives Time-­‐box  2h Sprint  backlog Team PO Team PO  +  Teams More  than  few  teams
  29. 29. Less.Works - Ran Nyman Product  Backlog  Refinement With few teams
  30. 30. Less.Works - Ran Nyman Product  Backlog  Refinement With few teams With many teams
  31. 31. Less.Works - Ran Nyman Product  Backlog  Refinement With few teams With many teams Refined Items
  32. 32. Gosei  Oy  all  rights  reserved. Introduction of Bug Tracking System 24
  33. 33. Gosei  Oy  all  rights  reserved. Remarks Growing from 2 to 6 teams was easy Coaching helps Do not underestimate resistance 25
  34. 34. Growing Phase 2 From LeSS to LeSS Huge 26
  35. 35. Gosei  Oy  all  rights  reserved. Offsite Teams Adding offsite subcontractor Training Visit to main site Same rules as for local teams Product Owner proxy Offsite technical helpers 27
  36. 36. Gosei  Oy  all  rights  reserved. LeSS Huge Introduced requirement areas Team working mainly in one requirement area 1-2 Teams per area Area Product Owners? From Product Management Feature experts 28
  37. 37. Gosei  Oy  all  rights  reserved. 29
  38. 38. LeSS Huge 30
  39. 39. Gosei  Oy  all  rights  reserved. LeSS Huge in Action Common cadence to all teams Sprint Review to Sequential PO + Feature Experts visiting each team Product Backlog refinement per Requirement Area Separate Sprint Review for offsite teams Offsite Proxy Product Owner key person 31
  40. 40. Less.Works - Ran Nyman Moving  to  LeSS  Huge
  41. 41. Less.Works - Ran Nyman Moving  to  LeSS  Huge Adds: Requirement Areas Area Product Owner Area Product Backlog
  42. 42. Less.Works - Ran Nyman Moving  to  LeSS  Huge Adds: Requirement Areas Area Product Owner Area Product Backlog
  43. 43. Gosei  Oy  all  rights  reserved. Observations Overall Retrospective How to get improvements done and keep people motivated What do with project mangers? Performance testing? 33
  44. 44. Gosei  Oy  all  rights  reserved. Analysis Impediment service Training Managers as development team worked fabulously Requirement Areas too Small -> No Area Product Owners Real Area Product Owners not Feature Experts Feedback and motivation for teams 34
  45. 45. Keeping Things on Track 35
  46. 46. Gosei  Oy  all  rights  reserved. Continuous Integration 36
  47. 47. Gosei  Oy  all  rights  reserved. Tooling 37
  48. 48. Gosei  Oy  all  rights  reserved. Tracking Progress 38
  49. 49. Gosei  Oy  all  rights  reserved. Better View on Status 39
  50. 50. Conclusions 40
  51. 51. Gosei  Oy  all  rights  reserved. Achievement Capability to release in 2 week cadence Fast reaction to changing requirements from customer “As a result of our Agility in developing products, we have been able to demonstrate the product capabilities at an early stage of the development cycle itself, helping us to win new customers cases.” Head of Business-line 41
  52. 52. Gosei  Oy  all  rights  reserved. Employee Feedback 42 We would have not succeeded without LeSS This is the only way of building products. We do not want to go back to sequential development. More collaboration, freedom, discussions, impacts on product Seeing the results with fast feedback Challenges How to keep architecture in good shape Seeing the whole difficult
  53. 53. Gosei  Oy  all  rights  reserved. Conclusions LeSS was only viable option We focused too much on developing product Focus on process is important also Coaching is not enough Offer training Involve higher management Having support only from product group is not enough Sustainable agile organization needs changes in organizational structure Customer visit! Moving from LeSS to LeSS Huge needs effort 43
  54. 54. Gosei  Oy  all  rights  reserved. Key Insight about Teams 44
  55. 55. Questions Upcoming LeSS Trainings in India: http://bit.ly/LeSS-BLR http://bit.ly/LeSS-PUNE More with LeSS: http://less.works 45
  56. 56. Thank You 46

×