One of the PMI-ACP domains is 'Stakeholder Engagement'. I often face issues with stakeholders who want detailed Gantt charts and fixed deadlines. What are the best Agile techniques to manage their expectations without reverting to Waterfall practices, especially for the exam scenarios?
3 answers
The key is "Transparency." Instead of Gantt charts, show them the "Product Roadmap" and "Burn-up Charts." Invite them to the Sprint Reviews so they can see the working software—this usually builds more trust than any document ever could. For the exam, focus on "Active Listening" and "Collaborative Games" to align their vision. If they demand a fixed deadline, explain the "Agile Triangle" (where Scope is variable, but Time and Cost are fixed). By showing them they have control over the priority of features, you give them a sense of security without promising a fixed-scope release.
Susan, what if the stakeholder is too busy to attend Sprint Reviews? How do we maintain engagement and "Value-Driven" feedback in that situation?
Education is the best tool. If they understand "Why" we are being Agile, they are much less likely to fight the "How."
True, Kimberly. I always start my Agile projects with a "Risk Workshop" for stakeholders to show them how Agile actually lowers their business risk.
David, that is a classic PMI-ACP scenario. The answer is often "Personas" and "Wireframes." If they can't be there, you must use tools that represent their needs accurately. However, the best answer is usually to educate the stakeholder on the importance of their involvement. Agile is a partnership. You might suggest a shorter, recorded demo or a "Product Wall" where they can see progress asynchronously. The goal is to keep the feedback loop as short as possible, even if it’s not a face-to-face meeting every two weeks.