SkarpChapter 9 of 20
Resource and Quality Management in Predictive Projects
Connect people, materials, and quality expectations to your predictive plan so that resources are available when needed and deliverables meet agreed standards.
Resource and Quality in Predictive Projects: Why They Matter
Where We Are in the Course
In a predictive life cycle, you lock in scope, schedule, and cost early. To make that plan real, you must connect it to resources and quality so the work can actually happen and deliverables are accepted.
Two New Layers
We add two layers to your existing schedule and cost skills: resource management (people, equipment, materials) and quality management (agreed standards for deliverables and processes).
CAPM Exam Angle
Expect scenarios about over-allocated team members, choosing between resource leveling and smoothing, explaining cost–quality trade-offs, and identifying what belongs in a quality management plan.
Learning Objectives
You will learn how resources are estimated and acquired, how resource calendars shape the schedule, how leveling differs from smoothing, what a basic quality management plan includes, and how changes ripple across constraints.
From Scope to Resources: Estimating What You Need
Start from the Scope Baseline
Resource planning starts from the scope baseline: the scope statement, the work breakdown structure, and the WBS dictionary. Work packages are where cost and duration are estimated and managed.
Identify Resource Types
For each work package or activity, identify resource types: human roles, physical equipment and facilities, and materials. A resource breakdown structure groups these into clear categories.
Estimate Quantities and Skills
Estimate how much of each resource is needed and at what skill level: effort in person-hours, quantities of identical units, and competency requirements such as certifications or experience.
Estimating Techniques
Use expert judgment, analogous estimating, and parametric estimating. These resource estimates drive both your schedule durations and your cost baseline, so they must be realistic.
Example: Building a Simple Resource Plan
Scenario Overview
You manage a predictive project to implement a new HR system. One work package is “Configure core HR modules”, broken into analyze options, configure system, and unit test configuration.
Identify Resources
For each activity, list roles: BA and HR SME for analysis; configurator and DBA for configuration; tester and HR SME for unit testing. Focus on roles, not names yet.
Estimate Effort and Duration
Estimate hours per role: e.g., 24 BA hours and 12 HR SME hours for analysis. Convert to days assuming 8-hour days, then align overlaps (e.g., SME overlaps BA’s analysis days).
Create Resource Views
Use the estimates to build a resource histogram (total demand per role) and update the resource calendar (specific days the HR SME and others are needed). These artifacts support schedule development.
Resource Calendars, Histograms, and Over-Allocation
What Is a Resource Calendar?
A resource calendar shows working and nonworking time for a specific person, team, or equipment: workdays and hours, holidays, absences, and part-time patterns that affect when work can occur.
Impact on the Schedule
Scheduling tools use resource calendars to compute start and finish dates. If Maria is available 4 hours per day and a task needs 16 hours, the task stretches across 4 working days.
What Is a Resource Histogram?
A resource histogram is a bar chart of resource usage over time, such as number of developers per week. It reveals peaks of over-allocation and valleys of under-use.
Spotting Over-Allocation
Over-allocation occurs when planned demand exceeds availability from the resource calendar, such as assigning 16 hours of work to one person in an 8-hour day or double-booking equipment.
Resource Optimization: Leveling vs Smoothing
Why Optimize Resources?
When resource calendars and histograms show over-allocation, you apply resource optimization techniques. For CAPM, you must distinguish resource leveling from resource smoothing.
Resource Leveling
Resource leveling delays or reschedules activities based on resource limits. It can change activity dates, the critical path, and the project end date. Resources are fixed; the schedule is flexible.
Resource Smoothing
Resource smoothing reshapes resource usage without changing the project end date or critical path. It moves only non-critical activities within their available float.
Common Exam Trap
If the project completion date must not change, choose resource smoothing. If resource limits are strict and the schedule may slip, choose resource leveling.
Example: Leveling vs Smoothing in a Simple Network
The Simple Network
Activities: A (Design UI, 3 days), B (Design DB, 3 days) in parallel, then C (Integrate, 2 days) after both. With parallel A and B, plus C, the original duration is 5 days.
Problem: One Engineer
Only one engineer is available, but A and B are scheduled in parallel. The resource histogram shows two engineer-days per day during days 1–3, which is an over-allocation.
Resource Leveling Outcome
With leveling, you run A days 1–3, B days 4–6, then C days 7–8. Over-allocation is removed, but the project duration increases from 5 to 8 days.
Resource Smoothing Scenario
If two engineers are available and the end date must stay at day 5, you keep A and B in parallel, then C. You might shift non-critical tasks, but you do not extend the project—this is smoothing.
Planning for Quality: From Requirements to Quality Management Plan
Quality Starts with Requirements
Quality planning begins from requirements, acceptance criteria, and applicable standards or regulations. These drive both product quality and process quality expectations.
What Is a Quality Management Plan?
It is a component of the project management plan describing how organizational quality policies will be implemented on the project, including objectives, standards, roles, and activities.
Key Components
Typical contents: quality objectives, applicable standards and metrics, roles and responsibilities, quality assurance activities, quality control activities, and quality tools and procedures.
Integration with Time and Cost
The plan must align with schedule and budget by allocating time and money for audits, inspections, and testing. Planning quality means defining “good enough” and how to measure it.
Integrating Scope, Schedule, Cost, and Quality in Predictive Projects
The Four Key Baselines
Predictive projects use interdependent baselines: scope, schedule, cost, and quality. Each is an approved reference version of the plan used to measure performance.
Scope Changes Ripple Out
Increasing scope usually adds work, which tends to extend the schedule, raise costs, and require more or higher-quality resources and quality activities.
Schedule and Cost Trade-offs
Schedule compression via fast tracking or crashing can raise cost and risk. Cost cuts often force reductions in scope, longer schedules, or lower quality if not managed carefully.
Raising Quality Has a Price
Stricter quality or acceptance criteria typically mean more work and testing, which increases cost and can lengthen the schedule. Changes go through integrated change control.
Quick Check: Leveling vs Smoothing and Calendars
Test your understanding of resource optimization and calendars.
A project manager discovers that a specialist is scheduled at 150% capacity for two weeks. The sponsor insists that the project completion date must not change. Which technique should the project manager try first, and which artifact will help identify when the specialist is available?
- Use resource leveling and review the resource breakdown structure.
- Use resource smoothing and review the resource calendar.
- Use resource leveling and review the quality management plan.
- Use schedule crashing and review the milestone chart.
Show Answer
Answer: B) Use resource smoothing and review the resource calendar.
The sponsor will not allow the project completion date to change, so the project manager should use resource smoothing, which preserves the end date and critical path by moving only non-critical work within float. To see when the specialist is actually available, the manager relies on the resource calendar, which shows working and nonworking time for that resource.
Quick Check: Quality Management Plan and Trade-offs
Check your understanding of quality planning and constraint impacts.
A customer requests stricter acceptance criteria for a key deliverable after the scope, schedule, and cost baselines have been approved. What is the MOST accurate description of the likely impact if the change is approved through integrated change control?
- Quality will improve with no impact, because acceptance criteria do not affect the baselines.
- Scope will decrease while schedule and cost remain the same, because quality replaces scope.
- Quality activities and possibly technical work will increase, likely impacting schedule and/or cost.
- Only the quality baseline will change; schedule and cost baselines are independent of quality.
Show Answer
Answer: C) Quality activities and possibly technical work will increase, likely impacting schedule and/or cost.
Stricter acceptance criteria raise the required quality level. Meeting them typically requires more work (additional testing, rework, higher-spec components), which tends to increase effort. That effort must be reflected in the schedule and cost baselines. In predictive projects, baselines are interdependent, so quality changes usually affect time and/or cost.
Thought Exercise: Resolving a Resource–Quality Conflict
Work through this scenario to practice integrated thinking about resources and quality.
Scenario
You manage a predictive project to deploy a new analytics dashboard for executives. The project is halfway through. A critical testing phase is scheduled next month, requiring:
- 2 senior testers full‑time for 3 weeks
- 1 performance testing environment
You check the resource calendar and discover:
- Only 1 senior tester is available (the other is assigned to a regulatory project that cannot slip).
- The performance testing environment is booked by another team for the middle week of your planned test window.
The sponsor says:
- "We must keep the current go‑live date."
- "Quality is critical; we cannot reduce testing."
- "We have limited budget left for this phase."
Your task
Think through these questions step by step (you can jot notes):
- Which artifacts would you review first to understand the constraints (name at least three)?
- Where do you see potential options involving resource smoothing? Where might resource leveling be required?
- What options could you propose that respect the sponsor’s statements as much as possible? Consider:
- Adjusting non‑critical activities
- Negotiating part‑time support or temporary staff
- Re‑sequencing tests around the environment’s availability
- For each option, briefly note how it affects scope, schedule, cost, and quality.
Reflection
After you outline your ideas, compare them mentally to what you know from this module:
- Did you use resource calendars and the schedule network to see where float exists?
- Did you protect quality objectives while exploring cost and schedule changes?
- Did you avoid assuming that time, cost, and quality are all fixed simultaneously?
On your next Skarp diagnostic or mock exam, look out for similar multi‑constraint scenarios. Practice quickly identifying which constraint is most flexible and which technique fits (smoothing, leveling, crashing, or scope adjustment).
Key Terms: Resource and Quality Management
Flip these cards to reinforce core concepts from the module.
- Resource calendar
- A calendar that identifies the working days and shifts on which each specific resource is available, as well as nonworking times such as holidays, vacations, and other commitments. It constrains when activities requiring that resource can be scheduled.
- Resource histogram
- A bar chart showing the amount of a resource used over time, such as the number of developers needed each week. It is used to detect over-allocation and under-utilization.
- Resource leveling
- A resource optimization technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply. It can change the critical path and project end date.
- Resource smoothing
- A resource optimization technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. It does not change the project completion date or the critical path and only uses float.
- Work breakdown structure (WBS)
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- Work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- Quality management plan
- A component of the project management plan that describes how applicable policies, procedures, and guidelines will be implemented to achieve the quality objectives of the project, including standards, metrics, roles, QA and QC activities.
- Acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- Quality assurance (QA) vs quality control (QC)
- Quality assurance focuses on process: audits, reviews, and improvements to ensure the right processes are used. Quality control focuses on product: inspections, tests, and measurements to verify deliverables meet specified requirements.
- Scope, schedule, cost, quality interdependence
- In predictive projects, scope, schedule, cost, and quality baselines are tightly linked. A change to one (e.g., higher quality) usually requires changes to at least one of the others (e.g., more time or cost).
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- quality control
- Product-oriented activities such as inspections and testing that verify deliverables meet specified requirements.
- quality assurance
- Process-oriented quality activities such as audits and reviews that ensure the project uses the right processes to meet quality standards.
- resource calendar
- A calendar that shows the working days and nonworking days, shifts, and availability patterns for a specific resource, used to determine when that resource can work on project activities.
- resource leveling
- A resource optimization technique that adjusts activity start and finish dates based on resource constraints, potentially changing the critical path and project duration.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
- resource histogram
- A bar chart showing the amount of a resource used over time, used to detect over-allocation and under-utilization.
- resource smoothing
- A resource optimization technique that adjusts activities within their float to avoid exceeding resource limits, without changing the project completion date or critical path.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- quality management plan
- A component of the project management plan that describes how applicable quality policies, procedures, and guidelines will be implemented to achieve the project’s quality objectives.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- resource breakdown structure
- A hierarchical representation of resources by category and type, such as labor, equipment, and materials, used to organize and plan project resources.