Certified Agile Service Manager Integrating ITSM, Lean, and DevOps 3 — Questions and Answers
Question 1: A company practicing DevOps implements automated canary deployments. How does this align with Lean thinking?
- It eliminates the need for incident management
- It reduces batch size and limits exposure risk during releases (Correct answer)
- It replaces the change advisory board permanently
- It automates customer feedback collection
Correct answer: It reduces batch size and limits exposure risk during releases
Canary deployments release changes to a small subset of users first, embodying Lean's principle of small batch sizes to reduce risk and enable fast feedback.
Question 2: In ITSM, the 'three ways' of DevOps — flow, feedback, and continual learning — most closely map to which ITIL guiding principle?
- Focus on value
- Think and work holistically
- Progress iteratively with feedback (Correct answer)
- Keep it simple and practical
Correct answer: Progress iteratively with feedback
The three ways emphasize iterative delivery, fast feedback loops, and learning from outcomes, which aligns directly with 'progress iteratively with feedback.'
Question 3: Which scenario best illustrates the integration of Lean's 'pull system' with ITSM service request management?
- Automatically provisioning resources when a service request is submitted
- Publishing a service catalog with pre-approved items for self-service consumption (Correct answer)
- Requiring all service requests to be approved by a change board
- Scheduling service requests based on predicted future demand
Correct answer: Publishing a service catalog with pre-approved items for self-service consumption
A self-service catalog where users pull what they need on demand mirrors Lean's pull system, preventing overproduction of services or resources.
Question 4: DevOps metrics such as deployment frequency, lead time for changes, MTTR, and change failure rate are collectively known as:
- Agile velocity metrics
- DORA metrics (Correct answer)
- ITSM KPIs
- Lean flow indicators
Correct answer: DORA metrics
DORA (DevOps Research and Assessment) metrics are the four key measures used to assess DevOps performance and software delivery capability.
Question 5: An ITSM team adopts the Lean concept of 'andon' — stopping work when a defect is detected. In a DevOps pipeline, this is best implemented as:
- A weekly defect review meeting
- Automated pipeline gates that halt deployments when tests fail (Correct answer)
- A manual sign-off step before each production release
- A change freeze during peak usage periods
Correct answer: Automated pipeline gates that halt deployments when tests fail
Automated pipeline gates that stop deployment on test failure replicate the andon principle of halting the line to prevent defects from progressing downstream.
Question 6: Which organizational structure best supports the integration of ITSM, Lean, and DevOps by breaking down silos between development and operations?
- Functional hierarchy with separate dev and ops departments
- Matrix organization with shared resource pools
- Cross-functional product teams with end-to-end ownership (Correct answer)
- Center of excellence model with centralized ITSM governance
Correct answer: Cross-functional product teams with end-to-end ownership
Cross-functional product teams with end-to-end ownership embody the DevOps 'you build it, you run it' principle while enabling Lean flow across the full value stream.
Question 7: In a Lean-ITSM context, 'genchi genbutsu' (go and see) is most analogous to which service management practice?
- Reviewing dashboards for incident trends
- Conducting on-site observation during a service review (Correct answer)
- Escalating unresolved incidents to senior management
- Running tabletop disaster recovery exercises
Correct answer: Conducting on-site observation during a service review
Genchi genbutsu means going to the actual place of work to observe reality firsthand, which mirrors on-site service observation rather than relying on secondhand reports.
A company practicing DevOps implements automated canary deployments.
How does this align with Lean thinking?