Coaching Path to Advanced Scrum
Welcome to the Coaches Academy. We offer a coaching-based path for Scrum Masters and Product Owners to continue their professional development journey, working one-on-one with an accredited coach to create an individualized program satisfying the Agile Coaches Alliance advanced learning objectives.

A Scrum-like approach

This program adopts a Scrum-like approach, following a learn by doing paradigm. The following sections describe the approach in terms of Scrum framework elements.

Our Scrum Team

Product Owner
Agile Coaches Alliance
The Agile Coaches Aliance has established standards of capability for each level of accredation. Based on the recommendation of an Accrediting Coach, developers are awarded an accredation recognized by the Agile Coaches Alliance.
Developer
Individual seeking certification

In this case usually a cross-functional, self-organizing, team of one: you! You're responsible for working with the Scrum Master to assess your current capabilty, identify goals, establish plans for meeting those goals, order the backlog according to your goals, and progress against your plan on an incremental basis.

Scrum Master

Accrediting Coach

As a coach, mentor, consultant, and trainer, the Scrum Master works with the Developer(s) to identify their unique learning path; facilitating learning, deepening understanding, providing feedback, and holding the Developer(s) accountable for their established goals.

Our Artifacts
Product Backlog
Provided by the Accrediting Coach
The Accrediting Coach provides the Product Backlog. The Product Backlog items use certain terms to identify the capability expected to demonstrate competence at the level required for accreditation. Since this program uses a competency based model, PBIs where the developer can demonstrate the expected level of competence has already been achieved can be immediately marked as Done.
Sprint Backlog
Maintained by the Developer(s)
The developer(s) will order the Product Backlog with support from the Scrum Master as needed. They will work with the Scrum Master to decide what work they will accomplish in the Sprint, and how they will accomplish their work. This flexibility allows you to demonstrate competency in a variety of ways tailored to your own learning preference (for example different individuals may use a visual model, a written case study, or a documented dialog with the coach to demonstrate competency).
Increment
Produced by the Developer(s)
Each Sprint the developer(s) is expected to complete the PBIs they have selected for the Sprint, demonstrating they have achieved the required level of competence to satisfy the related learning objective or the learning objective sub-set selected for the Sprint. The tangible outcomes you are producing can be assembled into a portfolio, providing real value for your current and future work.
Our Activities
The developer(s), working in collaboration with the Scrum Master, will determine Sprint duration. Consistent with Scrum, maximum Sprint duration will be one month or less (with a preference for shorter duration Sprints).
Sprint Planning
At the beginning of each Sprint the developer(s) will work, in collaboration with the Scrum Master, to identify the PBIs they will complete during the Sprint as well as the acceptance criteria that will allow validation that the PBIs are Done.
Daily Scrum
The developer(s) will be encouraged to have a mindful daily practice of reflecting on their progress, taking necessary steps to inspect, adapt, and assure transparency.
Sprint Review
At the end of the Sprint, or at the option of the developer(s) and the Scrum Master more frequently, PBIs that have been completed will be inspected and those that meet the acceptance criteria will be identified as Done.
Sprint Retrospective
The developer(s) and the Scrum Master will conduct a Retrospective at the end of each Sprint to determine how they can continue to improve to become even more effective in subsequent Sprints.
Our Values
The Scrum values: courage, commitment, openness, focus, and respect will be applied throughout the relationship. Professional coaching standards including a non-judgement and an environment of mutual trust will be applied. A working agreement specifying a commitment to respect these values, along with any other values or principles that the developer(s) and Scrum Master want to put in place, will be defined at the beginning of the relationship.

Next Steps

1
Assess
Determine program fit. Review the program and learning objectives and assess if the coaching approach is right for you.
2
Commit
Once you have determined fit, you can start working with your coach. Create a working agreement, order the Product Backlog, and establish your goals. Register to get started.
3
Sprint
Begin Sprinting. Based on what's meaningful to you in your context. identify your Sprint goal and work towards it. Your coach is there to challenge and support you along the way.
4
Reflect
Retrospecting is a continuous activity throughout the program. But more than looking back it's an opportunity to look to the future. Your journey continues.
Share this page