3.2 The Project Manager and Project Team

3.2 The Project Manager and Project Team

Quick Answer: The Project Manager is appointed to manage the project on a day-to-day basis, responsible for planning, delegating, monitoring, controlling, and delivering outputs within agreed tolerances (time, cost, quality, scope). While the Sponsor owns the business case, the Project Manager leads the project team—a temporary, cross-functional group of specialists who execute assigned work packages. In matrix organizations, project managers must balance authority with functional line managers who control resource allocation and career appraisals.

---

The Project Manager: Role and Core Responsibilities

The Project Manager (PM) is the individual formally authorized by the Project Sponsor to run the project on a day-to-day basis. The PM's primary mandate is to take the project requirements defined in the business case and project brief, translate them into a comprehensive Project Management Plan (PMP), and direct project execution to deliver the agreed outputs.

+-------------------------------------------------------------------------+
|                        PROJECT MANAGER MANDATE                          |
|                                                                         |
|   +-------------------+    +--------------------+    +--------------+   |
|   |     PLANNING      |    |     DELEGATING     |    |  MONITORING  |   |
|   | - WBS, Schedule   |    | - Work Packages    |    | - EVM, KPIs  |   |
|   | - Budget Baseline |    | - Team Direction   |    | - Milestones |   |
|   +-------------------+    +--------------------+    +--------------+   |
|             |                        |                      |           |
|             +------------------------+----------------------+           |
|                                      v                                  |
|                        +---------------------------+                    |
|                        |        CONTROLLING        |                    |
|                        | - Tolerance Management    |                    |
|                        | - Risk/Issue Escalation   |                    |
|                        | - Change Control          |                    |
|                        +---------------------------+                    |
+-------------------------------------------------------------------------+

The Core Functions of the Project Manager

1. Planning and Baseline Formulation: Developing the integrated Project Management Plan (PMP), including defining scope via Product Breakdown Structures (PBS) and Work Breakdown Structures (WBS), establishing scheduling networks, creating cost baselines, and authoring risk, quality, and communication plans.

2. Delegating and Work Package Definition: Packaging discrete technical assignments into formal Work Packages. Each work package specifies deliverables, quality criteria, budget constraints, delivery milestones, and reporting interfaces.

3. Monitoring and Tracking Progress: Continuously comparing actual performance against planned baselines using metrics such as Earned Value Management (EVM), milestone tracking, and quality audit logs. The PM ensures early detection of variances.

4. Controlling and Tolerance Management: Implementing corrective or preventive actions when minor deviations occur. The PM exercises autonomous control as long as the forecast completion remains within the delegated tolerances established by the Sponsor.

5. Risk and Issue Management: Maintaining the project risk register, facilitating risk identification workshops, assigning risk owners, designing mitigation responses, and resolving day-to-day operational issues.

6. Stakeholder Engagement and Communication: Serving as the primary communication hub for the project, delivering timely progress reports to the Sponsor and Governance Board while managing the expectations of external stakeholders, regulatory bodies, and suppliers.

7. Project Closure and Lessons Learned: Leading the formal handover of completed outputs to operational users, conducting post-project reviews, documenting lessons learned, and releasing project resources.

---

The Relationship Between Sponsor and Project Manager

The working relationship between the Project Sponsor and the Project Manager is the single most critical interpersonal dynamic in the project organization. While often described as a partnership, their roles are fundamentally complementary rather than identical:

• The Sponsor represents the business: Focused on outcomes, commercial return, strategic alignment, and benefits realization.
• The Project Manager represents the delivery mechanism: Focused on outputs, work execution, schedule milestones, cost control, and technical quality.

+-----------------------+                         +-----------------------+
|    PROJECT SPONSOR    |                         |    PROJECT MANAGER    |
+-----------------------+                         +-----------------------+
| Strategic Perspective |                         | Tactical Delivery     |
| Business Case Owner   | <---------------------> | PMP Delivery Lead     |
| Sets Tolerances       |  Trust, Transparency,   | Manages in Tolerances |
| Handles Escalations   |  Early Warning Reports  | Escalates Exceptions  |
+-----------------------+                         +-----------------------+

Pillars of an Effective Sponsor-PM Partnership

• No Surprises (Transparency): The Project Manager must provide honest, unvarnished visibility into project progress. Attempting to conceal emerging schedule delays or cost overruns damages trust and prevents timely governance intervention.
• Clear Escalation Protocols: When a variance breaches agreed tolerances, the PM does not attempt to unilaterally re-baseline the project. Instead, the PM submits an Exception Report detailing the root cause, business impact, and evaluated recovery options.
• Executive Mentorship and Protection: The Sponsor acts as an executive mentor to the PM, protecting the project team from external corporate politics and securing necessary interdepartmental support.

