[chimprich]

I agree with this. By far the least useful of the standard standup questions is "what did you do yesterday".

Focussing on the work to be done puts the emphasis on teamwork and skips the pressure on people to justify themselves or play politics by showing off.

That's assuming everyone is doing the work and they're being trusted to do the work. If that's not the case, then you have bigger problems than the format of your daily standup, and standup is not the best time to address them.

[Fire-Dragon-DoL]

We have been trying to show what we did code-wise (or explain if it was something that didn't end up with code). The goal however, is to show some coding practices or new functions created that other team members might find useful, as well as working as a brief "review" of the code itself.

The goal is not to explain what you did. Happy with the approach because knowledge is actually spreading across the team currently. Meeting do get much longer though (1 hour usually), but time is recovered mostly on code reviews which become shorter. Usually lot of discussions sprouts out of this, leading to better code overall.