Skip to main content
Next Step PM
Back to the library

Build · Add-on

Run prototype and pilot production builds (EVT, DVT and PVT)

Hardware is built several times before mass production. Each build has a purpose and exit criteria: first the design works, then it is right, then the factory can make it.

About 20-60 daysEvergreenLast reviewed 5 November 2026

Who this applies to

Skills it builds
Delivery and executionTechnical and AI fluency
PM types
Hardware or IoT
Product types
All
Starting points
All
Ways of working
All
Experience
All
Size of organisation
All

Steps, by experience

Beginner (under 1 year)

  1. Learn the three builds: engineering validation (EVT), design validation (DVT) and production validation (PVT).
  2. For each build, write down what it must prove before the next one starts.
  3. Agree how many units each build needs, including extras for testing and marketing.
  4. Track the issues found in each build and who is fixing them.
  5. Do not move to the next build until the exit criteria are met.

Intermediate (1 to 4 years)

  1. Plan the build schedule with time to fix issues between builds.
  2. Agree exit criteria for each build with engineering and the manufacturer.
  3. Shorten the build, test and fix cycle rather than squeezing the schedule.

Experienced (5+ years)

  1. Set build standards across products so schedules are comparable.
  2. Decide when an extra build is cheaper than shipping a known problem.
  3. Report build readiness to leadership with clear risks.

Who can do this

Owner: Product manager

Can be delegated to

  • Hardware / manufacturing engineer or Tech Lead: Agree exit criteria and the build schedule
  • QA / Tester or Hardware / manufacturing engineer: Run the tests for each build

Reviewed by: Hardware / manufacturing engineer, Tech Lead

Tool examples

Jira
Track issues by build, such as EVT or DVT.
Confluence
Write the exit criteria for each build on one page.

Definition of done

  • Exit criteria written for each build
  • Build quantities agreed
  • Issues tracked to closure before the next build

Common pitfalls

  • Calling a build DVT when the design is still changing
  • Too few units for testing
  • Squeezing the schedule instead of fixing faster

If you lead the team

What good looks like: Each prototype build has a clear purpose and exit criteria before the next one starts.

Ask your PM

  • What must this build prove, and did it?
  • What's blocking the move to the next build?

Warning signs

  • Builds move on with known problems unresolved.
  • Exit criteria are vague.

Do these first

Sources