SAFE-SP · Question #43
What replaces detailed requirements documents?
The correct answer is C. Stories. In Agile development, user stories replace traditional detailed requirements documents, capturing functionality from the end-user's perspective in short, informal descriptions (e.g., "As a user, I want to..."). Stories intentionally defer detailed specification until needed…
Question
What replaces detailed requirements documents?
Options
- APair work
- BTask boards
- CStories
- DUnit tests
How the community answered
(55 responses)- A4% (2)
- B2% (1)
- C95% (52)
Explanation
In Agile development, user stories replace traditional detailed requirements documents, capturing functionality from the end-user's perspective in short, informal descriptions (e.g., "As a user, I want to..."). Stories intentionally defer detailed specification until needed, enabling flexibility and collaboration over upfront documentation.
- A (Pair work) is an Agile practice (two developers at one machine) - it's about how code is written, not how requirements are captured.
- B (Task boards) (e.g., Kanban/Scrum boards) are workflow visualization tools for tracking progress, not requirement artifacts.
- D (Unit tests) describe code behavior at a technical level - they verify correctness, not capture business requirements.
Memory tip: Think "Stories replace specs" - both start with "S," and stories are the short, human-readable alternative to long specification documents.
Topics
Community Discussion
No community discussion yet for this question.