Agile Coaching
Agile coaching services that leave your team running its own sprints
Our agile coaching services work inside your team’s own sprints, in the tool it already uses: Jira or Azure Boards. The coach runs planning, review and retrospective alongside your team’s lead, fixes the board and the backlog, and hands every ceremony to the team by the end. Our coaches are people who deliver software for our clients.
For an IT leader whose team plans every sprint and still slips
Your team plans every sprint, and the work still slips. The board says one thing and the standup another, and the retrospective changes nothing.
Our agile team coaching works on that inside the team’s real work, in the tools it already uses, with coaches who build software themselves.
Start with one sprint. Coach one team.
The assessment shows what to coach. Team coaching does it, sprint by sprint, until the team runs every ceremony itself.
2 weeks
Agile assessment
One full sprint, observed from planning to retrospective, interviews with the team and its stakeholders, and a review of the board and the backlog.
How it runs
- Week 1 Planning and the sprint underway We sit in on sprint planning, watch how work moves across the board, and interview the team and the stakeholders who depend on it.
- Week 2 Review, retrospective and findings We see the sprint through its review and retrospective, review the board and the backlog, and write up our findings and a coaching plan.
What you get at the end
- Written findings
- A coaching plan for the team
12 weeks
Team coaching
Sprint by sprint with one team. The coach runs planning, review and retrospective alongside your team’s own lead, fixes the board and the backlog in the tool the team already uses (Jira or Azure Boards), and hands every ceremony to the team by the end. Each further team is its own engagement of the same length.
How it runs
- Weeks 1–4 The coach leads beside your lead The coach runs planning, review and retrospective with your team’s lead, and fixes the board and the backlog so they match how the team works.
- Weeks 5–8 Your lead runs it, the coach beside them Your lead runs the ceremonies with the coach alongside, and we read progress from the team’s own board data, such as cycle time and throughput.
- Weeks 9–12 Your team runs every ceremony The team runs planning, review and retrospective on its own, and the coach steps back to watch and adjust.
What you get at the end
- Every ceremony handed to your team
- A board and backlog that match how the team works, in the tool it already uses
Inside the work, not beside it
In your tools
We work in the Jira or Azure Boards your team already uses, and fix the board and the backlog there. Nobody moves to a new tool to be coached.
Alongside your lead
The coach runs planning, review and retrospective with your team’s own lead, then hands each one to the team.
From your own data
We read progress from your team’s board data, such as cycle time and throughput, not from a maturity score.
When it fits, and when it doesn’t
It fits when
- One team needs its sprints to work.
- The team already plans its work in Jira or Azure Boards.
- The team’s own lead will run the process once the coach steps back.
It doesn’t fit when
- You want every team changed at once. We coach one team at a time, and each further team is its own engagement.
- You want someone to run the process for the team indefinitely. Coaching ends with the team running it.
- The tool is the trouble, not the process. Start with a Jira health check.
FAQ
Who coaches, which tools, and what happens after.
Who are the coaches?
People who deliver software for our clients. They coach from the same kind of work your team does: planning it, building it and shipping it.
Is this scrum coaching?
If your team runs scrum, yes. The coaching works inside scrum’s own events: sprint planning, the sprint review and the retrospective.
Will you replace our scrum master or team lead?
No. The coach works alongside your team’s own lead and hands every ceremony to the team by the end.
Which tools do you coach in?
The one your team already uses, Jira or Azure Boards. We fix the board and the backlog there instead of moving the team to a new tool.
How do you tell whether coaching is working?
We read it from your team’s own board data, such as cycle time and throughput, sprint by sprint.
Can you coach more than one team?
One team at a time. Each further team is its own team coaching engagement, the same length as the first.
What happens after the agile assessment?
You keep the written findings and the coaching plan. If you want us to coach the team through the plan, that is the team coaching package.
What does it cost?
We quote it after the discovery call, once we know your team.
Next step
Is your team’s process working against it?
Tell us about the team and how it plans its work. We’ll tell you whether to start with the assessment or with coaching.