Team maturity path

Owned by Mats Janemalm
Last updated: 2019-04-01
2 min read

Cope level

Startup level

Delivery engine (full scrum)

Organisation

  • 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

Benefit

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

Organisation

  • One Scrum master 100%

  • One Product owner 100%

  • 5-8 Developers 100%

Benefit

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

 



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

Benefit

The team becomes high performing with an aligned purpose.

 



 

 

 

Metrics

  • Velocity in story Points / Iteration or other time frame

  • Always up to date remaining estimated hours of planned tasks

  • Team happiness index

Metrics

  • Idea on delivery quality

Metrics

  • Increasing Velocity in story Points / Iteration or other time frame

  • Technical debt

  • Test coverage

  • Delivery quality

  • SMART Sprint goals with outcome

Process

  • Regular Backlog refinement

  • Iteration planning meeting or Story kick-off

  • 15 minute Daily stand up at the most

  • Iteration review

  • Iteration retrospective

Process

  • Impediment handling

Process

  • Team working agreement

  • Can do production deployment on every story

  • Collective ownership

  • Pair working

Product Backlog

  • Story points on stories next in line

  • Reference story

  • Done checklist

  • Team backlog including local context

Product Backlog

  • Value on stories next in line

 

Product Backlog

  • Team enabler stories

  • No fake User Stories

  • No activities

 

Big Visible Radiators

  • Kanban board with Stories, Acceptance criteria and Tasks

  • Work in process limit on Stories

  • Sprint burn down

Big Visible Radiators

  • Work in process limit on stories less than number of persons in the team

  • Visible Impediment log

  • Sprint goal

  • Team mission

Big Visible Radiators

  • Quality board

  • Build light indicator

 

 

 

Craftsmanship

  • High degree of test automation

  • Continuous deployment pipeline

  • Test Driven Development

  • A plan for establishing A/B-testing

 

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