Kanban, Lean, and DevOps Flashcards
7 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 7 Kanban, Lean, and DevOps flashcards as text
In DevOps, 'shift left' testing means:
Answer: Moving testing activities earlier in the development lifecycle
Shifting left moves testing closer to development so defects are caught earlier when they are cheaper and easier to fix.
Which Lean concept describes matching the pace of production to the rate of customer demand?
Answer: Takt time
Takt time is the available production time divided by customer demand rate, setting the rhythm for delivering value.
A Kanban board shows items consistently piling up in the 'Testing' column. Using a systems thinking approach, what is the most appropriate first action?
Answer: Analyze why testing is slower than upstream stages and address the constraint
The Theory of Constraints approach requires identifying and addressing the root cause of the bottleneck before making other changes.
In the context of Agile Service Management, how does DevOps complement ITSM processes?
Answer: By accelerating delivery while maintaining governance and stability
DevOps enhances ITSM by enabling faster, automated delivery while preserving the governance that ITSM processes provide.
Which practice in DevOps provides the ability to quickly revert a deployment if a critical defect is detected?
Answer: Blue-green deployment
Blue-green deployments maintain two identical production environments so traffic can instantly switch back to the stable version.
In Lean, the '5 Whys' technique is primarily used to:
Answer: Identify the root cause of a problem
The 5 Whys iteratively asks 'why' to drill past symptoms and uncover the underlying root cause of a problem.
What is the key difference between 'Continuous Delivery' and 'Continuous Deployment' in DevOps?
Answer: Continuous Delivery still requires manual approval before production release; Continuous Deployment releases automatically
Continuous Delivery ensures software is always release-ready but uses a manual gate, while Continuous Deployment pushes every passing build straight to production.