Agile Process Design Principles 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 Agile Process Design Principles flashcards as text
An Agile process design team wants to prioritize which process improvements to tackle first. Which framework best supports this prioritization?
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.
What distinguishes an Agile process design from a traditional waterfall process design approach?
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.
In the context of Agile service management, a 'process owner' is best described as someone who:
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.
Which Agile process design principle is illustrated when a team limits the number of simultaneous service requests in progress?
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.
When using retrospectives as part of Agile process design, the primary output should be:
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.
A service management team is redesigning their request fulfillment process. Which Agile design pattern would reduce customer wait time most effectively?
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.
In Agile process design, 'timeboxing' is used primarily to:
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.