✊ Join the DEV-olution: A culture of empowered developers
•
0 j'aime•4 vues
Engineering leaders say their organizations struggle with productivity, collaboration, and tracking progress against goals. Some try to fix it by adding more dashboards, making strict rules, and asking for more reports. But just doing more doesn't solve the real issues developers face. Let’s build a culture that empowers developers to do the right things and starts a dev-olution. Join Sven and hear how empowered teams build trustful relationships, work asynchronously and synchronously, use data smartly, care about outcomes, stay curious, and always try new things. More importantly, you will learn how to establish such a culture evolutionarily. Empowering your engineers will amplify developer joy and supercharge your development effectiveness.
Recommandé
Recommandé
Contenu connexe
Similaire à ✊ Join the DEV-olution: A culture of empowered developers
Similaire à ✊ Join the DEV-olution: A culture of empowered developers (20)
Plus de Sven Peters
Plus de Sven Peters (20)
Dernier
Dernier (20)
✊ Join the DEV-olution: A culture of empowered developers
- 1. ✊ Join the DEV-olution A culture of empowered developers Sven Peters DevOps Advocate
- 2. In a galaxy far far away Just two methods of developing software
- 4. Chaotic Slow
- 5. Agile
- 8. Code is written here
- 9. Standardization can go too far
- 10. 43% of organizations say low productivity is the biggest challenge
- 11. Stuck in traffic
- 12. You are the traffic
- 13. ✊ DEV-olution Empowering Developers Give teams time and resources to solve their challenges You hired full grown adults. Treat them like that. Less processes . Teams run at their own pace It’s an evolution, not a revolution
- 16. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 17. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 18. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 19. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 20. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 21. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 22. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges?
- 23. Wait time Execution independence Speed to ship quality code Managing code, pipeline, and infra Managaing external standards Acess to tools, processes, and practices What are developers top challenges? 14% 23% 31% 9% 7% 16%
- 24. Building software . . . . . . . . . . . . . . . . . . . . . . . . . . . .
- 25. What’s a good build time? 10 min 10 sec Sucks for front- end software Great for mobile apps
- 26. 4:30 min Team Muppets 20 min Team Back 20 seconds Team Hello World 2:35 minutes Team Aquarium 2:35 minutes Team Heros 12:30 min Team Helpers Skelters 12 min Old Fashion 3:40 min Team Stranger Things Different teams Different goals 6:20 minutes Team Kick A$$
- 28. What are your top challenges? Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Waiting time Speed to ship quality code
- 29. What are your top challenges? Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Waiting time Speed to ship quality code Satisfaction
- 30. What are your top challenges? Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Waiting time Speed to ship quality code Satisfaction Importance
- 31. Managing code, tools , pipelines Satisfaction Importance Ramp up time Wait time Speed to ship Access to tools Execution independence Managing external standards Developer satisfaction
- 32. TEAM PLAYBOOK | DEVEX SURVEY
- 33. Build a culture of continous improving Empower your team to taggle their challenges ✊ 🌱
- 34. Improve Build stuff What’s the right balance?
- 35. Improve Build stuff 55% 10% What’s the right balance? Keeping the lights on 35%
- 36. Developer Experience Changing the business 55% 10% What’s the right balance? Running the business 35%
- 37. ATLASSIAN ANALYTICS | DEVELOPER TIME
- 38. ATLASSIAN ANALYTICS | DEVELOPER TIME
- 42. Spend your time intentionally Developer Experience Automate deployment Run the business Code Reviews Run the business Configure infrastructure Change the business Research per Experience ky test detector Change the business Customer Interviews he business mzing CI/CD Run the business Team Meetings Change the business Fixing bugs
- 43. Build a culture of spending time intentionally Empower your team to do what’s best for team, system, and business ✊ 🌱
- 45. User story As a user, I need to controll the air outlets in the middle console of the car, so the direction can be adjusted individually for the driver and the passenger.
- 48. User story Blame the product manager Arnaud Product Manager As a user, I need to controll the air outlets in the middle console of the car, so the direction can be adjusted individually for the driver and the passenger.
- 51. Product Engineer
- 53. What are we doing? Why are we doing it? How will success look like? Product Engineering Why What
- 54. Dark mode
- 55. Default to Dark mode
- 57. Feature Leading
- 61. Feature Leading
- 66. Build a culture of teams working closely together Empower your team to get the support they need… fast. ✊ 🌱
- 71. Demo Sessions
- 72. Demo Sessions
- 73. Async videos
- 74. Demo Sessions 😅 💡 👍 Why are we doing it this way?
- 75. Demos
- 78. #democulture 🎯 5000 demo videos in 2024
- 79. Open by default
- 80. Open by default
- 81. If it’s not in Confluence, it didn’t happen
- 85. Build a culture of open by default Empower your team to get the info they need… without friction ✊ 🌱
- 86. Megan
- 87. How should we continue with the Jira Mac App? ? ? Should we run a dark mode experiment? Can we use Swelte for the new Kanban board? ? Does it make sense to have ypou speak at our conference? ? What color should the CREATE button have? ?
- 88. How should we continue with the Jira Mac App? ? ? Should we run a dark mode experiment? Can we use Swelte for the new Kanban board? ? Does it make sense to have ypou speak at our conference? ? What color should the CREATE button have? ?
- 89. How should we continue with the Jira Mac App? ?
- 90. How should we continue with the Jira Mac App?
- 92. Discusses the options and make recommendations Move the decision-making forward Approves the decision Might be affected but are not involved CONFLUENCE | DACI TEMPLATE
- 93. CONFLUENCE | DACI TEMPLATE
- 94. CONFLUENCE | DACI TEMPLATE
- 95. CONFLUENCE | DACI TEMPLATE
- 96. TEAM PLAYBOOK | DACI
- 97. Async Sync
- 98. Hasn’t read the DACI Is trying to catch up during the meeting Has read the DACI page
- 99. 20% Reading Discussion 70% One-Pager Meetings No prep need No slides 5% Instructions 5% Next steps Intentional time
- 100. One pager Reading time < 6 min read 30 min meeting < 9 min read 45 min meeting < 12 min read 60 min meeting
- 101. One pager Reading time Cameras off Comment +
- 102. One pager Discussion time Inline comments Platform still doesn’t support Can be clearified after the meeting
- 103. One pager Discussion time Page comments Should be discussed during the meeting
- 104. One pager Single source of truth
- 105. Build a culture of intentional sync time Empower your team to get to decisions fast ✊ 🌱
- 106. Work
- 109. People
- 113. Team connection 27%
- 114. Team connection 27% after 4-5 months
- 115. Say thanks and celebrate great work Intentionally 🫶
- 118. $1.00 for a goal Carla Overbeck $1.50 for an assist
- 121. Build a culture of intentional togetherness Empower your team to to celebrate wins together ✊ 🌱
- 122. Empowered Teams Celebrate teams Intentional togetherness Measure what matters Feature lead process Time to fix DevEx Demo culture
- 123. Empowered Teams Celebrate teams Intentional togetherness Measure what matters Feature lead process Time to fix DevEx Demo culture Value and metrics
- 124. Empowered Teams Celebrate teams Intentional togetherness Feature lead process Time to fix DevEx Demo culture Value and metrics Continous improvement
- 125. Empowered Teams Celebrate teams Intentional togetherness Feature lead process Demo culture Value and metrics Continous improvement Suitable ways of working
- 126. Demo culture Empowered Teams Celebrate teams Intentional togetherness Feature lead process Value and metrics Continous improvement Suitable ways of working Shared understanding
- 127. Empowered Teams Celebrate teams Intentional togetherness Value and metrics Continous improvement Suitable ways of working Shared understanding Team cohesion
- 128. Empowered Teams Celebrate teams Intentional togetherness Value and metrics Continous improvement Suitable ways of working Shared understanding Team cohesion Engagement and support
- 129. Empowered Teams Engagement and support Encourage differences Balanced team Team cohesion Value and metrics Suitable ways of working Continous improvement Shared understanding
- 130. Engagement and support Encourage differences Balanced team Team cohesion Value and metrics Suitable ways of working Continous improvement Shared understanding Team Health
- 131. Team Health What’s your kryptonite? Engagement and support Encourage differences Balanced team Team cohesion Value and metrics Suitable ways of working Continous improvement Shared understanding
- 132. Team Health Engagement and support Encourage differences Balanced team Team cohesion Value and metrics Suitable ways of working Continous improvement Shared understanding
- 135. TEAM PLAYBOOK | HEALTH MONITOR
- 136. Build a culture of healthy teams Empower your team to fix thier team problems ✊ 🌱
- 144. Build a culture of empowered developers 😍
- 145. Build a culture of empowered developers Join the DEV-olution ✊
- 146. Join the DEV-olution Thank you! @svenpet svenpet.com/talks