SkarpChapter 11 of 21
Predictive Team and Resource Management in Functional and Matrix Environments
In many CAPM scenarios, you don’t control who works for you—learn how to negotiate for people, resolve conflicts, and keep the team performing within real‑world organizational constraints.
Organizational Structures and Your Resource Power
Why Structure Matters
Your power to choose and direct team members depends on the organizational structure. For CAPM, you must link functional, matrix, and projectized structures to how you plan, request, and manage resources.
Functional Organizations
In functional structures, staff are grouped by specialty and controlled by functional managers. Project managers have low authority and must request people, often getting part-time help.
Matrix Organizations
In matrix structures, staff report to both functional and project managers. Authority is shared. You constantly negotiate for people and time while using tools to coordinate across projects.
Projectized Organizations
In projectized structures, most people work in projects. Project managers have high authority over team, budget, and schedule, but still must plan capacity and keep teams stable and motivated.
Exam Signal
If a scenario shows you borrowing people or negotiating with department heads, you are likely in a functional or matrix environment. Expect questions on negotiation and resource planning.
Planning Resources in Predictive Projects
From Scope to Resources
Resource planning starts with the WBS and its work packages. For each work package, you identify needed skills, non-human resources, and effort so you can plan schedule and cost.
Key Artifacts
You must recognize: Resource breakdown structure (RBS), resource calendars, and resource histograms. They show what types of resources you need and when they are available or overloaded.
Detecting Over-Allocation
By mapping work to time, you can see when the same role or person is booked for more work than they can handle in a period. This is a red flag for schedule and quality risk.
Link to Schedule
Resource availability affects activity durations and start dates. Fewer people or part-time availability usually means longer tasks and a different critical path.
Link to Cost
Each resource unit has a cost. When you multiply usage by rates, you get activity costs and, summed across the project, your cost baseline. Exam items often test this linkage.
Resource Optimization: Leveling vs Smoothing
Why Optimize Resources?
When you load resources onto your schedule, some roles become overbooked. Resource optimization techniques help you fix this without breaking the project.
Resource Leveling
Resource leveling delays or splits activities to remove over-allocation, even if the project end date moves. It can change the critical path and usually lengthens the schedule.
Resource Smoothing
Resource smoothing evens out resource usage but keeps the project finish date unchanged. It only shifts activities within their available float, so the end date is preserved.
Exam Clues
If the finish date must stay fixed, think smoothing. If the schedule can change to fix over-allocation, think leveling. Both are applied after building the initial schedule.
Mental Picture
Picture weekly bars of work. Leveling can push some bars into new weeks, extending the timeline. Smoothing rearranges bars within the existing time frame to reduce peaks.
Example: Resource Conflicts in a Matrix Environment
Scenario Setup
You manage Project A in a balanced matrix. You need 3 full-time developers for 6 weeks, but the Development Manager offers only 2 developers at 50% each. You face a resource shortfall.
Quantify the Gap
Planned: 3 full-time developers for 6 weeks = 18 developer-weeks. Offered: 2 developers at 50% for 6 weeks = 6 developer-weeks. You are short by 12 developer-weeks.
Option 1: Extend Schedule
Use resource leveling: accept the limited capacity and extend the duration until total developer-weeks match the effort. This protects quality but delays go-live.
Option 2 and 3
Option 2: Ask for more or higher-allocation resources, possibly at higher cost. Option 3: Reduce or phase scope so less effort is needed before go-live.
Matrix Negotiation
In a matrix, you negotiate with functional managers, present business priority, and offer flexible solutions. Exam items test your ability to choose such a collaborative response.
Team Charters in Predictive Projects
What is a Team Charter?
A team charter is an agreement on how the team will work together. It sets norms for behavior, decisions, meetings, and conflict resolution, especially useful in predictive projects.
Purpose
The charter aligns people on values, clarifies who decides what, and defines how meetings and communication will run. It reduces misunderstandings before they become conflicts.
Typical Content
It usually covers team values, roles, decision rules, meeting guidelines, and step-by-step conflict resolution approaches. It complements, not replaces, other project documents.
Conflict Resolution Flow
Common flow: try to resolve directly between individuals, then involve the project manager, then escalate to functional managers or sponsor if needed, using interest-based problem solving.
Exam Signal
If you see recurring conflicts, unclear authority, or messy meetings early in the project, the best next step is often to create or refine the team charter, not jump straight to punishment.
Managing Part-Time Team Members and Availability
Part-Time Reality
In functional and matrix structures, many team members are part-time on your project. They juggle operations or other projects, causing availability and focus challenges.
Key Challenges
Expect unreliable availability, context switching, and conflicting priorities between functional and project managers. These can slow schedules and hurt quality.
Tools to Manage Availability
Use resource calendars, clear roles (RACI, team charter), timeboxed work blocks, and regular coordination with functional managers to protect project time.
When Availability Changes
If someone becomes unavailable, update the schedule, check the critical path, reassign work if possible, and negotiate with managers. Use change control if baselines are impacted.
Exam Expectation
You should recognize part-time constraints and respond with planning, negotiation, and formal control processes, not by pretending resources are full-time.
Developing the Team: Mentoring, Training, and Feedback
Why Develop the Team?
Even in predictive projects, you must grow team skills and performance. In functional and matrix structures, you influence mentoring, training, and feedback, even if HR reports elsewhere.
Mentoring
Mentoring pairs senior and junior staff to build skills and reduce risk. On projects, this can be technical or about stakeholder communication, improving both capacity and resilience.
Training
Plan technical, process, and soft skills training. Identify gaps early and include training time and cost in your schedule and cost baseline so it is realistic and funded.
Performance Feedback
Give specific, timely, balanced feedback. Share observations with functional managers and adjust assignments based on performance instead of immediately replacing people.
Exam Perspective
If a scenario shows skill gaps or repeated mistakes, look for answers involving coaching, mentoring, or training before jumping to punishment or removal.
Linking Resource Plans to Schedule and Cost Baselines
Resources Drive Duration
Activity duration depends on effort, number of resources, and their availability. Less availability makes tasks longer, changing the network diagram and float.
Resources Drive Cost
Each resource has a rate. Multiply usage by rate to get activity costs. Summed across all activities, this becomes your cost baseline.
Three-Way Trade-Off
Adding resources can shorten time but increase cost. Reducing resources saves cost but lengthens time. Changing scope alters both effort and value.
Baselines and Change
After schedule and cost baselines are approved, resource changes that affect them must go through integrated change control, with impact analysis and formal approval.
Exam Behavior
If a resource change impacts the committed finish date or budget, the correct move is to submit a change request rather than quietly editing the plan.
Thought Exercise: Negotiating in a Functional Organization
Scenario Overview
You need a senior designer full-time for 4 weeks in a functional organization, but the Creative Manager offers only a junior at 50% or a delay before a senior is free.
Key Questions
Ask yourself: What data do you need? How do options affect schedule and cost baselines? How will you clarify roles and expectations once a designer is assigned?
Next Formal Step
If neither option meets a hard launch date, what formal step must you take? Think in terms of integrated change control and stakeholder escalation, not informal shortcuts.
Exam Mindset
Use this to practice analyzing constraints, trade-offs, and the most professional next action consistent with project management processes.
Quiz 1: Structures, Resources, and Optimization
Check your understanding of organizational structures and resource optimization.
You are managing a predictive project in a balanced matrix organization. A key engineer is assigned at 25% availability instead of the 100% you planned, causing over-allocation and pushing some work past the planned finish date. Management insists that the project finish date must remain unchanged. What is the BEST technique to apply first?
- Use resource leveling to delay activities until the engineer is no longer over-allocated, even if the project end date moves.
- Apply resource smoothing by adjusting non-critical activities within their float so the engineer’s workload is balanced without changing the finish date.
- Immediately escalate to the sponsor and demand a different engineer with 100% availability.
- Remove scope from the project until the engineer’s workload fits the original schedule, without going through change control.
Show Answer
Answer: B) Apply resource smoothing by adjusting non-critical activities within their float so the engineer’s workload is balanced without changing the finish date.
Because management insists the project finish date must remain unchanged, the appropriate technique is **resource smoothing**, which adjusts activities within their available float to reduce over-allocation while preserving the end date. Resource leveling (A) allows the end date to move, which violates the constraint. Demanding a new engineer (C) may be necessary later, but the question asks for the BEST technique to apply first. Removing scope without change control (D) ignores formal processes and baselines.
Quiz 2: Team Charter and Conflict Resolution
Test your understanding of team charters and conflict handling.
In a predictive project within a weak matrix organization, team members frequently argue over who has authority to approve design changes, and status meetings often run long without clear decisions. The project is in early planning. What should the project manager do NEXT?
- Escalate immediately to the sponsor and request that all decisions be made only by the sponsor.
- Develop or refine the team charter to clarify decision-making rules, meeting guidelines, and escalation paths.
- Replace the team members who argue the most with new staff from other departments.
- Skip further planning and move to execution so that roles become clearer through experience.
Show Answer
Answer: B) Develop or refine the team charter to clarify decision-making rules, meeting guidelines, and escalation paths.
The described problems (unclear decision authority, ineffective meetings) are classic signals that a **team charter** is missing or weak. Early in the project, the best next step is to develop or refine the team charter to define decision rules, meeting guidelines, and conflict resolution approaches. Escalating all decisions to the sponsor (A) is inefficient. Replacing team members (C) is premature. Skipping planning (D) will likely worsen the confusion.
Flashcards: Key Terms and Concepts
Flip through these cards to reinforce core ideas from this module.
- Functional organization
- An organizational structure where work is grouped by specialty (e.g., IT, HR) and functional managers control staff and budgets. Project managers have low authority and must request resources.
- Matrix organization (weak, balanced, strong)
- A structure where staff report to both functional and project managers. Weak matrix is closer to functional (functional manager dominant), strong matrix is closer to projectized (project manager stronger), balanced matrix shares authority more equally.
- Projectized organization
- An organizational structure where most people work in projects and report to project managers, who have high authority over resources, schedule, and budget.
- Resource breakdown structure (RBS)
- A hierarchical list of resources by category or type (such as role, department, internal/external) used to organize and plan resource needs.
- Resource calendar
- A calendar that shows the working days, shifts, and planned unavailability (vacations, maintenance, training) for specific resources such as people or equipment.
- Resource histogram
- A bar chart that shows the quantity of a resource (e.g., number of developers) needed over time, useful for spotting peaks and over-allocation.
- Resource leveling
- A resource optimization technique that resolves over-allocation by adjusting activity start and finish dates, often changing the project end date and possibly the critical path.
- Resource smoothing
- A resource optimization technique that adjusts activities within their float to reduce resource peaks while preserving the project end date and critical path.
- Team charter
- A document that describes how the team will work together, including team values, roles, decision-making rules, meeting guidelines, and conflict resolution approaches.
- Part-time team member management
- The practice of using resource calendars, clear roles, coordination with functional managers, and formal change control to manage people who split their time between the project and other work.
- Linking resources to baselines
- The process of converting resource usage into activity durations (schedule baseline) and costs (cost baseline), and using integrated change control when resource changes impact these baselines.
Key Terms
- team charter
- A document that describes how the team will work together, including team values, roles, decision-making rules, meeting guidelines, and conflict resolution approaches.
- resource calendar
- A calendar that shows the working days, shifts, and planned unavailability for specific resources such as people or equipment.
- resource leveling
- A resource optimization technique that resolves over-allocation by adjusting activity start and finish dates, often changing the project end date and possibly the critical path.
- resource histogram
- A bar chart that shows the quantity of a resource needed over time, useful for spotting peaks and over-allocation.
- resource smoothing
- A resource optimization technique that adjusts activities within their float to reduce resource peaks while preserving the project end date and critical path.
- matrix organization
- An organizational structure where staff report to both functional and project managers, with varying degrees of shared authority (weak, balanced, strong).
- part-time team member
- A person who works on the project for only a portion of their time while also supporting operations or other projects.
- functional organization
- An organizational structure where work is grouped by specialty and functional managers control staff and budgets. Project managers have low authority and must request resources.
- projectized organization
- An organizational structure where most people work in projects and report to project managers, who have high authority over resources, schedule, and budget.
- integrated change control
- A process in predictive projects for reviewing, approving, and managing changes to scope, schedule, and cost baselines in a coordinated way.
- resource breakdown structure
- A hierarchical list of resources by category or type used to organize and plan resource needs.