Tag Archives: agile coaching


Developing an Internal Agile Coaching Program

Working myself out of a job has always been a goal of mine once I started consulting. I don’t expect my clients to be complete experts by the time I leave but as long as they know what they’re in store for and feel they’re on a path to get to where they want to go, I’m happy!

Recently myself and colleagues started an internal coach development program in the hopes we will be out of work in the coming weeks and/or months!

This is a large (40,000+ ) organization distributed across 4 timezones with multiple pockets of Agile being practiced from marketing through to IT teams.

Here’s how we approached this:

  • started organically through lean coffee to support existing scrum masters and to figure out who wanted to ‘become a coach’
  • adhoc support and pairing with people who would eventually become coach candidates
  • one-on-one coaching as requested or when necessary

This organic approach was intentional.  There wasn’t much of a point to starting a program right away because none of us (client included) knew what being a coach meant for this organization.

Fast-forward many months later and it was time to create a coaching program. We decided using the Agile Coaching Institute’s framework made the most sense.

Step 1 – Unconscious Incompetence

Noel Burch created the ‘Four Stages of Competence’ model (although it’s sometimes credited to Maslow) and we identified early that the people in the program didn’t know what they didn’t know. Actually, that’s what they told us.

So the first thing we did was run a session about de-mystifying “coaching”.  I gave the group an overview of the more popular coaching frameworks for two reasons:

  • to show how extremely deep the world of professional coaching is
  • to show them how closely tied together many of today’s coaching frameworks are

Summary of ICF, IAC, Results Coaching, ICAgile and ACI

This image shows the more popular coaching frameworks out there. We explored the similarities and differences to give people a strong indication of what they’re in for when they decide to become a ‘coach’.

At the end of this session we agreed to use ACI’s framework as a base, and customize it with IAC’s coaching competencies.

Step 2 – Create a Vision

We ran the visioning exercise from Management 3.0 and had the group create a poster that envisioned what being a coach meant to them.  They drew a picture of Yoda and completely bought into the servant leadership mantra that I believe works best.

During this exercise we also talked about what being a coach meant to the organization and we came up with some obstacles that we consciously chose to ignore for the time being:

  • what about an official title and job description?
  • how would a coaching team integrate into the hierarchy?
  • what would having ‘coaches’ mean to managers and directors? (IE: would it feel threatening to them?)

These are huge questions but it wasn’t necessary to answer them yet as these coach candidates would operate largely within their sphere of influence for the short term.

Step 3 – Building the Program

Our existing coaches, based on the outcome of Step 1, decided to build the program around ACI’s framework. Here’s the high level view of the program:

  • Set constraints:
    • candidates must have been a scrum master on a team for at least 6 months
    • candidates had to free up 1 day per week to be part of the program
    • candidates had to find their own replacement as they were still scrum masters on existing teams
  • 12 week program
    • 1 full day per week
    • Block 1 (4 weeks): Agile practitioner.  This block was focused on developing raw Agile skills from advanced Scrum to scaling frameworks, kanban and more
    • Block 2 ( 4 weeks): Facilitator and Coach: Building facilitation skills and doing a deep dive of the 9 IAC coaching competencies courtesy of the wonderful Sue Johnston.
    • Block 3 (4 weeks): Advanced practices such as large group facilitation, program and portfolio management and optional deeper dives on whichever topics the group felt they wanted to learn more about.

Our main challenge was figuring out how much of the program to design up front and how much to build over time. The challenge in enterprise organizations is the funding and planning part. The norm is to plan the whole thing up front, in excruciating detail, and know exactly what the outcome is.

We managed to balance that uncertainty by knowing where we were going but we set the expectations that the last 4 weeks would likely be completely changed from what the plan was.

The other challenge was how we could deal with different people wanting to focus on different masteries.  Should we split the group at the halfway point? What if each person had drastically different objectives? We solved that problem with Step 4!

Step 4 – Self-Assessment

The first day of the program we had the candidates do a self-assessment after a short discussion about the parameters of ACI’s coaching framework.




Each person did their own personal assessment by answering these questions:

In each competency and mastery area of ACI’s Framework, where are you now and where do you want to be?

Personal assessments

Personal assessments

aci-assessment.001Then we aggregated the assessments:


aci-assessment.002After that we had a discussion about what the aggregate data meant to the team. They felt that the group was largely skewed towards developing their professional coaching skills.

Finally, we had all the candidates write themselves a letter, dated 12 weeks from the day of the assessment:

What would your present self want to say to your future self 12 weeks from now?

We’re currently in week #3 with an average satisfaction score of 8.6 out of 10. We’re using feedback from the development program to evolve it over time with our (external coaches) goal to be to have the candidates help design the next coaching program.

There’s More Than Meets the Eye to Agile Coaching

This year at AYE Jerry Weinberg hosted a session titled “Coaching the Coaches“.   Jerry split the group up into people who self-identified as Coaches (coaches or managers who do coaching stuff), people who have been coached and people who didn’t feel they fit into either category.

Jerry asked the coaches how they received the title ‘Coach‘ and when it came to my turn I said it’s for marketing.  All the cool kids are doing it, that’s what the industry is asking for and it sounds a whole helluva lot cooler than ‘Business Process Consultant‘.

About a year ago while talking to a couple senior people at the organization I was working with, I realized there was a whole lot more to ‘Coaching‘ than I thought.  I was getting pressure to commit to having a project done with fixed scope for a fixed date and instead of trying understanding their perspective, I immediately went into ‘Agile Coach‘ mode and tried to explain to them why they were wrong.  Needless to say it failed miserably.   Over the last year I’ve had several epiphany’s about what a coach is and it all became crystal clear during a recent coaching session hosted by Michael Spayd. Continue reading

Position Paper for Agile Coach Camp 2010

Agile Coach Camp 2010 is coming the weekend of March 19, 2010 in North Carolina.    I’ve heard great things about Coach Camp and this is my first opportunity to attend.  You can check out their site here and for those who aren’t familiar with Coach Camp, it’s an Open Space conference focused on peer-to-peer learning and exploration as opposed to the traditional speaker/audience conferences I’m not a huge fan of.

Anywho, onto the position paper:  You’ll notice these are high-level points, that’s the point of Coach Camp.  The goal is to share experience and gain feedback from the Agile community.

Title: A Recipe for Enterprise Agile Transformation

Background and Challenges:

  • large department within large organization
  • tall hierarchy, great deal of office politics
  • heavily silo’d organization
  • complex product portfolio
  • mix of full time, contractors, outsourced developers and teams
  • limited people with Agile experience in the organization
  • no recognized Agile champion

Speaking and Presentation topics I plan to share:

  • transitioning focus of functional managers and other roles
    • there is much confusion about ‘where does my role fit’?
  • breaking down silos between multiple groups
    • having to prove you are worthy of being trusted
    • demonstrating and sharing success and failures
  • portfolio and team organization
    • how to structure your teams with the right skills for the project
  • techniques for handling ‘specialist’ groups
    • how these groups interface with teams
    • how these groups share information gained from working with multiple teams
  • cross-project knowledge sharing (technical or process related)
    • getting people together to talk about experiences.
  • How PMO and process teams evolve
    • more teaching and coach, less command and control
  • spreading Agile culture
    • making it about the organization, not the coaches
    • teaching the organization to think for themselves

The above topics will be accompanied by some fancy diagrams I’m working on for an experience paper and due to the format of Coach Camp, if my paper is accepted and put into the plan, the topics discussed with likely be determined by what my peers want to hear about.

I am still planning on writing and experience paper I had hoped to have finished by now where I can share more details.  Interested in your thoughts and experiences!