7 ms·
> ...everyone gets just a couple of minutes to sum up where they were yesterday, where they're going today and what's holding them up. Peer-to-peer, listing bl
by humanrebar 10y ago
> ...everyone gets just a couple of minutes to sum up where they were yesterday, where they're going today and what's holding them up.
Peer-to-peer, listing blockers is more or less the only thing that matters, followed distantly by making sure we're not stepping on each other (deploying the same thing, refactoring the same class).
It's also important to sync up that designs are good and work together, but that's outside the scope of Agile (and standups).
The bulk of the info in the yesterday-today-blockers standup is to let the manager get a quick rundown of what the employees are up to. It's a management tool, basically. And that info is all duplicated (if you're doing it correctly) in the agile board, the burndown chart, and in the version control system. So management could just create better queries and dashboards on top of existing data and get the same information.
- Nursie 10y agoWe've run the standups like that with no management involvement at all in some places. I still find them useful as they allow people to resolve dependencies a schedule work appropriately. Those other tools have a tendency to get ignored, get out of sync, out of date and add overhead.
- humanrebar 10y ago> Those other tools have a tendency to get ignored... That's basically my point. Managers should home their craft and improve their tools instead of molding the people around them to meet the needs of middle management.
- Nursie 10y agoWell, I'm not sure that the daily standups have always been about that, and as a developer I've found them useful.
- humanrebar 10y agoI've found them useful, but only to the extent that they focus on burndown and not presenting status reports to management while the rest of the team listens.