• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Visual Delivery Boards

Purpose and Strategic Importance

Visual Delivery Boards create a shared, real-time understanding of work in progress, blockers, and value flow. This practice enables faster decision-making, reduces confusion, and aligns teams and stakeholders around delivery progress.

By making work visible, teams can identify bottlenecks early, limit WIP effectively, and manage dependencies with greater transparency. It forms a foundation for inspect-and-adapt practices and fosters trust by enabling open, data-led discussions.


Description of the Practice

  • Teams visualise all stages of their workflow using a physical or digital board.
  • Cards represent work items and move across columns that reflect real delivery stages.
  • Blockers, dependencies, and priorities are clearly highlighted and owned.
  • The board is treated as a single source of truth and reviewed collaboratively.
  • Time-in-status and flow data are tracked and surfaced visually.

How to Practise It (Playbook)

1. Getting Started

  • Define delivery stages (e.g. Ready, In Progress, In Review, Done) clearly.
  • Use tools like Jira, Azure Boards, Trello or physical boards with sticky notes.
  • Include a "Blocked" indicator or column to flag work impeded by delays.
  • Review the board daily and use it as the anchor for stand-ups and syncs.

2. Scaling and Maturing

  • Add swimlanes for work types or team streams.
  • Track WIP limits and use cumulative flow diagrams to visualise flow health.
  • Include metadata on cards (e.g. size, risk, SLA class) to aid prioritisation.
  • Review time-in-status data weekly to identify and address slow stages.

3. Team Behaviours to Encourage

  • Keep the board updated in real time, not just before reviews.
  • Make blockers and delays visible and discuss them regularly.
  • Use the board to challenge unvalidated assumptions or stalled work.
Associated Standards
  • Flow-based metrics are used to guide delivery improvements
  • Delivery systems are designed to optimise feedback and reduce delay

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering