Project planning

Defining deliverables and acceptance criteria

Agreeing on what will be reviewed at completion supports design, communication and project closure.

01

Turn the objective into an observable condition

Statements such as “make it work better” leave too much room for interpretation. Describe the function, part and review conditions. If there is a measurable target, define its source and how it will be checked.

  • Required function
  • Part, variant and working condition
  • Agreed criterion and review method
02

Define the delivery package

Depending on the project, the package may include drawings, models, components, diagrams, programs and operating documentation. The proposal should identify included files and versions, as well as customer-supplied information.

  • Included files and documents
  • Equipment or components to deliver
  • Required access, licenses or information
03

Plan the checks from the start

Samples, interfaces and review conditions need to be available at the right time. For equipment modifications, agree on the work window and the people who will participate in the review.

  • Representative samples and variants
  • Equipment and utility availability
  • People responsible for review and observations
04

Record changes and closure items

When a part, sequence or function changes, review the impact on scope and schedule. At completion, distinguish accepted work, open observations and later phases. Order and standardization help maintain that clarity.

  • Requirement and design version
  • Changes agreed during development
  • Observations and closure documentation

Related applications

Let’s turn your need into a clear scope.