DevOps Iceberg agileindiaconf2016
•
3 likes•1,145 views
This document discusses the critical success factors for DevOps that lie below the visible surface. It argues that only 10% of DevOps success relates to visible processes, tools and artifacts, while 90% depends on invisible soft aspects like mindset, culture, values and behaviors. These include self-organizing cross-functional teams, servant leadership that empowers teams, and a focus on collaboration over individual functions. The document uses examples and models to illustrate how adopting these softer aspects can help break down barriers between functions and enable horizontal information flow needed for DevOps.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to DevOps Iceberg agileindiaconf2016
Similar to DevOps Iceberg agileindiaconf2016 (20)
More from Vishweshwar Hegde
More from Vishweshwar Hegde (18)
Recently uploaded
Recently uploaded (20)
DevOps Iceberg agileindiaconf2016
- 1. The Invisible, Intangible bottom of the DevOps Iceberg Agile India Conference Bangalore, Mar 2016 Vishu Hegde vishu@pm-powerconsulting.com
- 2. The DevOps cycle 2 Image source : blogs.msdn.com People Process Technology
- 3. What moves the iceberg? Wind Currents 10% Visible part 90% Invisible part 3
- 4. What makes DevOps successful? Hard aspects Soft aspects 10% Visible part 90% Invisible part Processes Ceremonies Artifacts Tools ………. ………. Values Principles Self-organizing teams Cross-functional collaboration Communication Shared-Vision, Motivation4
- 5. DevOps Challenge : Horizontal Integration 5 CIO Head Apps Head I&O Biz Prod Mgmt Dev Test Infra Ops Prod Mgmt Cust Organizations are designed vertically, but work flows horizontally and Customers experience the organization horizontally
- 6. DevOps Critical Success Factors 6 CIO Head Apps Head I&O Biz Prod Mgmt Dev Test Infra Ops Prod Mgmt CustInfra Scrum Kanban Self-organizing Teams Servant Leadership Cross-Functional Collaboration DevOps
- 8. When there is no cross-functional collaboration 8 http://www.energizedwork.com/weblog/2007/11/theres-a-hole-in-your-side-of-the-boat
- 9. Challenge of Horizontal Integration: Cross-functional Alignment How to make everybody see the ‘full elephant’? 9
- 10. ‘Seeing the full elephant’ example 10
- 11. Before ….. After Green – What’s going well Amber – What needs to improve/change Yellow – Action items 11
- 12. Cross-Functional Collaboration: A Critical Success Factor for DevOps No single Function creates business value for Customer Business value is created only by the contribution of all the Functions 12 PM BA Ux Dev QA Infra Ops QA Dev BA DBA Infra Ops Goal Biz Value Cooperation to Collaboration Industrial-era thinking Knowledge-era thinking
- 13. Making of Cross-Functional Collaborating Teams – Sandwich Approach Top-down Enablement to work in cross-functional teams Goal alignment across Functions (Strategy, Roadmaps, Priorities,…) Common Protocols (Processes & Tools) across Functions Push factor Bottom-up Self-organizing cross-functional team Pull factor 13
- 15. When teams are not self-organizing 15
- 16. What makes self-organizing teams? Internal factors (team level): Self-managed individuals – taking Responsibility Mutual Respect in team members, Trust Appreciating differences, diversity External factors (outside of team) Facilitative Leadership than command-control leadership Ask (70%) more than tell (30%) Empowerment of team Facilitating shared vision in the team Team rewards & recognitions 16
- 17. Making of Self-organizing Teams ‘Letting go’ by the manager(s) and ‘Taking up’ by the team should happen synchronously 17 Command-control Self-organizing When teams become self-organizing, Managers need new job Coaching/mentoring, developing people Strategic organizational initiatives, improvements – Enterprise Agility
- 20. Leadership 20 Command-Control to Facilitative leadership Change in Governance & Measurements Structural changes Change in people practices Leadership: Can make or break self-organizing teams and cross-functional collaboration
- 21. DevOps Transforamtion 10% Visible part 90% Invisible part 21 Mindset Change Thinking Change Behavior Change Usage of practices, tools in right spirit CultureChange
- 22. 22 Agile values and principles Transformation Dynamics Result pyramid - Tom Smith and Roger Connors In order to transform, break the cycle 10% Visible part 90% Invisible part
- 23. The invisible, intangible bottom of DevOps iceberg 23 Questions? Mindset > Toolset Self-organizing teams Cross-functional collaboration Servant Leadership
- 24. Thank You 24