Assuming you have a Kanban board for your work, and assuming the work is actually accurate on the board in terms of status (which most teams are terrible at without practice) AND assuming you properly have “waiting for testing” “testing” “waiting for review” “reviewing” columns (those waiting for columns are critical to seeing the true state of work), then you simply just “walk the wall” from right to left. As you scan through each column, team members call out if shit is a mess, otherwise you just get a thumbs up and move to the next thing.
Then, just use some analytics to highlight tickets stuck in a status too long, and bubble those up in the standup. “You keep saying this is on track, but it’s been here for a week, what’s the deal?”.
STANDUPS ARE NOT STATUS UPDATES. They’re for resolving blockers in person without letting shit linger too long.
As long as your board is accurate and respected as the source of truth, it is the status update mechanism. It’s no longer a human job.
(And yes, this is actually possibly, my agility team does this with 15+ scrumban teams right now)
