Firmly entrenched silos and a combative relationship between Dev and Ops is an example of:
Cultural debt---not just low trust or poor leadership---best describes the scenario of entrenched silos and combative Dev/Ops relations.
Cultural debt leads to resistance to new ways of working, lack of cooperation, and a focus on individual rather than collective success.
Why not the others?
Low trust and poor leadership are symptoms of cultural debt.
Change fatigue occurs after repeated failed initiatives; here, the core issue is cultural stasis.
Reference/Extract: ''DevOps transformation often fails without addressing cultural debt. Breaking down silos, building shared understanding, and changing incentives are essential for sustainable change.'' --- DevOps Handbook, State of DevOps Report, PeopleCert DevOps Foundation v3.6 Section 3.4
The IT department of a very large insurance company is trying to improve the collaboration and communication between development and operational teams without much success. The department has many silos that are organized by expertise and led by a different manager. The managers of each team do not seem to be particularly interested in DevOps since they have been operating this way for many years and like their silo culture.
What is this organization suffering from?
The scenario describes entrenched silos and resistance to change---managers are protective of their domains and don't see the value of DevOps.
This is a textbook example of cultural debt: the gap between the organization's current culture and the adaptive, collaborative culture needed for DevOps success.
Cultural debt, like technical debt, accumulates over time and ''must be paid back'' for transformation to succeed. It creates friction, slows delivery, and blocks cross-team collaboration.
Why not the others?
Organizational change is what's needed, not what they're suffering from.
Change fatigue arises when people are burned out by too much change, not resistance.
Low trust is a symptom, but the core problem here is ingrained culture.
Reference/Extract: ''Cultural debt is accrued when organizations fail to evolve their culture to match new ways of working, like DevOps. It manifests in resistance to collaboration, entrenched silos, and leadership unwilling to change.'' --- DevOps Handbook, Ch. 2, and PeopleCert DevOps Foundation v3.6 Syllabus Section 3.4
A major retail organization is experiencing declining sales and wants to boost its online business. Teams within Dev and Ops have been independently experimenting with DevOps practices to speed up changes to the company's website but have yet to see tangible benefits.
What can the IT management team do in this situation to achieve bottom-line benefits with DevOps?
When independent Dev and Ops teams adopt DevOps practices without coordination, results are limited.
The most important action IT management can take is to create a shared vision, goals, and incentives.
Shared goals align everyone to business outcomes, reduce conflicting priorities, and foster real collaboration.
Why not the others?
Intelligent risk taking (A) and high-trust culture (C) are important, but without a shared vision, teams won't move in the same direction.
Customer focus (D) is essential, but won't create cross-team alignment by itself.
Reference/Extract: ''Creating a shared vision and goals across Dev and Ops is critical to breaking down silos and delivering end-to-end value to the business.'' --- The Phoenix Project, Accelerate, and PeopleCert DevOps Foundation v3.6 Section 3.3
Why are Lean tools and practices critical to DevOps?
Lean tools and practices are foundational to DevOps because they help organizations systematically identify and eliminate waste, optimize value delivery, and continuously improve processes.
Lean thinking focuses on value stream mapping, reducing delays, bottlenecks, over-processing, handoffs, rework, and unnecessary tasks---core to making DevOps successful.
Option D, ''They help identify waste and assist in the creation of improvement practices,'' perfectly captures this focus.
Extract-style reference: ''Lean enables teams to identify value and non-value-added activities and to use continuous improvement techniques such as Kaizen, value stream mapping, and removing waste.'' --- DevOps Handbook PeopleCert DevOps Foundation v3.6: Lean tools like Value Stream Mapping, 5S, and Kaizen are cited as critical enablers for optimizing the flow and improving IT and business alignment.
Which of the following is NOT a characteristic of DevOps?
A fast flow of unplanned work into production is not a characteristic of DevOps. In fact, DevOps practices strive to minimize unplanned work (like emergency changes or outages) through automation, testing, collaboration, and rigorous change control. The other options---ensuring organizational success, working toward a common goal, and world-class stability/reliability---are all key DevOps characteristics. Reference: DevOps Foundation v3.6 syllabus section 1.4; State of DevOps Report.
Cynthia Bell
19 days agoRachel Campbell
29 days agoThomas Carter
2 months agoCynthia Jones
2 months agoMichael Baker
3 months agoCynthia Wilson
3 months agoRyan Carter
4 months agoKaren Hill
3 months agoDeborah Lewis
3 months agoMelissa Walker
3 months agoMelissa Reed
3 months agoJessica Roberts
3 months agoRosalind
4 months agoLaine
5 months agoHollis
5 months agoJerlene
5 months agoFrederica
5 months agoJamal
6 months agoGlory
6 months agoJoana
6 months agoMarya
6 months agoDaren
7 months agoDavida
7 months agoShawnda
7 months agoStanford
7 months agoJesus
8 months agoYaeko
8 months agoChristene
8 months agoCarole
8 months agoJolanda
9 months agoBarney
9 months agoChandra
9 months agoLili
9 months agoMarylin
9 months agoBettina
10 months agoShelia
10 months agoBrandon
10 months agoCarmela
10 months agoRikki
11 months agoPamella
11 months agoMonte
11 months agoCecilia
11 months agoUlysses
11 months agoKeneth
11 months agoMary
1 year agoThora
1 year agoCarla
1 year ago