Agile Requirements & Documentation Flashcards
7 cards from real AAC 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 Requirements & Documentation flashcards as text
A business analyst is working on a product where requirements frequently change. Which documentation approach best supports this in an agile context?
Answer: Maintain a living backlog with just-in-time elaboration
A living backlog with just-in-time elaboration allows requirements to evolve while keeping documentation lean and current.
What distinguishes an epic from a user story in agile requirements?
Answer: An epic is a large body of work that can be broken down into smaller user stories
An epic is a large, high-level requirement that is too big to complete in a single sprint and is decomposed into smaller user stories.
When writing acceptance criteria using the Gherkin 'Given-When-Then' format, what does the 'Given' clause represent?
Answer: The precondition or initial context of the scenario
The 'Given' clause describes the preconditions or initial state of the system before the action occurs.
A product owner wants to prioritize backlog items based on customer value and risk. Which technique is most appropriate?
Answer: Weighted Shortest Job First (WSJF)
WSJF calculates priority by dividing cost of delay by job duration, incorporating value, risk, and time criticality.
Which statement best describes the purpose of a Definition of Ready (DoR) for user stories?
Answer: It ensures a story has enough detail for a team to begin work in a sprint
A Definition of Ready ensures stories are sufficiently understood, estimated, and small enough to be taken into a sprint.
In agile analysis, what is the primary purpose of story mapping?
Answer: To organize user stories by user journey and identify gaps in product scope
Story mapping arranges stories along a user journey backbone, helping teams visualize the whole product and find missing functionality.
A team's backlog contains many user stories with unclear scope, causing frequent mid-sprint scope changes. What refinement practice should the BA recommend?
Answer: Conduct regular backlog refinement sessions to clarify and split stories before sprint planning
Regular backlog refinement (grooming) sessions ensure stories are clarified and properly sized before they enter a sprint, reducing mid-sprint disruption.