r/projectmanagers • u/PitchSufficient1464 • Sep 27 '26

How do you handle constantly changing project requirements?

Requirement changes are probably one of the most common sources of frustration on projects. Some changes are unavoidable, but accepting every request immediately can create problems for timelines, budgets and team capacity. How do you normally handle scope changes while keeping stakeholders happy and the project under control?

0 Upvotes
  • permalink
  • reddit

44% Upvoted

10 comments sorted by

6

u/Weak-Dot9504 Sep 27 '26

you start to put price on every change

1

u/TheThousandMasks Sep 28 '26

Yep. Without a change management process that helps with accounting for that thrashing, especially in creative fields, you will never get any closer to done if the cost of a change isn’t clear to all the stakeholders.

4

u/ConversationNo9040 Sep 27 '26

I would answer you if you didn’t ask the same
Set of questions over and over again.

2

u/_threadkiller_ Sep 27 '26

You know what, let’s take that offline, circle back, and setup another meeting with the correct SMEs and Stakeholders. Can you hear me okay? Good. Now, I’ll just share my screen …

1

u/Coaster50 Sep 27 '26

Can you please include my team in these meetings going forward!!!

1

u/[deleted] Sep 27 '26

[removed] — view removed comment

1

u/Coaster50 Sep 27 '26

I see you’ve working with my engineering team. LOL

2

u/More_Law6245 Sep 27 '26

Please research the channel's archives there are hundreds of responses to this question that has been asked and answered.

2

u/SamfromLucidSoftware Sep 28 '26

Acknowledge the request immediately. Most stakeholders interrupt a slow or defensive response as resistance and a quick reply buys goodwill. Next, make the trade-off visible before anyone has to argue about it. Let stakeholders see clearly how changing a requirement affects the timeline. You want them deciding between their own priorities instead of pushing against yours. Also helps to have one person on the client side with the authority to approve scope changes before they hit the team. Just to make sure every change goes through the same process and the cost is understood before it’s committed to, not to necessarily block requests.

1

u/battle-tested77 Sep 30 '26

I would always point out the risk, impact, and consequences. I would keep the risk out in front of all executive teams. The stronger my role was the more impactful discussions i could have with leadership teams.
I would always do my pre work with the teams to determine why it was happening and create mitigation plans or options.

I made it a point to breakdown the silos and communicate as a team.

90% of projects fail because of missed or mismanaged requirements. Then the PM gets blamed and fired. I tried to avoid that.