requirements-gathering

Effective requirements gathering establishes a shared understanding of what will be built, preventing misalignment and expensive changes later in the project. Minimal working example: Detailed implementations in the references/ directory: - Overview - When to Use - Quick Start - Reference Guides - Best Practices - Project kickoff and planning - Feature development initiation - Product roadmap planning - System modernization projects - Customer discovery - Stakeholder alignment sessions - Writing user stories and acceptance criteria - Engage all key stakeholders early - Document requirements in writing - Use specific, measurable language - Define acceptance criteria - Prioritize using MoSCoW method - Get stakeholder sign-off - Create traceability matrix - Review requirements regularly - Distinguish must-haves from nice-to-haves - Document assumptions and constraints - Rely on memory or verbal agreements - Create requirements without stakeholder input - Use ambiguous language (quickly, easily, etc.) - Skip non-functional requirements - Ignore constraints and dependencies - Over-document trivial details - Rush through requirements phase - Build without stakeholder agreement - Make scope changes without process - Forget about edge cases and error conditions