I've been in "10 minute" standup meetings that routinely went for an hour and a half.
And invariably, it's always the head of the meeting (the scrum master or manager) that's the one who both causes the meeting to go long, and who keeps telling the team that we can't keep wasting so much time in meetings.
When you report a problem with a system and the manager's response is to log into the system, in the meeting, drill down to where the problem was reported, and keep peppering the person with questions about the problem, you're not meeting, you're debugging.
Meeting managers, here's a hint. If you're logging into remote systems, bringing up XML files in an editor, or tracing through a git branch in a status meeting, that's not reporting status, that's working on the problem. And while you're doing that with the one guy who reported the issue, the other 15 people in the meeting are twiddling their thumbs as you explain XSLT syntax.
Oh, God, this. This soooo much, and it's always someone higher up you can't kick out. 😭
I've been in "10 minute" standup meetings that routinely went for an hour and a half.
And invariably, it's always the head of the meeting (the scrum master or manager) that's the one who both causes the meeting to go long, and who keeps telling the team that we can't keep wasting so much time in meetings.
When you report a problem with a system and the manager's response is to log into the system, in the meeting, drill down to where the problem was reported, and keep peppering the person with questions about the problem, you're not meeting, you're debugging.
Meeting managers, here's a hint. If you're logging into remote systems, bringing up XML files in an editor, or tracing through a git branch in a status meeting, that's not reporting status, that's working on the problem. And while you're doing that with the one guy who reported the issue, the other 15 people in the meeting are twiddling their thumbs as you explain XSLT syntax.