PMP · Question #1337
A project manager is working on a large project in another country and realizes that only a few people from the project team are working on all of the releases. What should the project manager do to p
The correct answer is C. Review user roles and update the team charter.. To address the issue of only a few team members handling all releases, the project manager should review and update the team charter to clarify roles and responsibilities.
Question
Options
- ASpeak to the customer and add the issue to the issue log.
- BDocument the risk register in the project charter.
- CReview user roles and update the team charter.
- DInvolve the product owner to rewrite the user stories.
How the community answered
(33 responses)- A9% (3)
- B3% (1)
- C82% (27)
- D6% (2)
Why each option
To address the issue of only a few team members handling all releases, the project manager should review and update the team charter to clarify roles and responsibilities.
Speaking to the customer and adding the issue to the issue log does not address the internal team resource allocation and role definition problem.
Documenting the risk register in the project charter is incorrect; the risk register is a separate, dynamic document, and this issue pertains to team structure and roles, not just a high-level project risk.
When only a few team members are consistently working on all releases, it indicates potential bottlenecks, lack of cross-training, or unclear role definitions. Reviewing user roles and updating the team charter allows the project manager to formalize responsibilities, ensure equitable workload distribution, and plan for skill development or resource allocation to prevent over-reliance on a limited few.
Involving the product owner to rewrite user stories pertains to product functionality and requirements, not the distribution of work or roles within the project team.
Concept tested: Team resource management and role definition
Source: https://learn.microsoft.com/en-us/project-management/project-team-roles-responsibilities
Topics
Community Discussion
9
Bao N.May 8, 2026C is correct. Reviewing user roles and updating the team charter directly addresses the resource allocation imbalance, and the team charter is where you establish ground rules for how work gets distributed across the team.
Yusuf A.Apr 6, 2026C is right, my senior said team charter handles role gaps. How detailed should that doc be?
Dervla O.Apr 8, 2026Agree on C for the exam but the team charter is a living doc, not a one-and-done writeup, so keep it detailed enough to clarify decision rights and ownership but light enough that the team actually revisits it when roles shift.
Dervla O.Apr 12, 2026C is correct here. The team charter is where you address team ground rules and resource allocation, and reviewing user roles gets at the root cause of why work keeps funneling to the same few people.
Prof. SaraApr 13, 2026Agreed on C, and since the team charter maps to PMP Domain 2 (Team Performance), remember the mnemonic CGRE for Charter contents: Communications plan, Ground rules, Resource assignments, and Expectations, so reviewing user roles fits cleanly under the R.
Prof. SaraMay 12, 2026Confirmed C on exam last week, saw this almost verbatim. The few people doing all the releases points to a team structure and role problem, so reviewing user roles and updating the team charter is your move, not escalating to the customer or product owner.
Dervla O.May 12, 2026Agreed on C, but read the stem carefully for any mention of approval authority, because if the few people doing releases are also the bottleneck for sign-off, the role review and charter update might need to happen before you touch the release process itself.
Orla P.Apr 24, 2026Confirmed C on exam last week. A is the trap because logging the issue with the customer sounds proactive, but the team charter is where you establish ground rules around workload distribution and role expectations.
Prof. SaraApr 25, 2026Good catch on C for Domain 3, and remember the mnemonic CHARter covers Communication, Help, Accountability, and Role expectations, which is exactly why A fails the smell test since escalating to the customer skips the team-level resolution step the blueprint assumes you try first.