The release plan had a short section titled “Out of scope.” Offline mode. Bulk export. Custom roles. The team wrote it deliberately, and the stakeholders signed off on it. Six weeks later, an account manager asked whether bulk export could go in “just for one customer.” It was a small ask, so it went in. Then custom roles came back as a dependency of something else. Nobody raised a change request, and the list on the wiki never changed. The release shipped five days late.
That is a composite, not a customer. The pattern is common, and it is easy to miss because the document still looks right.
What out of scope means
Out of scope means work the release has agreed not to do. Project teams also call this scope exclusions. It is usually one section of the scope statement: the requests, features and use cases a release will not deliver. A good list is specific, because “no performance work” invites argument and “no bulk export” does not.
The list is the team’s engineering judgment, made at the confidence vote. The people who will build the release decide what it will not carry, and the committed date reflects that choice. The list is a promise to say no.
How exceptions get in
Exceptions rarely arrive as a scope change. They arrive as favors: a “just this once” from a stakeholder, a “while you’re in there” from a developer, an escalation that reclassifies an exclusion as a defect. Each one is small enough to say yes to without a meeting. That is scope creep, the first of the three things that erode a committed release date. Dependencies surfaced too late and capacity changes move the same date in the same direction.
Three things make out-of-scope exceptions hard to see:
- The list does not change. The exception is created as an ordinary issue in the release, so the document still says “out of scope.”
- The estimate looks small. The ask is sized on its own, not against the days left to the committed date.
- The cost lands later. The forecast moves a little each time, and the board still says green.
Keep the promise, or price the exception
The fix is not a harder no. Sometimes the exception is right, and the business should have it. The fix is to make saying yes an informed decision.
- At the vote, record the committed date and the confidence the team committed at, next to the out-of-scope list.
- Treat an exception as a request to change the commitment, however small. Add it to the release as ordinary scope.
- Read what it does to the forecast, in days, at the committed confidence, before anyone agrees.
- Then choose: accept it and renegotiate the date, swap it for equal unstarted work, or decline it.
An illustration, not customer data. A release is committed for 14 May at 85% confidence. At the vote, the 85% forecast sits at 11 May: three days of margin. Bulk export is pulled in as one “small” item. The 85% forecast moves to 13 May. A second exception follows, a custom-role fix, and the 85% forecast reaches 16 May, two days past the commitment, so the release reads amber. Each ask looked like a day. Together they cost five. With the numbers in front of them, the team swaps bulk export for two unstarted Could-haves and keeps the date, and the account manager gets an honest answer about when export will ship.
Where Advanced Release Planning fits
Advanced Release Planning for Jira reads the Fix Version, the Jira issue links and the throughput window the team selects, and reports the committed date against its confidence band: P50, P85 and P95. It has no out-of-scope object and does not store the list. An excluded item that is pulled in enters the Fix Version as ordinary scope, and the forecast counts it like any other issue. Scope growth shows as a percentage and a per-day rate, and removals step the burn-up scope line down. A release reads green at or above P85, amber between P50 and P85, and red below P50. The team sets the assumptions: which throughput window, whose capacity, what is in scope. The app does the arithmetic at Monte Carlo scale and keeps it live. It does not tell the team whether to say yes. It tells the team what yes costs.
For the document behind the list, see the scope statement draws the boundary, it doesn’t watch it move. For what a signed scope leaves unpriced, see the scope baseline is signed once. For the cut when an exception has to be paid for, see why descoping is cheapest the week it becomes necessary. The mechanics are in the out-of-scope reference doc.
Key takeaways
- Out of scope means the work a release has agreed not to do. It is the team’s engineering judgment at the confidence vote.
- Exceptions enter as ordinary issues, so the list stays unchanged while the committed date moves.
- Price each exception in days at the committed confidence before agreeing to it.
- Accept, swap or decline. Make the choice with the numbers in front of the team.
FAQ
What does out of scope mean in a project?
It means work that falls outside the agreed boundary of the project or release. The out-of-scope list records what the team will not deliver, so that stakeholders share the same expectation.
Why list what is out of scope?
A written exclusion turns a vague “no” into something stakeholders can see and agree to. It makes an exception a visible decision rather than a favor.
What should a team do when an out-of-scope item is requested?
Treat it as a request to change the commitment. Add it to the release, read what it does to the forecast against the committed date, then accept it, swap it for equal work, or decline it.
Commit on the team’s judgment. Price every exception in days. See what each exception costs your committed date in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




Leave a Reply
Your email is safe with us.