“Our roadmap used to be a slide that was wrong by Wednesday. Now it is the work, and the Friday update writes itself from what merged.”
Two trackers, one argument
Nimbus runs deploys for 9,000 development teams. Its platform engineers lived in one tracker and its product engineers in another, and every Thursday twelve leads met for an hour to make the two agree. They rarely did.
“Every number on the roadmap slide came from someone’s memory,” says Théo Gagnon, VP Engineering. “We spent three hours a week in status meetings and still found out about slips from customers.”
Let the merge do the talking
Nimbus moved all nine teams into one Keel workspace over two weekends, then connected Burrow. Engineers copy the branch name from the issue (⌘⇧.), and from that point the pull request moves the issue: In progress on the first push, In review when the PR opens, Done on merge.
- 94% of issues now close on merge without anyone touching them.
- Reverts reopen the issue with a comment, so a rollback is never silent.
- Tripwire files regressions straight into the owning team’s triage inbox.
A roadmap drawn from the work
Projects in Keel are made of the same issues, so the roadmap fills as branches merge. Project health comes from projected finish against target date. When “Edge regions” slipped in October, the roadmap showed it on a Tuesday, eleven days before the target.
“We used to ask leads how their project was going. Now we read the update Keel drafted, and ask about the one line that looks wrong.”
The Thursday meeting is gone. Three of the four status meetings went with it; the one left is a 20-minute review of projects marked at risk.
A year on
| Two trackers | Keel | |
|---|---|---|
| Issues closed by merge | 0% | 94% |
| Status meetings | 4 a week | 1 a week, 20 min |
| Teams on the roadmap | 2 views, 1 slide | 9, live |