Certified Agile Service Manager Agile Process Design 5 β Questions and Answers
Question 1: In Agile process design, what is the purpose of a 'process canvas'?
- A document listing all approved ITSM tools
- A one-page visual overview of the key process elements, owners, inputs, outputs, and metrics (Correct answer)
- A template for writing user stories
- A matrix that maps team members to sprint tasks
Correct 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.
Question 2: Which metric BEST measures the efficiency of an Agile service process end-to-end?
- Number of story points completed per sprint
- Flow efficiency (value-added time divided by total elapsed time) (Correct answer)
- Team happiness score
- Number of incidents resolved per day
Correct 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.
Question 3: When should a team revisit and update a process design artifact in an Agile environment?
- Only at project completion
- At the end of every quarter regardless of changes
- Continuously, whenever the process or context changes meaningfully (Correct answer)
- Only when a senior manager requests a review
Correct 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.
Question 4: A service team's retrospective reveals that team members are unclear about process ownership. What should the CASM practitioner do?
- Assign all process ownership to the service manager
- Define clear RACI or similar roles for each process step collaboratively with the team (Correct answer)
- Add a new approval stage to every process step
- Hire a dedicated process coordinator
Correct 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.
Question 5: In Agile process design, 'inspect and adapt' refers to:
- Reviewing a competitor's process and adopting it
- Regularly examining process performance data and adjusting the process based on what is learned (Correct answer)
- Inspecting each work item before it is closed
- Adapting team size based on project budget
Correct 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.
Question 6: Which of the following represents a 'process smell' indicating poor Agile process design?
- Short daily stand-ups that surface blockers
- Multiple sequential approval stages that require sign-off from non-service team members (Correct answer)
- A lightweight Definition of Done agreed by the team
- Retrospectives held every two weeks
Correct 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.
Question 7: What distinguishes Agile process design from traditional process design?
- Agile process design requires more detailed upfront documentation
- Agile process design is iterative, feedback-driven, and prioritizes simplicity and adaptability over completeness (Correct answer)
- Agile process design relies on waterfall phases but with shorter timelines
- Agile process design eliminates all formal process steps
Correct 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.
In Agile process design, what is the purpose of a 'process canvas'?