Top 5 Ways to Fail at DevOps
0 likes32 views
The document discusses common pitfalls in DevOps practices, emphasizing that treating DevOps as a cost-cutting initiative and failing to transform culture and processes can lead to failure. Key failure points include upgrading tools without changing practices and vendor-driven transformations lacking cultural alignment. It advocates for co-location of teams and continuous improvement for successful DevOps implementation.
Top 5 Ways to Fail at DevOps
- 1. WAYS TO AT DEVOPS DevOpsDays Toronto– IgniteTalk @FawzyManaa @devopscouts Fawzy Manaa DevOps Practice - May 2017
- 2. Top Ways to Fail at DevOps -‐ Fawzy Manaa 2 WAYS TO FAIL AT DEVOPS In the Spirit of Continuous Improvement… • The case of most business transformations– “Easy” to conceptualize, “hard” to get right… • Reality is full of…
- 3. Top Ways to Fail at DevOps -‐ Fawzy Manaa 3 WAYS TO FAIL AT DEVOPS Approach: Sharing is Caring • Collection of personal experiences • Internal survey to colleagues • Just launched – http://devoops.fail Yep, you read that right
- 4. Top Ways to Fail at DevOps -‐ Fawzy Manaa 4 WAYS TO FAIL AT DEVOPS #5 – Using DevOps as a Cost-cutting initiative
- 5. Top Ways to Fail at DevOps -‐ Fawzy Manaa 5 WAYS TO FAIL AT DEVOPS #5 – Using DevOps as a Cost-cutting initiative - What? • Better?Faster? Cheaper? • It goes way back…
- 6. Top Ways to Fail at DevOps -‐ Fawzy Manaa 6 WAYS TO FAIL AT DEVOPS #5 – Using DevOps as a Cost-cutting initiative – What Now? • Faster? Yes, but practices should be pilot-ed in dev and make their way to production • Better?Yes, but norms take time to mature • Cheaper? Also yes, but NOT in the short term. Investment takestime to pay off in formof cost saving
- 7. Top Ways to Fail at DevOps -‐ Fawzy Manaa 7 WAYS TO FAIL AT DEVOPS #4 – ‘No Transformation’ Transformation Development Operations DevOps
- 8. Top Ways to Fail at DevOps -‐ Fawzy Manaa 8 WAYS TO FAIL AT DEVOPS #4 – ‘No Transformation’ Transformation – What? • Many of the innovation programs and digital labs that start silo-ed, continue being silo-ed forever • “They don’t want to change”… So, we pretend like they don’t exist… • Even more devastating in long run - the anti-DevOps
- 9. Top Ways to Fail at DevOps -‐ Fawzy Manaa 9 WAYS TO FAIL AT DEVOPS #4 – ‘No Transformation’ Transformation – Now What? http://collaborativejourneys.com/picture-‐collaboration-‐illustrated-‐guide-‐working-‐ together-‐solve-‐problems/
- 10. Top Ways to Fail at DevOps -‐ Fawzy Manaa 10 WAYS TO FAIL AT DEVOPS #3 – Upgrading Tools, but not Practices
- 11. Top Ways to Fail at DevOps -‐ Fawzy Manaa 11 WAYS TO FAIL AT DEVOPS #3 – Upgrading Tools, but not Practices – What? • New technology is created with a new philosophy in mind; using new technology in the same old fashioned way is counter-productive: • UpgradingCI server… but still having a centralbuildteam to run builds/deployments • Being in the cloud…but still having static environments
- 12. Top Ways to Fail at DevOps -‐ Fawzy Manaa 12 WAYS TO FAIL AT DEVOPS #3 – Upgrading Tools, but not Practices – Now What? • Software upgrade programs shouldn’t just be about replacing one tool with another • Focusing on using tools the ‘right’ way is more effective than focusing on upgrading to the ‘right’ tools • Applicable process adjustments and the appropriate training to end users must always be done
- 13. Top Ways to Fail at DevOps -‐ Fawzy Manaa 13 WAYS TO FAIL AT DEVOPS #2 – Vendor-Driven Transformation
- 14. Top Ways to Fail at DevOps -‐ Fawzy Manaa 14 WAYS TO FAIL AT DEVOPS #2 – Vendor-Driven Transformation– What? • The troublewith SoftwareVendor-DrivenTransformation: • Often, no correspondingcultural/processtransformation • Often times, implementationbecomesmore complexthan initiallyexpectedanyways - Customizations • Takes away abilityto make favourablefuturechoices– tight couplingvs. plug-and-play
- 15. Top Ways to Fail at DevOps -‐ Fawzy Manaa 15 WAYS TO FAIL AT DEVOPS #2 – Vendor-Driven Transformation– Now What? • No DevOps in a box, not really • No one softwarevendor has all the answers • Not all answers involve code • Best of breed adoption is “almost always” better than coupling to one ecosystem
- 16. Top Ways to Fail at DevOps -‐ Fawzy Manaa 16 WAYS TO FAIL AT DEVOPS #1 – Isolating Dev, QA, and Ops Physically
- 17. Top Ways to Fail at DevOps -‐ Fawzy Manaa 17 WAYS TO FAIL AT DEVOPS #1 – Isolating Dev, QA, and Ops Physically – What? • Many organizations still treat QA and Ops folks as back office people • Others put unnecessary barriers in the face of communication and cross team collaboration • QA/ Ops are completely outsourced/ offshored/ silo- ed/ not allowed to freely communicate, …
- 18. Top Ways to Fail at DevOps -‐ Fawzy Manaa 18 WAYS TO FAIL AT DEVOPS #1 – Isolating Dev, QA, and Ops Physically – Now What? • Co-locate people where you can –> Trust + Norms • If that cannot happen due to good reasons, then: • No double standards in work space features • Ensure to compensate for lack of face-to-face through other means: • Video Conferencing • Team member rotation • …
- 19. Top Ways to Fail at DevOps -‐ Fawzy Manaa 19 WAYS TO FAIL AT DEVOPS Last Words It will make you better. It will inspire others. #ContinuousImprovement
- 20. Top Ways to Fail at DevOps -‐ Fawzy Manaa 20 WAYS TO FAIL AT DEVOPS Get in Touch Share your top ways to fail at DevOps on http://devoops.fail Find me at Deloitteboothor shoot me an email fmanaa@deloitte.ca Followme on social media • @FawzyManaa • @devopscouts