Ah the daily standup. A time for the team to gather around their project board and discuss how things are going. Or, more likely, an opportunity to rattle off a bunch of ticket IDs and get back to actual work.
Standups can be super useful when used properly. Most standups I see happening could be a status report, or be tracked in Jira or whatever system being used.
This isn't a time for managers to get status updates on work in flight. If a manager needs to gather that level of context from a standup they either don't know where to find that information, the information doesn't exist, or they are lazy. If the info doesn't exist then you've got much bigger problems to solve.
Your system (Jira) should provide the current status of each work item and relevent comments as progress is made. Save time in the standup by not talking about tickets.
Standup isn't a performance management tool. You can't look at a person's standups to determine their productivity. You also can't look at a team's performance by their standup reports. That's crazy talk.
The three common standup questions are:
It's easy to see how a standup becomes a status report with these questions. The questions aren't really important. What is important is the cohesion and alignment that comes from continuously inspecting our work. With that in mind, here is what I think these questions are really after:
This is a conversation, not a report. It will surface action items and follow up discussions that will sharpen alignment. If done well a standup offers opportunities for team members to pair and work together. It also helps surface risks or problems that might need action asap.
Make your standup a conversation about the work being done. That is where the value is.
Every day? It depends. How new is the team? How aligned have they been in the past? Will there be value added to the project by stopping and inspecting more regularly, or is the scope clearly defined and we just need to execute.
Standups shouldn't happen by default. Put thought into whether standups will help the team, or feel like yet another management technique that makes engineers feel like big brother is watching.