5 ms·
> Also part time devs might not commit to daily meetings Daily meetings kill flow
by nextaccountic 5y ago
> Also part time devs might not commit to daily meetings
Daily meetings kill flow
- wpietri 5y agoThey don't have to! I've worked at places with very low meeting load. A first-thing, 15-minute daily standup (with the team actually standing in a circle and going over how to share the day's work) can be lively and energizing, which helps me get into a flow state once I sit down to code.
- lupire 5y agoWhat happens to everyone who doesn't start work at exactly the same minute you do? > 15 minute standup. It's literally called a "standup" to enforce the most important rule: it should be much shorter than 15 minutes.
- wpietri 5y agoNormally I'm an early arriver, so in those conditions I generally take care of non-coding stuff. If I run out of that, I start in on the coding work. Thanks, I'm familiar with why it's called a stand-up. On my teams the go-through-the-kanban-board phase of the meeting is generally faster than that. But that phase also tends to spark post-standup discussions. "Oh, you want to work on that subsystem too? Let's talk a bit about where we want to take it." I think it's better if people allocate time for that, which is why, especially in places like this, I'll talk about it as I did.