5 ms·
I see the value in daily communication and the general topics (yesterday, today, blockers) of the dailies, but at the same time the daily standups show how the
by petetnt 7y ago
I see the value in daily communication and the general topics (yesterday, today, blockers) of the dailies, but at the same time the daily standups show how the in general much of the modern work and communication has moved to asynchronous methods but the text book example still requires the events to happen in a synchronous way (eg. standup at 9 am) which obviously causes issues.
Then you move forward to move say the dailies in Slack, at which point they just get posted whenever people see fit, which sort of works unless the problems themselves need to be solved synchronously, as it is with many cases and they easily just end up being status reports instead of actual planning.
- celticmusic 7y agoI know, right? How would two consenting adults ever work together to solve problems by communicating? Thankfully we have them stand up daily, without which they'd both just continually walk into the wall like lemmings.
- petetnt 7y agoYou joke, but the "engineers engineer until ready don't break flow" trope is one of the most dangerous things that can happen to a project which is why putting emphasis on _daily_ communication (not just communication) is kinda important.
- matthewmacleod 7y agoI know you're being facetious but basically yes. Some developers are great at working together and communicating with no formal structure in place. I have found over my career that maybe 50% of developers are absolutely appalling at doing so, and prefer to continue stumbling round in the dark. This applies even to developers who are reasonably technically competent. For these people, the enforced daily standup solves that problem.
- twic 7y agoDon't lemmings turn round when they hit a wall?
- celticmusic 7y agoYou're thinking of a Rhoomba :P