SkarpSkarp

Chapter 5 of 20

Roles, Responsibilities, Cost, and Quality Fundamentals

Zoom in on who does what on a project and how cost and quality expectations are set, balanced, and monitored. This module connects people, money, and quality into a coherent picture that shows up repeatedly across exam questions.

27 min readen

Big Picture: People, Money, and Quality on Projects

Why This Module Matters

This module connects three exam-heavy themes: who does what on a project, who controls the money, and who guards quality. Most CAPM scenarios mix these together.

Links to Earlier Modules

You already met life cycles (predictive, adaptive, hybrid) and stakeholders and governance. Here we zoom into specific roles and how they relate to cost and quality.

What You Will Be Able To Do

You will distinguish PM, BA, sponsor, and team responsibilities, read RACI charts, understand cost and quality basics, and reason about trade-offs among scope, schedule, cost, and quality.

Core Roles: PM, BA, Sponsor, Team (Predictive vs Adaptive)

Project Manager (PM)

The PM leads the project to meet objectives, owns the project management plan, integrates all areas, and manages the team and stakeholders. Predictive: heavy upfront planning. Adaptive: servant leader, removes impediments.

Business Analyst (BA)

The BA focuses on requirements and value: eliciting, analyzing, and managing requirements. Predictive: detailed documentation. Adaptive: works with product owner to refine items in the product backlog.

Sponsor

The sponsor funds the project, sets high-level direction, approves major changes, and champions the project at senior levels. Think money, authority, and escalations.

Team Members

Team members create deliverables, provide estimates, identify risks, and contribute to quality. Adaptive teams are often cross-functional and self-organizing, heavily involved in iteration planning.

Role Clues in Exam Questions

Day-to-day coordination and trade-offs point to the PM. Requirements and value point to the BA. Funding and major approvals point to the sponsor. Doing or estimating the work points to the team.

Responsibility Assignment: RACI Basics

What is RACI?

RACI is a responsibility assignment tool. R = Responsible, A = Accountable, C = Consulted, I = Informed. It clarifies who does the work, who owns it, who gives input, and who gets updates.

How RACI is Structured

A RACI chart is a table: rows are activities, columns are roles. Each cell holds R, A, C, or I. It shows at a glance who is involved in each key task.

Key Rules and Exam Clues

There should be one Accountable per activity. A person can be both R and A. Consulted roles give input before or during work; Informed roles just receive updates afterward.

Mental Model for RACI

Who swings the hammer? Responsible. Whose neck is on the line? Accountable. Who must we talk to first? Consulted. Who just needs updates? Informed.

Reading a RACI Chart: Worked Scenario

Scenario Setup

We have four roles: Sponsor, PM, BA, Developer, and four activities: define needs, approve charter, elicit requirements, develop feature. Each activity has R, A, C, I assigned.

Sample RACI Highlights

Sponsor is A for business needs and charter. BA is A/R for eliciting requirements. Developer is A/R for developing the feature. PM is often R or C, coordinating and drafting.

Question 1: Charter Approval

Who signs off the charter? Look at activity 2. The Sponsor is Accountable, so they approve, even though the PM did most of the drafting work (Responsible).

Question 2: Missing Consultation

If a developer was not consulted on a requirement change, check activity 3. Developer is C, so they should have been involved. The PM should fix this process gap.

Question 3: Feature Outcome

Who owns the feature’s correctness? Activity 4 shows the Developer is both A and R. The PM coordinates, but the Developer is accountable for the technical result.

Cost Fundamentals: Estimates, Baselines, and Reserves

Cost Estimates and WBS

Cost estimates predict what work will cost. In predictive projects, they are often built from the work breakdown structure, down to work packages where cost and duration are estimated and managed.

Cost Baseline

The cost baseline is the approved, time-phased budget excluding management reserves. It is the reference for measuring and controlling cost performance and is changed only through formal change control.

Contingency vs Management Reserve

