Walking the Board: A Better Way to Run Your Daily Standup

Your Daily Standup Is Probably Backwards (And Slowing You Down)

If your daily standup sounds like this…

“Yesterday I did X, today I’ll do Y, no blockers.”

…you’re wasting everyone’s time.

Teams say they’re doing Scrum, but most “daily scrums” are 15 minutes of status reporting to the most senior person in the room. That’s not collaboration. That’s a micro status meeting with better branding.

Here’s the uncomfortable truth:
The classic “three questions” format is one of the least effective ways to run a standup.

A better way? Walk the board.
Start with the work, not the people. Optimize flow, not speeches.

Let’s break down what that actually means and how to do it well.

---

What Does “Walking the Board” Actually Mean?

Instead of going around the circle asking each person to talk, you:

1. Start at the right side of your board (e.g., “In Review”, “Ready for Release”, “Blocked”).
2. Talk through each ticket, column by column, right to left.
3. Ask: “What needs to happen to move this to Done?”
4. Decide: “Who’s helping, and what’s the next concrete step?”

The board becomes the agenda. The goal becomes clear:
Move work to Done, faster, with fewer surprises.

Why This Beats the “Three Questions” Format

The traditional standup questions:

• What did you do yesterday?
• What will you do today?
• Any blockers?

Sound structured, but they:

• Encourage individual hero narratives, not team collaboration.
• Turn into status updates to the manager, not coordination between peers.
• Hide bottlenecks because no one is looking at flow.
• Waste time on tickets no one cares about right now.

Walking the board flips the script:

• Focus on flow of work, not performance of individuals.
• Make bottlenecks visible (lots of items stuck in “In Review”? That’s your real problem).
• Drive team decisions: who swarms, who unblocks, what gets dropped.
• Reduce WIP (work in progress) instead of adding more half-done stuff.

A Quick Example

Board columns:
To Do → In Progress → In Review → Ready for Release → Done

In the standup, you:

1. Start at “Ready for Release”

   • “Ticket #452: Ready for Release. What’s left?”
   • Dev: “Just waiting on the deployment window.”
   • Scrum Master: “Okay, I’ll book that for this afternoon.”
     → Clear next step, owner, and time.

2. Move to “In Review”

   • “Ticket #447 and #449: both in review. Who can review them today?”
   • Two devs commit to specific times.
     → You’re unblocking flow instead of starting new work.

3. Only then look at “In Progress”

   • “Ticket #440 has been in progress for 4 days. What’s going on?”
   • Turns out it’s bigger than expected. Team decides to split it.
     → Risk surfaced early, not on the last day of the sprint.

No one recites a mini biography of their day.
You just move work forward.

---

Why Walking the Board Works (And What the Data Says)

If this sounds like Kanban sneaking into your Scrum, that’s because it is. And that’s good.

Flow > Busy

Research from the 2022 State of DevOps report and multiple lean studies consistently shows:

• High-performing teams focus on flow metrics (cycle time, WIP, throughput).
• Low-performing teams focus on utilization (“Is everyone busy?”).

Walking the board makes flow visible every day:

• You see aging items (stuck tickets).
• You see WIP overload (too many things started, nothing finished).
• You see review / testing bottlenecks.

And once you see those, you can actually fix them.

Standups That Don’t Suck = Higher Delivery Performance

Teams I’ve coached that switched to walking the board typically see:

• 10–30% reduction in cycle time within 2–3 sprints, just by:

  • Reducing WIP.
  • Swarming on stuck items.
  • Making reviews and testing explicit priorities.

• Shorter standups (often 8–12 minutes) because:

  • You stop listening to 10 variations of “no blockers”.
  • You only talk about work that matters today.

Is walking the board a silver bullet? No.
But it’s a simple, concrete change that moves you away from “ritual” and toward “results.”

---

How to Run a Standup by Walking the Board

Here’s a practical, step-by-step way to do it.

1. Make Your Board Reflect Reality

You can’t walk a board that’s lying to you.

Before you change your standup format, clean this up:

• Columns that actually mean something
  Avoid vague “Doing” or “Ongoing”. Use states that match your workflow:

  • To Do
  • In Progress
  • In Review
  • In Test (if relevant)
  • Ready for Release
  • Done

• WIP limits (even soft ones)
  Put numbers at the top of columns:

  • In Progress (max 4)
  • In Review (max 3)

• One ticket = one piece of work
  If a ticket is so big it lives in “In Progress” for 6 days, it’s not agile; it’s wishful thinking.

If your board doesn’t match reality, your standup is theater.

2. Start on the Right, Move Left

In the standup:

1. Share the board (physical or digital).

2. Start with the rightmost active column (usually “Ready for Release” or “In Test”).

3. For each ticket, ask:

   • “What’s blocking this from Done?”
   • “Who’s taking the next step, and when?”

4. Move left: “In Review”, then “In Progress”, then “To Do”.

You’re training the team to finish before starting.

3. Talk About Work, Not People

Ban the “round robin” by name. Instead:

• Use ticket IDs or short titles:
  “Let’s talk about API-231 (payment service timeout).”

• Involve only the people relevant to that ticket.
  Everyone else listens for:

  • Dependencies.
  • Opportunities to help.
  • Conflicts with their own work.

• Keep it tactical:

  • “I’ll pair with you after lunch.”
  • “I’ll review that before 11am.”
  • “Let’s book a 20-minute follow-up after this.”

If someone drifts into design debates or long explanations, cut it off:

“This sounds important, but not for the standup. Let’s park it and schedule time right after.”

