Skip to content

Project hypotheses

Sara Cope edited this page Oct 18, 2016 · 37 revisions

Template:

We believe <this capability>

What functionality we will develop to test our hypothesis? By defining a ‘test’ capability of the product or service that we are attempting to build, we identify the functionality and hypothesis we want to test.

Will result in <this outcome>

What is the expected outcome of our experiment? What is the specific result we expect to achieve by building the ‘test’ capability?

We will know we have succeeded when <we see a measurable signal>

What signals will indicate that the capability we have built is effective? What key metrics (qualitative or quantitative) we will measure to provide evidence that our experiment has succeeded and give us enough confidence to move to the next stage.

reference


We believe that

  • improving documentation and reusability
  • building in the open and using open source technologies
  • making the site user friendly
  • ensuring the site meets the U.S. Web Design Standard

Will result in other agencies using the open.gsa.gov site as a model.

We will know we are right when

  • we get questions from other agencies about the specifics of reusing our site or code
  • when we see the influence of our site in other agency development

Process

Development

Hackathon

Clone this wiki locally