Question 1

We've had agile coaches before and nothing changed. Why now?

Accepted Answer

Two reasons coaching engagements fail. The coach trained but never coached in flow, or the binding constraint wasn't the team's process, it was how work entered the team. We diagnose which one is hitting you in the first two sprints.

Question 2

Do we need to do Scrum or can we use Kanban?

Accepted Answer

Either. We coach the work, not the framework. If your work is highly variable (platform, DevOps, SRE) Kanban is almost always the right answer. If the work is project-shaped with hypotheses to test, Scrum fits better.

Question 3

How does Agile coaching connect to SAFe®?

Accepted Answer

Cleanly. Strong team-level agility is a prerequisite for SAFe® to work. We often do team-level Agile Consulting before standing up Agile Release Trains under SAFe®.

Question 4

How long do you stay on a team?

Accepted Answer

Three to six months on average. We start at full embed (3 to 4 days a week) and taper as the team's internal capability grows. By month four we're typically at one day a week. A certified internal coach is taking over the rest.

Question 5

Can we just hire an internal Agile coach and skip this?

Accepted Answer

Yes, if you can find a senior one and you have a clear coaching mandate. The reason teams hire us is that internal coaches often lack the political cover to push back on dysfunction. We bring that cover for the duration of the engagement, then transfer it to your coach.

Agile Consulting

Ready To Begin?

Ready to begin?