Integrating ITSM, Lean, and DevOps Flashcards
6 cards from real Certified Agile Service Manager practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Integrating ITSM, Lean, and DevOps flashcards as text
A company is integrating ITSM and DevOps. The development team complains that traditional ITSM change approval processes are creating significant delays in their CI/CD pipeline. Which approach best combines the governance of ITSM with the speed of DevOps?
Answer: Automating the creation of change records and pre-approving low-risk, standardized changes.
Integrating ITSM and DevOps effectively involves adapting processes, not eliminating them. Automating change record creation for every deployment and establishing pre-approved, standard changes for routine, low-risk deployments allows teams to maintain speed while ensuring governance and traceability, which is a core goal of ITSM.
In the context of integrating Lean, ITSM, and DevOps, what is the primary purpose of Value Stream Mapping (VSM)?
Answer: To visualize the flow of work, identify waste, and find opportunities for improvement.
Value Stream Mapping is a fundamental Lean technique used to analyze the end-to-end process of delivering value to a customer. It helps visualize all the steps, from request to delivery, making it possible to identify bottlenecks, delays (waste), and non-value-added activities, which is crucial for improving flow in a DevOps and ITSM context.
Which of the following is a core Lean principle that directly supports the DevOps goal of accelerating the flow of work from development to operations?
Answer: Eliminating waste, such as waiting times and partially done work.
The Lean principle of 'eliminating waste' (Muda) is central to improving workflow. In a DevOps value stream, waste includes anything that doesn't add value from the customer's perspective, such as waiting for approvals, handoffs between teams, correcting defects, and partially done work. By eliminating this waste, the overall flow of value accelerates.
An organization is adopting Agile Service Management principles. They want to ensure their ITSM processes, like incident and problem management, become more responsive. How does a combined DevOps and Lean approach contribute to this goal?
Answer: By using automation for monitoring and rapid response, and promoting cross-functional collaboration to solve problems.
DevOps emphasizes automation for rapid detection and response to incidents, aligning with ITSM goals for faster resolution. Both Lean and DevOps promote breaking down silos and fostering cross-functional collaboration, which is essential for effective problem management and learning from incidents to prevent recurrence.
What is the most significant cultural challenge organizations face when integrating the control-focused nature of traditional ITSM with the speed-focused culture of DevOps?
Answer: Resistance to change from teams accustomed to established, siloed processes.
While tool incompatibility and budget can be issues, the primary obstacle is often cultural resistance. ITSM teams may be wary of DevOps' pace, fearing a loss of control and stability, while DevOps teams may see ITSM processes as bureaucratic impediments. Overcoming this requires building a shared understanding of common goals like service quality and customer value.
An Agile Service Manager is tasked with improving the Change Enablement practice (formerly Change Management) to better support a DevOps environment. Which two aspects, derived from Agile and Lean thinking, are key to this transformation?
Answer: Shortening feedback loops and delivering value in small increments.
DevOps, inspired by Agile and Lean, thrives on rapid feedback and iterative delivery. By releasing small, incremental changes, the risk of each deployment is reduced. Short feedback loops, enabled by monitoring and testing, allow teams to quickly detect and remediate issues. This approach contrasts with traditional change management that often involves large, risky releases and lengthy approval cycles.