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
Which of the following is the MOST appropriate level of documentation for a Minimum Viable Product (MVP)?
Answer: Only the documentation necessary to validate core hypotheses with users
An MVP requires just enough documentation to test the core value proposition with real users, avoiding waste on unvalidated features.
A BA notices that multiple user stories in the backlog address the same underlying user need but from different angles. What is the BEST course of action?
Answer: Review for duplication and merge or split as appropriate to eliminate redundancy
Reviewing for duplication and restructuring ensures the backlog remains clean, avoiding rework and confusion during development.
What does the INVEST acronym stand for in the context of well-formed user stories?
Answer: Independent, Negotiable, Valuable, Estimable, Small, Testable
INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) is a checklist for evaluating the quality of a user story.
When should a business analyst create a process flow diagram during agile development?
Answer: When a complex workflow needs to be understood before story decomposition
Process flow diagrams are created on an as-needed basis when complexity warrants visual modeling to aid understanding before writing stories.
A stakeholder insists that every requirement be traced to a specific line of code. How should an agile BA respond?
Answer: Discuss the cost-benefit of traceability and explore lightweight alternatives like tagging stories to features
Agile BAs acknowledge the value of traceability but guide stakeholders toward lightweight approaches that provide needed traceability without excessive overhead.
Which technique helps a BA identify and document the boundaries of a system by showing what is inside versus outside scope?
Answer: Context diagram
A context diagram shows the system as a single entity and its interactions with external actors, clearly defining scope boundaries.
During sprint review, a stakeholder requests a significant feature addition. What is the correct agile process?
Answer: Have the BA document it and add it to the product backlog for prioritization by the product owner
New requests are captured and added to the product backlog, where the product owner prioritizes them relative to existing work.