Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Martin woodward - DevOps Habits - Part 2 of 4
- 1. Our Definition of Done
- 2. Collect data broadly (but carefully) Application Insights Analytics (Project Kusto) for • text search and queries over structured and semi-structured data • high volume ingestion • fast queries over very large data sets
- 3. But measure what’s important (KPI’s) • Original estimate • Completed hours • Lines of Code • Team capacity • Team burndown • Team velocity • # of bugs found Things we don’t watch• Acquisition • Engagement • Satisfaction • Churn • Feature Usage Usage • Time to Detect • Time to Communicate • Time to Mitigate • Customer Impact • Incident Prevention Items • Aging Live Site Problems • SLA per Customer • Customer Support Metrics Live Site Health • Time to Build • Time to Self Test • Time to Deploy • Time to Learn Velocity
- 4. Be Customer Obsessed Iterate over Pain Production First Mindset Team Autonomy + Enterprise Alignment Shift Left Quality Infrastructure as Flexible Resource Don’t over-think, learn how to fail fast Habits we’ve learned so far at Microsoft
- 5. Find what hurts and keep doing it a bit better Iterate over Pain Find the part of your process in getting value to customers that slows you down or hurts the most. Make it incrementally better each sprint. Re-evaluate and improve the next most painful. “ ”
- 6. Security Mindset ď‚„ Double blind test ď‚„ Full disclosure at or near end vs. ď‚„ Share tactics & lessons learned ď‚„ Continued evolution Assume Breach - Use War Games to the learn attacks and practice response
- 7. Feature Flags • All code is deployed, but feature flags control exposure • Reduces integration debt • Flags provide runtime control down to individual user • Users can be added or removed with no redeployment • Mechanism for progressive experimentation & refinement • Enables dark launch
- 8. Awesome! What could go wrong? • Features to be revealed at big event • We turned features on globally just before the keynote... • It didn’t go well.
- 9. Be Customer Obsessed Iterate over Pain Production First Mindset Team Autonomy + Enterprise Alignment Shift Left Quality Infrastructure as Flexible Resource Don’t over-think, learn how to fail fast Habits we’ve learned so far at Microsoft
Editor's Notes
- We’re a long way on the journey, and still have a lot to learn. But here are 5 habbits that we’ve learned so far. Customer focussed, Team Autonomy and Shifting Left are basically second decade agile DevOps brings Product First Mindset and Infrastructure as a Flexible Resource into play Note that they all result in some inter-related processes. We’ve got to where we are now over a long time, and it’s been a very iterative process. But we’re not done – we’ve still lots to learn.
- DevOps is the union of people, process and products to enable the continuous delivery of value to your end customers
- We’re a long way on the journey, and still have a lot to learn. But here are 5 habbits that we’ve learned so far. Customer focussed, Team Autonomy and Shifting Left are basically second decade agile DevOps brings Product First Mindset and Infrastructure as a Flexible Resource into play Note that they all result in some inter-related processes. We’ve got to where we are now over a long time, and it’s been a very iterative process. But we’re not done – we’ve still lots to learn.