What it means
Agile coaching and mentoring build capability through questions, observation, practice, feedback, modeling, and the deliberate transfer of judgment.
Why it matters
Training can introduce concepts, but teams need support applying them to ambiguous work, relationships, and organizational constraints.
Practical focus
- Distinguish when a person needs instruction, coaching, mentoring, facilitation, or direct decision support.
- Set a capability objective and create opportunities for the learner to practice with feedback.
- Reduce dependence on the coach by transferring ownership and making learning resources reusable.
- Retain the approved definitions, assumptions, decisions, ownership, exceptions, measures, and change history that demonstrate how Agile Coaching and Mentoring operates in real project work.
- Exercise this failure scenario: A specialist solves every difficult problem for the team, producing short-term speed while preventing the team from becoming independently capable.
Common mistakes
- Using Agile Coaching and Mentoring as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a template, meeting, tool screen, or status report as proof that Agile Coaching and Mentoring works consistently in normal delivery.
- Optimizing a single activity while ignoring dependencies, incentives, risk transfer, and the end-to-end outcome.
- Testing only the expected path and never rehearsing this failure condition: A specialist solves every difficult problem for the team, producing short-term speed while preventing the team from becoming independently capable.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: