Project Management

Please login or join to subscribe to this thread

How to handle a difficult stakeholder who constantly changes project requirements?

linkedin twitter facebook  
avatar
Rahul Patekar Project Manager| Xebrium Ca, United States
Can someone suggest some practical ways?

Thanks
Sort By:
< 1 2 >
avatar
Joshua Cedor Principal Consultant Sacramento, Ca, United States
I agree with Deepesh. In addition, a Requirements Traceability Matrix may be of assistance here. Although this is not necessarily the intent of an RTM, consider the alternate value it may provide in demonstrating the impact of the requirement 'drift' you are experiencing. As test cases and outcomes have to be constantly updated, you will be able to quantitatively show the strain and uncertainty (outcome = increased risk) the changing requirements are putting on both the project team members and the project's success criteria. If this difficult stakeholder is high up in the chain of command, they will be presented with a clear picture of their own impact. If they are lower in the chain of command, their supervisor/project sponsor will be able to see it. When data speaks, good leaders listen.
avatar
Rahul Patekar Project Manager| Xebrium Ca, United States
Feb 04, 2020 10:12 AM
Replying to Thomas Walenta
...
Rahul

try first to understand why he is behaving as he is. How he is feeling towards you, the project, the requirements (Guess he is insecure).
Then try to increase his trust in you, increase his security level.

Make sure he feels taken care of by you,
- respect him, acknowledge his status
- explain to him what you are planning to do (e.g. agree with him on a change management procedure)
- give him options to decide
- make sure he feels you are in the same team with him
- be honest and fair with him

Practically, start listing every change and its consequences on the project (a change register), and share it with him. Be careful not to threaten him with that but to use it as a fact base.

You as project manager must make your customer feel safe and secure.
Thanks Thomas, this really helps.
avatar
Rahul Patekar Project Manager| Xebrium Ca, United States
Feb 04, 2020 5:59 PM
Replying to Deepesh Rammoorthy
...
Golden rule :- Whoever holds the purse strings on the project has the biggest voice. If it's your sponsor, they are the most powerful .

Where's the project governance? the steering committee and Project Board?
Ask this stakeholder to put their change request in writing . Set the expectation that any Change Request would require evaluation and will affect scope, cost, schedule .
Inform your sponsor that you will need to invest time and effort to evaluate the change request and get their agreement and endorsement to go ahead to spend time on investigating the change.
IF the sponsor feels that such investment of effort is unnecessary , relay that back to the stakeholder.
IF the sponsor feels that you should go ahead with evaluating the change , then present the change and ask for formal sign off at the Project Board and Steering committee . And let it be minuted that you have been approved or rejected for the increased scope, time and/or cost.

IN the absence of a project board ...
if in the middle of a sprint , set the expectation with the stakeholder {even if they are the product owner} that the change will be evaluated by the team at the end of the sprint . Make sure your Product Owner is fully on-board with this .
Get the team to evaluate the change once the sprint is finished.
If the change presents a good value proposition after evaluation, present it to your sponsor and seek their endorsement . If sponsor agrees to implement the change , schedule it in with your team in one of the future sprints . If the sponsor rejects , then let your stakeholder know.

IF your sponsor does not back you up , then , Rahul, my friend, dust off the cobwebs from your resume. The market is waiting for you ! :)
Thank you so much, Deepesh, for such a detailed answer. I like the idea of seeking endorsement at the end of the sprint. Again challenge would be communicating such suggestions in front of the stakeholder. It seems it is necessary to bring them both i.e. project sponsor and the stakeholder on the same table.

The third solution will always be there if the sponsor himself does not back me up.
avatar
Rahul Patekar Project Manager| Xebrium Ca, United States
Feb 04, 2020 10:15 AM
Replying to Luis Branco
...
Dear Rahul
Interesting your question
Thanks for sharing

Is it the customer?
Is the sponsor?Or is it another stakeholder?
It is some other stakeholder. For me, it is easy to manage/handle people who change requirements in the following order 1) customers 2) Project Sponsor 3) Stakeholder (An influential person).
...
1 reply by Luis Branco
Feb 14, 2020 12:09 PM
Luis Branco
...
Dear Rahul
Thank you for your clarification

How do you treat other stakeholders? How do you position them in the "Power x Influence" or "Influence x Impact" matrix? What is the most appropriate strategy as a result of the result of that analysis?
Frequent requirement changes signify either a gap in the prioritization process as part of the regular project/program management cadence with the stakeholders or it could also be the result of gap during the scoping phase of the project as the value realization factor of the project was not properly validated for buy-in from all the stakeholders.
If the above factors are not true with respect to your project, then use a quantifiable parameter to evaluate the request based on the following parameters:
- Operational Mandate
- Grow Financial Future
- Customer Experience
- Business Risk Mitigation
- Team Member Experience/Efficiency
You can score them based on your organizational defined standards, there will be an initial overhead to do the exercise couple of times with the stakeholder, but once the stakeholder understands the relative importance you will receive the buy-in from the person. It also depends on how your stakeholders are structured from business unit standpoint.
Finally, try to keep it simple to only discuss in terms of value and impact instead of challenging the stakeholder or being defensive about technical change effort.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Feb 05, 2020 1:19 AM
Replying to Rahul Patekar
...
It is some other stakeholder. For me, it is easy to manage/handle people who change requirements in the following order 1) customers 2) Project Sponsor 3) Stakeholder (An influential person).
Dear Rahul
Thank you for your clarification

How do you treat other stakeholders? How do you position them in the "Power x Influence" or "Influence x Impact" matrix? What is the most appropriate strategy as a result of the result of that analysis?
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
We need to think of change as opportunities. Is it difficult to handle? Yes. We have tools, techniques, and processes to help us make the most of difficult situations.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"One never needs their humor as much as when they argue with a fool."

- Chinese Proverb

ADVERTISEMENT

Sponsors