-
Notifications
You must be signed in to change notification settings - Fork 1
Maturity Framework
Matthew Hall edited this page Jul 17, 2018
·
6 revisions
For the Organization as well as the Product team.
It is recommended that teams do an initial assessment of their maturity and then reassess over time to review their progress. The sample below is not meant to just be implemented. You should decide on the criteria that you want to evaluate and then determine the levels and definitions of what those levels look like.
Basic Sample:
Level | 3 Advanced | 2 Mature | 1 Evolving | 0 Basic | -1 :( |
---|---|---|---|---|---|
Category | organization has been structure around product teams and is practicing this at scale | multiple teams exists and are collaborating about it | A team exists that is starting to practice it | learning about it | Not doing |
Agile | |||||
Lean | |||||
Scrum | |||||
Transparency | |||||
Inspection | |||||
Adaptation | |||||
DevOps |
Scrum Sample:
Level | 3 Advanced | 2 Mature | 1 Evolving | 0 Basic | -1 :( |
---|---|---|---|---|---|
Category | organization is using at scale | multiple teams exists sharing experiences | A team exists that is using it | learning about it | Not doing |
Backlog | |||||
Burndown | |||||
Product Roadmap | |||||
Release Plan | |||||
User Stories | |||||
Acceptance Criteria | |||||
Definition of Done | |||||
Product Vision | |||||
Design Principles | |||||
Backend Unit Tests | |||||
Frontend Unit Tests | |||||
Test Driven Development | |||||
Functional Tests | |||||
Living Documentation | |||||
Static Code Analysis | |||||
Continuous Integration | |||||
Continuous Deployment | |||||
Production Smoke Test | |||||
Tagging and Release Notes | |||||
User Demonstrations | |||||
Backlog Refinement | |||||
Sprint Planning | |||||
Daily Scrum (Standup) | |||||
Sprint Review | |||||
Retrospective | |||||
One on One Coaching |