Top 5 Challenges in Scaling DevOps in Brownfield Environments
2 likes613 views
The document discusses the challenges of scaling DevOps in brownfield environments, emphasizing the importance of cultural norms and technology practices that enhance the flow of work while ensuring reliability and security. It outlines five key challenges, including optimizing deployment pipelines, bridging legacy systems with modern environments, and aligning business objectives with development processes. The overall goal of enterprise DevOps is to create a culture of continuous improvement and efficiency in delivery for better business outcomes.
Top 5 Challenges in Scaling DevOps in Brownfield Environments
- 1. Top 5 Challenges in Scaling DevOps for Brownfield Environments Banish the barriers. Escape the silos..
- 2. Meet the Speakers Gary Gruver Author and DevOps Consultant @GRUVERGary Mark Levy DevOps Evangelist Micro Focus @markorinlevy
- 3. What is DevOps? This is my personal definition: I would define DevOps by the outcomes. In my mind, DevOps is those set of cultural norms and technology practices that enable the fast flow of planned work from, among others, development, through tests into operations while preserving world class reliability, operation and security. DevOps is not about what you do, but what your outcomes are. So many things that we associate with DevOps fits underneath this very broad umbrella of beliefs and practices—which of course, communication and culture are part of them. “ ”Gene Kim
- 4. vv Original DevOps principles were developed by digital disruptors in Silicon Valley
- 5. Enterprise DevOps Same principles, whole new challenge.
- 6. Enterprise DevOps Same principles, whole new challenge. DEVOPS DIGITAL DISRUPTORS ENTERPRISE DEVOPS Single application Hundreds of applications Co-located teams Geographical dispersed teams Single stack “loosely coupled” infrastructure Many environments including mainframe both “loosely” and “tightly” coupled. Minimal security and compliance risks Highly regulated and high security risks Solely agile development Multiple development methodologies A single deployment pipeline across a single application stack Multiple deployment pipelines across a vast heterogenous system Simple application architecture Complex multi-platform architecture
- 7. Document, prioritize and optimize existing deployment pipelines Seek efficiencies to deliver better business outcomes THE GOAL OF ENTERPRISE DEVOPS Make the deployment pipelines as small as possible but no smaller
- 9. Create a culture of continuous improvement
- 10. Changing the system to change the culture https://www.lean.org/LeanPost/Posting.cfm?LeanPostId=223 Challenge #1
- 11. A bad system will beat a good person every time. W.EdwardsDeming
- 12. Challenge #2 System Thinking for the Enterprise
- 13. The Deployment Pipeline PLAN BUILD TEST RELEASE MONITOR
- 14. Challenge #3 Bridging the Old with the New
- 16. Bimodal Does Not Work
- 17. Challenge #4 Prioritizing Deployment Pipeline Optimization
- 18. Mobile Apps Loosely coupled infrastructure, Cloud and IoT High growth, lots of change, needs more resources New “Core” Apps Loosely coupled infrastructure but uses mainframe for backend High growth, uses mobile apps, needs more resources Website Loosely coupled infrastructure High number of change requests daily Legacy “Core” Apps Tightly coupled infrastructure, migrating to agile, Existing large revenue stream, moderate change, high costs Back Office Apps Tightly coupled infrastructure, waterfall, mainly mainframe, Keep the lights on, low growth, low number of changes, high costs Enterprise Deployment Pipelines - Example
- 19. Challenge #5 Where to Optimize Develop, Commit & Build Release and Deploy Aligning business objectives with the software development process Functional testing, UAT, Load/Performance, Security Testing. Helping maintain peak application performance and uptime. Provision Environments Time spent waiting Wrong solution, scrap and rework Too much manual effort Too many meetings, handoffs, and failed deployments Production Incidents
- 20. • kj DevOps is a Journey Time Expectations Quick early wins Solving the hard problems • Ensure everyone understands the business objectives • Change the system to change the culture • Document, prioritize, and optimize your deployment pipelines • Seek efficiencies to deliver better business outcomes
- 21. Getting Started Enterprise DevOps microfocus.com/enterprisedevops Gary Gruver Author DevOps Consultant
- 22. Micro Focus Supports DevOps at Enterprise Scale www.microfocus.com/enterprisedevops
- 23. Thank You Mark Levy, Director of Strategy [email protected] @markorinlevy