Managing Scope
Haat's Diwali sale is six weeks away, and the team is building "split payment": pay part with a wallet and part with a card. Halfway through, Rohan asks whether they could also add "pay with reward points", since "it's basically the same thing". The date can't move and neither can the team, so something has to give.
The rule
When new work comes in, other work goes out: say which, out loud.
Every project balances three things: time, people and scope, meaning what gets built. When the date and the team are fixed, as they are for a sale, scope is the only honest lever left.
There is also a dishonest lever: quality. A team that says yes to everything and still keeps the date usually does it by skipping tests, load checks and careful reviews. Nobody decides that on purpose; it just happens, and the bill arrives on sale day.
Good scope management means:
- Agree the must-haves up front. Sort features into must, should and could. For the sale, "pay with wallet plus card" is a must; "split across two cards" is a could.
- Price every change. A new request gets an estimate before it gets an answer.
- Trade, don't stack. If something comes in, something of similar size goes out, or the date moves. Offer the options and let the product manager choose.
- Write down the decision. One line in a decision log saves a month of "I thought we were doing that."
Watch for scope creep: many small additions, each "only a day", that together push the date. Each one looks harmless; the pile is not.
The shortcut
Cost it, pick the swap, record it. Don't answer a change request with yes or no. Answer with its price and the options.
Cost it
Farhan and the engineers estimate 6–8 days, plus a new API from the loyalty team, which is outside their control.
Notice that Meera never said no. She turned a vague request into a priced choice, and the person who owns priorities made it. That keeps scope conversations calm instead of turning them into a fight.
Drills
Answer fast — trust the rule.
The date and the team are both fixed. Which lever should the team use?
Rohan asks for "just a small tweak" in the middle of the sprint. What is Meera's first step?
What is scope creep?
The team kept the sale date by quietly skipping load tests. What really happened?
Remember
- When new work comes in, other work goes out: say which, out loud.
- Cost it, pick the swap, record it.
- Watch for scope creep, and never let quality become the hidden lever.
