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!
2. Konstantin Diener CTO und Gründer von cosee
3. Produktentwicklung starten Produktentwicklung skalieren
4. Discovery- Phase Backlog Experten-Teams Abrechnungs- modelle Auslieferung in Sprints Soft ware- Releases
5. Why should teams decide which technologies to use?
8. manager or architect manager or architect information decision
9. Robust? Resilient?
10. Team has all the relevant informationen.
11. You build it, you run it!
12. Everything’s fine, isn’t it?
13. „lone wolf“
14. Bring your own pet technology
15. „I’m not familiar with xyz!“
16. „We made a decision on that?“
17. everybody is involved
18. „Shadow CTOs“
19. manager or architect manager or architect information decision
20. Ops? Costs?
21. I give a sh**t on expert opinions
22. Any ideas? 🤔
23. http://www.commitstrip.com/en/2018/10/31/the-god-of-random-shall-decide/
24. three musketeers (3-Personen-Regel)
25. „A decision is made by those that stand up at night when it breaks“
26. • What is the decision about? (topic)
27. • What is the decision about? (topic) • What criteria do we use to decide?
28. • What is the decision about? (topic) • What criteria do we use to decide? • What options do we have?
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?
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?
32. Sam Kaner Facilitator's Guide to Participatory Decision-Making
33. Everything cool? 🤔
35. That means, every single team uses a di ff erent database?
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?
37. Who are the experts?
39. How do others do it?
40. http://www.infoq.com/presentations/spotify-evolution
41. http://www.infoq.com/presentations/spotify-evolution
42. http://www.infoq.com/presentations/spotify-evolution
43. Scaling Lean & Agile Development Craig Larman, Bas Vodde
44. Try … … use CoPs for functional learning cultivating Communities of Practice …
45. Communities of Practice
46. • shared standards („common baseline“ & common knowledge)
47. • shared standards („common baseline“ & common knowledge) • solve everyday problems
48. • shared standards („common baseline“ & common knowledge) • solve everyday problems • distribute knowledge
49. Emily Webber Building Successful Communities of Practice
50. • shared standards („common baseline“ & common knowledge) • solve everyday problems • distribute knowledge • foster innovation
51. Community Domain Practice
52. Participation is voluntary.
53. „… build a fire in the center of the community that will draw people to its heat.“
54. Etienne Wenger, Richard A. McDermott, William Snyder Cultivating Communities of Practice
55. What’s the community’s focus?
56. Helping Communities Knowledge Stewarding Communities Innovation Communities Best Practice Communities
57. Charta as working agreements
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