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.

Scaling Agile Fuck-Ups - presented at Tools 4 Agile Teams Dec 2017

144 views

Published on

What are typical mistakes being made when scaling agile systems? In here you will find some that I have experienced and comitted... Hope you can learn from it.

Published in: Software
  • Tired of being scammed? Take advantage of a program that, actually makes you money! ▲▲▲ https://tinyurl.com/y4urott2
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Scaling Agile Fuck-Ups - presented at Tools 4 Agile Teams Dec 2017

  1. 1. Scaling Agile Fuck-Ups Tools 4 Agile Teams 2017 Christof Braun manageagile.com
  2. 2. Disclaime r 1 The F*** word will be used – a lot
  3. 3. Context A fuck-up in one context might work well in another context What is learned from a fuck-up may also change from context to context Disclaime r 2
  4. 4. Fuck-ups will happen with every agile scaling framework No side will be taken in the framework wars Disclaime r 3
  5. 5. Disclaime r 4 No association with
  6. 6. Out of respect for the organizations and people who fucked up, no names will be mentioned The following are true stories It all happened some time between 2011 and 2017 Especially not the one that starts with Ch.. and ends with ..ristof
  7. 7. Scale without real need
  8. 8. Avoid scaling Accept larger team or (esp. late in project) do not add anyone or create independence by splitting project
  9. 9. Grow, but try to hold on to how it always was
  10. 10. Change is the new normal Best practice is past practice Learn (and teach) how to embrace change
  11. 11. The process trap
  12. 12. Less is more Set constraints (or high level process) Let teams make their own rules/process within the constraints Adapt processes to what is done
  13. 13. Many (new) roles
  14. 14. Few roles with goals Give decisions and responsibility to teams rather than roles – they can then delegate CoPs / Guilds of roles with decision power Rotate people to roles assignment
  15. 15. Functional Teams
  16. 16. Communication Teams Sort people into teams along their communication needs Cross-functional teams can take care of a requirement all alone Use CoP/CoI/Guild to have interaction of like minded and similarly skilled people Have functional service
  17. 17. Drop Inspect & Adapt
  18. 18. Do big, long retrospectives Invest in retros for entire organizational unit regularly Use multiple skilled facilitators Do it well and you have ROTI Reduce feedback cycle – have big retros often enough
  19. 19. Go and experiment with scaling! Don’t be afraid to fuck up! Just make sure you learn from it!
  20. 20. Thanks for listening! christof@manageagile.com @christofbraun

×