User Stories

Correct Answer: Include them in the acceptance criteria with clear conditions

Including assumptions in the acceptance criteria with clear conditions is the most effective approach because: 1. It keeps the assumptions visible and connected to the core functionality 2. It ensures all team members review and consider the assumptions during development 3. It helps in validation and verification during testing 4. It maintains a single source of truth within the user story itself Why other approaches are less effective: Creating a separate technical document introduces risk of documentation becoming disconnected from the story and may be overlooked. Adding assumptions as notes in the project management tool makes them less visible and might get lost among other comments and updates. Documenting assumptions in meeting minutes is problematic because: - Minutes may not be easily accessible - Information can be missed by team members who weren't in the meeting - Updates to assumptions would require new meetings

Correct Answer: Conversation between stakeholders and development team during story refinement

In the '3 Cs' model of user stories, Conversation is the most valuable component for capturing accurate requirements. Conversation between stakeholders and the development team during story refinement allows for: - Real-time clarification of requirements - Discovery of hidden assumptions - Shared understanding of business needs - Collaborative problem-solving - Immediate feedback and corrections The other options are less effective because: Physical cards are merely placeholders for conversations and should remain simple and concise, not detailed technical specifications. Extensive acceptance criteria during initial creation can be premature and may not capture the full context that emerges through discussion. Documenting all scenarios upfront contradicts the agile principle of progressive elaboration and may waste effort on unused scenarios. The strength of the '3 Cs' model lies in the human interaction and shared understanding that develops through conversation, making it the most effective way to capture true requirements and business value.

Correct Answer: The story should be negotiable to allow room for team discussions and refinement

A user story should be negotiable to promote collaboration and allow the cross-functional team to contribute their expertise during refinement. This aligns with the 'N' in INVEST (Negotiable). The negotiable aspect enables valuable discussions between the Product Owner and team members, leading to better solutions and shared understanding. It allows the team to explore different implementation approaches and incorporate diverse perspectives. The other options are incorrect because: Prescribing technical requirements and implementation details up front limits the team's ability to innovate and collaborate. Mandating detailed acceptance tests before development begins restricts the team's ability to discover better testing approaches during development. Trying to capture every possible scenario and edge case makes stories too large and complex, violating the 'Small' principle of INVEST.