Project Requirements

This topic provides students and community leaders with a structured approach to identifying, analyzing, and documenting what a project must deliver. Participants will learn how to manage conflicting opinions from different stakeholders to create a unified Requirements Documentation list. This ensures the project solves the right problem from day one.

Core Objectives:

• Types of Requirements: Distinguishing between Business Requirements (the high-level “why”), Stakeholder Requirements (what people need to do their jobs), and Functional Requirements (the specific features the solution must have).
• The Requirement Gathering Toolkit: * Interviews & Focus Groups: Engaging directly with the people the project affects.
  • Observations: Seeing the problem firsthand to identify requirements stakeholders might forget to mention.
  • Prototypes: Creating “rough drafts” or models to confirm the requirements before full-scale production.
• Requirements Prioritization: Using the MoSCoW method (Must have, Should have, Could have, Won’t have) to manage limited school or community budgets and focus on what provides the most value.
• Traceability: Understanding how to track a requirement from the moment it is requested until it is verified in the final deliverable.

Key Outcome: By the end of this topic, participants will be able to turn vague community feedback into a professional, prioritized list of requirements. They will gain the ability to manage expectations and ensure that the final result of their school or community project is exactly what was needed to achieve success.