4 ms·
I'm a PM and this does not resonate with me. If you're getting status twice a day... I think something is very wrong. The brutal truth of software development
by tschwimmer 7y ago
I'm a PM and this does not resonate with me. If you're getting status twice a day... I think something is very wrong.
The brutal truth of software development is that the quality of your output is going to vary with the quality of the engineers you work with. Good engineers don't need daily standups to build great products, and bad engineers aren't going to be helped by doing twice-daily checkins.
- parasubvert 7y agoI think you'd need to experience the flow of a place like Pivotal before passing judgement. I find it interesting that you've immediately jumped to "good vs. bad engineers". The mindset at Pivotal tends to be that all engineers are equal. There is no good or bad. This is why they rotate pairs. Checking in with a pair isn't a status update, it's really about collaboration and visibility. Estimates are often wrong, assumptions get tested, the team dynamic is "let's ensure we all understand this". Stories in tracker tend to be <1 day, so checking in occasionally isn't exactly a wrong thing (every half day to me is excessive), so priorities can be shifted, or big stories can be broken up.
- srean 7y agoCan you please clone as many copies of yourself sir. That would be task 1154162 on the dashboard.
- abc_lisper 7y agoI think you jumped the shark here. The point of doing multiple checkins a day is to make good engineers feel like they are barely good enough, and make them hungry to please the bosses! Pavlov at work here, I think.
- targonca 7y agoI'm not sure you're using "jumped the shark" correctly.
- abc_lisper 7y agoSorry. I should have read before using that phrase.