Authoring Elegant and Meaningful Agile User Stories

Project scope is the agreed description of what a project will deliver and what it will not, stated precisely enough that a change to it can be recognised as a change and decided rather than absorbed.

A work breakdown structure decomposes a project's total scope into a hierarchy of deliverables and, at the bottom, work packages small enough to estimate, assign and track, so that everything to be produced appears exactly once.

The critical path is the longest chain of dependent activities through a project's schedule, which sets the earliest possible finish date and on which any delay delays the whole project.

A retainer is a recurring fee that holds a supplier's time or availability open across a period, so what the client buys is first call on somebody's attention rather than any named artefact.

A day rate sells a bounded unit of a supplier's working time rather than a finished result, so the client rather than the supplier carries the risk that the job turns out bigger than it looked.

A client brief is the short written statement of what a piece of work has to achieve, for whom, and under which fixed constraints, agreed before either side commits to a solution.