Final answer:
B) Stories.In Agile and Scrum software development methods, detailed requirements documents are typically replaced by User Stories.
Step-by-step explanation:
In the context of modern software development practices, particularly Agile and Scrum methodologies, detailed requirements documents are often replaced by User Stories (option B). User stories serve as a tool for capturing a description of a software feature from an end-user perspective.
They help teams to understand what the user needs and why, thus defining the value behind the requirement.
User stories are usually written in a simple template: As a [type of user], I want [an action] so that [a benefit/a value]. This format keeps the focus on user needs rather than technical details.
Stories can be further broken down into tasks and added to Task Boards to manage progress and workflow. While Pair Work and Unit Tests also contribute to Agile software development, they do not serve as replacements for detailed requirements documents as they serve different purposes in the development process.
These stories describe software features from the user's perspective, focusing on their needs and the value the feature provides.