The project team and leadership basics

Projects are delivered by people, and a third of the 2026 PMP exam sits in the People domain. This lesson introduces the people side of project management at a foundations level: the roles found on predictive and adaptive projects, how responsibilities are clarified, how teams develop over time, the basics of motivation and conflict, and the realities of distributed teams. PMP-120 (leadership and teams) and PMP-121 (stakeholders, conflict and communication) develop each of these topics in depth, so treat this lesson as the map before the territory.

Roles on a project

Role names vary by organization and approach, but certain responsibilities appear on almost every project. A person may hold more than one role, and on small projects one person may hold several.

In Scrum, a widely used adaptive framework, there is no project manager role; the product owner, the Scrum Master and the developers share accountability. In practice, many organizations using Scrum still have project managers coordinating across teams, managing budgets and handling governance. Exam scenarios may place you in either situation, so read carefully: if you are described as a servant leader on an agile team, choose answers that enable the team to self-organize rather than assigning tasks yourself.

Clarifying responsibilities

Unclear responsibilities cause duplicated work, gaps and conflict. A responsibility assignment matrix (RAM) links work to people. The most common form is the RACI chart: Responsible (does the work), Accountable (owns the outcome and approves it; only one person per activity), Consulted (gives input before) and Informed (kept updated after).

How teams develop

Teams do not perform at their best from day one. The Tuckman ladder, widely cited in PMI material, describes five stages: forming (people meet and learn about the project; polite and uncertain), storming (differences emerge and conflict appears), norming (the team agrees ways of working and builds trust), performing (the team works effectively and solves problems together) and adjourning (the team completes its work and disbands). Teams can move back a stage, for example when new members join or the work changes significantly.

Project managers can help teams through these stages: in forming, by clarifying purpose, roles and norms; in storming, by addressing conflict openly and fairly; in norming, by reinforcing agreements, for example in a team charter; in performing, by stepping back and removing obstacles; and in adjourning, by recognizing contributions and capturing lessons. Co-location, team-building activities, recognition and training all support development.

Motivation in brief

Several classic theories appear in PMI-related study material. Maslow's hierarchy suggests people are motivated by needs from physiological and safety needs up to belonging, esteem and self-actualization. Herzberg distinguishes hygiene factors, such as pay and working conditions, which cause dissatisfaction if missing, from motivators, such as achievement, recognition and the work itself, which create satisfaction. McGregor's Theory X assumes people need close control, while Theory Y assumes people are self-motivated given the right conditions. Daniel Pink's more recent work emphasizes autonomy, mastery and purpose. Modern project guidance, especially for knowledge work, leans toward Theory Y, intrinsic motivators and Pink's three elements.

For the exam, the practical lesson is that recognition, meaningful work, growth opportunities and autonomy usually motivate more effectively than pressure or monetary bonuses alone, and that a project manager should understand what motivates each team member rather than assuming one approach suits all.

Conflict basics

Conflict is inevitable on projects and is not always harmful; disagreement about ideas can improve decisions. Common sources include schedules, priorities, resources, technical opinions, administrative procedures, cost and personalities. PMI describes five general approaches to conflict, drawn from the Thomas-Kilmann model.

Distributed and virtual teams

Many teams work across locations and time zones. Distributed teams give access to wider talent and can reduce costs, but they face challenges: less informal communication, time-zone gaps, cultural differences, technology dependence and difficulty building trust. Good practices include clear communication norms, overlapping core hours, shared digital workspaces, video for important conversations, periodic in-person meetings when possible, and extra attention to inclusion so that remote members are not overlooked.

Canadian teams often span six time zones, from Newfoundland to British Columbia, and may need to work in both official languages, especially on federal projects or in Quebec. Provincial employment standards set rules on hours of work and overtime that affect flexible scheduling.

Emotional intelligence and team leadership

Emotional intelligence (EI) is the ability to recognize and manage your own emotions and to recognize and influence the emotions of others. Common models describe four parts: self-awareness, self-management, social awareness and relationship management. Project managers with high EI tend to handle conflict better, build trust faster and adapt their style to the situation. Situational leadership models make a related point: the best leadership style depends on the team members' competence and commitment, moving from directing new or inexperienced people toward delegating to experienced, motivated ones. PMP-120 explores these models in depth.

Building a team charter

A team charter, sometimes called working agreements, records how the team will work together. It typically covers team values, communication guidelines (which channels for what, expected response times), decision-making criteria and process, conflict resolution process, meeting guidelines and, for adaptive teams, the definition of done. The team writes it together, which builds ownership, and revisits it when problems arise or membership changes. A project manager facilitates the conversation rather than writing the charter alone.

Recognition and rewards

Recognition is one of the cheapest and most effective motivators. It works best when it is timely, specific and fair, and when it recognizes behaviours the team values, such as helping others or raising a risk early, not just individual heroics. Reward systems that pit team members against each other can damage collaboration. In adaptive teams, celebrating team achievements at reviews and retrospectives reinforces shared ownership. Cultural differences matter: some people appreciate public praise, others prefer private acknowledgement, so a project manager should learn what each person values.

Finally, remember that people are not resources in the same sense as equipment. They have careers, families, cultures and ambitions. Projects that treat team members as interchangeable units tend to lose good people. Projects that invest in their growth, through stretch assignments, mentoring and training, often find that capability and commitment rise together. This is the practical meaning of the empowered culture principle.

PMP-120 returns to all of these topics, from leadership styles and team development to coaching, mentoring and emotional intelligence, with more scenarios and practice.

In summary, the people side of project management is not a soft extra layered on top of the real work. Clear roles, healthy team development, fair handling of conflict and genuine motivation are what allow plans to be carried out. Many projects with sound schedules fail because these foundations were neglected, while teams with strong relationships often recover from technical setbacks that would sink others. This is why the exam gives the People domain a full third of its weight.