I'm currently leading a software development project with a very tight fixed budget. The client keeps asking for "small" changes that are starting to add up, threatening our margin and the original deadline. How can I say no or negotiate these changes without damaging the relationship or appearing uncooperative? Are there specific Change Request templates that work best?
2 answers
The most important thing is to have a robust Change Management Plan agreed upon during the kickoff. When a client asks for a "small" change, don't say "no"—say "Yes, and here is how it affects the project." Show them the impact on the Iron Triangle: if scope goes up, either the budget or the timeline must also increase. I use a "Impact Assessment" document that clearly shows the cost and hours for every new request. Often, once the client sees the actual dollar value of their "small" request, they decide it’s not that important after all, or they agree to swap it for a lower-priority feature.
Do you think it’s possible that the initial requirements weren't defined clearly enough? Sometimes scope creep happens because the "must-haves" and "nice-to-haves" were never separated at the start.
Matthew, you hit the nail on the head. Using a MoSCoW prioritization matrix during the initiation phase is a lifesaver. It gives the PM a baseline to refer back to whenever the client tries to sneak in a 'Won't-have' item as a 'Must-have' later in the execution phase.