Team Health Check

Work through each delivery area. Check every statement that describes your team. Then click Show Results.

Deployment and Release

How your team ships software to production

The team treats deployments as high-risk events requiring coordination and full-team attentionWe need a dedicated stabilization period or hardening sprint before each releaseWe deploy to production monthly or less frequentlyEvery deployment requires approval from a change advisory board or managerWe cannot quickly reverse a deployment if something goes wrongDeploying one service requires coordinating and deploying other services at the same time

Testing Practice

How your team validates that software works before shipping

We rely on significant manual testing before each releaseRunning the full test suite takes 30 minutes or moreTests fail randomly without code changes - the team re-runs without investigatingWe have high test coverage numbers but bugs still reach productionRefactoring code breaks many tests even when behavior does not changeTests pass in one environment but fail in another

Code Integration

How your team merges and integrates code changes

Developers work on branches for more than a few days before mergingMerging branches regularly requires resolving significant conflictsPull requests sit for more than a day waiting for reviewThe team stops merging code for a period before each release to stabilizeDevelopers wait 30 minutes or more to learn whether a pushed change passed CI

Pipeline and Automation

How code moves from commit to running in production

There is no automated path from code commit to production deploymentWe need another team to make changes to our deployment pipelineOur staging and production environments are configured differentlyWe rebuild the application for each environment rather than promoting the same artifactEnvironments are provisioned and configured manually rather than through code

Visibility and Monitoring

How your team knows what is happening in production

Customers report production problems before the team knows about themIt takes more than 15 minutes to detect that a deployment caused a problemAlerts fire so often that the team routinely ignores or suppresses themCode works locally but fails in CI or production in ways that are hard to reproduceDuring incidents the team is unsure where to look or who is responsible

Team Dynamics

How your team collaborates, shares ownership, and improves

Only one or two people understand certain parts of the systemThe same people resolve every incident or production issueThe team has no protected time for technical improvement or reducing debtWhen things go wrong, the focus is on who made the mistake rather than what caused itNo one feels ownership over the operational health of services in productionCompleted features are handed off to a separate QA team before they can ship

Planning and Work Management

How your team plans, sizes, and tracks delivery work

Work items routinely take more than a week from start to doneMany items are in progress simultaneously but few are finishing each sprintSprint planning is dominated by negotiating cross-team dependenciesSprint commitments are routinely missed and delivery forecasts are unreliableStakeholders do not see working software until release dayEstimation sessions consume significant time but forecasts remain inaccurate