Certified Agile Service Manager Agile Process Design 4 — Questions and Answers
Question 1: In Agile process design, 'experiment-driven design' means the team should:
- Test all process changes in a lab environment before any team exposure
- Run hypothesis-based trials on process changes and measure outcomes before full adoption (Correct answer)
- Avoid changing processes until all risks are documented
- Implement every stakeholder suggestion to gather data
Correct answer: Run hypothesis-based trials on process changes and measure outcomes before full adoption
Experiment-driven design uses structured hypotheses and measured outcomes to validate process changes before committing to full-scale rollout.
Question 2: Which Agile value MOST directly supports designing processes that respond to customer feedback?
- Individuals and interactions over processes and tools
- Responding to change over following a plan
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation (Correct answer)
Correct answer: Customer collaboration over contract negotiation
Customer collaboration over contract negotiation drives teams to continuously engage customers and redesign processes around their actual needs.
Question 3: A service team uses a Kanban board for process design. What should trigger a process review?
- A scheduled quarterly review meeting
- When a manager requests a status report
- When metrics such as cycle time or throughput show a persistent negative trend (Correct answer)
- After every single completed ticket
Correct answer: When metrics such as cycle time or throughput show a persistent negative trend
Metrics-driven triggers ensure process reviews are based on objective evidence of performance degradation rather than arbitrary schedules.
Question 4: What is 'minimal viable process' (MVP-process) in Agile service management?
- A process with the fewest possible rules to satisfy legal compliance only
- The simplest process design that delivers the required service outcome, to be enhanced iteratively (Correct answer)
- A temporary process used only during incidents
- A process approved by a minimum viable number of stakeholders
Correct answer: The simplest process design that delivers the required service outcome, to be enhanced iteratively
A minimal viable process starts with only the essential steps needed to deliver value, then evolves based on feedback and learning.
Question 5: Which of the following BEST illustrates 'process transparency' in an Agile context?
- Sharing sprint velocity data only with senior management
- Making the workflow, status of all work items, and process metrics visible to the entire team (Correct answer)
- Publishing detailed process diagrams on the company intranet annually
- Requiring all team members to attend every meeting
Correct answer: Making the workflow, status of all work items, and process metrics visible to the entire team
Process transparency means all stakeholders can see the current state of work and key metrics in real time, enabling fast identification of issues.
Question 6: How does 'batch size reduction' improve an Agile service process?
- It reduces the number of team members needed for each task
- It decreases the time to receive feedback and lowers risk by delivering smaller increments (Correct answer)
- It eliminates the need for sprint planning ceremonies
- It ensures all work is completed before the sprint ends
Correct answer: It decreases the time to receive feedback and lowers risk by delivering smaller increments
Smaller batches mean feedback arrives sooner, defects are caught earlier, and the cost of rework is minimized.
Question 7: A CASM practitioner is asked to design a change management process. Which Agile approach is most appropriate?
- Create a comprehensive multi-stage approval workflow modeled on ITIL v3
- Design a lightweight process with a small change advisory board meeting in short cadences (Correct answer)
- Eliminate change approvals entirely to maximize speed
- Delegate all change decisions to external auditors
Correct answer: Design a lightweight process with a small change advisory board meeting in short cadences
An Agile change process is lightweight, with frequent short cadence reviews rather than heavy sequential approvals, balancing speed with governance.
In Agile process design, 'experiment-driven design' means the team should: