Project constraint
A limit on how the project is run: time, budget, team, tools.
What it is
A project constraint limits the project rather than the product: live within three months, a budget ceiling, a team of two, only approved tools, no production access for contractors.
Why it matters
Time and money shape every technical choice. A design that is right for a two-year programme is wrong for a three-month launch. Making the limits explicit lets everyone choose solutions that fit them.
What goes wrong without it
- The team designs for an ideal world and runs out of time.
- Scope is cut at the last moment instead of planned.
- Tools or services are adopted that the organisation cannot pay for or support.
What it gives an AI agent
Agents do not know your deadline or budget. A project constraint lets the agent prefer the simpler option, flag work that will not fit, and avoid paid services the project cannot use.
Example: Clinic Booking
| Weak | Strong |
|---|---|
| We need this soon. | The system is live in three months, before the spring rush. |
How it relates to the rest
- Constrains the whole project or specific requirements.
- Differs from a project requirement: a constraint limits how the project runs, a project requirement is something it must deliver.
- Work packages and their dates are planned within it.
In Corpole
- Type Project Constraint (PJC), in the Constraints group.
- Acceptance criteria are optional.
- Agents receive project-wide constraints with every piece of work.