scaling agile done right (xp 2017 version)
TRANSCRIPT
![Page 1: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/1.jpg)
Giovanni Asproni email: [email protected] twitter: @gasproni linkedin: http://www.linkedin.com/in/gasproni
Scaling Agile Done RightXP 2017, Köln, Deutschland
![Page 2: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/2.jpg)
![Page 3: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/3.jpg)
![Page 4: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/4.jpg)
My Experience
• Mostly projects involving 4-5 teams • One involving ~80 teams with ~700 developers • One involving ~120 teams with ~1300 developers • One involving 8 teams with ~80 developers
![Page 5: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/5.jpg)
In One Slide
• Usual reasons for scaling • Gotchas • Prerequisites • How to do it
![Page 6: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/6.jpg)
![Page 7: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/7.jpg)
![Page 8: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/8.jpg)
Fundamental Law Of Scaling:
Scaling up amplifies the bad and makes the good more difficult
![Page 9: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/9.jpg)
Scaling up creates new problems
![Page 10: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/10.jpg)
Why?
Before scaling up make sure you have some compelling reasons
![Page 11: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/11.jpg)
Prerequisites
• Clear shared goals • High quality • Suitable architecture • Availability of resources • Automation • Communication • Skills • Metrics • User stories • Prioritisation and planning
![Page 12: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/12.jpg)
Clear shared goals
![Page 13: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/13.jpg)
High quality standards and ability to manage technical debt effectively
![Page 14: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/14.jpg)
A system / software architecture suitable for scaling up the number of people and teams
![Page 15: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/15.jpg)
Availability of hardware and software resources
![Page 16: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/16.jpg)
Automate all the things
![Page 17: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/17.jpg)
Effective and efficient communication channels
https://www.flickr.com/photos/qousqous/57607074
![Page 18: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/18.jpg)
People with the necessary skills (managerial, and technical)
![Page 19: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/19.jpg)
Appropriate metrics in place to measure productivity, quality and other interesting aspects of the project
![Page 20: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/20.jpg)
Ability to create good user stories
![Page 21: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/21.jpg)
Very good prioritisation, planning and coordination skills
![Page 22: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/22.jpg)
Prerequisites Recap
• Clear shared goals • High quality • Suitable architecture • Availability of resources • Automation • Communication • Skills • Metrics • User stories • Prioritisation and planning
![Page 23: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/23.jpg)
First Paradox Of Scaling:
Most projects are scaled up because they don’t fulfil the prerequisites for scaling
![Page 24: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/24.jpg)
Second Paradox Of Scaling:
Projects fulfilling the prerequisites for scaling have a lesser need to scale
![Page 25: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/25.jpg)
Try This First!
![Page 26: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/26.jpg)
How do we do it?
• How much “faster” can we go? • How much more process structure is necessary? • How do we add more people and teams? • Feature or component teams?
![Page 27: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/27.jpg)
“Adding manpower to a late software project makes it later [...] The number of months of a project depends upon its sequential constraints. The maximum number of men depends upon the number of independent subtasks. From these two quantities one can derive schedules using fewer men and more months. (The only risk is product obsolescence.) One cannot, however, get workable schedules using more men and fewer months.”
Amdhal’s Law
![Page 28: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/28.jpg)
http://asprotunity.com/blog/scaling-agile-how-many-teams-are-too-many/
![Page 29: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/29.jpg)
Process and structure
![Page 30: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/30.jpg)
The only roles successful software products ALWAYS need are programmers and users. Everybody else is optional
![Page 31: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/31.jpg)
The role of methodologies should not be to control people, but to help them become more efficient and effective
![Page 32: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/32.jpg)
The right methodology depends on the context of the company and the project. One size does not fit all.
![Page 33: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/33.jpg)
Large scale Agile frameworks have limited applicability
![Page 34: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/34.jpg)
“My strong and increasingly passionate argument was that SAFe is not only a betrayal of the promise offered by AGILE but is a massive retrograde step giving the managerial class an excuse to avoid any significant change.”
David Snowden
http://cognitive-edge.com/blog/safe-the-infantilism-of-management/
![Page 35: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/35.jpg)
![Page 36: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/36.jpg)
• Context specific shortcut strategies • Give flexibility but maintain some
consistency • Can produce better decisions • Allow for synchronisation “on the fly”
![Page 37: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/37.jpg)
1. Understand What Your People Do 2. Reinforce Integrators 3. Increase the Total Quantity of Power 4. Increase Reciprocity 5. Extend the Shadow of the Future 6. Reward Those Who Cooperate
![Page 38: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/38.jpg)
Informal communication can go a very long way
![Page 39: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/39.jpg)
What’s In It For Me?
![Page 40: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/40.jpg)
“A complex system that works is invariably found to have evolved from a simple system that worked.”
Adding People And Teams
![Page 41: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/41.jpg)
Involve the team in the decision of increasing team size. Then increase it incrementally and measure the effects using the metrics in place
![Page 42: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/42.jpg)
When Adding A new Team
• Make sure scope is well understood, and with minimal dependencies on other teams
• Start small. 3-4 people maximum with the required skills • The team is given all the necessary resources to perform their
job • There is an architect available • Measure the effects. If necessary, revert the decision and
remove the team from the project
![Page 43: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/43.jpg)
Team Organisation
• Feature • Component • Mix
![Page 44: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/44.jpg)
Component teams with virtual feature teams
![Page 45: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/45.jpg)
Recap In One Slide
• Usual reasons for scaling • Gotchas • Prerequisites • How to do it
![Page 46: Scaling Agile Done Right (XP 2017 version)](https://reader033.vdocument.in/reader033/viewer/2022051710/5aab049f7f8b9a336d8b47a1/html5/thumbnails/46.jpg)
Final Thoughts
• Scaling up may not be necessary • Often customers want predictability, not speed • Methodologies purpose is to help people do a good job,
not to control them • Methodologies are context dependent. Large scale ones
even more so