> he usefulness of people telling what they will be doing or what problems they are facing at the moment is that they might not know there is somebody else in t

> he usefulness of people telling what they will be doing or what problems they are facing at the moment is that they might not know there is somebody else in the team that can help them solve this problem very quickly. I have worked on teams of chickens running around with their heads cut off before. While that is one way to try and rein them in, would you not be better served by moving away from making and instead towards engineering? > I also like to think it puts a little bit of pressure on people to get something done so they can show some progress on the next standup. From experience, initially it does. But soon you realize that when you're racing the clock you end up taking shortcuts (introducing bugs, making poor design decisions, not properly documenting your work, etc.) that will harm you and your team later. Appearances aren't worth sacrificing the company over. It is far better to be seen as a poor employee than to be seen as the superhero of a failed business.