Download as PDF, PPTX
Uploaded byThoughtworks
DevOps - Agile on Steroids by Tom Clement Oketch and Augustine Kisitu
This document discusses challenges with traditional Agile approaches and how DevOps aims to address them. It notes that while organizations may think they are Agile, problems still arise around deployment pain points, inability to adapt to change, and dissatisfied clients. DevOps focuses on automating processes, breaking down silos between teams, and continuous delivery through culture change, infrastructure automation, measurement, and information sharing. The presentation emphasizes that DevOps is not a role or certification but a relationship and approach centered on collaboration and automation.
More Related Content
![Cloud implementation by vaishali sahare [katkar]](https://cdn.slidesharecdn.com/ss_thumbnails/cloudimplementationbyvaishalisaharekatkar-170302102605-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to DevOps - Agile on Steroids by Tom Clement Oketch and Augustine Kisitu
DevOps - Agile on Steroids by Tom Clement Oketch and Augustine Kisitu
- 1. Body Level One BodyLevel Two Body Level Three Body Level Four A g i l e A f r i c a 2 0 1 5 DEVOPS - AGILE ON STEROIDS
- 2. So you thinkyouāre Agile?
- 3.
- 4.
- 5. User Stories andStory Walls
- 6.
- 7.
- 8.
- 9.
- 10. When itās timeto deployā¦
- 11. DEPLOYMENT IS APAINā¦ ā«ļøDeployment is manual. Requires context ā«ļøSnowļ¬ake servers ā«ļøDoes the code actually work? Is it not going to introduce bugs ā«ļøVersioning and rollback?
- 12.
- 13. DONāT DELIVER ONTIME ā«ļøProcess bottlenecks ā«ļøOrganisational ā«ļøTeam
- 14. Fail to adaptto changing requirements
- 15. CHANGING REQUIREMENTS ā«ļøBig DesignUp Front (BDUF) ā«ļøSpeciļ¬c implementation details ā«ļøNo process to manage changes
- 16. Not disruptive inthe market
- 17. NOT DISRUPTIVE ā«ļøNo information! ā«ļøNoinsights into customer trends ā«ļøNo opportunity to iterate over ideas
- 18.
- 19. DISSATISFIED CLIENTS ā«ļøMissed deadlines ā«ļøFirst-moveradvantage ā«ļøSoftware doesnāt meet the requirements
- 20. Where did wego wrong?
- 21.
- 22. What are theactual problems? ā«ļøCulture? ā«ļøAre we spending time doing the same thing over and over again? ā«ļøUser Feedback? ā«ļøKnowledge Silos?
- 23.
- 24. Agile is DEAD! Letāslook for another buzzword
- 25.
- 26. CULTURE ā«ļøTeamwork ā«ļøDiļ¬erent stakeholders andskill-sets, but the SAME team ā«ļøWe have the same GOAL ā«ļøThere has to be TRUST (Autonomous Teams) ā«ļøCollaboration ā«ļøCommunication ā«ļøBreak the SILOS. ā«ļøHow do we optimise communication within the organisation processes?
- 27.
- 28. AUTOMATE EVERYTHING! ā«ļøAutomated Deployment ā«ļøContinuousIntegration ā«ļøEvery change/commit should be production ready. ā«ļøAutomated testing Deployments should be boring.
- 29. AUTOMATE EVERYTHING! ā«ļøAutomated Infrastructure ā«ļøInfrastructureas code ā«ļøTreat your infrastructure as cattle and not horses (phoenix servers) If itās painful do it often
- 30.
- 31. MEASUREMENT ā«ļøMetrics ā«ļøPerformance metrics ā«ļøPage load-times ā«ļøTimeto deploy ā«ļøProcess metrics ā«ļøHow long does it take to release a feature? ā«ļøPeople metrics ā«ļøUser trends (time of greatest activity)
- 32.
- 33. SHARING ā«ļøEliminate the SPECIALIST ā«ļøSharedata in a way that makes sense to each stakeholder ā«ļøMake information visible ā«ļøBuild monitors ā«ļøMonitoring dashboards ā«ļøGraphs of usage trends etc
- 35.
- 36. DEVOPS IS NOTā¦ ā«ļø*A certiļ¬cation ā«ļø* A role ā«ļø* A set of tools ā«ļø* A prescriptive process
- 37. DEVOPS IS ā¦ ā«ļø*About the relationship between dev and ops ā«ļø* Cross-functional teams over organizational silos ā«ļø* Products not projects ā«ļø* Automation over documentation (and more automation... and more...) ā«ļø* Knowing that good software doesn't end with development / release
- 38.