Every change needs a boundary, and the boundary has four parts:
- In scope: what the change will deliver. "Online returns for delivered orders, refunded to the original card."
- Out of scope: what it will not, stated so nobody assumes it. "Exchanges; returns of items bought in store."
- Assumptions: things taken as true that the project does not control. "The carrier keeps collecting daily." Each one is a risk if it turns out false: track it.
- Constraints: limits the solution must work within. "Live before January 5", "within $180,000", "on the existing returns system".
Writing "out of scope" feels negative, but it prevents the most expensive arguments. An assumption nobody wrote down becomes a surprise; a constraint nobody wrote down becomes a design that cannot be built in time.
A dependency is related: something the change needs from outside it, such as another team's interface by a date.