Download as PDF, PPTX
Uploaded bySven Peters
Microservice Teams - How the cloud changes the way we work
The document discusses the evolution of team organization in the context of microservices and cloud technology, highlighting the shift from traditional structures to more autonomous microservice teams. It emphasizes the importance of support tooling, documentation, and metrics in improving developer efficiency and satisfaction. The presentation also touches on the necessity of continuous improvement and adaptability within teams to meet the evolving demands of the software development landscape.
More Related Content
Similar to Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
- 1. MICROSERVICE TEAMS @svenpet Sven Peters DevOpsAdvocate HOW THE CLOUD CHANGES THE WAY WE WORK
- 5. Our living enviroment changedhow we orginze our lives
- 6.
- 7. In a galaxyfar, far away
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. Jira | Confluence Unicornplatform Linux derivative
- 14. Jira | Confluence Unicornplatform SINGLE TENANT APP ONE CUSTOMER - ONE JVM DIFFICULT TO SCALE
- 16.
- 17.
- 18.
- 19.
- 20. SHARED AND RE-WRITTENCODE CONFLUENCE JIRA BITBUCKET
- 21.
- 23.
- 24.
- 25.
- 26.
- 29. TECHNOLOGY A distributed archtecture inthe cloud. Shared microservices
- 30. TECHNOLOGY A distributed archtecture inthe cloud. Shared microservices TEAMS ?
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. Small teams Oncall
- 40. WE NEEDED TOCHANGE THE WAY WE WORK
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47. 17,000 DOCKER CONTAINER CI/CD CONFIG ADDOBSERVIBILITY … times
- 48. COPY | PASTE| CHANGE 17,000 times
- 49.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58. We created aspreasheet
- 59.
- 60. Microscope Documentation tool formicroservices
- 62. Microscope Documentation tool formicroservices
- 63. Microscope Documentation tool formicroservices Communication teams
- 64. Microscope Documentation tool formicroservices Communication teams API changes
- 66. Is the service ready? Ownerteam Documentation No open Jira Issues Added to Microscope
- 67. Before take off:Let’s go through the checklist
- 68. READY Service Before deployment: Checkservice readiness
- 69. READY Service Before deployment: Checkservice readiness Owner team ✅ Added Description ✅ Added Deployment time < 5 min ⚠ Currently 6.2 min Documentation ❌ Missing Service readiness
- 71.
- 72.
- 73.
- 74.
- 76.
- 77.
- 78.
- 79. A PLAYBOOK FOR DEVS Understand their needs. START SMALL Buildan MVP. Evolve from there. API FIRST Make it easy to run and integrate services. OPEN SOURCE Let developers help. FOR PLATFORM TEAMS
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87.
- 88. Pull Request reviews- How many reviews Lines of cod Time to Restore - Time to bring a service up again ry points completed Bug resolutions - Critical b ectives Incident Response Time -How fast are we reacting? Change Failure Rate - Ratio between successful and failed deploys Comments on Reviews Earlier g aying “login fail” Test covorage Ticket Cycle Time - how much time from backlog to deployment Wait time - time used to wait for tests to complete Build time Unit tests 1/2 T g position Le
- 89. Pull Request reviews- How many reviews Lines of cod Time to Restore - Time to bring a service up again ry points completed Bug resolutions - Critical b ectives Incident Response Time -How fast are we reacting? Change Failure Rate - Ratio between successful and failed deploys Comments on Reviews Earlier g aying “login fail” Test covorage Ticket Cycle Time - how much time from backlog to deployment Wait time - time used to wait for tests to complete Build time Unit tests 1/2 T g position Le Every team has different challenges
- 90.
- 91.
- 92. Measure what isimportant, don’t make important what you can measure. Robert McNamara
- 93. Speed to shipquality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Developer Experience Survey
- 94. Speed to shipquality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Developer Experience Survey
- 95. Speed to shipquality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Satisfaction
- 96. Speed to shipquality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Satisfaction Importance
- 97. Satisfaction Importance Ramp up time Waittime Speed to ship Managing code, tools , pipelines Access to tools Execution independence Managing external standards Developer satisfaction
- 98. TEAM PLAYBOOK |DEVEX SURVEY
- 99. TEAM PLAYBOOK |CHECKOPS
- 100.
- 101. Team Playbook Guidance forall teams
- 102. We hire smartpeople. We don’t need to tell them what to do. We just show them the way.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108. Learn Better tester Better designers Betterproduct managers
- 109.
- 110. Devs Exploratory Test AutomatedTest A Q
- 111.
- 112. QA Kick-off Testing ImplementationDemo Deploy QA Kick-off for team autonomy
- 113. Dependency Autonomy with support QADeveloper
- 114.
- 117.
- 118. Standard bricks Sven’scastle
- 119. Special bricks InstructionsSven’s castle Designed by Lego
- 120.
- 121.
- 122.
- 123. You build it, yourun it Werner Vogel, AWS
- 124. You build it, yourun it, you improve it Sven Peters, Atlassian
- 125.
- 126.
- 127.
- 128.
- 129. New feature PROBLEM SOLUTIONPROTOTYPES CODE TEST DEPLOY BLACK HOLE
- 130. Contextual Feedback As aservice Insights help me to get a better overview of my development process
- 131. Dependency Autonomy with support Customerexperience Developer
- 132.
- 133.
- 134.
- 135.
- 138.
- 139.
- 140.
- 141.
- 142.
- 143.
- 144.
- 145.
- 146. Demo Sessions 😅 💡 👍 Why are we doingit this way?
- 147.
- 148.
- 149. #democulture 🎯 5000 demovideos in 2024
- 151.
- 152. What is aproject? Two people or more. Longer than two weeks.
- 153. What’s the status? Updatesare due every Friday. You just got 280 chars. Go!
- 154. ATLAS | PROJECTABOUT
- 155. ATLAS | PROJECTUPDATES
- 156.
- 157.
- 158.
- 159.
- 160. THE WAY WEWORK DID CHANGED ?
- 161. THE WAY WEWORK DID CHANGED ?
- 162. THE WAY WEWORK DID CHANGED ?
- 163. THE WAY WEWORK DID CHANGED ?
- 164.
- 165. WE NEEDED TOCHANGE THE WAY WE WORK
- 166. WE WILL CHANGE THEWAY WE WORK
- 167.
- 168. THIS IS US 300KCUSTOMERS 5K ENGINEERS 20 YEARS OLD PRODUCT COMPETITIVE MARKET
- 169. Thank you @svenpet CHANGE IS THEONLY CONSTANT MICROSERVICE TEAMS