Tech Decisions to the people

It sounds completely obvious: Let your teams decide what technologies to use - not by the CTO or a higher-level architect. The developers in the self-organized teams know the problems to be solved and the possible solutions best.

A practical report on pragmatic approach for self-organized team-based technology decisions.

Transcript

1. Konstantin Diener | konstantin.diener@cosee.biz | @coseeaner
   … in a pragmatic way
   Tech decisions to the people!
   

   View Slide

2. Konstantin Diener
   CTO und Gründer von cosee
   

   View Slide

3. Produktentwicklung
   starten
   Produktentwicklung
   skalieren
   

   View Slide

4. Discovery-
   Phase
   Backlog
   Experten-Teams
   Abrechnungs-
   modelle
   Auslieferung
   in Sprints
   Soft ware-
   Releases
   

   View Slide

5. Why should
   teams decide
   
   
   which technologies to use?
   

   View Slide

6. View Slide

7. View Slide

8. manager or architect
   manager or architect
   information decision
   

   View Slide

9. Robust?
   
   
   Resilient?
   

   View Slide

10. Team has all the
    
    
    relevant
    informationen.
    

    View Slide

11. You build it,
    
    
    you run it!
    

    View Slide

12. Everything’s fine,
    
    
    isn’t it?
    

    View Slide

13. „lone wolf“
    

    View Slide

14. Bring your own
    
    
    pet technology
    

    View Slide

15. „I’m not familiar
    with xyz!“
    

    View Slide

16. „We made a
    decision on that?“
    

    View Slide

17. everybody is
    involved
    

    View Slide

18. „Shadow CTOs“
    

    View Slide

19. manager or architect
    manager or architect
    information decision
    

    View Slide

20. Ops?
    
    
    Costs?
    

    View Slide

21. I give a sh**t on
    expert opinions
    

    View Slide

22. Any ideas? 🤔
    

    View Slide

23. http://www.commitstrip.com/en/2018/10/31/the-god-of-random-shall-decide/
    

    View Slide

24. three musketeers
    
    
    (3-Personen-Regel)
    

    View Slide

25. „A decision is made by those that
    stand
    up at night when it
    breaks“
    

    View Slide

26. • What is the decision about? (topic)
    

    View Slide

27. • What is the decision about? (topic)
    
    
    • What criteria do we use to decide?
    

    View Slide

28. • What is the decision about? (topic)
    
    
    • What criteria do we use to decide?
    
    
    • What options do we have?
    

    View Slide

29. • What is the decision about? (topic)
    
    
    • What criteria do we use to decide?
    
    
    • What options do we have?
    
    
    • Who is part of the team? Who decides?
    

    View Slide

30. • What is the decision about? (topic)
    
    
    • What criteria do we use to decide?
    
    
    • What options do we have?
    
    
    • Who is part of the team? Who decides?
    
    
    • Who are relevant experts?
    

    View Slide

31. View Slide

32. Sam Kaner
    Facilitator's Guide
    to Participatory
    Decision-Making
    

    View Slide

33. Everything cool?
    🤔
    

    View Slide

34. View Slide

35. That means,
    
    
    every single team uses
    
    
    a di
    ff
    erent database?
    

    View Slide

36. • What is the decision about? (topic)
    
    
    • What criteria do we use to decide?
    
    
    • What options do we have?
    
    
    • Who is part of the team? Who decides?
    
    
    • Who are relevant experts?
    

    View Slide

37. Who are the
    experts?
    

    View Slide

38. View Slide

39. How do others do
    it?
    

    View Slide

40. http://www.infoq.com/presentations/spotify-evolution
    

    View Slide

41. http://www.infoq.com/presentations/spotify-evolution
    

    View Slide

42. http://www.infoq.com/presentations/spotify-evolution
    

    View Slide

43. Scaling Lean &
    Agile Development
    Craig Larman, Bas Vodde
    

    View Slide

44. Try …
    …
    use CoPs for functional
    learning
    cultivating Communities
    of Practice
    …
    

    View Slide

45. Communities of
    Practice
    

    View Slide

46. • shared standards („common baseline“ &
    common knowledge)
    

    View Slide

47. • shared standards („common baseline“ &
    common knowledge)
    
    
    • solve everyday problems
    

    View Slide

48. • shared standards („common baseline“ &
    common knowledge)
    
    
    • solve everyday problems
    
    
    • distribute knowledge
    

    View Slide

49. Emily Webber
    Building Successful
    Communities of
    Practice
    

    View Slide

50. • shared standards („common baseline“ &
    common knowledge)
    
    
    • solve everyday problems
    
    
    • distribute knowledge
    
    
    • foster innovation
    

    View Slide

51. Community
    Domain
    Practice
    

    View Slide

52. Participation is
    
    
    voluntary.
    

    View Slide

53. „… build a fire in the center of the
    community that will draw people to its
    heat.“
    

    View Slide

54. Etienne Wenger, Richard A.
    McDermott, William Snyder
    
    
    Cultivating
    Communities of
    Practice
    

    View Slide

55. What’s the
    
    
    community’s
    focus?
    

    View Slide

56. Helping Communities
    Knowledge Stewarding
    Communities
    Innovation
    Communities
    Best Practice
    Communities
    

    View Slide

57. Charta
    
    
    as working agreements
    

    View Slide

58. View Slide

59. View Slide

60. View Slide

61. konstantin.diener@cosee.biz | @onkelkodi
    Picture credits:
    
    
    Cover: https://www.shutterstock.com/de/g/EVANATTOZA
    Like what you see?
    Konstantin Diener | cosee GmbH
    cosee.biz
    

    View Slide