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

To have meaningful and effective discussions teams need access to shared models.

Each context is different, however in our experience at least three models will be needed to ensure discussions are valuable without excessive cognitive load.

The three models correspond to different time horizons and levels of detail:

Model purpose Horizon Granularity Owner Level of detail
Strategic Few years Months Leadership Company and Value Stream
Product increments/Market movements
Value stream tactical - SIS Few iterations Weeks Team Teams in a value stream
Deliverables/Epics/Milestones
Team tactical Few weeks/sprints Days Team Individuals in a team
Tasks/User stories

SIS is mainly concerned with the value stream tactical level, including events and decisions which affect at least one team, with a time sensitivity in the order of a few weeks.

At the strategic level, we assume there is an up-to-date, fit-for-purpose set of strategic models available. For example, an internal roadmap and strategy document; possibly OKRs or KPIs to formalise and measure goals.

We also assume that teams already have, or will quickly adopt, a task-level model to synchronise and learn in-team. For example, a cloud-based task tracking system.

All levels must share the same language to allow linking items between the different models.

Value stream models

The iteration models at value stream level are key to cross-team synchronisation. They describe the interface to the rest of the value stream, for each team or functional contributor.

For a successful SIS, you need to keep all models easily understandable by everyone in the value stream. There should be a common minimum visual language.

However, avoid complete standardisation of the models for two reasons:

  1. Allow the teams to develop a fit-for-purpose model to suit their needs.
  2. Allow the emergence and spread of innovation in the models.

A useful model improvement usually only takes a couple of iterations to become standard across the value stream.

Tactical model requirements

SIS comes with its own recommended model: the SIS Delivery Board. Every context is different, so adapt or devise a different one as necessary.

Here is a prioritised list of what is considered important when designing the Delivery Board:

  1. Must be editable by all teams in real time so that it describes the best information available at all times - not what the plan used to be before life happened.