Scaling Dimensions - Scaling is more than adding people to a product team
5 likes710 views
Christoph Mathis discusses the principles and challenges of scaling Agile in organizations, highlighting the importance of team dynamics, continuous improvement, and effective metrics. He emphasizes the need for organizational adaptability and the role of values in creating a shared culture within Agile methodologies. The presentation also outlines actions for successful transformation, including refining processes, promoting autonomy, and measuring learning.
Scaling Dimensions - Scaling is more than adding people to a product team
- 1. Scaling Dimensions Christoph Mathis Scaling Agile for the Enterprise 2015, Brussels, 22-‐Jan-‐2015 h@p://brussels2015.agileconsorEum.net/ 1
- 2. About me WriEng and building soHware since many years First exposure to Lean in the early 1980s Return to developing soHware First XP exposure in 2000, Scrum 2003 Slowly connecEng the dots .. Today: Coaching OrganizaEons in Agile Culture, Methods, PracEces and Principles, Training in Scrum 2 h@p://improuv.com christoph.mathis@improuv.com 2
- 3. About improuv is an agile consultancy located in München and Hamburg. Our experEse is Lean and Agile change: • Scrum, Kanban Trainings and CerEficaEons • Agile Change Assessment, Coaching and Mentoring • Agile TransformaEon using Scrum, Kanban, XP, SAFe 3 3
- 4. We are drivers in the Agile Community 4 DeutscheScrum -‐ Beginning in 2007, we organize a yearly non-‐ profit conference for the German speaking Scrum Community www.deutschescrum.org Agile Tuesday München -‐ Since 2008 we organize a monthly event with contribuEons from the agile Community in München www.agiletuesday.org ScrumAlliance -‐ we are member and Registered EducaEon Provider of the ScrumAlliance. h@p://srumalliance.org ContribuEons to Conferences -‐ we are frequent contributors to several conferences and workshops -‐ see h@p://improuv.com/ de/publikaEonen 4
- 5. Working in the large 5 5
- 8. Industrial Scaling: Process first, adding resources 8 8
- 9. 9 9
- 10. Talking about adding resources… 10 10
- 12. 12 12
- 13. When is this model successful Taylorism relies on • cheap, replaceable resources • a dominant market posiEon (stable planning environment) 13 13
- 14. How did we end up talking about small groups of people 14 14
- 15. Adding people to a late project makes it later Brooks’s Law 15 15
- 16. 7±2 16 16
- 18. A surprising number of things can be achieved with smaller Teams 18 18
- 19. Experiences and Achievements with small Teams 19 19
- 20. Achievements … 1. Augmented learning 2. Predictable development 3. Fast feedback 4. Fun and personal development 20 20
- 21. and: 5. Isolate teams from dysfuncEonal organizaEons 21 21
- 22. Augmented Learning 22SECI model by Nonaka, Takeuchi 1994ff 22
- 23. Learning speed = Development Speed Alistair Cockburn 23 23
- 24. Predictable Development XP -‐> defined and measurable results • Working soHware is the primary measure of progrss (Agile Manifesto) Regular Sprints -‐> Controlling flow under uncertainty • F5: The principle of Periodic ResynchronizaEon: Use a regular cadence to limit the accumulaEon of variance (Don Reinertsen, Principles of Product Development Flow) 24 24
- 25. Fast Feedback 7±2 • stable teams • collecEve responsibility • avoid handovers • controlling uncertainty through short regular cycles People have limited bandwidths 25 25
- 26. Fun and personal development „Carrots & SEcks are so last Century. Drive says for 21st century work, we need to upgrade to autonomy, mastery and purpose.“ Daniel Pink, The surprising truth about what moEvates us 26 26
- 27. Scaling Challenges these Achievements 27 27
- 28. Scaling Dimensions and Challenges More complex products • Understanding the whole product becomes harder Complete value chain • Eliminate tradiEonal division of work involves more different job types Up the corporate mountain • Higher levels of hierarchy need different abstracEons to funcEon More people • ResulEng in the need to involve more people • CommunicaEon bandwidth, faster learning 28 28
- 29. A (scaled) environment is never perfect • ConEnuously imperfect organizaEon • ConEnuously imperfect people (hopefully: diverse people) • ConEnuously changing environment • Diverse learning cycles 29 29
- 30. Scaling is about choosing a path Values • Values are necessary for creaEng a shared mindset and culture Principles and PracEces • What are desirable pracEces A StarEng Point (a framework?) • Not a Blueprint Agile EvoluEon • Provide help for a conEnuous improvement 30 30
- 31. Scaling needs constant adap?on 31 31
- 32. How to select metrics 32 32
- 33. Metrics modify behavior (1) 33 Lines of Code Personal Performance In Time, scope, budget Bloated Code Rivalry, not CooperaEon Sloppy SoHware 33
- 34. Metrics modify behavior (2) 34 Customer SaEsfacEon Team SaEsfacEon Bugs in ProducEon Code € MoEvaEon, ProducEvity Life Cycle Cost 34
- 35. Who measures Whom 35 I measure (secretely) I measure (transparently) Team measures Fear Gaming the Metrics Autonomy 35
- 36. The Problem of KPIs KPIs should inspire improvement KPIs loose effecEveness over Eme KPIs should be reEred 36 36
- 37. From: Performance EvaluaEon => To: Maximize Learning 37 37
- 38. Alignment > Compliance Alignment: • we share the same goals Compliance: • do as I say or else … 38 38
- 39. Agile Evolu?on 39 A framework for conEnuous improvement 39
- 40. For Teams, this could mean to assess: • Product Quality • PredicEve Quality • Consistent Delivery • CollaboraEve Work • Inter-‐Team CollaboraEon • Empowerment • ConEnuous Improvement 40 40
- 41. 1. Product Quality Teams that excel in this area • have a good understanding of who their customer is and what their customer‘s needs are • know the cost of delay is for each feature and align with their customer‘s strategies to minimize them • share a clear product vision that states their target market and compeEEve advantages • have backlog items that reflect value to the customer, grouped into Minimal Marketable Features • strive for simplicity, thus maximizing the amount of work not to be done • maintain a barely sufficient backlog to fulfill their architectural and predicEve needs • have loosely coupled product increments that allow organic growth in small increments and thus a steady accrual of value 41 41
- 42. 7. ConEnuous Improvement Teams that excel in this area • are master of their process and improve it in a regular, fast cadence (e.g. retrospecEves) • do retrospecEves effecEvely, leading to acEonable items that regularly get executed • provide transparency about core informaEon and regularly reflect on it • celebrate reflecEon as high-‐leverage Eme, not as “unproducEve not-‐working” • make progress through small safe-‐to-‐fail experiments • accept failure and exercise them as learning opportunity • experience management support and regularly face management’s demand to improve the process 42 42
- 43. Seven Rules for Scaling 43 43
- 44. 1. Don’t do it 44 44
- 45. Think again: what created the need to scale Look for • Complexity in your product • Handovers • Skill limits 45 45
- 46. 2. Make Agile sEck 46 46
- 47. 3 Steps to make Agile sEck To make Agile sEck • Pursue solid Agile pracEces • Improve conEnuously • Make agile part of your company’s DNA 47 47
- 48. 3. Clean up your mess 48 48
- 49. To clean up … Accidental vs. essenEal complexity • Simplify your product Clean up your soHware code base • Loose coupling is the one principle that survived all hypes • Indicator: can you deliver conEnuously ? Clean up organizaEonal impediments • Conway’s law: a product will be structured like the organizaEon which created it • Handovers are evil 49 49
- 50. 4. Think about your values 50 50
- 51. Agile EvoluEon Values • Trust • Respect • Curiosity • Excellence • Alignment 51 51
- 52. 5. Consider your environment 52 52
- 53. Things tend to change rapidly these Emes From defending your posiEon to thriving in a changing environment • Adaptability • CreaEve Change Towards a CreaEve Economy 53 53
- 55. Turn your matrix organizaEon upside down A typical matrix organizaEon • Focuses on resource uElizaEon • Obscures the important part: value streams 55 55
- 56. 7. Measure to accelerate learning 56 56
- 57. Measure the right way Why • Metrics help to idenEfy „be@er“ What • Product, process, skills How • Support autonomy and leadership on every level 57 57
- 58. Implement an Agile EvoluEon Assess and improve • Agile is a path, not a status -‐ Agile EvoluEon helps to walk the walk Have a system of metrics • Helps asking powerful quesEons and to derive improvement objecEves Guide and measure an improvement and transformaEon process • Use metrics to steer the implementaEon Agile and Lean A reference model • Have a Big Picture of your Agile TransformaEon -‐ evolve this picture constantly 58 58
- 59. 59 h@p://improuv.com christoph.mathis@improuv.com Ask the Team Inspect and Adapt Deliver every Sprint Treat People as Adults 59