Scrum for Service Management 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 Scrum for Service Management flashcards as text
In Scrum for service management, an 'increment' at the end of a Sprint should be:
Answer: A potentially shippable improvement to the service
Each Sprint must produce a usable, potentially releasable increment that adds value to the service.
A service management team notices that the same types of incidents recur every Sprint. Which Scrum event is MOST appropriate for addressing root causes?
Answer: Sprint Retrospective
The Sprint Retrospective focuses on continuous process improvement, making it the right forum to analyze and solve recurring incident patterns.
In Scrum, 'velocity' in a service context is BEST used for:
Answer: Forecasting how much work the team can complete in future Sprints
Velocity is a planning tool that helps teams forecast future throughput based on historical Sprint data, not a performance metric.
Which role in Scrum is accountable for maximizing the value of the work performed by the Development Team?
Answer: Product Owner
The Product Owner is solely accountable for maximizing the value of the product resulting from the Development Team's work.
A service team consistently fails to complete all Sprint Backlog items. The MOST likely root cause in a Scrum context is:
Answer: The team is over-committing during Sprint Planning
Consistently incomplete Sprints typically indicate over-commitment during planning, often because capacity or complexity is underestimated.
Which statement about the Daily Scrum in a service context is TRUE?
Answer: It is a 15-minute synchronization event for the Development Team
The Daily Scrum is a 15-minute, time-boxed event for the Development Team to inspect progress and adapt their plan toward the Sprint Goal.
When Scrum is applied to service management, 'Product Backlog Refinement' serves to:
Answer: Break down and estimate backlog items so they are ready for future Sprints
Refinement ensures backlog items are well-understood, estimated, and small enough to be planned into upcoming Sprints.