5 ms·
The biggest problem with standups is that they inevitably balloon into all-encompassing, dragging status meetings where 95% of the stuff discussed is not releva
by thrower123 5y ago
The biggest problem with standups is that they inevitably balloon into all-encompassing, dragging status meetings where 95% of the stuff discussed is not relevant to more than one or two people present.
The other problem with standup meetings, although this is more of an issue back in the before-times when we actually went to the office, is that they turn into a de facto clock-in time. If the standup is at 10 AM, then over time, nobody bothers showing up until 9:55, because there's not sufficient time to do anything worth doing before being interrupted the standup, and if you had plans for the day, they'll get tipped ass-over-beanbox by some new urgent request from somewhere at the standup.
I'm deeply envious of those fabled software developers of the past, before the Agile Manifesto, who were allowed to go work by themselves in a room for a whole day at a time, sometimes even two or three days. What luxury! Just imagine what you could do without people poking you with a stick every hour or so?
- malermeister 5y agoThe waterfall bogeyman agile types conjure up honestly sounds like such a nice way to work. You get requirements that don't change and you get time to implement them without bullshit status meetings interrupting? When did we decide that was a bad thing? And how did we get brainwashed into thinking agile was better for ICs?
- ajaynomics 5y agotime for "agile waterfall?" ;)
- thrower123 5y agoIs this the one where we have all the Agile gymnastics, but we're still locked into a featureset and a timeframe by management, or the one where we do 2-week waterfalls and call them sprints? To be honest, I'm usually in a purely reactive mode most of the time. Planning what work I'm going to even do tomorrow is not really possible, until I see what crap has been landed on my calendar overnight...