<aside> <img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> Shared Models

Key items

There are four kinds of items on the SIS delivery board:

Deliverable: anything that offers value to someone else. A deliverable could be a feature, a piece of infrastructure, a release, or the answer to a research question.

Dependency: anything that the team needs from somebody else, internally, or externally. By the end of the Sync Event all dependencies must have an owner responsible for resolving it. If the owner is another team in the value stream, their delivery board should have a corresponding deliverable.

Question: a piece of information that the team needs to find the answer for. The further right on the board, the more questions there should be.

Risk: any key potential problem that the team needs to remember or warn others about.

Work is not represented on delivery boards, following the model principles. However, immature teams may not be able to start thinking in terms of deliverables from day one. So, for one iteration or two, some work representation may be helpful.

Visualising changes

When an item is “done-done”, you can choose to tick it off or change its colour to make it less visible, eg to a neutral grey or white. When something has failed, you can use a cross or an exclamation mark. As time passes, anything not resolved will stand out.

Some teams prefer to visualise when deliverables move compared to their plans, with either arrows or ± markers. This can help learning and inform to make better plans next time.

Additional visualisations

You can use lines or arrows to show how items flow into each other.

Add important information, for example holidays, external events, joiners, leavers.

Around the delivery board(s), you can add different visualisations of any useful information, creating a dashboard centred around your tactical iteration model.

For example:

<aside> ℹ️ Reflect after each iteration about how the model is working and if you want to change anything. We recommend being conservative about adding more visual language - every new item introduced makes the delivery board harder to understand. It has to be worth it!

</aside>