How do I handle a stakeholder who constantly changes requirements after the project has started?

All answers to this question.

Always document everything. If it's not in the project management software or an email, the change doesn't exist.

   Answered 2024-03-15 by Patricia Davis

• Exactly, Patricia. I’ll add that a "Scope Statement" signed at the beginning of the project is your best shield. When things get heated, you can always refer back to what was originally agreed upon.

     Commented 2024-03-16 by Sarah Jenkins

Do you think a "Fixed Scope" contract is actually realistic in today's fast-paced software development environment?

   Answered 2024-03-20 by James Wilson

• James, honestly, fixed scope is becoming a relic. Most successful PMs I know are moving toward "Fixed Budget, Variable Scope" models. This allows the stakeholder to swap features in and out as long as they stay within the total hour allotment. It fosters a more collaborative environment where the stakeholder feels they have agency without breaking the project's financial constraints.

     Commented 2024-03-22 by Robert Miller

The key is to implement a formal Change Control Board (CCB) process immediately. In a 2023 infrastructure project I managed, we had a similar issue. Instead of saying "no," I started using a "Change Request" form that required the stakeholder to document the business value of the change. We then presented the impact on the timeline and budget back to them. Usually, once they see that a "small" button change adds two weeks to the launch, they become much more selective. This shifts the focus from you being a "blocker" to you being a "steward" of the company's resources and project health.

   Answered 2024-05-18 by Linda Montgomery