Assumptions are truths about the system we simply take for granted. Hidden assumptions kill projects (or at least cause significant pain). With the list assumptions activity, we take assumptions out of the shadows by writing down as many assumptions as we can. Use this information to plan further design work, prioritize next steps, improve ASRs, and improve the team’s shared knowledge about the architecture.

Benefits

• Head off misunderstandings about the true goals and requirements.
• Great for ad hoc analysis. Does not require a formal workshop or agenda.
• Avoid missing important requirements.

Activity Timing

15--30 minutes

Participants

Whole team working in pairs or small groups (no more than 3--5 people).

This can be done as a solo exercise, but you would need to share your assumptions list with someone; otherwise, your assumptions will remain hidden!

Preparation and Materials

• Any writing surface and writing tool: pen and paper, marker and whiteboard, or sharpie and sticky notes

Steps

1. Kick off the activity with the adage You know what happens when we assume too much, right? It makes an ass out of you and me!

2. Explain the goal of the activity. Over the next 15 minutes we’re going to write down all the assumptions we have about the system.

3. Prompt participants by focusing on an area where assumptions need to be flushed into the open.

4. Write down the assumptions mentioned so everyone can see them.

5. As the pace slows, move on to the next topic or end the session by planning follow-up actions.

Guidelines and Hints

• Start by asking, what do we think we know about X?

• Write down everything mentioned, even if it seems like common knowledge.

• Pause to discuss assumptions that are surprising or generate a reaction from one or more participants.

• Record the assumptions in your team wiki.

Example

Here is an assumptions list drawn up immediately following Activity 19, ​Whiteboard Jam​: