Staffbase: from stalled process to a team that ships on cadence

#The challenge

A three-person squad at Staffbase, one team lead and two developers, owned a sizeable internal product on a roadmap that kept growing. Capacity was not the real problem. The problem was rhythm. Planning was reactive, reviews ran ad hoc, and every shift in priority taxed the team in context switches. What people called agility had quietly stopped happening.

When the team is this small, process drag is not a footnote. It is the bottleneck.

#What we did

We started with the team, not the tooling. Two days of coaching mapped how the squad actually worked, where decisions stalled, and which rituals carried weight versus which were just on the calendar. From there we rebuilt the cadence around three people, not a department.

Stand-ups got shorter and more honest. Planning shifted to a thin, rolling backlog with acceptance criteria written before work started, not negotiated mid-sprint. Code review went from a queue back to a conversation, with pairing on the patterns we wanted reused, so the next ticket cost less than the last.

Training ran on the live product, not on a slide deck. Symfony conventions, testing strategy, and the architectural choices we wanted to bake into the codebase were taught while shipping, with the team building the muscle in the same engagement. The mindset behind onboarding into a codebase you did not write is something we wrote up separately, read more about how we approach an unfamiliar Symfony codebase here.

#What changed

The squad now runs on a cadence the lead and stakeholders can plan around. The lead spends the day leading, not chasing status. The developers spend more time writing code than negotiating what code to write. The roadmap is still ambitious, but it no longer depends on heroics.

Agility is back, not as a label, but as something the team feels every week.