---

Project Team Members and Work Package Managers

A Project Team is a temporary social and operational unit assembled to execute the tasks outlined in the Project Management Plan. Project teams are inherently cross-functional, bringing together specialists from disparate disciplines who may have never worked together previously.

Roles Within the Project Team

• Specialist Team Members: Technical experts (e.g., software engineers, civil structural designers, business analysts, safety inspectors, procurement buyers) responsible for executing specific operational activities according to defined quality specifications.
• Team Leaders / Work Package Managers: On mid-sized and large projects, the Project Manager cannot directly supervise every individual specialist. The PM delegates discrete segments of work to Work Package Managers or Team Leaders. A Work Package Manager acts as a local coordinator, directing specialist team members, monitoring daily progress, verifying quality, and providing regular status updates to the PM.

Responsibilities of Project Team Members

1. Technical Delivery: Executing assigned tasks in accordance with engineering drawings, technical standards, and quality specifications.
2. Time and Effort Tracking: Accurately reporting hours worked and costs incurred against assigned work packages to maintain reliable project accounting.
3. Proactive Risk and Issue Reporting: Immediately notifying the Work Package Manager or Project Manager when technical impediments, defects, or emerging risks arise.
4. Adherence to Processes: Following project-wide configuration management, change control, and documentation protocols.

---

Organizational Structures and Matrix Management

Project managers and teams do not operate in a vacuum; their level of formal authority and access to resources are heavily dictated by the parent enterprise's organizational structure.

                      ORGANIZATIONAL CONTINUUM

  Functional               Matrix Structure              Projectized
  Structure       Weak        Balanced        Strong      Structure
<-------------+-----------+--------------+-----------+------------->
  PM Authority: None      Low           Medium       High       Total
  Line Authority: Total   High          Medium       Low        None

1. Functional Organization

In a traditional functional structure, the organization is divided into permanent departmental silos (e.g., Marketing, Engineering, Finance, Human Resources), each headed by a functional line manager.

• PM Authority: Very low or non-existent; the PM often acts merely as a project coordinator or expediter without budgetary control.
• Resource Access: Team members report solely to their functional line managers; project work is viewed as secondary to ongoing operational duties.
• Challenges: Severe communication barriers between functional silos; slow decision-making; lack of project focus.

2. Projectized (Project-Oriented) Organization

At the opposite end of the spectrum, the enterprise organizes its core operations around projects. Most of the organization's resources are involved directly in project delivery.

• PM Authority: High to complete; the Project Manager has full authority over the team, controls the project budget, and makes direct staffing decisions.
• Resource Access: Team members are dedicated full-time to the project and report directly to the PM for the duration of the lifecycle.
• Challenges: Duplication of facilities and specialist personnel across multiple projects; lack of a permanent functional "home" for team members once the project disbands ("projectitis").

3. Matrix Organization

The matrix organization represents a hybrid approach that attempts to blend the technical expertise of functional departments with the delivery focus of projectized structures. In a matrix structure, team members report to two managers simultaneously: their permanent functional line manager and a temporary project manager.

• Weak Matrix: The functional line managers maintain primary authority over budgets and resource allocation. The Project Manager acts as an expediter or staff assistant, coordinating meetings and tracking deadlines without formal authority.
• Balanced Matrix: Authority is shared equally. The Project Manager defines what needs to be done and when it must be completed (project schedule and deliverables), while the functional manager decides who will perform the work and how the technical work should be executed (standards and staffing).
• Strong Matrix: Project managers operate from a centralized PM department and possess primary authority over project budgets and task assignments. Functional managers act as resource suppliers who provide specialist staff and maintain technical excellence.

Managing Matrix Challenges

Matrix management introduces inherent organizational friction:

• Dual Reporting Tension: Team members face conflicting demands from their project manager (demanding urgent milestone delivery) and their line manager (demanding routine operational support).
• Resource Competition: Multiple project managers frequently compete for the same scarce, high-performing technical specialists.
• Appraisal Ambiguity: Functional managers often conduct annual performance appraisals, leading team members to prioritize line duties over project tasks unless the PM contributes directly to performance feedback.

To succeed in a matrix environment, the Project Manager must rely heavily on soft skills, including negotiation, conflict resolution, active listening, and relationship building, rather than relying solely on formal command-and-control authority.

---

Comparison of Core Project Roles