# Assumptions / Test Board

**Supplies needed:** Whiteboard, Markers, Post-its

**Estimated time:** 30 minutes

## Best to use when

It is best to always keep track of the assumptions that you and your team are making about your product through the life of the product. During the product sprint this should be done throughout all phases. It is best to analyze and figure out how to test the assumptions during Converge.

## Instructions:

1. Have a dedicated space to collect Assumptions on the whiteboard.
2. Throughout the sprint have everyone write down assumptions

   that they are making or that they hear other people making

   and put them up on the whiteboard.
3. At the end of Converge, create a table with 3 columns:

   Assumption, Test, Validated if.
4. List out all of the assumptions that team is making.
5. For each assumption decide how you plan on testing

   to see if the assumptions are valid or not

   and how you know if that assumption is valid.
6. Repeat till all assumptions have a test for them.

## Example

![Galen's Assumption Test board](http://images.thoughtbot.com/the-product-design-sprint/assumptions.jpg)

From [The Product Design Sprint](http://robots.thoughtbot.com/the-product-design-sprint)

![Assumption Test Example](https://3785438829-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LES2BX2yazCNj3mBDVY%2F-LES5DMW6a8fJ-W0ettt%2F-LES5ORGRQ1TB_SFazLq%2Fassumption-test.jpg?generation=1528422832924075\&alt=media)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://playbook.messy.design/converge-choose-the-right-path/exercises/assumptions-test-board.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.