Plan a project
From a customer's list of needs to a release, one step at a time. Each step links the page that does it. It is for the scoper and the builder together, before a quote.
Build the shortlist
Find each of the customer's needs and tick it. The shortlist below gives the order to build them in, the recipes and samples once each, the limits to tell the customer and the requests to file. It lives in this page's address: copy the address to send it to a colleague.
The steps
- Write the wish list in the customer's own words, one need per line: "no more than 50 of one item on a line", not "a quantity validator".
- Find each need's card in the needs catalogue (its A to Z list is in the customer's words), or at a terminal with
python3 tools/needs/needs.py search <words>. A need with no card: place it on the ladder yourself, or ask for an extension point. - Fill the blueprint: copy its template or print the form (how to fill it);
python3 tools/needs/needs.py blueprint <id> <id> …prints its section (b), one row per card, with the verdict, the door and the limits. - Quote: read every limit to the customer and write it into the proposal; each card's Tell the customer line is written for that. Group the needs into as few apps as you can.
- Build each need from its card's recipe and sample, on your sandbox (build).
- Test: the samples' tests, the kit's checks and the money kit (chapter 14).
- Release through the customer's own release gate (chapter 14) and, for an app others install, the App library.
What is refused
Anything that breaks one of the four rules. The catalogue's What is not possible page lists the needs iVendNext cannot meet today, Not yet and Not possible, and what to do instead.