The glossary
Every word you'll meet in AI and machine learning, explained in everyday language.
The checks that say a ticket is done, written so anyone can run them.
A ticket is one piece of work with four parts: a title that starts with a verb ("Add a refunds table"), acceptance criteria that say how anyone can check it is done, a size small enough to finish in about three days, and an estimate written as a range. Criteria are easiest to write as given, when, then: given an order that was paid, when a support agent refunds it, then its status is "refunded" and the customer's balance goes up by the amount.
Each bar is a ticket at its likely size. Two people can work in parallel only once the endpoint exists.
Scoping and estimating work · A vague request cut into tickets with acceptance criteria and a first shippable slice, estimates as ranges, an honest update for a slip, and a ticket linked to its pull request. About 30 minutes.
1286 terms in the glossary, each with the lesson that teaches it.
Every word you'll meet in AI and machine learning, explained in everyday language.
A vague request cut into tickets with acceptance criteria and a first shippable slice, estimates as ranges, an honest update for a slip, and a ticket linked to its pull request.
Never trained an AI? Teach a small one to write, right in your browser. It takes about 20 seconds and needs no account. Teach it to write