Contingency reserve covers identified risks and is inside the cost baseline. Management reserve covers unforeseen work, is outside the cost baseline, and is usually controlled by management or the sponsor.

Total Project Budget

The total project budget equals the cost baseline plus management reserve. Exam trap: do not treat management reserve as part of the cost baseline.

Who Can Spend What

PMs typically manage contingency according to the plan. Management reserve usually requires higher-level approval. Using contingency does not change the baseline if it was planned into it.

Cost Scenario: Which Money Do We Use?

Numbers in the Example

Estimates total $900,000. Contingency reserve is $90,000. Management reserve is $60,000. We will compute the cost baseline and total project budget.

Baseline and Budget

Cost baseline = $900,000 + $90,000 = $990,000. Total project budget = $990,000 + $60,000 = $1,050,000.

Known Risk Occurs

An identified risk costs $20,000. You use contingency reserve, which is already part of the cost baseline. Consuming it does not change the baseline; it was planned.

Unknown Risk Occurs

A new regulation forces a $30,000 design change. This was not identified. You request to use management reserve, with sponsor or management approval and possibly adjust the baseline via change control.

Exam Shortcut

Identified risk → contingency (inside baseline). Unidentified but in-scope work → management reserve (outside baseline, needs higher approval).

Quality Fundamentals: Fitness, Conformance, and Cost of Quality

Quality vs Grade

Quality is how well requirements are met and defects are avoided. Grade is the level of features. You can have low grade but high quality, or high grade but low quality.

Fitness for Use

Fitness for use asks whether the product actually works for users in real conditions. A tool that meets specs but crashes in normal use is not fit for use.

Conformance and Acceptance Criteria

Conformance means meeting requirements, standards, and acceptance criteria: a set of conditions required to be met before deliverables are accepted.

Prevention vs Inspection

Prevention avoids defects (training, good design, automated tests). Inspection finds defects after they occur (testing, audits). Quality management prefers prevention.

Cost of Quality

Cost of conformance covers prevention and appraisal. Cost of nonconformance covers internal failures (rework) and external failures (warranty, reputation). Exams favor choices that reduce nonconformance.

Balancing Scope, Schedule, Cost, and Quality

The Big Four Constraints

Projects juggle scope, schedule, cost, and quality. Changing one typically affects at least one other. Many CAPM questions test whether you see these interactions.

When Scope Increases

More features usually mean higher cost and longer schedule, unless you add resources. If you refuse to change time or cost, quality is likely to suffer.

When Schedule Shortens

If the deadline moves up, you may reduce scope or increase cost. If neither changes, you risk lower quality due to rushed work and less testing.

Budget Cuts and Higher Quality

Budget cuts often force scope reduction or longer schedules. Raising quality standards usually raises cost and/or schedule due to more testing or better materials.

Predictive vs Adaptive Trade-offs

Predictive: scope is fixed, changes affect time and cost via change control. Adaptive: time and cost per iteration are fixed, scope is flexible while you protect quality.

Quiz 1: Roles and RACI

Test your understanding of roles and responsibility assignment.

A project is running late. The developer says they were never consulted about a requirement that turned out to be technically complex. The RACI chart shows the developer as 'C' for 'Define detailed requirements'. What should the project manager have ensured?

  1. That the developer was marked as 'R' instead of 'C' for defining detailed requirements
  2. That the developer was involved early to provide input before requirements were finalized
  3. That the sponsor personally reviewed all technical requirements with the developer
  4. That the business analyst was removed from the requirements process to avoid confusion
Show Answer

Answer: B) That the developer was involved early to provide input before requirements were finalized

In RACI, 'C' (Consulted) means the role must provide input before or during the work. The PM should have ensured the developer was actually consulted when defining requirements. They do not need to be Responsible (doing the work), but their input is required. The sponsor and BA roles are not the core issue here.

Quiz 2: Cost and Quality Trade-offs

Apply cost and quality concepts to a realistic scenario.

