[wpietri]

> hint: you probably don't unless you are manager/team lead/product owner

Depends on how you're working. I prefer a collective responsibility model. I know some people prefer to have their units of work spoon-fed to them, and are willing to trust some manager that everything will fit together in the end. But especially at startups, I think things go better when everybody feels responsible for the results.

I do agree that minimizing 1 and 2 is good, but I think you can get a lot of that just by holding the meeting around a physical Kanban board and letting people point at things.

[swanson]

Sure - definitely agree with you on seeing all the pieces fit together. I get a way better picture of that with other methods (Kanban, story map) than from someone listing which classes they wrote yesterday.

Once you learn to "read the board" as a team, 1/2 can largely go away. And the best part is that the board is asynchronous - I can go look at it whenever I want without bothering anybody.

[wpietri]

If people are actually listing classes in the stand-up, I agree that's a problem. For me the stand-up "did yesterday" content is more, "We worked on X and have it almost finished. In the course of that, we made a neat utility for X, and cleaned up some ugly code in Y. If anybody wants to talk about refactoring Y further, let's talk."