Idea Flow
Models
Idea Flow
  • Welcome!
    • Why Models?
    • Why Principles?
  • Agility & Transformations
    • Intro to Agile
      • What Does Agile Mean?
      • What Is An Agile Mindset?
    • Intro to Transformation
      • Why Transform?
      • How Is The Transformation Done?
      • Who Transforms?
      • Which Areas or Functions Transform?
      • How Long Does A Transformation Take?
  • Agile Transformation (Idea Model)
    • Intro to IDEA
      • Leadership-Strip (Tanzaku)
      • Managing The Change
      • Metrics
      • Coaching Plan
        • Coaching Assessment
    • Initial Exposure
      • Training & Coaching
      • Assessment
    • Develop Basics
      • Training & Coaching
      • Assessment
    • Evolve & Reflect
      • Training & Coaching
      • Assessment
    • Accelerate & Kaizen
      • Training & Coaching
      • Assessment
  • Delivery Approach (Flow Model)
    • Intro to Flow
      • Flow of Work
      • Dev Sec Ops
    • Conceptualise
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Commence
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Construct
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Confirm
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Complete
      • Process
      • Outputs
    • Check
      • Process
  • Scrum, Kanban & Other Agile Frameworks
    • Double-Loop Scrum
    • Kanban
  • 3D Work-Breakdown
    • Intro to Work Breakdown
    • Direction
    • Discovery
    • Delivery
    • Flow & 3D Work-Breakdown
  • Roles & Responsibilities
    • Overview
      • Trust Circles
      • Enterprise View
    • Core Team Roles
      • Scrum Master / Iteration Manager
      • Product Owner
      • Developer
      • Tester
      • Business Analyst
      • Infrastructure
    • Extended Team Roles
      • Product Manager
      • Test Lead
      • Tech Lead
      • Subject Matter Expert (SME)
      • UX/UI Designer
      • Infrastructure Lead
      • Project Manager
      • Solution Architect
      • Delivery Manager
      • Change Analyst
    • Trusted Advisor Roles
      • Project Sponsor
      • Stakeholders
  • Topics
    • Prioritisation
    • Estimation
      • Estimation Overview
      • Epic Estimation
      • Initiative Estimation
    • Planning
      • Sprint / Iteration Planning
      • Release Planning
      • Quarterly Planning
      • Problem Statement
    • Ceremonies
      • Showcase
      • Scrum of Scrums
      • Stand-up
      • Retrospective
      • Elicitation
      • Elaboration
      • Acceptance Criteria (AC)
    • Artefacts
      • Tech Spike
      • Definition of Done
      • Social Contract
      • Personas
      • Lean Canvas
      • User Stories
    • Toolkit
      • Success Sliders
      • ICaRuS Scoring
      • Accountability Cards
    • Quality
      • Test Strategy
      • Test Plan
      • Quality Attribute Definitions
      • Test Type Definitions
      • Regression Test Suite Definitions
      • Defect Definitions
      • Defect Severity
      • Defect Priority
      • Agile Testing Quadrants
      • Risk-Based Testing
    • Templates
      • 3rd Party Handover Template
      • Audit Logs
    • Data
      • Information Management
    • Kanban
  • Agile Testing (4Aces Model)
    • Intro to Agile Testing
      • Test Principles
        • Test Automation Principles
      • Test Artefacts
      • Test Triangle
      • Agile Testing Quadrant
    • Arrange
    • Act
    • Assert
    • Annihilate
  • INCIDENT MANAGEMENT (TRACeR MODEL)
    • Intro to TRACeR
      • What is Incident Management
      • Incident Management Workflow
    • Triage
    • Review
    • Action
    • Check
    • Resolve
  • Change Management (3C Change Model)
    • Intro to 3C Change
      • What is Change?
      • What is Change Management?
      • 7Rs of Change Management
      • Model States
      • Implementation
    • Capture
      • Priority
      • Experience
      • Impact
      • Change Types
    • Consider
      • Risk
    • Conduct
      • Plan
        • Change Activities Matrix
      • Perform
        • Rollback or Roll-forward
      • Prove
        • Change Result/Status
  • Faciliation
    • Intro to Faciliation
      • Agile Facilitation
      • Planning and Running a Workshop
    • Meetings
      • Meeting Prep
    • Workshops
      • Quarterly Planning Workshop
      • Integrated Culture Workshop
    • Games
      • Dice Game
      • Battleships
      • Kanban Pizza Game
    • Icebreakers
      • Check Your Personal Thinking Style
  • Agile Coaching (A6 Model)
    • Intro to Coaching
    • Agree
    • Address
    • Assess
    • Align
    • Assign
    • Account
  • Agile Leadership
    • Intro to Agile Leadership
  • Strategy
    • What is Strategy?
    • What is Vision?
    • What is a Mission?
    • What are Values and Drivers?
    • Intent-based Outcomes
    • MunroMaps
  • OKRA
    • OKRS + ACTIONS = OKRA
      • Implementation
      • Cycle Cadence
    • Objectives
      • OKRs
    • Key Results
    • Actions
  • Agile Software Architecture (C4 Model)
    • Intro to Architecture
      • Role of the Architect
      • SOLID Principles
      • DRY Principle
      • Single Source of Truth (SSOT)
    • Context
      • Examples
    • Container
      • Examples
    • Component
      • Examples
    • Code
      • Examples
    • Patterns
      • Back-end for Front-end (BFF)
      • Event-Driven Microservices
  • Portfolio Management (PMO Practice Model)
    • Intro to Portfolio Management
      • Practices & Flow
      • Objectives
      • Types
      • Maturity Assessment
      • Setting Up
        • Charter
    • Demand Practice
    • Risk Practice
    • Performance Practice
      • Cost of Delay (CoD)
      • Metrics
    • Report Practice
    • Delivery Practice
    • Asset Practice
    • Change Practice
  • RAFT
    • RAFT Framework
  • Tools
    • Jira
      • Best Practice
      • Printing Physical Cards
    • Confluence
      • Best Practice
      • Example Confluence Layout
    • Power BI
      • Power Query M
    • Miro
      • Best Practice
  • FAQs
    • Frequently Asked Questions
    • Glossary of Terms
  • Thanks & Contributors
    • Thanks
    • License
