VA1tech ltd
software, decided

p.07 / Notebook

Notes worth keeping.

Short, practical resources for anyone commissioning software, plus the three tools from the front page. Useful whether or not you work with us.

N-1

A brief in one page

Five headings: the problem today; who has it; what would be different if solved; fixed constraints (dates, budget range, systems that must stay); what you do not know yet. Keep feature lists out of the first draft.

N-2

Twelve questions to ask any studio

  1. Who will actually do the work?
  2. How often will I see something working?
  3. How are changes to scope agreed?
  4. Whose name are the accounts in?
  5. What happens if you are unavailable?
  6. How do you test on real devices?
  7. What accessibility standard do you aim for?
  8. How do you handle personal data in testing?
  9. What documentation will I receive?
  10. What does support cost after launch?
  11. Which technologies, and why?
  12. What would make you turn this project down?

N-3

Five screen states

Ideal, empty, loading, partial and error. Ask to see all five for every important screen before development starts.

N-4

Handover checklist

T-1

Scope trimmer

Scope trimmer illustrative

Tick the features you are considering. For each, say how many users need it on day one. The trimmer splits a first release from later ones, keeping the first within the effort budget you set.

First release

    Later

      T-2

      Decision log

      Decision log yours to keep

      Record a decision, the reason, and when to revisit it. Export as plain text for your project folder. Entries stay in this browser only if you accept optional storage.

        T-3

        Release-notes tidier

        Release-notes tidier illustrative

        Paste raw change lines, as developers write them. Lines starting with fix, add, change or remove are grouped and rewritten into plain-English release notes.