One weekend, I looked across my team’s commit patterns and came back to our standup with a different question: were we using the meeting to coordinate, or just to report activity? I changed the check-in to focus on blockers, handoffs, and the next useful step. The commit log helped me ask the question; it could not tell me who was productive or why work was moving as it was.
What a commit log can—and can’t—show
Commits are traces of work recorded in a repository, not a complete account of software development. They can prompt questions about when work is landing or where coordination may be needed. They do not, by themselves, establish an individual’s productivity, the value of a change, or the reason a stretch of work is quiet. Design discussions, review, debugging, planning, and helping a teammate may not appear as a neat sequence of commits.
As an Amazon Associate I earn from qualifying purchases.
So I treated the patterns as context, not a scorecard. I did not rank people or infer intent from activity. The useful question was whether our existing check-in helped us connect work, surface dependencies, and decide what needed attention next.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What I changed in the standup
I shifted the conversation away from a round of task-by-task status updates and toward coordination: what is moving toward our shared goal, where someone is blocked or waiting on a handoff, and what needs a decision or help today. The point was not to add more reporting about commits. It was to leave the meeting with a clearer shared picture and an actionable next step.
#1 Best Overall
- The Five Dysfunctions of a Team
- English
- hardcover
- First Edition
- gelatine plate paper
That is a change to try with a team, not a guaranteed fix. A standup that does not produce information, problem-solving, or a useful plan may be consuming time without earning it. A 2016 grounded-theory study of 12 software teams across three companies—drawing on interviews with 60 people and observations of 79 daily standups—associated information sharing and opportunities to discuss and solve problems with positive attitudes. Manager-directed status reporting and meetings experienced as too frequent or too long were associated with negative attitudes. Those findings describe the teams studied, not a universal forecast for every meeting. 2016 study of daily standups
Make the meeting serve a goal
For Scrum teams, the Daily Scrum is meant to inspect progress toward the Sprint Goal and adapt the plan, not simply recite completed tasks. The 2020 Scrum Guide calls it a 15-minute event for the Developers of the Scrum Team and lets them choose its structure as long as it focuses on the goal and results in an actionable plan. It does not require the familiar fixed script of three questions. The 2020 Scrum Guide
Rank #2
That guidance is useful even if your team does not use Scrum: start from the coordination problem the check-in is supposed to solve. A meeting can be brief and still waste attention if it produces no shared understanding or next move. Conversely, a live conversation can be worthwhile when people need to resolve a blocker together.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose live, async, or a different cadence deliberately
There is no categorical answer in the cited evidence that asynchronous updates are always better than a live standup, or vice versa. The right arrangement depends on what your team needs to coordinate and what interruption it can tolerate. GitHub’s developer-experience research describes collaboration as a mix of synchronous and asynchronous touchpoints—such as chat, documentation, pull requests, issues, and well-run meetings—and also highlights uninterrupted work time. GitHub developer-experience research
Rank #3
- Author: Bungay Stanier, Michael.
- Publisher: Page Two
- Pages: 244
- Publication Date: 2016-02-29
- Edition: 1
- Keep a live check-in when the team needs quick discussion, shared context, or help unblocking work.
- Try an async update when the main need is a written status signal and a live meeting is mostly interrupting focused work. Keep a route open for discussion when an update raises a problem.
- Adjust the cadence or length if the meeting feels too frequent or routinely runs long, while checking that blockers and dependencies still become visible in time.
These are options to test, not evidence-backed rankings. Whatever format you choose, look for information sharing, visible requests for help, and a clear next action without creating a status-report ritual.
Why the same standup can feel different to different people
In a 2017 survey of 221 professional developers, 87% of respondents who used agile methods said they used daily standups. Respondents’ average view of the meetings was neutral, but attitudes varied: junior developers were more positive on average, while senior developers and people on larger teams were more negative on average. This is a survey result, not proof that seniority or team size causes a particular view. Stray, Moe, and Bergersen’s 2017 survey
A separate 2018 study observed 102 daily standups and interviewed 60 members of 15 teams in five countries. Its researchers found that making the practice beneficial for the whole team can be challenging and proposed changes to improve it. Together, these studies are a reason to ask your own team how the meeting works for them rather than assume everyone experiences it the same way. 2018 study of daily standups
Recommended Free Tools
Run a small standup experiment
- Name the problem. Pick one issue the check-in should address, such as missed handoffs, blockers discovered too late, or a meeting dominated by task reporting.
- Change one thing. For a short trial, adjust the prompt, format, length, or cadence. Avoid changing several parts at once if you want to understand what helped.
- End with a next step. Ask what decision, coordination, or help is needed now, and who will follow up. In Scrum, connect that plan to the Sprint Goal.
- Ask the team what changed. Check whether people have a better shared picture, blockers are surfaced in time, and the meeting creates less unnecessary interruption. Include people who are newer, more experienced, and working across different parts of the team.
- Keep, revise, or stop. If the trial does not improve coordination, change the format again or reconsider whether a recurring meeting is needed for that purpose.
My weekend with the commit patterns was useful because it led me to question the meeting, not because the repository held a definitive verdict. A check-in earns its place when it helps the team coordinate toward its goal and decide what to do next.
Quick Recap
Best Value
- Author: Gordon, Jon.
- Publisher: Wiley
- Pages: 192
- Publication Date: 2007
- Edition: 1
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
