Plus/Minus Scope Review¶
Review ritual — instantiates Scope Creep Containment
A recurring review that refuses to let any addition in without naming, in the same session, the cut, deferral, or buffer draw that pays for it — making scope changes symmetric instead of additive-only.
A Plus/Minus Scope Review is a standing session whose single non-negotiable rule is that every proposed plus must be paired, then and there, with a minus — something removed, deferred, downgraded, or drawn from a declared reserve to fund it. Its defining move is to make scope changes symmetric: additions and subtractions happen in the same breath, at the same table, so the perimeter cannot grow silently one favor at a time. Where most scope processes treat "should we add this?" as a standalone yes/no, the plus/minus review reframes it as "add this instead of what?" It is a ritual of enforced tradeoff, not a storage list and not an authority: its job is to keep the total roughly conserved by making the cost of each addition a concrete, same-session sacrifice rather than a promise to worry later.
Example¶
A game studio is eight months into a fixed ship date for a mid-budget action title. The creative director keeps having good ideas: a photo mode, a harder difficulty tier, destructible cover, a second boss encounter. In a purely additive culture, each would be greenlit in a hallway and the date would quietly slip toward a crunch.
The producer runs a Plus/Minus Scope Review every sprint. The rule is posted on the wall: nothing gets added without a matching cut of comparable size. When photo mode is proposed, the room agrees to it — but only by cutting an unloved second traversal ability that was eating the same animation budget. Destructible cover is a big plus, so it is funded partly by deferring the second boss to a possible post-launch update and partly by spending an explicitly-reserved two weeks of schedule slack the studio set aside at the start for exactly this. The harder difficulty tier is proposed with no offsetting minus on the table, and under the rule it simply doesn't get added that sprint. By ship, the feature set has changed a lot and grown very little — and every trade is one the team chose out loud.
How it works¶
What distinguishes the review from ordinary prioritization is the conservation rule and the same-session pairing:
- Pair or park. An addition without a named offset does not enter. The offset can be a cut, a deferral, a quality downgrade, or a draw against a declared reserve — but it must be concrete and named now, not "we'll find the time somewhere."
- Comparable size. The minus must plausibly pay for the plus; trading a large feature for a trivial cleanup is how the rule gets gamed into pure addition.
- A declared reserve is the legitimate exception. When there is genuine slack set aside up front, spending it is an allowed way to fund a plus — but it is a visible withdrawal from a finite account, not free room.
- The ritual is recurring. Because it runs every cycle, it catches drift continuously rather than at a late, painful reckoning.
Tuning parameters¶
- Exchange strictness — strict one-for-one conservation versus a looser "roughly net-neutral." Tighter conservation holds the line harder but frustrates teams during genuine learning; looser rules risk slow additive drift.
- Reserve size — how much slack is declared as spendable buffer at the start. A larger reserve absorbs more good surprises but is a bigger cushion for creep to hide in; too small and the rule blocks all adaptation.
- Currency of the trade — whether pluses and minuses are measured in effort, schedule, story points, or feature count. The chosen currency shapes which trades look "fair."
- Cadence — how often the review runs; frequent reviews keep the set of open trades small and current, but cost meeting time.
When it helps, and when it misleads¶
Its strength is that it makes the cost of "yes" immediate and concrete, converting an abstract worry about creep into a visible, chosen sacrifice — a discipline in the spirit of the project-management "iron triangle," where scope cannot expand without something in time, cost, or quality giving way.[1] It is unusually good at preserving responsiveness: teams can still absorb great ideas, but only by consciously trading, so the plan changes without swelling.
Its failure mode is the rigged trade — cosmetic minuses (deleting dead backlog items, "cutting" work already finished) offered to unlock real pluses, so the rule is honored in form while scope grows in fact. It can also become false rigidity, blocking a genuinely necessary addition because no equal cut is handy, or quietly draining a buffer that was never really there. The guarding discipline is to insist the minus be real and comparable and to treat the reserve as a finite, visible account — a plus/minus review whose minuses don't hurt isn't containing anything.
How it implements the components¶
subtraction_or_tradeoff_path— the review is the subtraction path made mandatory and immediate; it operationalizes removal, deferral, and downgrade as the price of every addition.scope_buffer— it treats a declared reserve of slack as a spendable currency for funding pluses, making buffer draws explicit withdrawals rather than silent absorption.
The review decides the trade but doesn't track the perimeter over time: it does not maintain the scope_change_ledger (that is the Scope Change Request Template's running record) and it does not chart cumulative drift — the original_vs_current_scope_comparison is the Scope Drift Dashboard's.
Related¶
- Instantiates: Scope Creep Containment — the review is where additions and subtractions are kept symmetric.
- Consumes: Impact Assessment Checkpoint supplies the sizing that makes a plus and a minus "comparable."
- Sibling mechanisms: Deferred Scope Parking Lot · Change Control Board · Scope Drift Dashboard · Rebaseline Workshop · Scope Freeze Protocol
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Plus/Minus Scope Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a recurring review that refuses to let any addition in without naming, in the same session, the cut, deferral, or buffer draw that pays for it — making scope changes symmetric instead of additive-only.
Independent corroboration: The frozen evidence defines Plus/Minus Scope Review as 'A recurring review that refuses to let any addition in without naming, in the same session, the cut, deferral, or buffer draw that pays for it — making scope changes symmetric instead of additive-only', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Rule, Policy & Commitment — Plus/Minus Scope Review includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The mechanism is a project and portfolio governance ritual: managerial scope control makes every addition compete explicitly with an existing commitment.
Related originating lineages:
- Operations Research — Operations Research supplies the capacity-constrained allocation logic that makes additions and cuts symmetric.
Review resolution: Both blind reviewers agree that organizational management is the primary origin. Reconciliation resolves reported ambiguity, alternate origin disagreement, origin mode disagreement. Formative alternate lineages are retained as operations_research; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The exact plus/minus ritual appears to be an encyclopedia-specific synthesis rather than a standard named method.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The plus/minus review and the Deferred Scope Parking Lot both touch subtraction, but they are not the same act: the review is the room where the tradeoff is decided (this in, that out, now), while the parking lot is only the shelf where a deferred item is stored. Deferral is often the minus a review reaches for — so the two are complementary, one deciding and one holding, not interchangeable.
References¶
[1] Atkinson, R. "Project Management: Cost, Time and Quality, Two Best Guesses and a Phenomenon, Its Time to Accept Other Success Criteria". International Journal of Project Management 17(6), 337–342 (1999). Identifies cost, time, and quality as the traditional project-management Iron Triangle. registry ↩