Certified Agile Service Manager Agile Process Design Principles 4 — Questions and Answers
Question 1: An Agile process design team wants to prioritize which process improvements to tackle first. Which framework best supports this prioritization?
- MoSCoW prioritization based on value and urgency (Correct answer)
- Alphabetical ordering of improvement backlog items
- Random selection to avoid bias
- Seniority-based voting among team leads
Correct answer: MoSCoW prioritization based on value and urgency
MoSCoW (Must have, Should have, Could have, Won't have) is a practical Agile prioritization technique that helps teams focus on highest-value improvements first.
Question 2: What distinguishes an Agile process design from a traditional waterfall process design approach?
- Agile designs are completed in one phase with no revisits
- Agile processes are designed iteratively with frequent stakeholder feedback (Correct answer)
- Traditional designs always produce better documentation
- Agile eliminates the need for any process governance
Correct answer: Agile processes are designed iteratively with frequent stakeholder feedback
Agile process design is iterative and collaborative, incorporating stakeholder feedback throughout, whereas waterfall designs processes linearly with feedback only at the end.
Question 3: In the context of Agile service management, a 'process owner' is best described as someone who:
- Performs all tasks within the process personally
- Is accountable for the process design, performance, and continuous improvement (Correct answer)
- Approves every individual work item that passes through the process
- Writes the process documentation without involving others
Correct answer: Is accountable for the process design, performance, and continuous improvement
The process owner is accountable for ensuring the process is fit for purpose, performs well, and is continuously improved — not necessarily the person doing the work.
Question 4: Which Agile process design principle is illustrated when a team limits the number of simultaneous service requests in progress?
- Continuous deployment
- Limiting Work in Progress (WIP) (Correct answer)
- Big Bang integration
- Waterfall sequencing
Correct answer: Limiting Work in Progress (WIP)
Limiting WIP is a core Kanban-Agile principle that prevents overloading the system, reduces context-switching, and improves throughput and quality.
Question 5: When using retrospectives as part of Agile process design, the primary output should be:
- A blame report identifying who caused process failures
- Actionable improvement items added to the team's backlog (Correct answer)
- A formal audit report submitted to senior leadership
- A request to increase the team's headcount
Correct answer: Actionable improvement items added to the team's backlog
Retrospectives should produce concrete, actionable improvement items that the team commits to implementing, driving continuous process improvement.
Question 6: A service management team is redesigning their request fulfillment process. Which Agile design pattern would reduce customer wait time most effectively?
- Adding more approval layers to ensure accuracy
- Self-service automation for common, low-risk requests (Correct answer)
- Routing all requests through a single senior approver
- Requiring full documentation before any request is started
Correct answer: Self-service automation for common, low-risk requests
Self-service automation handles routine, low-risk requests instantly, dramatically reducing wait time and freeing human capacity for complex work.
Question 7: In Agile process design, 'timeboxing' is used primarily to:
- Limit the number of participants in a process review meeting
- Create fixed time boundaries that force prioritization and prevent endless scope creep (Correct answer)
- Measure how long each team member spends on tasks
- Schedule maintenance windows for IT systems
Correct answer: Create fixed time boundaries that force prioritization and prevent endless scope creep
Timeboxing sets a fixed time limit on activities, forcing teams to prioritize what matters most and delivering value incrementally rather than pursuing perfection indefinitely.
An Agile process design team wants to prioritize which process improvements to tackle first.
Which framework best supports this prioritization?