The show and tell: what it’s for and how to do it right

  • bring the team together, helping stakeholders and others bond with the team by sharing success and improving collaboration
  • let teams you’re working with know what you’re up to, highlight progress where dependencies exist and keep teams connected
  • tell stakeholders what you’ve been doing and take their questions and feedback — a form of governance
  • Don’t ad lib: 30–60 minutes of preparation to decide what to focus on is ideal, but don’t prepare extra material just for the show and tell
  • Spread the work of running and presenting the show and tell across the team
  • The delivery manager or product owner typically leads the meeting, but this needn’t be the case (the issue is often the confidence of others to do it)
  • If show and tells are a new thing at your organisation, remind people what they are and why you do them (also mention this in the meeting invitation)
  • Start by recapping on why you’re doing the work (vision, goals) and what you’ve been focusing on in the past increment (tying that back to the goals if it isn’t clear)
  • Show — software, user research, prototypes, clickable screens, content, analytics data (anything that makes sense to show)
  • Show your work in progress — get feedback — but make it clear it’s not yet shippable
  • Talk about what you’ve learned, new insights, (in)validated hypotheses — don’t just show your artefacts
  • Do it at your team’s wall or in a separate room
  • Minimise technology and other dependencies — rehearse technology (screens, mics, video conferencing etc) ahead of time if needed
  • Invite stakeholders, people you’re collaborating with, interested parties
  • Be mindful of your audience needs — what’s in it for them to participate — as well as what you need to get out of their involvement
  • Remember that some people may be new to agile ways of working and how Show&Tells work as well as being new to your project
  • Don’t spend a long time preparing for a show and tell — it shouldn’t be a theatrical production
  • Don’t just talk about the work — show it! Tell a story about how you did it; what you’ve learned — make the meeting engaging and tie what you’ve done to stakeholder or user needs
  • If you’ve done ‘backend’ work talk about what it enables that your stakeholders or users care about. This can be a difficult sometimes so you may have to do extra work to ‘spice up’ how you present that
  • Talk about what you’ve learned: show user research clips, prototype interfaces, your analytics data
  • Talk about stuff you tried but that didn’t work out — explain why it didn’t work out
  • Take questions throughout — but be prepared to take long discussions offline and keep the questioning focused
  • Make sure everyone knows their role in the meeting
  • Explain to your audience ahead of time what’s expected of them if they are unfamiliar with the purpose of the meeting
  • As an audience member, be supportive, ask questions, offer praise, thanks and constructive criticism
  • Keep the audience engaged, get their feedback — during the meeting, ask stakeholders to demo or talk about what you’ve learned to make them feel part of the work
  • Create a “How to do show and tells” guide for your organisation, including technology set-up, and evolve it as you learn more
  • the team isn’t focusing enough on delivering value in each increment
  • the team isn’t getting value from them
  • stakeholders are not participating



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mark Dalgarno

Mark Dalgarno

Freelance Agile Coach | Interim Manager | Agile Programme or Project Manager. Conference Organiser. Improver.