4 ms·
Agreed. This is yet another source of distraction for actually getting things done, and turns into side discussions of tangential topics far more often than a
by dogcomplex 4y ago
Agreed. This is yet another source of distraction for actually getting things done, and turns into side discussions of tangential topics far more often than a useful source of information. Beats wasting everyone's time asking questions in a standup, but should at least be understood to be very asynchronous with no need for timely replies lest it become an attention hog. Might favor just setting aside time for devs to add to a wiki document about their area of the system than just being always available for individual questions.
- chiefalchemist 4y agoAgreed. This is yet another source of distraction for actually getting things done Yes and no. Yes, some individuals might suffer in the short term from the friction. No, the lack of that friction is not good for the team. The context (i.e., article) is collaboration. That's not about individual GTD, it's about the health and long term well being of the team. Granted, there are non-team situations but if size and or scale are involved that's less likely. A non-dysfunctional team has overhead. Skip that and while you may not have a dysfunctional team, you'll have a suboptimal one. Either way, that creates friction. The messy shitty kind.