Skip to content
textor.consulting

Project · Agile Transformation

Agile transformation in the mid-market – what really worked.

From rigid project phases to functioning Scrum teams in 9 months – and the realization that culture beat method. An honest practical report from a mid-sized industrial company.

The starting point

The company – around 400 employees, a traditional line organization – had set out to "become more agile." What that should mean in concrete terms was unclear at first. What was clear: product development cycles were getting too long, markets too fast, competitors too nimble.

My assignment: consult on and support the transformation in three pilot teams – with the option to scale the approach later.

Five levers that really worked

1. The question first, then the framework

We deliberately did not start with "we're doing Scrum now." Instead, three weeks of discussion: what problem do we actually want to solve? Only then did we select a method. Result: two teams with Scrum, one team with Kanban – matched to their respective workflow.

2. Leadership first

Before a team can work in an agile way, the environment has to allow it. We started with leadership coaching – not with team training. It sounds unspectacular, but it was the lever with the biggest effect.

3. Hybrid instead of either-or

Existing stage-gate processes weren't abolished, but supplemented with agile building blocks. That created acceptance, because established routines weren't wiped out.

4. Visible wins within 6 weeks

We rolled out the first increment after 6 weeks – deliberately small, deliberately unspectacular, but functioning. That built more trust than any roadmap slide.

5. Taking retrospectives seriously

The most effective routine in the whole project: an honest, well-facilitated retrospective every two weeks. Not as a mandatory meeting, but as a learning tool.

What didn't work

The first attempt to build a "Center of Excellence" for agility failed – too centralized, too far removed from day-to-day operations. Only once we switched to decentralized Agile Coaches embedded in the business units did things start moving.

The result after 9 months

  • Time-to-market in the pilot teams reduced by around 35%
  • Three permanently established Scrum teams plus one Kanban team
  • Six trained Scrum Masters and two internal Agile Coaches
  • A leadership team that actively protects agile ways of working rather than merely tolerating them

My takeaway

Agile transformation isn't a method rollout – it's a culture process with a methodical backbone. Whoever starts with the framework loses. Whoever starts with the question – "what do we want to get better at?" – gains time and trust.

My architecture background helped here: understand the floor plan first, then choose the building blocks. That's exactly how I plan change.