Scrum Health Checklist

A structured checklist to assess how well your Scrum team collaborates, inspects value, and adapts based on feedback – with a simple scoring model to track progress over time. It consists of 3 main areas, 6 subareas, and 47 questions.

Transparency: Between Scrum Team and Stakeholders

Is the Product Vision known to every Scrum Team Member?

Does the Product Backlog show with high probability what will be done in the near future? (1-2 sprints)

Does each Product Backlog Item describe the Business Value it brings to the Product?

Is the Scrum Team able to predict the approximate date of completion of the milestone?

Has the Scrum Team provided Stakeholders with tools to predict the approximate completion date of the Milestone?

Is the Sprint Backlog the complete and only source of information about what the team is working on during the sprint? (functionalities, technical debt, retro improvements, etc.)

Does the Scrum Team inform Stakeholders during the Sprint Review about the achievement or non-achievement of the Sprint Goal?

Does the Scrum Team understand how the introduced changes affect the end user?

Does the Scrum Team understand how the introduced changes affect the business?

Does the Scrum Team confirm the roadmap/priorities for the near future with Stakeholders during the Sprint Review?

Does the Scrum Team manage business risks and communicate them to stakeholders?

Does the Scrum Team track and effectively manage technical risks/technical debt?

Technical Health Checklist

THC 2.0 is a self-assessment of your product's technical health: 59 questions across six areas — Architecture, Testing, CI/CD, Observability, Data, and Security.Use it to check whether your foundations are strong enough for how you build and scale today — and to spot gaps before they turn into delivery delays, rework, or painful handovers. This is not a rigid audit or documentation for its own sake; it makes technical risk visible so you can act early.When you finish, you receive a personalized PDF report with your score, findings by area, and practical recommendations on what to improve first.

Architecture

Is our architecture approach explicitly defined and documented?

Is our documented architecture pattern consistently followed in the codebase?pattern consistently followed in codebase?

Is our architecture appropriate for our system's scale and complexity?

Is our business logic separated from infrastructure and does it clearly model business concepts?logic is separated from infrastructure and clearly models business concepts?

Do our service boundaries support independent evolution of components?

Are dependencies between our components controlled?

Are our backend services stateless?

Does our architecture support our performance and scalability requirements?

Are our API contracts defined, versioned, and backward compatible?

Are our asynchronous operations idempotent and safe to retry?

Is our external communication resilient (timeouts, retries, fallbacks)?

Is our external communication resilient (timeouts, retries, fallbacks)?

Is our architecture documentation available and maintained?

Product Health Checklist

This is a product health assessment checklist that helps a team evaluate how well a product is functioning across areas like strategy, discovery, delivery, and leadership. Based on Yes/No answers, it calculates an overall score and highlights the product’s biggest gaps and areas that need clarification or improvement.

Strategy & Direction

Is the product strategy aligned with and driven by our business strategy?

Is there an outcome-oriented roadmap built with key stakeholders, actively used for prioritization decisions?

Were planned milestones/outcomes delivered in the last 2 sprints (during last month)?

Is at least 1 key product success metric defined and regularly discussed with the stakeholder?

Is an inspiring product vision defined and known to both the team and key stakeholders?