People — Leading Projects →easyMultiple ChoiceObjective-mapped

PMP People — Leading Projects Practice Question

Your team is about to start a new project. To ensure a common understanding of rules and expectations, you want to create a team charter. When should this be developed?

⚠ Common exam trap

Test-takers frequently confuse the team charter with the project charter, leading candidates to think it is created by the project manager alone (Option D) or at the start of planning, rather than collaboratively during the kick-off meeting.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

During the project kick-off meeting with the entire team

The team charter is developed during the project kick-off meeting with the entire team to establish shared expectations, ground rules, and operating norms from the outset. This collaborative creation ensures buy-in and alignment before work begins, reducing ambiguity and preventing conflicts later. The PMBOK Guide emphasizes that the team charter is a product of the team, not the project manager alone, and is created during the 'Develop Team' process within the People domain.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
During the project kick-off meeting with the entire team
Why this is correct
The project kick-off meeting is the optimal time to collaboratively develop the team charter with the entire project team. This early engagement ensures that all team members contribute to establishing shared values, communication protocols, decision-making processes, and conflict resolution guidelines before project work fully commences. By defining these working agreements proactively, the team sets a strong foundation for effective collaboration and mutual accountability, preventing many common interpersonal issues.
✗
At the end of the project for lessons learned
Why it's wrong here
Developing the team charter at the end of the project for lessons learned is fundamentally misaligned with its purpose. The team charter is a proactive planning and guidance tool designed to establish operational norms and expectations from the outset, not a retrospective artifact. Its value lies in preventing misunderstandings and conflicts throughout the project lifecycle, rather than merely documenting past behaviors or issues after they have occurred.
✗
After the first conflict arises to guide resolution
Why it's wrong here
Waiting until the first conflict arises to create a team charter is a reactive approach that undermines its primary benefit. The team charter's purpose is to proactively establish clear guidelines and a framework for how the team will address disagreements and resolve issues, ideally preventing conflicts from escalating. Implementing it only after a problem emerges means the team lacks pre-agreed mechanisms, potentially prolonging the conflict and damaging team cohesion.
✗
Developed solely by the project manager and then shared with the team
Why it's wrong here
Developing the team charter solely by the project manager and then sharing it with the team diminishes its effectiveness and the team's buy-in. A team charter gains its authority and adherence from the collective ownership and agreement of all team members. Without active participation in its creation, the team may perceive it as a set of imposed rules rather than shared commitments, leading to reduced accountability and less effective guidance for team behavior.

Go deeper

PMP People — Leading Projects Practice Question

Why each option matters

Option-by-option breakdown

Related to this question