Earlier quoted context omitted.
> CS graduates from MIT and Stanford could be expected to justify hours of their time in "Scrum ceremonies" (which means that they aren't trusted, which means that their credentialing institutions and work experiences aren't trusted). Even average programmers in the bowels of Fortune 500's IT organizations had more autonomy than the typical "Agile" programmer today. If that's been your experience with Agile, you've h…
"Seriously, stand-up isn't supposed to be about accounting for your time" And yet, in most places, it devolves into just that. "In my (very positive) experience, stand-up is about maintaining situational awareness in the team." And how could this not be more easily done with bug trackers and status emails? "it's an opportunity to pick the collective brain and gain some clarity / help with what you're doing." Most peo…
As far as I'm concerned, bug trackers and status emails are functionally equivalent to stand ups at a scrum board. I find email to be a terrible form of communication for open-ended discussion and would much rather do so face to face, but it's self-evidently a matter a personal preference.
> "Seriously, stand-up isn't supposed to be about accounting for your time" > And yet, in most places, it devolves into just that.
The fact that some people do it wrong is a straw man.
> "it's an opportunity to pick the collective brain and gain some clarity / help with what you're doing." > Most people don't pay attention to other's updates; especially updates that they know aren't relevant to what they're working on.
I've always found people are pretty good at picking up on the verbal cues when somebody's asking a question and answering it, even if they weren't paying particularly close attention.