Impact of DevOps on governance
Download as PPTX, PDF1 like686 views
The document discusses the impact of DevOps on governance, highlighting challenges such as incremental approvals, mixed funding, and undefined results. It emphasizes the need for frequent, smaller changes and practices like peer reviews and automation. The focus is on transforming the business model and optimizing project governance for better value realization.
Impact of DevOps on governance
- 1. The impact of DevOps on governance
- 2. What if I told you…
- 5. 10,000 pushes to Prod a day
- 6. Challenges • product not project: feature based • incremental approval and funding • mixed capex and opex • nimble stage gates • undefined results: time and costs are fixed, scope is variable • multiple risk profiles • segregation of duty • commodity services • deploying smaller changes more frequently • peer review instead of external change approvals • minimal documentation • informal handoffs • access to logs and data • automation of production deployments • continuous testing • cloud
- 7. Controls: Get out of the way
- 8. Controls • parallelise • iterate • shift left • bake it in • challenge ceremony • optimise • eliminate • justify Project Control Go live Cost of delay Build Go live Project
- 9. Governance • Business cases • Realisation of value • Measurement • Engagement • Underwriting • Operating model
Editor's Notes
- #2: © Two Hills Ltd 2016 Created and published by Two Hills letterbox@twohills.co.nz www.twohills.co.nz This work by Two Hills Ltd is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Content must be attributed to "Two Hills Ltd www.twohills.co.nz". Images copyright CanStockPhoto.com unless otherwise stated
- #3: The bizarre world of DevOps Image copyright CanStockPhoto.com
- #4: Development owns as much of the lifecycle as possible, possibly including deployment to production. Toolsmiths and boilermen Rugged DevOps Operations move to more of a supervisory capability, setting policy and controls and overseeing environments, with execution of many operational tasks performed by Development teams. Operationally ready code
- #5: Automation is key to increasing deployment speed and frequency without sacrificing quality: automation of merge, build, test, approve, release, deploy. The extreme ideal is a "deploy" button which allows a developer to deploy through all environments, tests, and controls into production without intervention.
- #6: Automation Unicorns Continuous Deployment means code is released at any time, unconstrained by windows or schedules.
- #8: Trust Empowerment Change facilitation Improved flow Let them do their own risk assessment
- #11: Transformation Business Suppliers Customers Regulators