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 activities

During the Build and Test phase, focus on building features in small batches and testing those with real users.

Key questions to answer

  • Which user stories for the MVP are best suited to address basic user needs?

  • Does the technical solution work at scale, and do its integrations with other services work well?

  • Is the MVP solution consistent with other Veteran-facing Services Platform design patterns?

  • Is the MVP solution accessible?

  • Which metrics make sense to measure the success of the MVP?

  • What business or policy changes are needed for the MVP?


MVP activities

During this phase, you’ll build your MVP. You’ll also complete other activities to support the launch of your service and to evaluate the readiness of your service to launch on the Veteran-facing Services Platform.

When you plan for this phase, be sure to include enough time for these activities. Your Build and Test plan should include time before launch to fix any issues found during UAT and/or load testing.

Communications
Talk with your DSVA Contact about how to create a communications plan for the launch of your service.

Building and testing
Group the user stories and features you’ve identified for the MVP into small, testable chunks that you can build, deploy, and test iteratively.

  1. Code locally and deploy to staging (with automated testing).

  2. Conduct user research to test the features you’ve deployed to staging.

    • Focus on usability testing to ensure that user stories and features work well for your users.

    • Analyze and synthesize the user feedback you’ve collected.

    • Document your research findings.

    • Use your research findings to refine your Build and Test plan — adjusting existing features and adding new features (if these are critical to supporting your users’ basic needs).

  3. Repeat the cycle of developing incrementally and conducting user research until

    • You’ve deployed all the features you planned for the MVP service, or

    • The MVP provides value by meeting basic user needs

Information architecture
Define the information architecture for your MVP. Then request an Request an IA Review.

ATO
Request a preliminary ATO review for your MVP.

Success metrics
Define the metrics you’ll use to measure the success of the MVP.

Continuous improvement

  • Create a prioritized backlog of features you plan to build after the MVP launches.

  • Create a plan for the Learn and Improve phase — how you’ll monitor, evaluate, user research/test, and build from your backlog.

Complete pre-launch activities
Complete the pre-launch activities after you’ve completed all the MVP activities.


Pre-launch activities

Start these activities when the complete and final build is on staging and you’ve completed all the MVP activities.

  1. Conduct cross-browser QA testing.

  2. If you’ve made any changes to your service’s information architecture (page titles, URLs, navigation) since your last IA Review with DSVA, request another IA Review.

  3. Request a Design QA.

  4. Request a Content QA.

  5. Request an Accessibility/508 review.

  6. Request a Call Center Review.

  7. Request a Pre-launch ATO review.

  8. Set up Google Analytics.

  9. Perform user acceptance testing.

  10. Load test your service.



< Build and Test introduction
Build and Test checklist >