3 ms·

"A team of say 10 people will quickly fragment along e.g. backend / frontend lines in my experience, both in general exchange and code review." Then you effect

"A team of say 10 people will quickly fragment along e.g. backend / frontend lines in my experience, both in general exchange and code review." Then you effectively have two teams, isn't it? I've been in the exact situation before and that's the conclusion we've reached. With a very conservative two minutes per update and the absolute best conditions, you've got a 20 minutes standup at the very strict minimum, and that's with military discipline. How do you get to 10 minutes? At this point, you're either not saying anything important or not having any discussion. In both cases, everyone would save time either typing a one line status update on slack, or having more thorough and focused discussions outside of standup.

beingflo 5y ago
> Then you effectively have two teams, isn't it? I've been in the exact situation before and that's the conclusion we've reached. In principle, but that doesn't mean you get two PMs now or that the customer makes a meaningful distinction between that two. > With a very conservative two minutes per update and the absolute best conditions, you've got a 20 minutes standup at the very strict minimum, and that's with military discipline. How do you get to 10 minutes? We tend to give a very short update on what we're working on and what problems we have encountered, 30s - 1 minute I would say. Then there might arise some quick interaction, oftentimes leading to more discussion outside of the daily with the people involved. We have ~10 teams operating this way, works just fine for everyone.