Definition of Done Making a case for DevOps
Download as PPTX, PDF3 likes684 views
This document discusses DevOps and its core themes of culture, automation, measurement, and sharing. It emphasizes that DevOps aims to lower the risk of change, promote synergy across functions, and keep organizations competitive. Automation, infrastructure as code, automated testing, and continuous deployment are seen as enabling more time for design and repeatable results. Measurement of everything through monitoring is key for learning and feedback. Sharing goals, problems, priorities, locations, communication, codebases, responsibilities, workflows, and successes/failures fosters collaboration.
Definition of Done Making a case for DevOps
- 1. DEVOPS Adetunji Sunmonu D e f i n i t i o n o f D o n e
- 2. When is your software project done? 2
- 3. You are not paid for your code to run on machine, but in production 3 Tunji Sunmonu
- 4. 4
- 5. THEMES 5
- 7. CULTURE 7
- 8. Lowering the risk of change (from all aspects of delivery) 8
- 9. “Synergy” between different functions of business. 9
- 10. Keep the organization competitive not just keep the light on 10
- 11. There is no one right way 11
- 12. Scrum Master == DevOps Engineer? Retros == Logstash? 12
- 13. AUTOMATION 13
- 14. “Automation allows more time for Design” “Repeatable Results, Faster” 14
- 17. One Source of Truth 17
- 18. Consistency - which enables sharing and caring 18
- 20. MEASUREMENT 20
- 21. Monitoring 21
- 23. Learn from your Infrastructure. Anticipate 23
- 25. Metrics for learning and feedback. 25
- 26. SHARING 26
- 27. Shared Goal – improve reliability and speed 27
- 28. Shared Problem Space – deployment, delivery 28
- 29. Shared Priorities – what gets improved first 29
- 30. Shared Location – minimize communication effort, make it personal 30
- 31. Shared Communication – chat, wiki, mailing list 31
- 32. Shared Codebase – code and infra code 32
- 33. Shared Responsibility – fix the build, fix the deploy 33
- 34. Shared Workflow – one button deply 34
- 36. Shared Success and Failure – common experience, history 36
- 37. ANTI-PATTERN 37
- 38. 38
- 39. 39
- 40. 40
- 41. 41
- 42. 42
- 43. 43
- 44. 44
- 45. 45
- 46. The software isn’t finished until the last user is dead 46 Sidney Markowitz
- 47. References Patrick Debois - Devops with the S for sharing Matthew Skelton - What Team Structure is Right for DevOps to Flourish? 47