How to become a great DevOps Leader, an ITSM Academy Webinar
3 likes291 views
The document discusses the role of a DevOps leader in driving transformational change within organizations by optimizing software delivery through cultural, process, and technological improvements. It outlines key attributes and responsibilities of DevOps leaders, emphasizing the importance of servant and transformational leadership styles in supporting team performance and continuous improvement. A comprehensive approach is suggested, involving phases of engagement, experimentation, and scaling, along with methods such as value stream mapping to enhance overall workflow efficiency.
How to become a great DevOps Leader, an ITSM Academy Webinar
- 1. HOW TO BE A GREAT DEVOPS LEADER 1 Mustafa Kapadia IBM, Global Business Consulting
- 2. • What is DevOps? • Leadership Skills • Building A Vision • Typical Transformation Journey • Rules Of The Road 2
- 3. What Is DevOps 3 Time To Market Idea Customer Deploy Get Feedback Feature / Bug Fix / Enhancement Optimize the flow of work across your SDLC so that you can 1. Bring ideas to market faster and 2. Be more responsive to your customers
- 4. Key difference between Traditional & DevOps software delivery models Key Driver Cost Flow (Time) Organization Skill Centric Silos Autonomous Teams Batch Size Large Micro (MVP) Scheduling Complex, Time Consuming Decentralized Release High Risk Event Non Event Culture “I did my job” “Its ready to deploy” Timeliness 40% Large Projects Are Late Deliver At Business Cadence Features Upto 40% Never Used* Deliver Only What Is Needed & Iterate Success Cost Business KPIs KeyCharacteristicsImpact Traditional IT DevOps *Standish Group, Feature Usability Study 4
- 5. Optimizing the flow of work requires changes to people, process, and technology Key Building Blocks People&Process (NewWaysOfWorking) Technology Speed As A New Metric Small Batches Autonomous Teams Automate Flexible Infrastructure Velocity impacts both cost & quality Create MVP, continuously test, and constantly iterate Cross functional, co-located, dedicated, product focused teams + support Push button code deploy across delivery pipeline – build, test, deploy, rollback, monitoring etc. Provision a full stack environment on demand that looks just like production 5
- 6. 6
- 7. A DevOps Leader Is a tactical or strategic individual who helps design, influence, implement or motivate the cultural transformation proven to be a critical success factor in DevOps adoption Understands the human dynamics of cultural change and is equipped with practices, methods and tools to engage people across the DevOps spectrum Embraces systems thinking, agility, lean principles and the flow of the value stream from idea to realization Everyone is a leader! 7
- 8. • Environment Management & Configuration • Release & Deploy • Testing • API • MicroServices • Agile • Builds a vision • Challenges Teams Status Quo • Inquisitive • Inspires pride in being part of the team • Cares about individuals • Acknowledges improvements • Celebrates success 8
- 9. Servant leaders and transformational leaders differ in their focus Servant leaders focus on their followers' development and performance Transformational leaders focus on getting followers to identify with the organization and engage in support of organizational objectives 9 DevOps Leaders Are Transformational
- 10. 10 A transformational leader's influence is seen in their support of their teams' work, both in technical practices and in the teams' product management capabilities. The positive (or negative) influence of leadership flows all the way through to IT performance and organizational performance. Source: 2017 State of DevOps Report https://puppet.com/resources/whitepaper/state-of-devops-report
- 11. 11 https://puppet.com/resources/whitepaper/state-of-devops-report Source: 2017 State of DevOps Report (Puppet Labs/DORA https://puppet.com/resources/whitepaper/state-of-devops-report
- 12. 12
- 13. • It is a time diagnostic of your software delivery lifecycle • A flow based representation of how end to end work is currently done • VSM is a tool that is used to evaluate processes to identify bottlenecks, waste, and ultimately improvement opportunities Value Stream Mapping (VSM) 13
- 14. • End to end map of the current “flow of value” is usually not available within the enterprise • Current metrics track cost and capacity, but not impact of time • Most effective Lean method to identify waste • Creates a common language when completed • Provides a framework for future state design 14
- 15. Small Project ProductionDeploy Get Feedback 90 days 20 days (Agile) 70 days Development Build QA SIT UAT Prod Developer Build Engineer QA Team Integration Tester User/Tester Operations Tasks Artifacts 2 - 5 days 2 - 5 days 10 – 12 days 2 - 5 days Bottlenecks Months 15
- 16. You never get to a stable future state – you have to keep reiterating (continuous improvement) 16
- 17. 17
- 18. Phase 1: Engage the Team Phase 2: Invest and Experiment Phase 3: Refine and Scale • Create an Application Transformation team • Build a customized transformation plan • Build capabilities • Pilot, experiment and learn • Spread change to other parts of the team • Continuous improvement Move from resistance to openness / commitment Move from Fear to Courage, Self Sustaining Experiment with purpose GoalBehaviorsTime 2 -3 Weeks VariesVaries 18
- 19. Phase 1: Engage the Team • Create a transformation Team • Develop initial Value Stream Map • Define what best looks like • Determine Transformation Plan • Agree on Metrics Phase 2: Invest and Experiment • Mobilize Technology Capability Teams • Train team • Pilot new operating model • Prepare for Failure • Track Metrics • Codify new ways of working- • Update Value Stream Map • Identify new areas for improvement • Repeat Phase 2 • Share / Experiences, Celebrate Success • Track Metrics Phase 3: Refine and Scale 19
- 20. Goal New Technology Capability Teams Transformation Adoption Team Build new technology capabilities Assist applications teams adopt new capabilities Environments Configuration (Cloud) Build / Deploy / Release Automation Test Automation API / MicroServices Add (as needed) Key Responsibilities • Design and Build new technology capabilities • Determine the right tooling • Assists Application teams during transformation • Domain experts that SMEs can call on • Transition new capabilities to a support organization / support it themselves • Guide the team through the 3 Phases (coaching) • Assist Adoption on the new capabilities • Keeping the change on track • Train Application Teams • Conduct Value Stream Mapping workshops Technical Domains 20
- 21. 21
- 22. • Pick the right applications to transform • Perform a value stream to understand where waste is • Prioritize bottlenecks, build a roadmap • Build a business case • Attack one bottleneck at a time • Restructure the work for better flow 22
- 23. • Organize teams around value • Create squads • Make sure information is created / consumed in real time • Create a change management plan • Use time as a key performance metric • And don’t forget about the Tools 23
- 24. 24
- 25. Mustafa Kapadia Devops Consulting Service Line Leader Mobile: (623) 202 8767 Email: [email protected] Sign Up For My Monthly Newsletter – Digital Top 5 25