Skip to content
PMPCAPM

Prototyping

Prototyping is a requirements elicitation technique that creates a working model of the expected product before building the final version, enabling early feedback and iterative refinement.

Explanation

Prototyping involves building a preliminary, functional model of the product or component to allow stakeholders to interact with it and provide feedback before the final version is developed. Prototypes can range from low-fidelity mockups (paper sketches, wireframes) to high-fidelity working models that closely simulate the final product.

This technique is particularly valuable in software development, product design, and any project where stakeholders may have difficulty envisioning the final product from written requirements alone. By providing something tangible to evaluate, prototyping helps uncover misunderstandings, identify missing requirements, and refine the solution iteratively. It supports the agile principle of delivering working increments and gathering feedback frequently.

Prototyping is closely related to the concept of storyboarding and can be used in conjunction with design thinking. While prototyping requires additional upfront effort, it typically reduces rework by catching issues early, before they become expensive to fix in the final product.

Key Points

  • Creates a working model for stakeholder feedback before final development
  • Ranges from low-fidelity mockups to high-fidelity working models
  • Uncovers misunderstandings and missing requirements early
  • Reduces costly rework by validating solutions iteratively

Exam Tip

Prototyping is the best answer when stakeholders cannot define requirements abstractly or when early validation of the solution is needed to reduce risk.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.