Free Certified Agile Service Manager Kanban, Lean, and DevOps Questions and Answers — Questions and Answers
Question 1: A service management team is consistently overloaded with requests, leading to context switching and long lead times for resolving incidents. Which core Kanban practice would be MOST effective in addressing this specific problem?
- Implementing feedback loops
- Visualizing the workflow
- Making process policies explicit
- Limiting Work in Progress (WIP) (Correct answer)
Correct answer: Limiting Work in Progress (WIP)
Limiting Work in Progress (WIP) is a fundamental Kanban practice designed to prevent overload and reduce context switching. By setting a cap on the number of active items, the team is forced to focus on completing existing work before starting new tasks, which directly addresses the problem of being overloaded and improves flow, thereby reducing lead times.
Question 2: In a DevOps environment, which of the following BEST represents the 'Lean' principle within the CALMS framework?
- Implementing a shared code repository and automated testing to ensure seamless integration.
- Creating a culture of shared responsibility and blameless post-mortems.
- Focusing on minimizing waste by reducing batch sizes, managing queue lengths, and aiming for continuous process improvement. (Correct answer)
- Using dashboards to track metrics like deployment frequency and mean time to recovery (MTTR).
Correct answer: Focusing on minimizing waste by reducing batch sizes, managing queue lengths, and aiming for continuous process improvement.
The 'L' in the CALMS framework stands for Lean. In a DevOps context, this means applying Lean principles like eliminating waste, optimizing for flow, and continuous improvement. This includes practical steps like reducing the size of work batches, visualizing and managing queues, and removing non-value-adding activities to accelerate software delivery and improve quality.
Question 3: A service delivery organization wants to adopt a DevOps culture to improve collaboration between their development and operations teams. Which of the following is a primary goal of integrating DevOps with IT Service Management (ITSM)?
- To enforce stricter, more rigid change control processes.
- To increase the specialization and separation of duties between developers and operations staff.
- To combine the agility and speed of DevOps with the stability and control of ITSM. (Correct answer)
- To replace all ITSM processes with fully automated pipelines.
Correct answer: To combine the agility and speed of DevOps with the stability and control of ITSM.
Integrating DevOps and ITSM aims to create a balanced approach. It leverages DevOps' focus on speed, automation, and collaboration to make ITSM processes more agile and efficient, while using ITSM's structured approach to ensure stability, governance, and reliability. The goal is not to eliminate ITSM but to adapt it to a high-velocity environment.
Question 4: A team is using a Kanban board to manage service requests. They notice that tasks in the 'In Review' column are piling up, creating a significant bottleneck. According to Kanban principles, what does this bottleneck MOST likely indicate?
- The team is not creating enough new service requests.
- The 'Definition of Done' for the 'In Progress' stage is too simple.
- A systemic issue or constraint in the review process that needs to be addressed. (Correct answer)
- Team members are not respecting the established pull system.
Correct answer: A systemic issue or constraint in the review process that needs to be addressed.
In Kanban, bottlenecks (where work piles up) are visual cues that highlight a constraint or problem in the workflow. A pile-up in the 'In Review' column indicates that the capacity of the review step is less than the capacity of the preceding steps. This signals a systemic problem—such as insufficient reviewer capacity, an overly complex review process, or external dependencies—that the team needs to investigate and resolve to improve flow.
Question 5: Which Lean principle is primarily focused on identifying and eliminating non-value-adding activities from a service delivery process?
- Pursue Perfection
- Create Flow
- Map the Value Stream (Correct answer)
- Establish a Pull System
Correct answer: Map the Value Stream
Mapping the Value Stream is the Lean principle that involves visualizing all the steps required to take a service or product from request to delivery. The primary purpose of this activity is to analyze the workflow to identify and distinguish between value-adding activities and non-value-adding activities (waste), with the goal of eliminating the latter.
Question 6: A service team is adopting DevOps practices. They want to automate the process of merging code changes from multiple developers into a central repository, where automated builds and tests are then run. What is this specific practice called?
- Continuous Deployment
- Value Stream Mapping
- Continuous Integration (CI) (Correct answer)
- Infrastructure as Code (IaC)
Correct answer: Continuous Integration (CI)
Continuous Integration (CI) is the DevOps practice of automating the frequent integration of code changes from multiple contributors into a shared repository. Each integration is then verified by an automated build and automated tests, allowing teams to detect problems early.
Free Certified Agile Service Manager Kanban, Lean, and DevOps Questions and Answers
A service management team is consistently overloaded with requests, leading to context switching and long lead times for resolving incidents.
Which core Kanban practice would be MOST effective in addressing this specific problem?