Tool
How ready are your requirements?
Ten questions about the business need behind a project. You get a score, what to firm up first, and the service and template that fit where you are.
- It takes a few minutes and you do not have to give your name or email.
- It measures how clear and agreed the need is, not how good the idea is.
- It is a conversation starter, not a verdict.
The questions
Choose the answer that is closest to the truth today
Your result
out of 30 points
An early idea
You have a direction, but the problem, the users and the measures are not yet written down. That is a normal place to start.
Next step: Put the business need on paper first: the problem, who it affects, how you will know it worked, and what is in and out of scope.
Taking shape
Some parts are clear and others are still assumptions. The gaps listed below are the ones most likely to cause rework later.
Next step: Finish the business requirements document, starting with the areas below, and get the approvers to sign it before anyone specifies a solution.
Mostly clear
Your business need is largely settled. A few areas need firming up before a developer can build from it with confidence.
Next step: Close the remaining gaps, then turn the requirements into a specification: roles, data, security, integrations and tests.
Ready to specify
The business need is clear, agreed and measurable. You are in a good position to write the specification and plan the build.
Next step: Write the software requirements specification, so that what is built, tested and accepted is written down before the build starts.
Firm these up first
The areas where you answered at the lowest levels, weakest first.
This is a starting point for a conversation. It looks only at how clear your requirements are, and it is not advice, a quote or a timeline.