{
  "format": "sf-survey-template-example",
  "version": 1,
  "order": 10,
  "slug": "team-maturity-tmi",
  "name": "Team Maturity Index: team health and delivery process",
  "description": "A large maturity survey for reviewing team mission, task flow, quality, release discipline, and core team practices.",
  "type": "tmi",
  "blocks": [
    {
      "name": "Mission and team goals",
      "weight": 1,
      "questions": [
        { "text": "The team has a shared understanding of what it owns and what product or service it builds." },
        { "text": "The team clearly understands its mission and area of responsibility." },
        { "text": "Engineers understand why the current tasks matter and what outcome they are expected to produce." },
        { "text": "The team has clear and explicit quarterly goals." }
      ]
    },
    {
      "name": "Board and work transparency",
      "weight": 1,
      "questions": [
        { "text": "All significant team work is visible on the board, with little or no hidden work." },
        { "text": "The board makes the near-term plan and current priorities understandable." },
        { "text": "The team has a unified and understandable way to visualize work across different roles and functions." },
        { "text": "The board workflow is defined and understood by team members." }
      ]
    },
    {
      "name": "Incoming task flow and backlog",
      "weight": 1,
      "questions": [
        { "text": "The team has a structured and understandable backlog management process." },
        { "text": "Business and technical analysis are performed regularly and with sufficient depth." },
        { "text": "The team uses DOR, DOD, and acceptance criteria, and these practices are genuinely helpful." },
        { "text": "Readiness and completion criteria are applied consistently rather than formally." },
        { "text": "Task prioritization is transparent and understandable to the team." },
        { "text": "Technical tasks, debt, and engineering improvements enter the active work stream regularly." },
        { "text": "Tasks rarely come back for rework as a normal pattern." },
        { "text": "The share of urgent work outside the main process remains under control." }
      ]
    },
    {
      "name": "Task artifacts and engineering practices",
      "weight": 1,
      "questions": [
        { "text": "Tasks are estimated before development and those estimates help planning." },
        { "text": "The team tracks time or effort in a form that is useful for management." },
        { "text": "Tasks leave a concise and understandable trail of what was done." },
        { "text": "Documentation is maintained as part of the workflow rather than as an afterthought." },
        { "text": "Code review is a stable and useful part of the development process." },
        { "text": "Design review or architectural alignment is used where it is actually needed." },
        { "text": "Average task size and duration remain manageable and predictable." }
      ]
    },
    {
      "name": "Delivery and release process",
      "weight": 1,
      "questions": [
        { "text": "The release process is clear, predictable, and regularly used by the team." },
        { "text": "There is a realistic rollback or risk-reduction strategy for bad releases." },
        { "text": "Responsibility for operating production is clearly defined." },
        { "text": "Customers and integration teams are informed about deliveries and changes in a timely way." },
        { "text": "The team regularly demonstrates outcomes to customers or internal stakeholders." },
        { "text": "Feedback on delivered work is collected and influences future decisions." },
        { "text": "Incident reviews or postmortems are carried out and produce practical improvements." }
      ]
    },
    {
      "name": "Risk and quality",
      "weight": 1,
      "questions": [
        { "text": "Testing is a real part of the development process in this project." },
        { "text": "The project has test cases or equivalent practices for checking expected behavior." },
        { "text": "Test automation covers a meaningful share of product risks." },
        { "text": "The team tracks bugs, failures, and task returns and uses that data for improvement." },
        { "text": "The process for detecting and fixing production bugs is organized and understandable." }
      ]
    },
    {
      "name": "Team and development",
      "weight": 1,
      "questions": [
        { "text": "Team retrospectives happen regularly and lead to concrete improvements." },
        { "text": "The team has regular personal feedback or one-to-one reflection practices." },
        { "text": "Team health and motivation are monitored and discussed systematically." },
        { "text": "There is a clear process for employee growth and development in the team." },
        { "text": "The team uses metrics to analyze its work and support decisions." }
      ]
    }
  ]
}