3 ms·
I've been on "all" sides of that table, and I've had teams where I had to force daily calls to get people to stay focused, and teams where I could chase people
by vidarh 4y ago
I've been on "all" sides of that table, and I've had teams where I had to force daily calls to get people to stay focused, and teams where I could chase people individually, but the aggregate amount of team members time I've needed to spend to stay up to date have tended to stay relatively similar.
Key thing being, if your standup is a large proportion of the time you spend closing those feedback loops, it's likely your standups are much to long or your one on one follow-up may be on the low side. But there are also all kinds of exceptions - a team of very senior people who know each other can often do with less, for example.
Lest you think I like meetings, one of the most effective "meeting killers" I put in place at a past team was a weekly report where I got HR to give me average salary numbers across the different job functions and added up the salary cost per work item, with meetings broken out.
The number of meetings plummeted when people saw the opportunity cost in dollars as a proportion of salaries to put a dozen engineers in a room for an hour. I absolutely loathe pointless meetings. But it's important to be aware of what function a given meeting actually serves before deciding whether or not it's pointless.