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:

Know it well enough for the exam? Questions on Prototyping are scenario-based, not definitional.

Practice it free

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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

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.

Part of

Tools & Techniques

Study full domain →

Practice Prototyping

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.