What are the most effective techniques for managing difficult stakeholders during requirements gathering?

All answers to this question.

To handle conflicting priorities, I recommend using a weighted prioritization matrix like MoSCoW or a Kano Model analysis. Invite both stakeholders to a workshop where you clearly define the project objectives and constraints. By facilitating a data-driven discussion on the value versus complexity of each requirement, you shift the focus from personal opinions to business value. It’s also helpful to conduct individual interviews beforehand to understand their underlying concerns. Documenting everything in a Stakeholder Engagement Plan ensures transparency and accountability throughout the project lifecycle.

   Answered 2024-03-16 by Susan Miller

That workshop approach is solid, but how do you handle a stakeholder who is technically superior but refuses to provide clear functional requirements? Are you using specific elicitation techniques like prototyping or shadowing to bridge that gap when the verbal communication starts to break down?

   Answered 2024-03-18 by Thomas Harris

• Thomas, in those cases, I rely heavily on "Context Diagrams" and "Process Mapping." Showing them a visual representation of the current state often triggers them to point out what is missing or incorrect. It acts as a catalyst for technical stakeholders to provide the specific details we need for the functional design documents.

     Commented 2024-03-20 by Karen White

I find that the RACI matrix is a lifesaver here. Clearly defining who is Accountable versus just Consulted prevents too many "cooks in the kitchen" from derailing the requirements.

   Answered 2024-03-22 by Mark Davis

• I agree with Mark. Implementing a RACI matrix early in our last Agile sprint saved us from three weeks of circular arguments between the product owner and the lead architect.

     Commented 2024-03-24 by Susan Miller