From three-hour planning marathons to ninety minutes — every sprint
When Marcus Osei joined Acme Engineering as Engineering Director three years ago, the first thing that struck him wasn’t the technical debt. It was the calendar. Every other Monday, eighty-five engineers across six product squads would block out three to four hours for sprint planning ceremonies that left everyone drained before a single line of code was written.
“We had smart, motivated people sitting in rooms re-explaining context that should have already been visible to everyone,” Marcus said. “A senior engineer billing at our internal rate costs real money. Multiply that across eighty-five people, twice a month — the math is uncomfortable.”
The coordination tax was killing velocity
Acme Engineering builds infrastructure tooling for mid-market financial services companies. Their work is complex by nature: tight compliance requirements, overlapping dependencies between squads, and a product surface that demands constant cross-team communication. By early 2024, the team had grown from forty people to eighty-five in under eighteen months, and the planning process hadn’t scaled with them.
Before Pulse, Acme used a combination of a legacy ticketing tool, shared spreadsheets for capacity planning, and a rotating cast of Slack channels that nobody could quite keep track of. Story pointing happened in real time during planning calls, which meant engineers were making estimates cold, without adequate context, while twenty other people waited.
“We were losing roughly 340 engineer-hours every single sprint just to planning overhead,” said Priya Natarajan, Acme’s Head of Engineering Operations. “That’s before you count the time spent updating trackers after the meeting, correcting stale estimates, or chasing down dependency confirmations.”
Switching to Pulse: the first ninety days
Acme piloted Pulse with two squads — Platform Infrastructure and API Services — in Q1 2024. The migration took less than a week. Within the first sprint cycle, both squads reported that async story refinement in Pulse had eliminated the need for a standalone refinement ceremony altogether. Engineers were commenting on tickets, adding context, and flagging blockers in Pulse throughout the week, so by the time planning arrived, most of the groundwork was done.
By month two, they had rolled Pulse out to all six squads. Sprint planning sessions dropped from an average of 194 minutes to 116 minutes — a 40% reduction. More importantly, the quality of planning improved. Dependency conflicts that previously surfaced mid-sprint were now caught during async refinement, when they were cheap to resolve.
“The first time we caught a three-squad dependency conflict in Pulse before it became a blocker, I think Priya literally cheered,” Marcus said. “That one catch probably saved us a week of scrambling.”
Outcomes after six months
- Sprint planning time reduced by 40% — from 194 minutes to 116 minutes per cycle
- Unplanned mid-sprint dependency blockers down 62%
- On-time sprint delivery rate improved from 67% to 84%
- Estimated savings of $280,000 annually in reclaimed engineer time (based on fully-loaded cost per engineer-hour)
- Cross-squad visibility score in internal surveys rose from 3.1 to 4.6 out of 5
What changed for engineers on the ground
For Sven Brandt, a Staff Engineer on the Platform Infrastructure squad, the biggest change wasn’t the shorter meetings. It was the quality of the work coming out of planning.
“I used to dread planning because I knew I’d be estimating stories I hadn’t fully read yet, while everyone was watching,” Sven said. “Now I review everything in Pulse earlier in the week, drop my questions async, and by Monday I actually know what I’m signing up for. My estimates are better. My commitments are more realistic. I feel less like I’m just reacting.”
Priya echoed the sentiment from an operational standpoint. Pulse’s capacity view — which shows each squad’s velocity, carryover, and available points at a glance — replaced three separate spreadsheets that were always slightly out of date. “That alone would have justified the switch,” she said.
Looking ahead
Acme is now exploring Pulse’s roadmap and OKR linking features as they head into H2 planning. Marcus is particularly interested in the executive reporting layer, which will let him communicate engineering throughput to the C-suite without manually assembling data from multiple sources.
“We’re not done improving,” he said. “But Pulse gave us the foundation to have that conversation — where does time actually go, and where do we invest next. That’s a conversation we couldn’t even have before.”