Prototypes
Creating a functional mock-up of the product so stakeholders can review and validate requirements early, before building the full solution.
Key Points
- Used to elicit and confirm requirements by showing how the product will work.
- Can range from low-fidelity sketches to high-fidelity interactive models or simulations.
- Reviewed in short cycles; feedback is used to refine scope and requirements.
- Helps reduce rework and misunderstandings, but may raise expectations if mistaken for the final product.
Example
A project team developing a customer portal builds a clickable screen prototype that demonstrates login, account view, and payment flows. Stakeholders test it in a workshop, identify missing fields and navigation issues, and the team updates the requirements before design and development begin.
PMP Example Question
During requirements elicitation, the sponsor asks to see how the solution will behave before development starts. Which tool should the project manager use?
- Prototypes
- Context diagrams
- Benchmarking
- Check sheets
Correct Answer: A — Prototypes
Explanation: Prototypes provide an early, working model that stakeholders can review to validate and refine requirements before the product is built.
