Skip to content
Fred Mastropasqua
← Case studies

SiteZeus

Fractional Chief Agile Officer · 2023

Cut SaaS delivery cycles from six weeks to two by rebuilding the team's Scrum discipline from scratch.

Delivery cycle before
6 weeks
Delivery cycle after
2 weeks
Engagement length
12 months
Outcome
Embedded long-term

The situation

A six-week delivery cycle on a SaaS team that should have been shipping every two.

After SiteZeus acquired Synuma in 2023, I stayed on as Fractional Chief Agile Officer through the end of the year. One of the first things I noticed: a core product team was running on six-week delivery cycles. They called it Scrum, but most of what they were doing was sprint theater. Ceremonies happened, but the iterative delivery underneath had broken down. Engineers were heads-down on long-running branches; product was disconnected from what was actually being built; leadership was getting status updates that were closer to fiction than fact.

The diagnosis

The framework was fine. The discipline had eroded.

Nothing about the team was broken. They were good engineers, good product people, good designers. What had eroded was the basic Scrum discipline: definition of done, vertical slicing, shippable increments every sprint, retrospectives that actually changed behavior. Without those, the framework collapses into ceremony and a six-week cycle becomes the new normal.

The intervention

Rebuilt the operating cadence from scratch.

We rebuilt definition of done together. We re-sliced the backlog into stories that could actually finish inside a sprint. We made retrospectives short and binding. One improvement per sprint, and we'd hold ourselves to it. We restored the daily standup as a planning meeting, not a status meeting.

On the leadership side, I cut several recurring meetings that existed to compensate for the broken feedback loop and replaced them with a single weekly forum where the right information moved fast. Executives got better signal in less time. Engineers got their afternoons back.

The result

Two-week cycles, every sprint, holding.

Within the engagement, the team moved from six-week to two-week delivery cycles and held it. Usable, high-quality increments every sprint. Leadership got faster feedback on bets. Engineers reported significantly higher satisfaction with the work. What had felt like a grind started feeling like a flywheel again.

The Agile playbook got embedded across the broader org from there.

What I'd take into the next one

When a team that "does Scrum" isn't shipping, the fix is almost never "adopt a new framework." The fix is to go back to basics: what does shippable mean here, are stories small enough to finish, are retros actually changing behavior, is the daily standup planning the day or reporting the day. The unsexy answer is usually the right one.

The other observation: most leadership meetings are a tax the organization pays because the underlying feedback loops have broken. Fix the loop, the tax goes away on its own.

Want to talk about something similar?

Get in touch →