Agile Frameworks Flashcards
7 cards from real CAPM 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 Frameworks flashcards as text
Which of the following best describes an Agile Release Train (ART) in SAFe?
Answer: A long-lived team of Agile teams that delivers value on a PI cadence
An ART is a long-lived team of Agile teams (typically 50-125 people) aligned to a common mission that delivers value every Program Increment.
A stakeholder asks for a feature that is 'nice to have' but not essential. Using MoSCoW prioritization, how would this be classified?
Answer: Could Have
In MoSCoW prioritization, 'Could Have' items are desirable but not necessary, and are included only if time permits.
Which Agile concept refers to the team's commitment to deliver a potentially shippable product increment at the end of every iteration?
Answer: Potentially Shippable Increment (PSI)
A Potentially Shippable Increment (PSI) or Product Increment is a working, tested product delivered at the end of each Sprint.
In Kanban, what is the purpose of setting explicit process policies?
Answer: To make workflow rules transparent so decisions are consistent
Explicit policies make the rules of work visible and shared, enabling the team to make consistent, transparent decisions about workflow.
An Agile team's burndown chart shows a flat line for several days. What does this most likely indicate?
Answer: Work is not being completed or not being tracked
A flat burndown line indicates that remaining work is not decreasing, suggesting blocked work, inaccurate tracking, or team impediments.
Which Agile practice involves the entire team collectively owning and being responsible for the quality of all code?
Answer: Collective code ownership
Collective code ownership, an XP practice, means any team member can modify any part of the codebase, distributing responsibility for quality.
A team practicing Scrum wants to improve their process. Which event is specifically designed for this purpose?
Answer: Sprint Retrospective
The Sprint Retrospective is held after the Sprint Review so the team can inspect their process and plan improvements for the next Sprint.