Resources

Discovery phase checklist

Use this checklist before a build starts. If you can answer every question in a section, that part of discovery is done. If you cannot, you have found a risk while it is still cheap to fix. Each section matches a stage of the discovery template, and one covers the regulatory and compliance questions that are easiest to miss.

1. How to use this checklist

  1. Run it in the last week of discovery, or at any point when someone asks "are we ready to build?".
  2. Answer each question yes, no or not yet, and name the person who owns each no.
  3. A no is not a failure: it is an open question or a risk, so write it down with an owner and a date.
  4. Run the checklist again before sign-off. Every section should be a yes, or a risk the sponsor has accepted in writing.

2. People and context

  • Do we know who approves scope, budget and the final result?
  • Have we spoken to the people who will use the product, not only the ones who pay for it?
  • Do we know who can say no, and what would make them do so?
  • Is the current process or product documented, with its pain points?
  • Do we know what was tried before and why it did not work?
  • Are budget, deadline and fixed technology choices written down?

3. Problem and goals

  • Can we state the problem in two sentences without naming a solution?
  • Do we have evidence that the problem is real: data, quotes or support tickets?
  • Does every goal have a metric, a current value, a target and a date?
  • Do stakeholders agree on which goal matters most?
  • Have we said what is out of scope?

4. Users and journeys

  • Are the user types and their goals listed?
  • Is the main journey of each user mapped step by step?
  • Do we know where users get stuck or drop off today?
  • Are the key processes drawn as flows that everyone has read?
  • Are special cases covered: first use, errors, permissions, empty states?

5. Requirements

  • Is every requirement short, specific and testable?
  • Does each Must have acceptance criteria?
  • Is every requirement linked to a goal, and every goal to at least one requirement?
  • Are non-functional needs named: performance, security, availability, accessibility, compliance?
  • Are priorities agreed using MoSCoW, with no more than about 60% Musts?
  • Do two requirements contradict each other?

6. Architecture and integrations

  • Is there a diagram showing the system and the systems around it?
  • Do we know every integration, its owner and whether its API exists and is documented?
  • Do we know where the data comes from, where it is stored and who may see it?
  • Are the important technical choices recorded with the options that were compared?
  • Have we checked licenses, hosting and compliance constraints?

7. Regulatory and compliance questions

Ask these early. A regulatory duty found after the build starts can change the architecture, the hosting and the budget.

  • Which laws, standards or industry rules apply to this product, such as privacy law, accessibility rules or sector regulation?
  • What personal, financial or health data will the product handle, and where may it be stored and processed?
  • Do any customers require a security review, a data processing agreement or a particular hosting region?
  • Who in the client’s company owns compliance, and have they seen the scope?
  • Are retention, deletion and audit-trail needs written down as non-functional requirements?
  • Which of these answers are assumptions, and who will confirm them? Move each one to the open questions list.

This is a list of questions, not legal advice. Have a qualified person confirm which rules apply to your project.

8. Estimates, roadmap and risks

  • Are estimates given as ranges, with the assumptions behind them?
  • Is the work split into milestones that each deliver something visible?
  • Are dependencies between milestones and teams written down?
  • Is each risk described with likelihood, impact and an owner?
  • Are open questions listed with who answers them and by when?
  • Do the client and the team read the same plan?

9. Sign-off

  • Has the executive summary been read by the decision maker?
  • Is the scope for the first release agreed in writing?
  • Is the next step clear: build, a smaller pilot or stop?
  • Is the whole discovery in one shareable document rather than scattered across files?

10. Signs that discovery is not finished

  • Goals have no numbers, or nobody can say what today’s value is.
  • Most requirements are marked Must, or none has acceptance criteria.
  • An integration is on the list, but nobody has checked that its API exists.
  • The estimate is a single number with no stated assumptions.
  • There are no risks or open questions on the list.
  • The people who will use the product have not been interviewed.