PMP · Question #1376
The stakeholders in an agile project are upset because some of the final products do not meet their expectations. When the project manager asks the team about the stakeholders' expectations, the team
The correct answer is C. Teach the team how to use the user persona technique.. To bridge the gap between team understanding and stakeholder expectations in an agile project, the project manager should teach the team techniques like user personas to better empathize with and capture user needs.
Question
Options
- AMotivate the team to create and use an agile project charter.
- BEncourage the team to use an information radiator to analyze expectations.
- CTeach the team how to use the user persona technique.
- DRemind the team that face-to-face communication is the best method.
How the community answered
(39 responses)- A5% (2)
- B15% (6)
- C72% (28)
- D8% (3)
Why each option
To bridge the gap between team understanding and stakeholder expectations in an agile project, the project manager should teach the team techniques like user personas to better empathize with and capture user needs.
An agile project charter defines high-level vision and scope, but it doesn't provide the detailed understanding of specific user expectations needed to build products that specifically meet those expectations.
An information radiator is a visual display for sharing project progress and information, not a tool designed for analyzing, capturing, or deeply understanding detailed stakeholder or user expectations.
User personas help the team develop a deeper, empathetic understanding of target users' needs, goals, and pain points, translating abstract project objectives into concrete, user-centric features that directly address stakeholder expectations.
While face-to-face communication is valuable, it is a communication method, not a specific technique for analyzing and documenting nuanced stakeholder expectations in a structured way that the team can internalize and build upon.
Concept tested: Capturing user/stakeholder requirements in agile
Source: https://learn.microsoft.com/en-us/azure/devops/boards/get-started/writing-good-user-stories?view=azure-devops
Topics
Community Discussion
3
Mateus R.Jan 27, 2026C is correct. Think of a builder framing a house with only a vague goal of "shelter" but never asking who is moving in; you get rooms that do not fit the family's life. The user persona technique is how we sketch out those specific occupants so the team builds features that actually match stakeholder expectations instead of just the high-level project objective. A charter or an information radiator will not fix the core problem if the team never truly understood the end user in the first place.
Carlos M.Jan 29, 2026C is the answer. User personas force the team to think beyond the high-level objective and actually understand who the stakeholders are and what they need. That gap between knowing the project goal and knowing stakeholder expectations is exactly what personas fix. I had this one on my exam last month and almost talked myself into A because charter sounded authoritative, but the question is about understanding expectations not governance. Personas are the tool that bridges that disconnect.
Yuki V.Feb 5, 2026Confirmed C on my exam last month. The team confusing the high-level objective with actual stakeholder needs is the giveaway here, and user personas force you to think about who the end user really is and what they actually expect from the product.