Concept

Objective

A measurable outcome the project exists to achieve. Every other record should trace back to one.

What it is

An objective says what must be true when the project has succeeded, in a way someone can measure. It is not a feature and not a task; it is the reason features and tasks exist.

Why it matters

Objectives are how a team decides what matters. When two requirements compete for time, the one that serves an objective better wins. Without objectives, every request looks equally important, and the project grows in every direction at once.

They also tell you when to stop. A project whose objectives are met is done, even if the backlog is not empty.

What goes wrong without it

  • Features pile up that no one can connect to a goal.
  • Priorities are decided by whoever asks loudest or last.
  • Success is argued about after launch, because it was never defined before it.
  • Scope creeps, because nothing says a request is out of scope.

What it gives an AI agent

An agent that knows the objective behind a requirement makes better choices where the requirement is silent. Asked to build a booking form, an agent that knows the goal is "book in under a minute" will keep it short; one that does not may add every field it can think of.

Objectives also let people see, before code is written, which proposed work serves no goal at all.

Example: Clinic Booking

WeakStrong
Improve the booking experience.Patients can book, move or cancel an appointment online in under a minute (measured on 95% of sessions).

The strong version names who, what and how you will know.

How it relates to the rest

  • Business requirements refine an objective: what the organisation needs to reach it.
  • Themes and epics serve an objective: the work that contributes to it.
  • Objectives are rarely changed; when they are, everything below them deserves a second look.

In Corpole

  • Type Objective (OBJ), in the Intent group.
  • Business requirements are linked to it with refines; themes and epics serve it.
  • Corpole flags an objective that no business requirement refines, and requirements that trace to no objective.
  • Acceptance criteria are optional for objectives, but a measurable statement is the point.