4. Make Aging Visible

Add simple visual cues:

• Aging markers:

  • Color tags or labels for tickets older than X days in a column.
  • Example: “If it’s been in ‘In Progress’ for 3+ days, we talk about why.”

• Questions to ask:

  • “Why is this still here?”
  • “What’s the smallest next step?”
  • “Do we need to split this?”

The goal is not blame. It’s early risk detection.

5. End with a Quick Alignment Check

After walking the board, take 60 seconds to align:

• “Is anyone starting something new today?”
  If yes:

  • “Does that make sense given our WIP and priorities?”

• “Any cross-team dependencies we’re ignoring?”

Then stop. Don’t turn it into a planning session.

---

Common Mistakes When “Walking the Board” (What Not to Do)

Switching formats won’t magically fix a weak culture. Here are traps to avoid.

Mistake 1: Still Treating It as Manager Status Time

If the most senior person:

• Opens every ticket.
• Asks all the questions.
• Makes all the decisions.

…you’ve just changed the script, not the movie.

Fix it:

• Rotate who facilitates the standup weekly.
• Ask team members to pull the conversation:
  • “Who’s on this ticket? What’s next?”

The standup is for the team, not for leadership.

Mistake 2: Ignoring WIP Limits

Walking the board only works if you respect WIP.

If you see:

• “In Progress” column overflowing.
• People starting new tickets while others sit in review.

You’re just watching your bottlenecks in HD.

Fix it:

• When a column hits its WIP limit:
  • No one starts new work.
  • People help move existing tickets rightward.
  • If that’s impossible, you revisit the WIP limit itself.

WIP limits are constraints you learn from, not rules you ignore.

Mistake 3: Turning It Into a Problem-Solving Meeting

A good standup surfaces problems. It does not solve them in detail.

Symptoms you’ve gone off track:

• Standup regularly runs 25–30 minutes.
• You’re whiteboarding architecture.
• Half the team is silently checking email.

Fix it:

• Introduce a “parking lot”:

  • When a topic needs deeper discussion, write it down.
  • At the end, schedule a follow-up with the relevant people.

• Timebox:

  • Aim for 10–15 minutes max.
  • If you’re consistently over, your tickets are too big or your board is a mess.

Mistake 4: Not Updating the Board in Real Time

If all the updates happen during the standup, your board is stale.

Warning signs:

• Tickets move multiple columns during the standup.
• People say, “Oh yeah, I finished that yesterday, I’ll move it now.”

Fix it:

• Expect updates as work happens, not once a day.
• Use the standup to inspect, not to data-enter.

---

How to Transition Your Team Without Chaos

Changing a ritual people are used to will feel uncomfortable. Do it deliberately.

Step 1: Explain the “Why” in Concrete Terms

Don’t say, “We’re doing Kanban now.”
Say:

• “We want to finish more, start less.”
• “We’re spending 15 minutes a day on status and still getting surprised.”
• “We need to see bottlenecks earlier.”

Tie it to pain the team already feels:

• Last-minute testing crunch.
• Surprise carry-overs every sprint.
• PRs sitting unreviewed for days.

Step 2: Try It for 2 Weeks as an Experiment

Frame it as:

“For the next 2 weeks, we’ll walk the board in standup. After that, we’ll decide what to keep, change, or drop.”

Then:

• Keep it simple: no new tools, no fancy metrics.
• Ask for feedback in your next retrospective:
  • “Did this help you understand what really matters today?”
  • “Did we reduce surprises?”

Step 3: Adjust the Board Based on What You Learn

Common tweaks after a couple of weeks:

• Split “In Progress” into:
  • “In Dev”
  • “Waiting for Review”
• Add an explicit “Blocked” column.
• Tighten WIP limits where work piles up.

Your board should evolve as your understanding of your flow improves.

---

Tactical Tips to Make Walking the Board Actually Stick

Use these to avoid backsliding into old habits.

• Stand up and face the board (even on Zoom/Teams):

  • Share screen.
  • Keep cameras on if possible.
  • The board is the center of attention.

• Start at the same time, every time:

  • Late arrivals catch up by looking at the board history, not by rehashing.

• Define “Done” clearly:

  • If “Done” actually means “deployed and observable in production,” write that down.
  • Don’t hide unfinished work behind vague “Done” statuses.

• Use simple flow metrics (lightweight, not a dashboard explosion):

  • Track:
    • Average cycle time.
    • Number of items carried over each sprint.
  • Review in retros, not every standup.

• Protect focus:

  • No laptops/phones for unrelated work.
  • No Slack side conversations.

---

Tools That Help (Without Taking Over)

You don’t need fancy tools to walk the board well, but a few things help:

• A board that’s easy to update (Jira, Trello, Azure DevOps, etc.).
• Lightweight ways to run quick planning and retros so your board stays meaningful.

For example, teams I work with often use ScrumPoi for fast planning poker and retros: it’s free for teams, supports anonymous voting to reduce anchoring bias, and plugs into Jira so the work you estimate or discuss actually flows onto the board you’re walking.

---

Conclusion: Stop Talking About Work. Start Moving It.

Daily standups shouldn’t be a ritual where everyone proves they were busy.

They should be:

• A short, sharp check-in on the flow of work.
• A way to spot bottlenecks early.
• A daily chance to recommit as a team to getting things done.

Walking the board does exactly that:

• You focus on the work that matters today.
• You finish more and carry over less.
• You replace status theater with real collaboration.

If your standup feels like a chore, don’t add more rules.
Change the game: start with the board, walk right to left, and make Done your daily north star.