Free self-assessment

Delivery health check

Ten questions, two minutes, no email required to see your result. Answer for one specific project or team — honestly, not aspirationally.

1 / 10 · Visibility of the next 30 days

Is there a single, current view of what will ship in the next 30 days?

No — plans live in heads and chat threads A plan exists but it’s out of date Mostly current, but not everyone trusts it Yes — one plan, current, and believed

2 / 10 · Working software cadence

When did a stakeholder last see working software — not a slide deck?

Can’t remember / months ago Last quarter In the last month In the last two weeks

3 / 10 · Commitments kept

Does the team commit to work per iteration and usually finish it?

There are no real iterations Commitments roll over more often than not Usually finished, with regular exceptions Yes — commitments are typically met

4 / 10 · Delivery ownership

Is one person clearly accountable for delivery end-to-end?

No one owns it A committee / it’s shared Someone owns it as a side job Yes — one named owner with authority

5 / 10 · Path to production

How long does a small code change take to reach production?

Weeks, or nobody knows About a week, with manual steps A day or two Hours — releases are routine

6 / 10 · Budget vs. progress

Are budget and forecast reviewed against actual progress?

No — spend is discovered, not tracked Only when something feels wrong Quarterly Monthly or better

7 / 10 · Risk awareness

Could you name the top three risks to delivery right now?

No Vaguely — nothing written down Yes, but nobody owns them Yes — named, owned, and being worked

8 / 10 · Priority stability

How often do priorities change mid-iteration?

Constantly — every week brings a new #1 Often enough that plans feel pointless Occasionally, for genuine emergencies Rarely — priorities hold between planning points

9 / 10 · Release confidence

Can you release without a manual testing marathon?

Every release is a high-stakes event Days of manual testing each time Some automation; manual spot checks Automated tests carry most of the load

10 / 10 · Key-person risk

If your most critical developer left tomorrow, how bad would it be?

Catastrophic — it all lives in their head Months of disruption Painful but survivable Manageable — knowledge is shared and documented

0 of 10 answered — your score appears when all ten are done.