According to the PMBOK® Guide, the Collect Requirements process is the stage where the project team determines, documents, and manages stakeholder needs and requirements. Because requirements can often be difficult for stakeholders to articulate, specific tools are used to extract this information.
Prototypes: This is a key Tool and Technique of the Collect Requirements process. A prototype is a working model of the expected product before actually building it. It allows stakeholders to interact with a " mock-up " of the final product, which helps them identify missing requirements, clarify expectations, and uncover potential risks early in the project life cycle.
Progressive Elaboration: Prototyping supports the concept of progressive elaboration because it follows an iterative cycle of mock-up creation, user review, feedback generation, and prototype revision.
Visual Confirmation: For many stakeholders, seeing a visual representation (like a wireframe for software or a small-scale model for a building) is much more effective than reading a technical document. This ensures that the final " Requirement Documentation " is accurate and agreed upon.
Why other options are incorrect:
Option A: Inspection: This is a tool and technique used in Validate Scope and Control Quality. It involves examining a work product to determine if it conforms to standards. It happens after the work is done, not during the collection of requirements.
Option B: Decomposition: This is a tool and technique used in the Create WBS process. It involves breaking down the project scope and project deliverables into smaller, more manageable components.
Option C: Product analysis: This is a tool and technique used in Define Scope. It is used to translate high-level product descriptions into meaningful deliverables by asking questions about the product ' s function and purpose.
