Glossary

An iterative approach to delivery that focuses on user needs, frequent learning, visible progress and continuous improvement.

A phase used to test possible solutions and risky assumptions before committing to full build.

The agreed conditions that must be met for a deliverable, story or milestone to be accepted.

A prioritised list of work items to be delivered or investigated by the team.

Pre-existing intellectual property owned by the company or a third party before the project starts.

A phase where the preferred solution is built and tested with real users before live operation.

The process for assessing and approving material changes to scope, cost, time, risk, acceptance, security, data or IP.

The agreed standard that must be met before work is considered complete.

The agreed standard that must be met before work is ready for delivery planning.

A phase used to understand the problem, users, constraints and opportunities before committing to a solution.

Intellectual property created during and for a specific project.

The phase where a service is operated, monitored, supported and continuously improved.

A test artifact used to learn. A prototype is not automatically production-ready.

Risks, Assumptions, Issues and Dependencies.

A planning artifact that shows direction, expected phases, key outcomes, dependencies and decision points.

The document that defines the authorised work package, including scope, deliverables, milestones, acceptance criteria and commercial terms.

A time-boxed investigation used to answer a technical question or reduce uncertainty.

A statement of what a user needs to achieve and why it matters.

Last updated 3 months ago

Was this helpful?