2 ms·
You can't use methodology to change what is largely a people-problem. Your projects are failing not because you didn't have daily status meetings correctly, the
by moron4hire 11y ago
You can't use methodology to change what is largely a people-problem. Your projects are failing not because you didn't have daily status meetings correctly, they're failing because your organization has a culture of lying to itself about work. Thinking you can fix that by fixing daily status meetings is a symptom of that culture.
A daily status meeting is about seeing what is going on, comparing that to what needs to happen, and changing course if necessary. You don't need a checklist of how to do that. If you can't figure out how to communicate with people you see every day on those points, then I don't know if you're clever enough to figure out how to write code in the first place. You're fired. Pack up your things and get out.
I've seen way too many organizations use "we're standing up" to mean "therefore, we're having a productive meeting". I've seen places do 50-person standup meetings. Yes, they would go two hours. I've seen other places get the number of people right but do full-status-report standup meetings. Yes, they would also go two hours. That's a quarter of your work day, probably half of your productive work day, just wasted on an emotionally draining process.
Last time I had daily status meetings that worked, I had my entire team in one room, we had a large whiteboard with every task we were working on between us, and when everyone got in, had their coffee, got through their emails, I would turn around in my chair, ask if everyone was ready, and we'd just go through the list. We would scratch things off when they'd get finished, so we always knew who was getting what done anyway, and everyone had their names next to what they were working on, so we knew what they were working on already. It was mostly just a chance for someone to ask for help on something. It took about 15 minutes. If new tasks didn't fit on the board, they didn't fit in the team's workload.
I think there is something to be said for not placing the focus on individual contributors but on the tasks as a whole, on the team as a whole. My meetings didn't pit people against each other, "oh, Jim got 3 things done yesterday and has never been blocked on 1 thing for over a week, but Dave has made zero progress on his task since two days ago. Shame, Dave, shame. Let us not question whether the task was specified correctly or appropriately broken down."