Why your DevOps Culture Transformation Failed?

Today, fewer people talk about DevOps's culture and people. The move to DevOps involves a review of the systems, technology, responsibilities, culture and even behaviours to ensure teams can work together effectively for a shared goal, but one person must be a leader and lead the effort. Your organization's management style has a direct influence on how organizations respond to these significant changes, so if you genuinely strive to streamline all dimensions of your organization with DevOps, you must upgrade the way your DevOps team's culture and mindset. So, this talk will elaborate on how strong DevOps culture and people are to measure the success of DevOps transformation in an organization. This talk also will highlight the common challenges in DevOps transformation and how you can solve them, which you may refer to my article in the medium platform, https://shorturl.at/knvx0

Transcript

1. TRACK: CULTURAL TRANSFORMATION NOVEMBER 12, 2020 Najib Radzuan Why your DevOps Culture Transformation Failed?
2. TRACK: CULTURAL TRANSFORMATION About Me • 36 Year Old • Married with 3 kids. • Graduated with a Bachelor’s Degree in Electrical Engineering(Instrumentation) • He was a Software Developer / Programmer • He became IT Operations / Software Architecture • Now full-time DevOps Consultant / DevOps Ambassador • I’m love to help organization to do DevOps adoption and transformation. • Created DevOps4Me Global to advocate for DevOps Adoption/Transformation. • Mentoring new Human of DevOps - DevOps & DevSecOps. Najib Radzuan
3. TRACK: CULTURAL TRANSFORMATION 1. State of DevOps 2021 Report a. DevOps Culture Transformation Blocker 2. Why DevOps Culture Transformation Failed? a. The Key Challenges b. Use-Cases c. How can you solve it? 3. Summary Agenda
4. TRACK: CULTURAL TRANSFORMATION Low-Level Evolution Organization Mid-Level Evolution Organization “Challenges related to culture are most critical among low-evolution organizations” 21% Discourage Take Risk 20% Unclear Responsibilities 18% Fast Flow Not Priority 17% Insufficient Feedback Loop Culture Blocker
5. TRACK: CULTURAL TRANSFORMATION Dysfunctional Culture Accountability Resistance to Change Lack of Investment Lack of Planning Why is DevOps Transformation does failed?
6. TRACK: CULTURAL TRANSFORMATION - Culture is very hard to define and seems very hard to change. It’s the values and behaviors of the people in an organization and needs to be addressed at this human level; it requires we talk about emotions and feelings, not just bits and bytes. - Often time we have situation where people are punished for raising problems or knowledge and information is hidden which will stop people from sharing and collaborating. - Some of organization also practicing where failure is seen to be something to be avoided, people will try and cover up mistakes rather than learn from them and they will be afraid of trying new things. Dysfunctional Culture
7. TRACK: CULTURAL TRANSFORMATION
8. TRACK: CULTURAL TRANSFORMATION - Create Culture Function According to DevOps Principles - Build the trust by face-to-face collaboration rather than using email or video conferencing as such roadshow/knowledge sharing session if the teams are dispersed. - The goal is to meet everyone at least once in order to build relationships and streamline goals. - DevOps Knowledge Base & FAQ - The visibility and easy access to the information that motivates them to search and read it by themselves and even contribute. This kind of information can be held in collaborative platforms such as Atlassian Confluence, Microsoft Teams, & Slack. - Applying Westrum Organizational Culture Practices: Pathology, Bureaucratic & Generative - Create a generative culture that encourage data stream and trust:Performance Oriented i. High Cooperative ii. Messenger Trained iii. Risk are shared iv. Bridging encouraged v. Failure lead to inquiries vi. Novelty implemented-Continuous Learning Dysfunctional Culture - Solve It!
9. TRACK: CULTURAL TRANSFORMATION • The development team is focused on change and the IT Ops team on stability. As a result, the sense of accountability is diluted, and instead of increasing deployment velocity, additional bottlenecks are created. • Developers are held accountable at the heart of DevOps, but what about the responsibilities and requirements of highly trained IT Ops team whose hearts are not in development? • Additionally, often time organizations outsource work such as DevOps/QA testing or IT operations that complicated the teamwork efforts. • Significantly different geographical regions increased the challenge due to time-zone and language complications. Accountability
10. TRACK: CULTURAL TRANSFORMATION Accountability Boss: Should you raise a change request? Dev: OPS is thing of the past, I know my Application than ANYONE!. OPS: Our Devices are now 100% secure. Boss: How did you do that? OPS: I turned them all OFF
11. TRACK: CULTURAL TRANSFORMATION - Creating Cross-Team Collaboration - If development teams are conducting daily scrums as part of their agile practices, inviting IT Ops to participate can help with impediment removal related Infra/Network they facing faster. - Inviting them to sprint planning can ensure those non-functional requirements are considered in the sprint, thus streamlining the value delivery process. - Create common Communication Channels - It really help here by making it possible for collaboration to be continuous. - The “Alert/Notification” chat group or channel also needs to be properly managed, so that issues can be directed to the correct team and escalated fast using the correct action to take to solve the issue/bug. - Issue/Bug/Problem need to be visible - Making Backlog/Kanban issue visible , it trigger people to inquiry and start collaborate on the issue. Accountability - Solve It!
12. TRACK: CULTURAL TRANSFORMATION • Not many people like to change their way of working; There are neurological reason why change is so hard because your Brain is designed to stop you from changing, Change requires you to do things that are uncertain, scary or new. • Many people prefer working in silos and might not want to communicate with others and so DevOps leaders frequently face resistance in the transformation process. • Humans are fundamentally wired to resist change for evolutionary reasons. Resistance to Change
13. TRACK: CULTURAL TRANSFORMATION Resistance to Change
14. TRACK: CULTURAL TRANSFORMATION - Addressing Resistance To Change - According to DevOpsologist, Philippa Hale, we can address certain group people’s moods and emotions toward changes then we can apply different engagement strategies to approach them toward DevOps initiatives - Implement Change in several stages - Change does not occur all at once. Companies should first prepare for the change, then act on the change and develop a plan for managing it, and finally support the change and ensure that everything is going as planned. Resistance to Change - Solve It!
15. TRACK: CULTURAL TRANSFORMATION • Time & Tools: • The shift to DevOps does not happen overnight; the aim of deployment automation require suitable tooling and the discovery and elimination of bottlenecks. • Often time, DevOps doesn't get management support/time which their involvement are required to keep things moving forward. • Upskill & Knowledge: • For most companies, this is where the process goes down: a dramatic announcement like "we're shifting to DevOps" and it followed by quick expectations of advantages without ongoing engagement/investment in removing critical challenges and bottlenecks. • Often time also company seeking external/vendor to do DevOps tasks that added the complexity of the transformation process. Lack of Investment
16. TRACK: CULTURAL TRANSFORMATION Lack of Investment
17. TRACK: CULTURAL TRANSFORMATION Lack of Investment - Solve It! - Time & Tools - Not each possible tool or solution that you listed you able to apply or implement in your organization. Your budget allocation also plays a significant factor to choose your toolchain.In short, your tool of choice should consider below scenario; - Introduce Value Stream Mapping (VSM) that give management visualize high-level of benefit of we buy a tool and create new approach for our product improvement and fast delivery. - Upskill & Knowledge - Instead of hiring or ask external party to do your DevOps transformation, organization can upskill their current team/staff and bring the skill into the company and train the team in-house. Hence, this approach give them advantage of cost and time as well. To Build: When existing resources and tool can achieve your DevOps goals. Then you can use it to solve your issue and problem. It also includes your team’s capacity to maintain and support when something with built tools. To Buy: When existing resources and tool not meet your DevOps goals you set and cannot solve your issue and problem. Then you need to buy solution/tool or seek external expert for your DevOps journey.
18. TRACK: CULTURAL TRANSFORMATION - Most organizations have failed to realize that DevOps Transformation it needs to be implemented and managed as an enterprise-wide change which requires long-term planning and commitment from the top to bottom groups within the company. - Failure to invest enough time and effort upfront in planning and engagement will eventually result in issues and fragmented DevOps implementation/adoption. Lack of Planning
19. TRACK: CULTURAL TRANSFORMATION Lack of Planning
20. TRACK: CULTURAL TRANSFORMATION - Forum & Knowledge Session - Establishing forums to bring together all teams, including the IT Ops Team, QA Team, Dev Team, and Database Team, is critical for collaboration. - This ensures that everyone has a role to play and a piece of work to do. - Collaboration & Share Responsibility - Make clear your DevOps transformation goals to all levels in the company. Streamline the goals and keep them motivated lastly, appreciate the team when one job finished. - Interactions and dependencies with other teams work better when people are putting their hand up for a piece of work. Lack of Planning - Solve It!
21. TRACK: CULTURAL TRANSFORMATION - DevOps Transformation: Culture still our main blocker for low & mid-level evolution organization according to State of DevOps Report 2021. - There are main culture blocker we can highlight. - We also guide on how can we solve some of the challenges in DevOps culture transformation. Summary
22. TRACK: CULTURAL TRANSFORMATION • >> Is Culture Shift/Change is a requirement? OR It’s just result of doing DevOps? << STOP Thinking, START Doing!
23. TRACK: CULTURAL TRANSFORMATION Thank you for your passion devops4me @devops4me @najibradzuan blog.devops4me.com