Agile Process Design 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 flashcards as text
In Agile process design, what is the purpose of a 'process canvas'?
Answer: A one-page visual overview of the key process elements, owners, inputs, outputs, and metrics
A process canvas provides a concise visual summary of a process on a single page, making it easy to discuss, adapt, and communicate.
Which metric BEST measures the efficiency of an Agile service process end-to-end?
Answer: Flow efficiency (value-added time divided by total elapsed time)
Flow efficiency measures what percentage of total lead time is actually spent on value-adding work, directly exposing waste in the process.
When should a team revisit and update a process design artifact in an Agile environment?
Answer: Continuously, whenever the process or context changes meaningfully
Agile process artifacts are living documents updated whenever significant changes in context, team learning, or performance data warrant it.
A service team's retrospective reveals that team members are unclear about process ownership. What should the CASM practitioner do?
Answer: Define clear RACI or similar roles for each process step collaboratively with the team
Collaboratively defining roles (such as via a RACI matrix) ensures team members understand their responsibilities and removes ambiguity without creating bottlenecks.
In Agile process design, 'inspect and adapt' refers to:
Answer: Regularly examining process performance data and adjusting the process based on what is learned
Inspect and adapt is the empirical Agile cycle of observing actual results and using that information to improve the process iteratively.
Which of the following represents a 'process smell' indicating poor Agile process design?
Answer: Multiple sequential approval stages that require sign-off from non-service team members
Multiple sequential approvals by outsiders create queues, slow flow, and signal a bureaucratic design that conflicts with Agile principles.
What distinguishes Agile process design from traditional process design?
Answer: Agile process design is iterative, feedback-driven, and prioritizes simplicity and adaptability over completeness
Agile process design embraces iteration, customer feedback, and simplicity, evolving the process over time rather than defining it fully upfront.