Powered by GitBook
On this page
  • Coaching Model (A6)
  • Core Assumptions for Effective Coaching
  • Agile Coaching Competency Framework

Was this helpful?

  1. Agile Coaching (A6 Model)

Intro to Coaching

Last updated 7 months ago

Was this helpful?

A successful coaching relationship is also built on passion and commitment from the coach, who is deeply invested in helping the coachee achieve success. Trust is the cornerstone of this dynamic, ensuring that all coaching conversations remain confidential and that the professional relationship is mutual respect.

Effective Agile coaching requires balancing multiple coaching stances. Relying too much on just one aspect—being overly directive (content-focused) or too hands-off (pure coaching)—can hinder progress. Clients may feel stuck if a coach only asks powerful, open-ended questions without addressing real barriers. Coaches must strike a balance by adapting to the needs of those being coached, especially when struggling to progress.

The coachee is believed to possess the answers to their challenges internally, and the coach's role is to act as a guide rather than a problem solver. In this capacity, the coach is a catalyst—facilitating the coachee's growth without directly driving the change. The responsibility for progress lies with the coachee, who must actively engage in the process and implement the steps necessary for improvement. The coach, however, lays the groundwork by providing structure and support.

Coaching Model (A6)

The A6 Coaching Model (original concept © 2017 The Painefree Group, LLC) is a structured approach that guides coaches through six essential stages:

  1. Agree: Establish mutual goals and expectations.

  2. Address: Tackle key challenges directly and collaboratively.

  3. Assess: Evaluate the current state and identify areas for growth.

  4. Align: Ensure shared understanding between coach and client.

  5. Assign: Delegate tasks and responsibilities for ongoing progress.

  6. Account: Maintain accountability to foster continuous improvement.

Core Assumptions for Effective Coaching

  1. The Coachee Already Has the Answers: Agile coaches believe their role is to guide, not to provide solutions. The client is capable of finding the answers within themselves.

  2. The Coach is a Catalyst: While the coach doesn't create the change, they serve as an essential facilitator, enabling the client to move forward.

  3. Accountability is Key: The client holds responsibility for progress, while the coach provides the framework to make that progress possible.

  4. Passion for Transformation: A coach must have a genuine passion for seeing their clients succeed, serving as a motivator for both the process and outcomes.

  5. Trust is the Foundation: A successful coaching relationship is built on confidentiality and mutual respect, ensuring clients feel secure.

Agile Coaching Competency Framework

Key competencies within the Agile Coaching framework include:

  1. Agile-Lean Practitioner: Coaches must understand Agile frameworks and Lean principles, not just at a surface level, but by deeply internalising the underlying values that drive these practices. This knowledge allows for innovation in applying Agile concepts appropriately.

  2. Professional Coaching: Coaching with the client's best interests at the forefront, without being swayed by the coach's expertise or opinion, is crucial for empowering the client to take ownership of their growth.

  3. Facilitation: Agile coaches act as neutral guides, steering teams through discovery processes while keeping them aligned with their goals and definitions of success.

  4. Mentoring: Sharing personal experience and insights helps grow the client's knowledge base, but the focus remains on fostering the client’s ability to navigate similar domains.

  5. Teaching: Coaches must deliver the right knowledge at the right moment, ensuring that it is absorbed effectively by teams or individuals to enhance their learning experience.

  6. Technical Mastery: Coaches often demonstrate technical leadership, whether through architecture, design, coding, or other engineering practices, to foster technical craftsmanship. Mastery of Agile scaling structures is also essential.

  7. Business Mastery: Coaches must apply business strategy and management principles, incorporating techniques like Lean Start-Up, product innovation, and flow-based process management to enable Agile as a competitive advantage.

  8. Transformation Mastery: This involves guiding organizations through change, using principles from organizational culture, systems thinking, and change management to lead transformative initiatives.

A6 Coaching Model
Agile Coach Competency Framework was developed by Lyssa Adkins and Michael Spayd as part of their work at the Agile Coaching Institute (ACI)