Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

A maturity path is a practical explanation of the ever-ongoing change journey an organizational unit is willing to undertake. The purpose is not for anyone to approve or judge the organizational unit, it is a tool for themselves to enable planning and get support to take the next step. It is also important to make the future path visible.

Cope level

Startup level

Delivery engine (full scrum)

  • One Scrum master at least 50%

  • One Product owner at least 50%

  • 3 - 9 Developers 100%

  • No doubt about who is in the team or outside as "experts"

  • No doubt about who is or are the line manager(s) for the team

The team members can start to explore their future work roles and line managers get practical experience from building teams.



  • One Scrum master 100%

  • One Product owner 100%

  • 5-8 Developers 100%

The team members know their long term team role and can start to define and align team mission with the surrounding organisation.



  • Frequent line manager support

  • The Product Owner owns the priority

  • The Developers owns the solution

  • The Scrum Master has a working improvement backlog for the team

The team becomes high performing with an aligned purpose.



  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
 

All material on this site is published in accordance with Konomark.

null