1. Dev vs Ops => DevOps
Mercury @DevOps
an intimate understanding between the development and operations teams
2. History
• 2007 | Belgium | Patrick Debois
• 2008 | Toronto | Agile Infrastructure | Agile Conference | Andrew Shafer
• 2009 | San Jose | 10+ Deploys per day Flickr | Velocity | John Allspaw, Paul Hammond
• 2009 | Belgium | DevOpsDays | Patrick Debois, John Willis & others | #DevOps born
• 2010 | US | DevOpsDays | Damon Edwards, Andrew Shafer, John Willis
• 2011 | Gartner Prediction | Cameron Haight | Prediction was DevOps embrace 20% by 2015
• 2012 | DevOpsDays | Bangalore->Boston | Become must-attend events
• 2013 | DevOps Books | The Phoenix Project, Lean Start-up, Continuous Delivery
• 2014 | Bnz DevOps | ATM & Windows Team | Automated Deployments with OctopusDeploy
• 2015 | DevOps become mainstream | State of DevOps Report by Puppet Labs
• 2016 | Bnz DevOpsDays | Bnz DevOps Community
3. DevOps movement
• From practitioners, by practitioners
• Not a product, specification, job title
• An experience-based movement
• Decentralized and open to all
• Not usually driven from the top down
• Improves organization efficiency and effectiveness
4. Silos are #1 enemy of throughput and quality
-Damon Edwards
5. Principles and Practices
• CALMS – Culture, Automation, Lean, Metrics, Share
• Understand the flow
• Reduce cycle time & waste (Lean)
• Work in small batches
• Limit the hands-off
• Test early, often, faster feedback
• Monitor the environment, use tools for APM, collect and understand
metric
• ........
6.
7. The DevOps journey began when Nordstrom stopped optimizing for
cost, and instead started optimizing for delivery speed
-Courtney Kissler
8. High performance is achievable no matter if your apps are
greenfield, brownfield or legacy
- 2015 State of DevOps report
9. Bnz DevOpsDays - Next
Monday 29th August 2016
HQ, Wellington
For more details follows us on @DevOps community
10. Follow us on @DevOps
(mercury community)
bnzdevops@bnz.onmicrosoft.com