For the stand-up meeting, teams commonly use a format which aims to be both quick and comprehensive:
- The team stands around the task board.
- Each team member, in turn, describes what they achieved yesterday, what they intend to achieve today, and what blockers they may be facing.
- Aim to keep the meeting short and less than 15 minutes.
- That’s it!

Using this format, people are often more focused on being busy than actually progressing the work, so let's switch to a model where Work Items attend rather than people.

What is a snapshot of the current project progress? The task board!
So, instead of hearing each team member in turn, let's hear a summary of each task on the board.

How do we decide what order to go through the tasks on the board? Walk the board from right to left!
The goal of each story is to get it done; so what does this story need to jump to the next column?
For example, a common question could be: “What needs to be done to move this story to QA? Do you need any help?”
By asking these questions to move the project along, you’re creating a more organized workflow so your team can accomplish its goals in a step-by-step manner.

This approach ensures work that is closest to completion, and has had the most time invested in it (therefore most valuable in terms of effort), is discussed first. As each work item is covered, the board walker can ask the team members working on the story to report on progress and if there are any issues. The whole team can join the discussion if they can see any way to help progress.

Walking the board also helps reduce the time it takes for work to get across the board and into production. Whenever a team member completes a task they can view the board and ‘walk’ it in their head. When they get to a task they can help with, they can jump on it. For example a developer may notice that a release is ready that they can arrange to deploy to production immediately rather than picking up a new task from the backlog. Another example might be a bug found on UAT that is holding up the next release. The developer can start fixing the bug immediately to get UAT back on track rather than picking up new work from the backlog.

Obviously having a board is a pre-requisite which not all teams will have. In that case, a person-by-person structure is more appropriate. Moreover, the difference in the process is subtle if only one person is working on that particular story, however if multiple people are actively working on the story you will see the difference.
I can definitely say that changing to a different format has dramatically improved the speed and usefulness of the daily sync.
It will shift the focus to the story and promote coordination.
Give it a try, you won’t regret it!

Source:
This post was inspired by https://www.audiodog.co.uk/blog/2017/12/10/better-stand-up-by-walking-the-board/