Scrum Health ChecklistA 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 StakeholdersIs the Product Vision known to every Scrum Team Member? Yes Partially No Not applicable Does the Product Backlog show with high probability what will be done in the near future? (1-2 sprints) Yes Partially No Not applicable Does each Product Backlog Item describe the Business Value it brings to the Product? Yes Partially No Not applicable Is the Scrum Team able to predict the approximate date of completion of the milestone? Yes Partially No Not applicable Has the Scrum Team provided Stakeholders with tools to predict the approximate completion date of the Milestone? Yes Partially No Not applicable 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.) Yes Partially No Not applicable Does the Scrum Team inform Stakeholders during the Sprint Review about the achievement or non-achievement of the Sprint Goal? Yes Partially No Not applicable Does the Scrum Team understand how the introduced changes affect the end user? Yes Partially No Not applicable Does the Scrum Team understand how the introduced changes affect the business? Yes Partially No Not applicable Does the Scrum Team confirm the roadmap/priorities for the near future with Stakeholders during the Sprint Review? Yes Partially No Not applicable Does the Scrum Team manage business risks and communicate them to stakeholders? Yes Partially No Not applicable Does the Scrum Team track and effectively manage technical risks/technical debt? Yes Partially No Not applicable NextTransparency: Scrum Team internallyDoes every Scrum Team Member know who is the Scrum Master? Yes Partially No Not applicable Does every Scrum Team Member know the Definition of Done? Yes Partially No Not applicable Is the knowledge obtained in the Refinement process written down in such a way that any Developer with appropriate competences can implement the change? Yes Partially No Not applicable As a result of Sprint Planning, does the entire Scrum Team know the detailed plan for achieving the Sprint Goal? Yes Partially No Not applicable If any problems arise, does each Developer transparently communicate them to the Scrum Team so that they can solve them together? Yes Partially No Not applicable Back NextInspection: ValueDuring the Sprint, does the Scrum Team provide single finished Sprint Backlog Items to Stakeholders for review? Yes Partially No Not applicable During the Sprint Review, do Stakeholders verify the Increment and provide feedback? Yes Partially No Not applicable During the Sprint Review, does Scrum Team uses near-production environment* to review changes / receive feedback? * near-production environment is treated like production, is not affected by devs outside main flow (e.g. no direct database updates) Yes Partially No Not applicable Does the Scrum Team measure what value the delivered Increment brought? Yes Partially No Not applicable Does the Scrum Team measure the quality of the delivered Increment? Yes Partially No Not applicable Does the delivered Increment not decrease the quality of the Product? Yes Partially No Not applicable Has every Developer checked whether every change they make meets the Definition of Done? Yes Partially No Not applicable Is the Daily Scrum focused on inspecting progress towards the Sprint Goal? Yes Partially No Not applicable Does the Scrum Team check during the Sprint whether it needs additional Refinement to plan the next Sprint? Yes Partially No Not applicable When planning future work (next sprint), does the Scrum Team verify whether there is technical debt that needs to be paid off? Yes Partially No Not applicable Does the Scrum Team verify new ideas and functionalities in terms of their contribution to the Product Goal? Yes Partially No Not applicable Back NextInspection: ProcessDuring Retro, does the Scrum Team verify whether previously planned improvements have been implemented? Yes Partially No Not applicable Does the Scrum Team measure the effectiveness of the improvements made? Yes Partially No Not applicable During Sprint Retrospective, does the Scrum Team identify the causes of mistakes made? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team check how the Sprint was going in terms of team cooperation? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team check how the Sprint was going in terms of cooperation with stakeholders? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team check how the Sprint was going in terms of processes? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team check how the Sprint was going in terms of tools? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team check how the Sprint was going in terms of the Definition of Done? Yes Partially No Not applicable Back NextAdaptation: ValueDoes the Scrum Team adapt the Roadmap / Product Backlog based on available feedback? Yes Partially No Not applicable Does the Scrum Team adapt the Roadmap / Product Backlog based on metrics? Yes Partially No Not applicable Is the Backlog modified based on changes in the Product environment (e.g. market conditions)? Yes Partially No Not applicable During the Daily Scrum, if a risk of not achieving the Sprint Goal is detected, does the Scrum Team modify the action plan to maximize the chances of achieving the Sprint Goal? Yes Partially No Not applicable Does Daily Scrum result in an actionable plan for the next working day? Yes Partially No Not applicable With growing understanding, do Developers clarify or negotiate with the Product Owner the scope of work for the upcoming sprints? Yes Partially No Not applicable Does the Scrum Team, by implementing changes, pay off the technical debt in the area it is changing? Yes Partially No Not applicable Back NextAdaptation: ProcessDuring Sprint Planning, does the Scrum Team take into account the availability of Scrum Team Members in the planned Sprint? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team plan activities to improve quality? Yes Partially No Not applicable During the Sprint Retrospective, does the Scrum Team plan activities to increase efficiency? Yes Partially No Not applicable During the Sprint, does the Scrum Team accomplish improvements planned in the previous Sprint Retrospective? Yes Partially No Not applicable Back NextYour details First name Last name Email (required) Company I consent to processing my personal data for marketing purposes. Back Submit Survey Technical Health ChecklistTHC 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.ArchitectureIs our architecture approach explicitly defined and documented? Yes Partially No Not applicable Is our documented architecture pattern consistently followed in the codebase?pattern consistently followed in codebase? Yes Partially No Not applicable Is our architecture appropriate for our system's scale and complexity? Yes Partially No Not applicable Is our business logic separated from infrastructure and does it clearly model business concepts?logic is separated from infrastructure and clearly models business concepts? Yes Partially No Not applicable Do our service boundaries support independent evolution of components? Yes Partially No Not applicable Are dependencies between our components controlled? Yes Partially No Not applicable Are our backend services stateless? Yes Partially No Not applicable Does our architecture support our performance and scalability requirements? Yes Partially No Not applicable Are our API contracts defined, versioned, and backward compatible? Yes Partially No Not applicable Are our asynchronous operations idempotent and safe to retry? Yes Partially No Not applicable Is our external communication resilient (timeouts, retries, fallbacks)? Yes Partially No Not applicable Is our external communication resilient (timeouts, retries, fallbacks)? Yes Partially No Not applicable Is our architecture documentation available and maintained? Yes Partially No Not applicable NextTestingIs our core business logic covered with unit tests? Yes Partially No Not applicable Do our integration tests verify interaction with infrastructure? Yes Partially No Not applicable Do our end-to-end tests cover critical user flows? Yes Partially No Not applicable Do our smoke tests validate basic system functionality after deployment?tests validate basic system functionality after deployment Yes Partially No Not applicable Is our test environment reproducible locally and in CI? Yes Partially No Not applicable Is our test data strategy defined? Yes Partially No Not applicable Is our test suite reliable and trusted by the team? Yes Partially No Not applicable Are our performance and load characteristics verified with tests? Yes Partially No Not applicable Back NextCI/CDDoes our automated CI pipeline build, test, and validate code? Yes Partially No Not applicable Do we have an automated deployment pipeline? Yes Partially No Not applicable Is our failure recovery strategy defined and effective? Yes Partially No Not applicable Do we have artifact versioning and traceability? Yes Partially No Not applicable Is our release process defined and repeatable? Yes Partially No Not applicable Is our environment configuration managed properly? Yes Partially No Not applicable Does our deployment process support safe releases? Yes Partially No Not applicable Is code quality enforced via reviews and automated checks? Yes Partially No Not applicable Is our infrastructure managed as code and are our environments reproducible? Yes Partially No Not applicable Does our branching strategy support fast and safe integration? Yes Partially No Not applicable Back NextObservabilityDo we have centralized logging available? Yes Partially No Not applicable Are our logs structured and useful? Yes Partially No Not applicable Is an error tracking system integrated? Yes Partially No Not applicable Are application metrics collected? Yes Partially No Not applicable Is alerting configured and actionable? Yes Partially No Not applicable Are correlation / trace IDs implemented? Yes Partially No Not applicable Is observability used in practice by our team? Yes Partially No Not applicable Back NextDataIs our database schema evolution versioned and safely deployable? Yes Partially No Not applicable Is our data access centralized and isolated? Yes Partially No Not applicable Is data ownership clearly defined? Yes Partially No Not applicable Is our backup and restore strategy defined and tested? Yes Partially No Not applicable Is our data consistency strategy defined? Yes Partially No Not applicable Are our data access patterns efficient and appropriate? Yes Partially No Not applicable Are our data access and changes observable? Yes Partially No Not applicable Is our data lifecycle defined and managed? Yes Partially No Not applicable Is our data synchronization and conflict resolution strategy defined? Yes Partially No Not applicable Back NextSecurityIs an authentication mechanism implemented? Yes Partially No Not applicable Is our authorization model defined and enforced? Yes Partially No Not applicable Are secrets managed securely? Yes Partially No Not applicable Is communication encrypted where required? Yes Partially No Not applicable Does our system comply with applicable regulatory and security standards? Yes Partially No Not applicable Are security headers properly configured on our web applications? Yes Partially No Not applicable Are our dependencies monitored, maintained, and scanned for vulnerabilities? Yes Partially No Not applicable Is sensitive data handled securely? Yes Partially No Not applicable Are security-relevant actions logged and traceable? Yes Partially No Not applicable Are basic abuse protection mechanisms implemented? Yes Partially No Not applicable Are external inputs validated and sanitized? Yes Partially No Not applicable Are security risks periodically reviewed and audited? Yes Partially No Not applicable Back NextYour details First name Last name Email (required) Company I consent to processing my personal data for marketing purposes. Back Submit Survey Product Health ChecklistThis 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 & DirectionIs the product strategy aligned with and driven by our business strategy? Yes Partially No Not applicable Is there an outcome-oriented roadmap built with key stakeholders, actively used for prioritization decisions? Yes Partially No Not applicable Were planned milestones/outcomes delivered in the last 2 sprints (during last month)? Yes Partially No Not applicable Is at least 1 key product success metric defined and regularly discussed with the stakeholder? Yes Partially No Not applicable Is an inspiring product vision defined and known to both the team and key stakeholders? Yes Partially No Not applicable NextDiscovery & LearningIs the team engaged in validating insights and solutions before development starts? Yes Partially No Not applicable Did we have contact with a real user or customer in the last 4 weeks that influenced a product decision? Yes Partially No Not applicable Do we know what our biggest current product assumption is, and are we testing it? Yes Partially No Not applicable Is there a structured product analytics approach in place to measure the effects of what we ship? Yes Partially No Not applicable Back NextDelivery & QualityAre sprint goals delivered as planned? Yes Partially No Not applicable Are product quality metrics defined and monitored? Yes Partially No Not applicable Are production incidents/downtimes systematically logged with mitigation plans communicated to stakeholders? Yes Partially No Not applicable Is the backlog prioritized by business value, well-refined, and ready at least 1 sprint ahead? Yes Partially No Not applicable Is technical debt recognized, visible in the backlog, and actively managed? Yes Partially No Not applicable Is there a clear business rationale documented behind new functionalities being built? Yes Partially No Not applicable Back NextClient & Executive AlignmentHas the decision-maker/person paying confirmed the current product direction in the last 6 weeks? Yes Partially No Not applicable Do we know our real north star – what we consider the measure of success for this product? Yes Partially No Not applicable Do key stakeholders understand the value we've delivered in the last sprint (outcomes, not just features)? Yes Partially No Not applicable Is the engagement free of political, relational, or trust risks that could impact product outcomes? Yes Partially No Not applicable Is the budget/financial model stable and supporting the planned product outcomes? Yes Partially No Not applicable Back NextTeam Leadership & OwnershipDoes the Product Team participate in strategy discussions both internally and with stakeholders? Yes Partially No Not applicable Is the team encouraged to dig into the problem cause with stakeholders rather than just delivering the defined solution? Yes Partially No Not applicable Does the Product Team self-organize its work focusing on outcomes to be delivered and user problems to be solved? Yes Partially No Not applicable Do all key stakeholders, including person paying, actively participate in Sprint Review giving feedback and business updates? Yes Partially No Not applicable Does feedback from key business stakeholders lead to actual changes in product decisions/backlog? Yes Partially No Not applicable Back NextYour details First name Last name Email (required) Company I consent to processing my personal data for marketing purposes. Back Submit Survey
