Agile Team Alignment

IMG 5183


In todays world, the focus has shifted from Scrum and Kanban to an overall driving principle of Agility. It is still true, however, that the specific techniques of Scrum and Kanban are still widely used and so we will be discussing those techniques within the overall principle of Agility.

We trust your Agile journey is going forward and the implementation getting better and better. Sometimes the journey is on track and as an Agile team we quickly adopt and become better, sometimes the journey can be painfully slow. The reason for being slow can be many, such as organizational resistance, lack of empowerment in the Agile Team, lack of understanding the core of Agile. It is also called “We do Agile but…”, e.g. We do Agile, but the PO does not have the final say how to prioritize.

As the focus has evolved towords Agility, one way of making sure the Agile Team is on track and fully understands true Agility is to attend a one-day class of Agile Team Alignment, a deep dive into the essence of Agility. As Ken Schwaber told me years ago, “The Devil is in the Details”.

Button One Button Two Button Three



Agile Team (RE-)Alignment – Agenda



      Exercises, videos

      The Spirit of Agility

      You don’t have to do Scrum.

Agility & AI

      Integrate AI into an Agile Team

–    Video: Henrik Kniberg Generative AI

 Team Principles : 

      Autonomous Team

      5 Dysfunctions of a Team

      Team Values (eg. Alabama coach, UCLA sixties, Olympic Hockey Lake Placid)

      Working agreement (not to length, what is most important)

      Team Member (AgileCoach/ScrumMaster, Product Owner, Developers)


      Sprint Planning

      Daily Scrum

      Sprint Review


–    Product Backlog Refinement


      Product Backlog Management

      Sprint Backlog Management

      Product Increment (Build-ability, clean code, user outcome/benfit)

 Impediment Backlog (what gets delayed, what is slow, eg. PO not there to clarify, how well do we deliver user value)

      What should be included?

      Value Stream Mapping


      Categories (Can change, can influence, can’t do anything about, can AI help).

–    Impediment Review

–    Part of Retro?

 Closing Event

  •    Team Photo

      Certificate (Picture, Team Name, Name, possible phrase)


  1. TEAM owns the problems… And it is up to the team to identify solutions/next steps

There are 5 key project health areas:

1. Stuck / Slow / CumbersomeEasy, rapid, clear movement / flow
2. Resource Gap
Roles not clear
Clear roles
Knowledgeable people in place
3. Dependencies / Critical PathsLook ahead / what are our complexities/uncertainties?
Engage other teams early
Begin complex tasks early
4. Priorities are not user-based
Unclear priorities
Clear, ranked User Goals
Set up experiments/proposed solutions
Ongoing feedback loop
5. Unclear overall plan, unclear milestones
Locations not clear
Processes not clear
Clear overall plan with milestones
Clear locations
Clear, documented, simple processes


  1. TEAM Activity:  Create list of misaligned areas. Scrum Impediment Backlog
  2. TEAM Activity:  Now rank them in importance (not solvability at this point).
  3. TEAM Activity:  Top Three:  Identify volume solutions/next-steps.

FACILITATOR/Scrum Master Activity:  Set up an easy weekly or bi-weekly checkpoint, preferably as a post-scrum/16th minute to review progress. To see how we are doing and to identify a next step.

Price: ?

Price includes:

  • Bounded course Material
  • Certificate
  • Etc.

You provide: (we can be helpful)

  • Venue
  • Lunch
  • Projector/TV
  • Flip chart
  • Post-it notes.
  • Etc.


  • Read the ScrumGuide
  • Attendance by whole Scrum Team (maximum 10)

Take this opportunity to refine the Agility skills with expert guidance. Align your practices for success, together. As a Scrum Team we are all in this together with no hierarchy.

Cheers to your continued growth.