Templates and checklists
Everything to decide before development starts
Changes are cheap on paper and expensive in code. This checklist covers the decisions that most often get missed until a project is half built: who can see and change what, what happens when something goes wrong in a workflow, which data comes in and in what state, which systems must be connected, how each feature will be checked, and who looks after the system after launch. Use it with your team before you ask for quotes, or with the development team in the first workshop. Each item is a question to answer, not a feature to buy.
How to use it
- 1.Go through one section at a time with the people who know that part of the work.
- 2.Tick an item only when the answer is written down somewhere the team can find it.
- 3.Leave "we don't know yet" as an answer where it is true; it is better than a guess.
- 4.Share the result with every team you ask for a quote, so they price the same thing.
Everything to decide before development starts
0 of 27 ticked
From NOVA Solutions · novasolutions.bassemhazem.com
Questions
Is this a full requirements document?
No. It is the list of decisions a requirements document needs. Once the items are answered, a team can turn them into a written scope with milestones.
Do I need every answer before asking for quotes?
No. Users, the main workflows and the first-version scope are enough to start. Mark the rest as open, and a good team will help you decide.
Which part is most often forgotten?
Exceptions in workflows and the state of existing data. Both are invisible in a demo and decide how long the real project takes.
Sounds like your week?
Tell us how the work happens today. A person from NOVA reads every brief and answers.