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.

Share:

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

High-yield topics our learners drill most before exam day.

Matrix Diagrams

Matrix diagrams are a data representation technique that uses a grid format to show relationships between two or more groups of factors, commonly used for responsibility assignments and prioritization.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Tools & Techniques

Study full domain →

Test your knowledge

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