Vact Agile Coaching: Helping Teams Improve Through Facilitation
Agile coaching is the practice of helping teams and organizations adopt and improve agile practices. Unlike traditional management, which directs teams on what to do, agile coaching helps teams discover better ways of working through facilitation, teaching, mentoring, and observation. The agile coach does not have authority over the team but has influence through expertise, relationships, and the results their coaching produces.
Agile Coaching: Helping Teams Improve Through Facilitation
The Coaching Stances
Lyssa Adkins, author of “Coaching Agile Teams,” identifies four coaching stances that agile coaches move between based on the situation:
Teaching
When the team lacks knowledge, the coach teaches. This includes explaining Scrum ceremonies, demonstrating estimation techniques, and introducing concepts like WIP limits or value stream mapping. Teaching is most prevalent with teams new to agile.
Mentoring
When the team has knowledge but lacks experience applying it, the coach mentors by sharing their own experiences and guiding the team through situations they have seen before. Mentoring is one-on-one or small group and is based on the coach’s personal experience.
Facilitating
When the team needs to make decisions or solve problems together, the coach facilitates. Retrospectives, sprint planning, and workshops are facilitation opportunities. The facilitator does not contribute content but guides the process to ensure productive outcomes.
Coaching
Pure coaching involves asking powerful questions that help the team discover their own solutions. Rather than telling the team what to do, the coach asks: “What would happen if you tried…?” or “What is preventing you from…?” This stance builds the team’s problem-solving capability rather than creating dependency on the coach.
What Agile Coaches Do
Team-Level Coaching
At the team level, the coach (often the Scrum Master) helps with:
- Facilitating effective ceremonies
- Teaching and reinforcing agile practices
- Observing team dynamics and providing feedback
- Removing impediments that the team cannot resolve alone
- Helping the team establish and maintain a definition of done
- Supporting the Product Owner in backlog management
Organization-Level Coaching
At the organization level, agile coaches work with leadership to:
- Design and support agile transformation initiatives
- Restructure teams and reporting lines to support agile delivery
- Modify budgeting and governance processes for agile compatibility
- Train managers in servant leadership and agile management practices
- Establish communities of practice and knowledge sharing
Coaching Techniques
Powerful Questions
Instead of providing solutions, ask questions that help the team think deeper:
- “What do you think is the root cause of this problem?”
- “What have you already tried?”
- “What would success look like?”
- “What is the smallest experiment you could run to test that?”
- “How did that work last time?”
Observation and Feedback
Attend team ceremonies and observe patterns: Who speaks? Who stays silent? Where does the conversation stall? What is the energy level? Share observations without judgment: “I noticed that three team members did not speak during sprint planning. What do you think about that?”
Modeling Behavior
Demonstrate the behaviors you want the team to adopt. If you want the team to embrace failure as learning, share your own mistakes openly. If you want the team to use data for decisions, bring data to every conversation.
Visualization
Make invisible things visible. Create a Kanban board for impediments. Chart the team’s cycle time over sprints. Display retrospective actions on the wall. Visualization turns abstract concerns into concrete items the team can act on.
Measuring Coaching Effectiveness
Coaching effectiveness is measured by team outcomes, not by the coach’s activity:
| Indicator | Improving | Declining |
|---|---|---|
| Sprint goal achievement | Above 80% | Below 60% |
| Impediment resolution | Under 48 hours | Over one week |
| Retrospective actions completed | Above 70% | Below 40% |
| Team self-sufficiency | Increasing | Decreasing |
| Stakeholder satisfaction | Improving | Declining |
The ultimate measure of a coach’s success is when the team no longer needs the coach. If a coach has been with a team for two years and the team still cannot run effective ceremonies or resolve impediments without the coach’s help, the coaching approach needs to change.
Common Coaching Anti-Patterns
The hero coach. A coach who solves every problem personally creates dependency rather than capability. The coach’s job is to help the team solve problems, not to solve them.
Coaching without consent. Teams that do not want coaching will resist it. Effective coaching requires the team’s willingness to be coached. If a team is not receptive, the coach should start with building trust and demonstrating value, not forcing practices.
Process police. A coach who focuses on adherence to agile rules rather than team outcomes misses the point. Agile methodologies are means to an end. If a team achieves great outcomes with a modified process, the coach should celebrate, not correct.
Ignoring organizational impediments. A coach who only works at the team level while ignoring the organizational barriers that constrain the team will eventually hit a ceiling. Effective coaching addresses both team practices and organizational structures.
Developing as an Agile Coach
Start as a Scrum Master for one team. Master facilitation and team-level coaching before attempting organizational coaching. Build expertise in multiple agile frameworks, not just Scrum. Study professional coaching techniques from organizations like the International Coaching Federation. And most importantly, practice continuous improvement on yourself — the same inspect-and-adapt cycle you teach teams applies to your own coaching practice.