Requirements Gathering

This is a structured approach to collecting and documenting what you're building before you build it. You get frameworks for stakeholder discovery, elicitation techniques, documentation templates, and a traceability matrix to connect requirements to implementation. The stakeholder categorization (primary, secondary, tertiary) and MoSCoW prioritization method are solid fundamentals. Honestly, the value here is less about novel techniques and more about having a checklist so you don't skip the boring but critical step of getting everyone aligned on paper. Most projects fail because requirements were assumed, not because the code was bad. Use this at project kickoff or when adding major features.