Midway through a predictive project, a previously unknown safety regulation is introduced. Meeting it will require extra design work and testing, increasing cost. The risk was not in the risk register. What is the BEST action for the project manager?

  1. Use contingency reserve because the risk affects quality and safety
  2. Use management reserve, following the organization’s approval process and update the cost baseline through change control if approved
  3. Reduce testing activities to free up budget and keep the baseline unchanged
  4. Ask the team to work unpaid overtime to absorb the impact without changing cost or schedule
Show Answer

Answer: B) Use management reserve, following the organization’s approval process and update the cost baseline through change control if approved

This is an unforeseen requirement (unknown-unknown), so it is a candidate for management reserve, not contingency. The PM should follow the organization’s process to access management reserve, and if approved, adjust the cost baseline via formal change control. Cutting testing or asking for unpaid overtime would endanger quality and ethics.

Thought Exercise: Predictive vs Adaptive Decisions

Use this mental walkthrough to contrast predictive and adaptive decisions around scope, cost, and quality.

Imagine two versions of the same project: building a mobile app.

  1. Predictive version
  • Scope, time, and cost are determined early (predictive life cycle).
  • Halfway through, a stakeholder asks for two extra features.

Ask yourself:

  • If you accept the extra scope, what must you do to schedule and cost?
  • Likely extend schedule and/or increase budget.
  • What formal process do you follow?
  • Initiate change control, update the scope baseline, schedule, and cost baseline if approved.
  • How do you protect quality?
  • Ensure testing and acceptance criteria are updated; do not compress quality activities just to keep the date.
  1. Adaptive version
  • You are using an adaptive life cycle with 2-week iterations.
  • The same stakeholder asks for two extra features.

Ask yourself:

  • What usually stays fixed in adaptive: time and cost per iteration.
  • What is flexible: scope (how many items fit into a sprint/iteration).
  • What do you do with the new features?
  • Add them to the product backlog, reprioritize with the product owner.
  • Some lower-priority items may be postponed to keep iteration time and quality stable.
  1. Reflect (write down or say aloud):
  • In each version, which constraint moved first (scope, schedule, cost, quality)?
  • How did the PM protect quality while responding to change?

Use this pattern when reading exam questions: Predictive → change control and baseline updates. Adaptive → backlog reprioritization and scope flexibility.

Key Term Review: Roles, Cost, and Quality

Flip through these cards to reinforce the core terms from this module.

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.
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.
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.
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.
RACI: Responsible
The role that performs the work to complete a task or deliverable.
RACI: Accountable
The single role ultimately answerable for the result and who approves the work.
Contingency reserve
Budget within the cost baseline set aside for identified risks (known-unknowns), managed by the project according to the risk plan.
Management reserve
Budget outside the cost baseline set aside for unforeseen work within scope (unknown-unknowns), typically controlled by senior management or sponsor.
Cost baseline
The approved, time-phased project budget excluding management reserves, used to measure and control cost performance.
Fitness for use
The degree to which a product or service works for the user in real conditions and fulfills its intended purpose.
Conformance to requirements
The extent to which the product or process meets specified requirements, standards, and acceptance criteria.
Cost of quality (CoQ)
The total cost of ensuring quality (prevention and appraisal) plus the cost of failing to meet quality (internal and external failures).
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.

Key Terms

RACI
A responsibility assignment model where roles are marked as Responsible, Accountable, Consulted, or Informed for each activity.
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.
cost baseline
The approved, time-phased project budget excluding management reserves, used to measure and control cost performance.
cost of quality
The total cost of ensuring quality (prevention and appraisal) plus the cost of failing to meet quality (internal and external failures).
fitness for use
The degree to which a product or service works for the user in real conditions and fulfills its intended purpose.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
management reserve
Budget outside the cost baseline set aside for unforeseen work within scope (unknown-unknowns), typically controlled by senior management or sponsor.
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.
contingency reserve
Budget within the cost baseline set aside for identified risks (known-unknowns), managed by the project according to the risk plan.
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.
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.
conformance to requirements
The extent to which the product or process meets specified requirements, standards, and acceptance criteria.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself