Creating the conditions for an awesome DevEx

It's 2022, and software development and delivery is a fractious experience in many large organisations.

Developers and teams struggle to get going and the development platforms are not fit for purpose. Cloud foundations do not evolve in line with the requirements of the development teams.

This session will explore the conditions needed to facilitate developer autonomy and create an awesome DevEx

Transcript

1. Creating The Conditions For An Awesome Developer Experience Hibri Marzook • Software Practice Lead
2. 2 Hibri Marzook Software Practice Lead Helps teams deliver fast and enjoy doing it Likes the challenge of using Public Cloud and Continuous Delivery to help teams deliver sustainably. Likes to use systems thinking to navigate the challenges of complexity @hibri www.hibri.net
3. The Wall of Confusion
4. Impact of a poor DevEx Cochran, T. (2021)
5. What is DevEx? Developer Experience is about creating an environment in which a developer can do their best work.
6. How do developers feel about the processes, systems and services they use?
7. Why is DevEx important? Developer productivity underpins the success of your organisation.
8. Srivasta, S. et al. (2020)
9. Hire expensive developers and make it hard to do their jobs . . Profit?
10. DevEx is contextual Developers exist in an environment that is unique to your organisation and environment ?
11. A good developer experience is emergent
12. Create boundaries for risk and responsibility
14. Good fences make good neighbours
15. Create a shared responsibility model
16. Create Team Interactions for Fast Flow
17. Conway’s Law 17 Conway’s Law “Organisations which design systems are constrained to produce designs which are copies of the communication structures of these organisations”
18. Conway’s Law affects the developer experience 18
19. Understand Team Interactions
20. Adopt an Internal OSS Model Adopt Communities of Practice
21. Create Fast Feedback Loops
22. The Simplest Feedback Loop is a Conversation 22
23. Optimize Feedback Loops, Not Pipelines 23
24. Get to Real Users Quicker. Only Prod Matters 24 https://twitter.com/copyconstruct/status/974530841190608897
25. How do we measure DevEx?
26. The SPACE Framework S - Satisfaction and Well-being P - Performance A - Activity C - Communication and Collaboration E - Efficiency and flow Yu, A. (2021)
27. Key findings Finding flow is key, and interruptions are a drag. Minimal or no interruptions give developers an 82% chance of having a good day, but interruptions throughout the day decrease the chance of a good day to just 7%. Meetings are both awesome and terrible. Collaboration improves our work, but too many meetings can be a blocker; going from two to three meetings per day lowered the chances of developers making progress toward their goals by 60%. A two minute daily reflection can help developers improve their days
28. Why?
29. A good Developer Experience helps devs find flow and reduces interruptions
30. A good Developer Experience reduces the cognitive load for a developer
31. A good Developer Experience creates an environment of psychological safety
32. References Cochran, T. (2021) Maximizing Developer Effectiveness. Available at: https://martinfowler.com/articles/developer-effectiveness.html (Accessed: January 11, 2021) Srivasta, S. et al. (2020) How software developers can drive business growth | McKinsey, www.mckinsey.com. Available at: https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-s oftware-excellence-fuels-business-performance. Yu, A. (2021) Introducing Developer Velocity Lab – A Research Initiative to Amplify Developer Work and Well-Being, TECHCOMMUNITY.MICROSOFT.COM. Available at: https://techcommunity.microsoft.com/t5/azure-developer-community-blog/introducing-developer-velocity-lab-a-research -initiative-to/ba-p/2333140 (Accessed: 5 May 2022).
33. Q&A 33
34. Atlanta atlanta@contino.io Thank You contino.io continohq contino London london@contino.io New York newyork@contino.io Melbourne melbourne@contino.io Sydney sydney@contino.io 34 Brisbane brisbane@contino.io