This document discusses various aspects of DevOps practices and culture. It provides definitions of DevOps, discusses how organizations have implemented DevOps to significantly improve performance metrics like deployment frequency and lead times. It also addresses challenges like change approval boards, security and compliance, adopting an agile mindset, and shifting to see work as developing products rather than projects to better manage risk. Throughout, it emphasizes automating processes, reducing waste, collaborating across teams, and focusing on business outcomes over documentation and processes.
11. excella.com | @excellaco
Federal agency.
9 two-pizza teams.
Lead time for changes under 60 minutes.
Up to 40 deploys per day.
MTTR less than 3 minutes.
The Art of the
Possible.
15. excella.com | @excellaco
“We found that external approvals were
negatively correlated with lead time,
deployment frequency, and restore time,
and had no correlation with change fail
rate. In short, approval by an external
body (such as a manager or CAB)
simply doesn’t work to increase the
stability of production systems,
measured by the time to restore service
and change fail rate. However, it
certainly slows things down. It is, in fact,
worse than having no change approval
process at all.”
16. excella.com | @excellaco
1. Reduce dependencies (and complexity) in your architecture.
2. Use heavy doses of automation.
3. Improve monitoring and observability.
4. Institute effective peer reviews.
Instead of the CAB.
17. excella.com | @excellaco
Preserve emphasis on finding
issues before going to
production.
Increase emphasis on reducing
impact of finding issues after
going to production.
22. excella.com | @excellaco
Lengthens cycle times and
feedback loops.
Creates waste and inefficiency.
Involves decision-makers distant
from the actual work.
Can be circumvented.
Hurts situational awareness.
Counter-
productive
.
27. excella.com | @excellaco
Integrate non-functional requirements from the beginning with automation.
Engage security, compliance, and audit early and often.
Be transparent and share information.
Shift left.
28. excella.com | @excellaco
Because we all care about
developing and operating
reliable, secure, high
performance systems at scale.
“I care. I care a lot.
It’s kinda my thing.”
-- Leslie Knope
39. excella.com | @excellaco
16.2% of projects were deemed successful by being completed on time and
budget, with all the promised functionality.
52.7%, were over cost, over time, and/or lacking promised functionality.
31.1% failed, which means they were abandoned or cancelled.
41. excella.com | @excellaco
Perspective.
Risk of not
accomplishing the
business objective in
the quickest, most
cost-effective way
>>
Risk of not meeting
cost, schedule, and
scope objectives
42. excella.com | @excellaco
Shift from project to product.
Project Oriented Product Oriented
Budgeting
Funding of milestones predefined at project scoping. New
discretionary budget means the creation of a new project.
Funding of value streams adjusted based on business results.
New budget allocation based on demand.
Timeframes
Term of the project (e.g., one year). Defined end date. Not
focused on the maintenance/ health after the project ends.
Life cycle of the product (multiple years) includes ongoing
health/maintenance activities.
Success
Cost center approach. Measured to being on time and on
budget. Capitalization of development results in large
projects.
Profit center approach. Measured in business objectives and
outcomes met (e.g., revenue). Focus on incremental value
delivery and regular checkpoints.
Prioritization
Program and portfolio management, project plan-driven, with
a focus on requirements delivery. Projects often drive
waterfall orientation.
Roadmap and hypothesis testing-driven, with a focus on
feature and business value delivery. Products drive Agile
orientation.
Delivery
IT is a black box. Project management offices create complex
mapping and obscurity.
Direct mapping to what the business wants that enables
transparency.
From “Moving from Project to Product”, 2018 DevOps Enterprise Forum.
If you’ve heard of DevOps, you might also be familiar with this acronym – “CALMS” – coined by John Willis, Damon Edwards, and Jez Humble – members of the DevOps Illuminati. CALMS identifies five key aspects of what DevOps is all about. “Culture” is one of those key aspects. “Sharing”, which is related to culture, is also a key aspect.
I’m really talking about changing our mindset. Changing our mindset is about changing our assumptions, attitudes, values, and how we interpret different situations.
http://inutile.club/estatis/brain-transplant/img/scheme.png