Back to templates

Team Maturity Index: team health and delivery process

Team Maturity Index

A large maturity survey for reviewing team mission, task flow, quality, release discipline, and core team practices.

Sign in to copy Register Export JSON
Blocks
7
Questions
40
Answer types
Scale
What this preview shows
This is a read-only preview of the template structure. After copying it, you can edit the questions, adjust wording, and launch the survey for your own teams.

1. Mission and team goals

Block weight: 1
4
1.1 The team has a shared understanding of what it owns and what product or service it builds.
Scale Scale: 1–5
1.2 The team clearly understands its mission and area of responsibility.
Scale Scale: 1–5
1.3 Engineers understand why the current tasks matter and what outcome they are expected to produce.
Scale Scale: 1–5
1.4 The team has clear and explicit quarterly goals.
Scale Scale: 1–5

2. Board and work transparency

Block weight: 1
4
2.1 All significant team work is visible on the board, with little or no hidden work.
Scale Scale: 1–5
2.2 The board makes the near-term plan and current priorities understandable.
Scale Scale: 1–5
2.3 The team has a unified and understandable way to visualize work across different roles and functions.
Scale Scale: 1–5
2.4 The board workflow is defined and understood by team members.
Scale Scale: 1–5

3. Incoming task flow and backlog

Block weight: 1
8
3.1 The team has a structured and understandable backlog management process.
Scale Scale: 1–5
3.2 Business and technical analysis are performed regularly and with sufficient depth.
Scale Scale: 1–5
3.3 The team uses DOR, DOD, and acceptance criteria, and these practices are genuinely helpful.
Scale Scale: 1–5
3.4 Readiness and completion criteria are applied consistently rather than formally.
Scale Scale: 1–5
3.5 Task prioritization is transparent and understandable to the team.
Scale Scale: 1–5
3.6 Technical tasks, debt, and engineering improvements enter the active work stream regularly.
Scale Scale: 1–5
3.7 Tasks rarely come back for rework as a normal pattern.
Scale Scale: 1–5
3.8 The share of urgent work outside the main process remains under control.
Scale Scale: 1–5

4. Task artifacts and engineering practices

Block weight: 1
7
4.1 Tasks are estimated before development and those estimates help planning.
Scale Scale: 1–5
4.2 The team tracks time or effort in a form that is useful for management.
Scale Scale: 1–5
4.3 Tasks leave a concise and understandable trail of what was done.
Scale Scale: 1–5
4.4 Documentation is maintained as part of the workflow rather than as an afterthought.
Scale Scale: 1–5
4.5 Code review is a stable and useful part of the development process.
Scale Scale: 1–5
4.6 Design review or architectural alignment is used where it is actually needed.
Scale Scale: 1–5
4.7 Average task size and duration remain manageable and predictable.
Scale Scale: 1–5

5. Delivery and release process

Block weight: 1
7
5.1 The release process is clear, predictable, and regularly used by the team.
Scale Scale: 1–5
5.2 There is a realistic rollback or risk-reduction strategy for bad releases.
Scale Scale: 1–5
5.3 Responsibility for operating production is clearly defined.
Scale Scale: 1–5
5.4 Customers and integration teams are informed about deliveries and changes in a timely way.
Scale Scale: 1–5
5.5 The team regularly demonstrates outcomes to customers or internal stakeholders.
Scale Scale: 1–5
5.6 Feedback on delivered work is collected and influences future decisions.
Scale Scale: 1–5
5.7 Incident reviews or postmortems are carried out and produce practical improvements.
Scale Scale: 1–5

6. Risk and quality

Block weight: 1
5
6.1 Testing is a real part of the development process in this project.
Scale Scale: 1–5
6.2 The project has test cases or equivalent practices for checking expected behavior.
Scale Scale: 1–5
6.3 Test automation covers a meaningful share of product risks.
Scale Scale: 1–5
6.4 The team tracks bugs, failures, and task returns and uses that data for improvement.
Scale Scale: 1–5
6.5 The process for detecting and fixing production bugs is organized and understandable.
Scale Scale: 1–5

7. Team and development

Block weight: 1
5
7.1 Team retrospectives happen regularly and lead to concrete improvements.
Scale Scale: 1–5
7.2 The team has regular personal feedback or one-to-one reflection practices.
Scale Scale: 1–5
7.3 Team health and motivation are monitored and discussed systematically.
Scale Scale: 1–5
7.4 There is a clear process for employee growth and development in the team.
Scale Scale: 1–5
7.5 The team uses metrics to analyze its work and support decisions.
Scale Scale: 1–5