Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Build and Test introduction

The Build and Test phase is about incrementally building (and testing) the user stories and features you've identified for the MVP. Your goal is to launch the first working version of your service at the end of this phase.

What is the Build and Test phase?

In the Build and Test phase, it’s tempting to try to build all the features and functionality you imagine for your service. But stay focused on your vision for the MVP. As soon as your service can provide value by meeting basic user needs, it’s ready to launch!

During this phase, you’ll build the user stories and features from your backlog in small batches of functionality. As you build these batches, you’ll test them with your users to ensure they work well. Then you’ll use that user feedback to refine your service, adding and adjusting features until your MVP service is complete.

The final step in the Build and Test phase is to launch the MVP, which you’ll do after the Checkpoint meeting.


Planning

  • Different services will spend different amounts of time in the Build and Test phase, depending on what the team plans to build as the MVP. In general, plan to spend
    • 6-8 weeks for a new feature
    • 8-12 weeks for a new service
    • Note: If your planned MVP will take longer than 12 weeks to build and test, reconsider the scope of your MVP.
  • Schedule the Build and Test Checkpoint at least a week in advance.

Resources and help



< Prototype checklist
Build and Test activities >