Ask any engineering lead two questions:
- What does your project board say is in progress right now?
- What did your team actually merge in the last 48 hours?
If those answers match, your team is the exception. For most, the board is a work of historical fiction — updated in standups, polished before reviews, and quietly diverging from the repo the rest of the time.
Why the drift is structural, not personal
Ticket trackers only know what humans type into them. Engineers, correctly, prioritize shipping over bookkeeping. So the card moves when someone remembers — usually right before the meeting where it’ll be discussed. Multiply by every task and every day, and the board becomes a lagging indicator of what people reported, not what shipped.
The failure modes are always the same:
- “In review” for nine days — the PR merged a week ago; nobody moved the card.
- “Almost done” — the card moved; the code is on a branch that hasn’t seen a commit since Tuesday.
- Done-but-not — ticket closed, CI red, feature flagged off, customer sees nothing.
What the gap costs
- Status meetings exist to reconcile it. Most standups and status calls are just diff-checking the board against reality, verbally.
- Leads make decisions on stale data. Hiring, deadlines, scope — all priced off a board that’s days behind.
- Trust erodes in both directions. Engineers feel surveilled; managers feel lied to. Nobody is lying. The system is lying.
The fix: make the repo the source of truth
Code doesn’t forget to update its status. A merged PR is done. A failing CI run is not. A branch with no commits in five days is stalled, whatever the card says.
So the habit is simple to state: stop asking people to report status, and start reading status from the artifacts. Put commits, PRs, and CI next to the tasks they belong to, and the board stays honest with zero bookkeeping.
That’s exactly what Kahoona does — whiteboard, project board, and live GitHub activity in one workspace. Point it at your repo and your first project builds itself in ~30 seconds. Free to start.
👉 See what your team is actually shipping
Go deeper: How to run async standups from your GitHub activity · 9 best Jira alternatives for small dev teams