Play: Team Demo

Owen Manby
Signal Noise
Published in
2 min readMar 12, 2021

When to run the play

Daily Demos are run every day.

Why Run This Play

To ensure the team is united on what each stream of work is doing, how they depend on each other, and to remove blockers to work. This can feel like a lot more talking than doing — remember that the talking sometimes IS the doing.

“What can you show me that you’ve done?” Ask to see a working thing. If there’s no working thing yet, ask to see the insights that will inform the working thing. Don’t be satisfied with insights for very long. — UsTwo`

We were previously using the scrum stand up to align teams on a daily basis. But we found that verbal updates often became routine, boring and ineffective. So we started using visual, not verbal cues to spark peoples attention and boost understanding.

How To Run This Play

The focus of this meeting is to demo (share live) exactly what you are doing. For developers this means sharing their local version of the code, for designers, this means looking at work in progress designs. From doing this demonstration a few things happen:

> Team members understand what you are working on; good for team unity
> Team members can directly see what you are doing that might impact their stream of work e.g. a design decision might impact how the front end should be built; good for visibility
> Team members regularly raise new design or technical challenges that need to be considered; good for quality

Agenda

  • The producer asks each team member (including themselves) to share their work. Pick an order that suits you as a team. This has to be done actually sharing screens
  • After each ‘share’ there is time for all project team members to ask questions and interrogate

Rules

  1. Happens daily with the full project team, being careful to ensure that the meeting is scheduled to Protect Flow
  2. Is allowed to continue on as long as it needs to until all team members have no further questions or comments; everyone is aligned
  3. Producers should share a list of actions if helpful afterwards
  4. Improvements to the format or agenda are always welcomed by the team

--

--

Owen Manby
Signal Noise

Delivery Coach at Signal Noise. Trying To Be Better.