CAPM : Predictive Plan-Based Methodologies (Domain 2)
PMI - CAPM : Certified Associate in Project Management - Domain 2 - Predictive, Plan-Based Methodologies
The Certified Associate in Project Management (CAPM) certification underwent a significant evolution in late 2023, expanding its scope to incorporate a diverse range of methodologies. Central to this evolution is Domain 2: Predictive, Plan-Based Methodologies. This domain represents 17% of the examination, translating to approximately 26 questions on the 150-question test. Mastery of this domain requires a deep understanding of traditional project management, where scope, schedule, and cost are defined early in the life cycle. This guide provides an exhaustive synthesis of the predictive framework, ranging from organizational suitability to the mathematical rigor of variance analysis.
1. The Strategic Application of Predictive Methodologies
Predictive methodologies, often referred to as “Waterfall” or “Plan-Driven” approaches, are characterized by a sequential flow of project phases. In these environments, the project team invests significant effort upfront to define the scope and requirements. This approach is most effective when the project’s outcomes are well-understood and the requirements are unlikely to change significantly throughout the execution.
A primary task for a project professional is determining when a predictive approach is appropriate. This decision is heavily influenced by the organizational structure and the nature of the work. For instance, projects with physical sequencing, such as construction, hardware manufacturing, or plant commissioning, necessitate a predictive model because rework is prohibitively expensive.
Suitability and Organizational Structures
The effectiveness of a predictive plan is often dictated by how the organization is arranged. The following structures play a critical role in determining methodology suitability:
- Hierarchical Structures: Traditional “top-down” organizations where authority is clearly defined. Predictive projects thrive here due to the clear lines of reporting and established processes.
- Matrix Structures: Organizations that blend functional and project-based reporting. In a matrix, a project manager must navigate shared resources, making the rigid scheduling of predictive methodologies both a challenge and a necessity for resource coordination.
- Virtual and Colocation: The physical or digital location of the team influences how predictive controls are documented. Colocated teams may use physical artifacts, while virtual teams rely on digital versions of predictive controls to ensure alignment across different geographies.
2. Integration Management: Cohesion within the Predictive Framework
Integration management is the “glue” that holds a predictive project together. It involves the processes and activities required to identify, define, combine, unify, and coordinate the various project management processes. Within a predictive framework, integration is a proactive endeavor. It begins with project initiation and benefit planning, ensuring that the project remains a viable vehicle for organizational change.
An Integration Management Plan is a primary component of the overarching project management plan. It describes how the various project components—such as scope, schedule, cost, and quality—will be integrated and managed. This includes determining the activities within each process and identifying typical activities that move the project from one phase to the next.
The Role of the Project Manager in Integration
The project manager acts as the primary integrator. This role requires the individual to serve as an initiator, negotiator, coach, facilitator, and listener. In a predictive environment, the project manager must also be a “working member” of the team, facilitating communication between the project sponsor and the project team. The project manager’s emotional intelligence (EQ) is vital here, as they must manage stakeholder expectations and resolve conflicts between shared resources in matrix or hierarchical setups.
3. Architecture of the Work Breakdown Structure (WBS)
The Work Breakdown Structure (WBS) is a foundational artifact in predictive projects. It provides 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 Packages: The Terminal Element
At the lowest level of the WBS are “Work Packages.” These are the units of work that can be realistically estimated for cost and duration. By breaking the project down into work packages, the project professional can assign responsibility and monitor progress with a high degree of granularity. In predictive tracking, the WBS serves as the baseline for all subsequent planning activities, including scheduling and resource allocation.
Translating WBS to Other Methodologies
While the WBS is a predictive staple, modern project management requires the ability to translate these structures. Domain 2 knowledge includes understanding how a predictive WBS might be translated into an adaptive iteration or how requirements in a product backlog might mirror the scope defined in a WBS. However, in the pure predictive sense, the WBS remains static once the baseline is approved, ensuring that the project does not suffer from unauthorized scope changes.
4. Advanced Scheduling and the Critical Path Method (CPM)
Scheduling is perhaps the most mathematically rigorous aspect of Domain 2. Predictive project tracking relies on a pre-defined schedule baseline to measure success. A key component of this is the Critical Path Method (CPM).
The Critical Path Method Defined
CPM is a technique used to determine the minimum project duration and the level of scheduling flexibility on the logical network paths within the schedule model. The critical path is the longest sequence of activities in a project plan which must be completed on time for the project to finish by its due date. Any delay in a critical path activity directly impacts the project finish date.
Activity and Duration Management
To build a schedule, the project professional must distinguish between different project components:
- Tasks vs. Milestones: A task has a specific duration (the time it takes to complete), whereas a milestone is a point in time with zero duration, representing a significant event or deliverable.
- Resource Determination: The schedule is heavily dependent on the number and type of resources available. Predictive planning requires a clear determination of resources during the planning phase to ensure the schedule is realistic.
5. Quality Management in Plan-Based Projects
Quality is not an afterthought in predictive methodologies; it is planned in from the start. A Quality Management Plan defines the standards, requirements, and objectives that the project must meet, as well as the activities that will be used to ensure the project reaches these benchmarks.
Application of Quality Controls
In a predictive environment, quality is managed through specific activities within the process, such as audits, inspections, and rigorous testing against predefined specifications. Because the scope is fixed early on, the quality criteria are usually well-defined and measurable. This differs from adaptive approaches where quality is often defined through iterative feedback and acceptance criteria. In Domain 2, the focus is on meeting the specific quality requirements laid out in the initial planning phase.
6. Developing the Schedule Baseline and Variances
Once the WBS, CPM, and resource requirements are established, the project professional creates the schedule baseline. This baseline serves as the yardstick against which actual performance is measured. In predictive, plan-based projects, success is often defined by the project’s ability to stick to this original plan.
Understanding Variances
The ability to calculate and interpret variances is a core requirement for the CAPM exam. Variance analysis compares the actual performance against the baseline.
- Schedule Variance (SV): This is a measure of schedule performance. It indicates how much the project is ahead of or behind the planned schedule at a given point in time.
- Cost Variance (CV): This measures cost performance. It identifies if the project is under or over budget by comparing the actual cost of work performed against the planned value.
Calculation of these variances allows the project manager to identify trends and implement corrective actions before the project deviates too far from its objectives.
7. Performance Measurement and Project Controls
Project controls are the data gathering, management, and analytical processes used to predict, understand, and constructively influence the time and cost outcomes of a project. Predictive projects rely on a variety of artifacts to maintain these controls.
Predictive Artifacts
Artifacts in Domain 2 are structured and formal. They include:
- Risk Register: A document used to identify, analyze, and manage project risks. Unlike adaptive projects where risks might be managed through daily standups, predictive projects use the risk register as a living document to track risk responses throughout the project life cycle.
- Stakeholder Register: This identifies all individuals or groups interested in the project and documents their requirements and influence.
- Project Management Plan: The comprehensive document that includes all sub-plans (schedule, cost, quality, etc.).
- Requirements Traceability Matrix: A grid that links product requirements from their origin to the deliverables that satisfy them.
8. Financial Management and Cost Control
Budgeting and financial forecasting are integral to Domain 2. Because predictive projects are often large and involve fixed-price contracts or rigid budgets, the financial oversight must be meticulous.
Budgeting and Forecasting
Predictive budgeting involves estimating the costs for each work package in the WBS. These costs are then aggregated to create the cost baseline. Financial management in this domain includes:
- Cost Estimates: Determining the approximate monetary resources needed.
- Budgeting: Mapping these costs over time.
- Calculating Variances: Continually assessing if the actual spend aligns with the planned spend to ensure the project remains financially viable.
9. Project Roles and Responsibilities
A clear understanding of roles is essential for maintaining order in a plan-based project. Predictive methodologies rely on a specific division of labor between the project manager, the sponsor, and the team.
PM vs. Sponsor vs. Team
- Project Sponsor: Usually the individual who provides resources and support for the project and is accountable for enabling success. They often help navigate organizational hurdles and provide the high-level initiation.
- Project Manager: The individual assigned by the performing organization to lead the team that is responsible for achieving the project objectives. They are the primary negotiators and coach the team through the execution of the plan.
- Project Team: The group of individuals performing the work of the project. In predictive environments, the team’s responsibilities are often clearly defined by the work packages they are assigned to.
10. Project Closure and Transitions
The final phase of a predictive project is closure. Unlike adaptive projects, which may end with a final iteration and a handoff of the product backlog, predictive projects have a formal, structured closure process.
Formal Closure Activities
- Administrative Closure: Ensuring all documentation is complete and archived.
- Contract Closure: Finalizing any external agreements or vendor contracts.
- Transitions: The formal process of moving the project’s product, service, or result to the operational environment or a new phase. This involves documenting lessons learned and updating organizational process assets to benefit future projects.
Scenario-Based Short Answer Questions
-
Scenario: You are managing a bridge construction project where the designs must be approved by the city council before any ground is broken. Changes to the design after construction starts will cost millions. Which methodology should you use, and why?
- Answer: You should use a predictive methodology because the scope is fixed, requirements are well-understood, and rework is prohibitively expensive.
-
Scenario: A project manager is working in a matrix organization and finds that a key engineer is being pulled into another project. Which project artifact should the manager consult to address this resource conflict?
- Answer: The project manager should consult the resource requirements within the Project Management Plan and the stakeholder register to negotiate with the functional manager.
-
Scenario: You are reviewing the WBS and notice that a specific unit of work is too large to estimate accurately. What is the smallest unit you should break it down into?
- Answer: The work should be broken down into “Work Packages,” which are the smallest units in a WBS that can be estimated for cost and duration.
-
Scenario: During a project status meeting, you report that the project is on track because the “Critical Path” is being met. What does this indicate about the project’s finish date?
- Answer: It indicates that the sequence of activities with the longest duration is on schedule, and therefore the minimum project completion date is secure.
-
Scenario: A project manager identifies a potential event that could negatively impact the project’s budget. Where should this be documented?
- Answer: This should be documented in the Risk Register, which is the primary artifact for tracking risks and their potential impacts.
-
Scenario: You have completed the project planning and have a baseline. A stakeholder asks for a major change that was not in the original scope. What should the project manager do?
- Answer: The project manager should follow the formal change control processes defined in the Integration Management Plan to evaluate the impact on time, cost, and quality.
-
Scenario: The actual cost of work performed is $50,000, but the planned value was $45,000. What is the Cost Variance (CV), and is the project over or under budget?
- Answer: The Cost Variance is -$5,000 (CV = EV - AC), indicating the project is over budget.
-
Scenario: A project manager needs to ensure that every requirement is linked directly to a deliverable. Which tool should they use?
- Answer: They should use a Requirements Traceability Matrix to link product requirements to their corresponding deliverables.
-
Scenario: An organization is very hierarchical and has rigid rules about reporting. Which methodology is typically better suited for this environment?
- Answer: A predictive, plan-based methodology is generally better suited for hierarchical organizations due to its structured nature and clear lines of authority.
-
Scenario: The project is nearing completion. What is the final step the project manager must take to move the deliverable to the customer?
- Answer: The project manager must conduct formal project closure and transitions, ensuring all documentation is finalized and the results are officially handed over.
Open-Ended Design Questions
- Describe how you would design a communication strategy for a predictive project being executed by a virtual team across three different time zones.
- Propose a framework for integrating a Quality Management Plan into a WBS for a high-stakes medical device manufacturing project.
- Design a set of criteria for determining when a project in a matrix organization should shift from a predictive model to a hybrid model.
- Develop a template for a Risk Register that specifically addresses the unique challenges of long-duration predictive projects (e.g., projects lasting 3+ years).
- Explain the design logic for establishing a schedule baseline when the project involves a high number of shared resources and fixed milestones.
Glossary of Key Terms
- Artifact: Any document, template, or output used in project management to monitor, manage, or control progress.
- Critical Path Method (CPM): A scheduling technique that identifies the longest sequence of dependent activities and determines the shortest possible project duration.
- Cost Variance (CV): A mathematical measure of cost performance, calculated by subtracting actual costs from the earned value of work performed.
- Integration Management Plan: A document that outlines how different project components will be unified and coordinated throughout the project life cycle.
- Matrix Structure: An organizational setup where employees report to both a functional manager and a project manager.
- Milestone: A significant point or event in a project that has zero duration.
- Organizational Process Assets (OPAs): The plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization.
- Predictive Methodology: A project management approach where the scope, time, and cost are determined in the early phases of the project life cycle.
- Project Life Cycle: The series of phases that a project passes through from its start to its completion.
- Project Management Plan: A formal, approved document that defines how the project is executed, monitored, and controlled.
- Project Sponsor: An individual or group that provides resources and support for the project and is accountable for enabling success.
- Quality Management Plan: A component of the project management plan that describes how an organization’s quality policies will be implemented.
- Requirements Traceability Matrix: A grid that links product requirements from their origin to the deliverables that satisfy them.
- Risk Register: A repository in which outputs of risk management processes are recorded.
- Schedule Baseline: The approved version of a schedule model that can be changed only through formal change control procedures.
- Schedule Variance (SV): A measure of schedule performance expressed as the difference between the earned value and the planned value.
- Stakeholder Register: A project document including the identification, assessment, and classification of project stakeholders.
- Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work to be carried out by the project team.
- Work Package: The work defined at the lowest level of the work breakdown structure for which cost and duration can be estimated and managed.
Leaderboard
No scores saved yet. Be the first!
25 Questions — PMI - CAPM : Certified Associate in Project Management - Domain 2 - Predictive, Plan-Based Methodologies
Expand any question to reveal the correct answer and explanation.
-
1 A project manager is overseeing a predictive project where Path A-B-C has a duration of 12 days and Path A-D-C has a duration of 15 days. If activity B is delayed by 2 days, what is the new total float for activity B?
Calculate the difference between the critical path and the sub-critical path before and after the change.
1 day
The original float for Path A-B-C was 3 days ($15 - 12$); a 2-day delay consumes 2 days of that float, leaving 1 day remaining.
-
✗ 3 days
This represents the original float before the delay was applied to the non-critical path.
-
✗ 0 days
This would only be true if the delay was equal to or greater than the original float of 3 days.
-
✗ 2 days
This confuses the amount of the delay with the remaining slack available on the network path.
-
-
2 A project has a Planned Value ($PV$) of $1,200, an Actual Cost ($AC$) of $1,500, and an Earned Value ($EV$) of $1,300. Which statement accurately describes the project status?
Compare $EV$ to $PV$ for schedule and $EV$ to $AC$ for cost.
The project is ahead of schedule and over budget.
The $SV$ is positive ($1,300 - 1,200 = 100$) indicating ahead of schedule, while the $CV$ is negative ($1,300 - 1,500 = -200$) indicating over budget.
-
✗ The project is behind schedule and under budget.
This assumes a negative $SV$ and positive $CV$, which contradicts the provided numerical data.
-
✗ The project is ahead of schedule and under budget.
While the schedule status is correct, the actual costs exceed the value of the work performed.
-
✗ The project is behind schedule and over budget.
This incorrectly interprets the positive schedule variance as a delay.
-
-
3 In a predictive environment, a project manager is decomposing work. They have reached the lowest level of the Work Breakdown Structure (WBS). What have they identified?
Consider the specific term for the final deliverable-based units in the WBS hierarchy.
Work packages
The WBS is a deliverable-oriented hierarchy where the lowest level is the work package, used for cost and duration estimation.
-
✗ Activities
Activities are the specific actions required to produce work packages and are typically defined in the activity list, not the WBS itself.
-
✗ Milestones
Milestones represent significant points in time with zero duration rather than a level of work decomposition.
-
✗ Control accounts
Control accounts are management points where scope, budget, and schedule are integrated, typically positioned above work packages.
-
-
4 Calculate the Cost Performance Index ($CPI$) for a project where the Earned Value ($EV$) is $4,500 and the Actual Cost ($AC$) is $5,000.
Divide the value of work completed by the actual amount spent.
$0.90$
The $CPI$ is calculated as $EV / AC$, which in this case is $4,500 / 5,000$.
-
✗ $1.11$
This result occurs if the formula is inverted to $AC / EV$, which does not represent cost efficiency.
-
✗ $-500$
This is the Cost Variance ($CV$), not the index, representing the absolute dollar difference rather than efficiency.
-
✗ $0.80$
This is a common calculation error that does not follow the standard Earned Value Management ratio.
-
-
5 Using the 1-based scheduling method provided in the source material, if an activity has an Early Start ($ES$) of day 5 and a duration of 6 days, what is its Early Finish ($EF$)?
Apply the standard formula where the start day is counted as part of the total duration.
Day 10
Using the formula $EF = ES + \text{Duration} - 1$, we calculate $5 + 6 - 1 = 10$.
-
✗ Day 11
This ignores the 'minus one' logic required when the start day is included as the first full day of work.
-
✗ Day 12
This result would assume the activity starts after day 5 rather than on day 5.
-
✗ Day 9
This calculation incorrectly subtracts two days instead of one from the total sum.
-
-
6 A project manager is operating in a Strong Matrix organization. Who primarily controls the project budget and the team members' evaluations?
Focus on the shift of authority toward the project manager in 'Stronger' matrix variants.
The project manager controls the budget; the functional manager and project manager share evaluation input.
In a Strong Matrix, the project manager has high authority over the budget, but personnel management is often shared with functional heads.
-
✗ The functional manager controls both the budget and the evaluations.
This description characterizes a Functional or Weak Matrix organization rather than a Strong Matrix.
-
✗ The project manager controls both the budget and the evaluations.
This high level of authority is typical of a Projectized organization where functional managers have little to no role.
-
✗ The project sponsor controls the budget; the functional manager controls evaluations.
While a sponsor may authorize funds, the day-to-day control of the budget in this specific structure resides with the project manager.
-
-
7 During the planning phase of a predictive project, the project manager identifies that the Schedule Performance Index ($SPI$) is $0.85$. What is the most likely cause of this metric?
Recall the meaning of an efficiency index when the value is less than one.
Work is being completed slower than originally planned.
An $SPI$ less than $1.0$ indicates that the Earned Value is less than the Planned Value, meaning the project is behind schedule.
-
✗ The project is currently trending under budget.
The $SPI$ measures schedule efficiency, not cost; budget status is determined by the $CPI$ or $CV$.
-
✗ The critical path has been shortened through crashing.
Shortening the path through crashing would likely result in an $SPI$ of $1.0$ or greater, as work would be accelerated.
-
✗ More work has been completed than was originally scheduled.
This would result in an $SPI$ greater than $1.0$, indicating a performance that exceeds the plan.
-
-
8 A project manager needs to determine the $Total Float$ for an activity. The Late Finish ($LF$) is day 25 and the Early Finish ($EF$) is day 20. What is the $Total Float$?
Find the difference between the latest possible completion and the earliest possible completion.
5 days
Total Float is calculated as $LF - EF$ or $LS - ES$, which in this case is $25 - 20 = 5$.
-
✗ 0 days
Zero float is only present on the critical path, where the late and early dates are identical.
-
✗ 45 days
This is the sum of the dates, which does not represent any valid project management metric for slack or duration.
-
✗ $-5$ days
Negative float suggests the project is behind its required completion date, but the standard calculation order is $LF - EF$.
-
-
9 An organization is building a highly regulated nuclear power plant where the scope is extremely stable and changes are expensive. Which development approach is most appropriate?
Consider which lifecycle favors extensive upfront planning and rigorous documentation.
Predictive
Predictive approaches are ideal for regulated industries with stable requirements where upfront planning reduces risk and cost.
-
✗ Adaptive
Adaptive approaches rely on iterative changes, which are often unsuitable for projects with high regulatory constraints and fixed physical scope.
-
✗ Incremental
While increments are possible, the core need for stability and upfront regulatory approval favors a sequential, predictive lifecycle.
-
✗ Agile
Agile methodologies thrive on evolving requirements, which contradicts the stability needed for heavily regulated construction projects.
-
-
10 The Project Management Office (PMO) provides a project manager with a set of templates and best practices but does not exert direct control over the project. What type of PMO is this?
Identify the PMO type that serves as a resource center rather than a governing body.
Supportive
Supportive PMOs act as consultants by providing templates and training without enforcing compliance or direct management.
-
✗ Controlling
Controlling PMOs require compliance with specific frameworks or the use of particular tools, representing a higher level of oversight.
-
✗ Directive
Directive PMOs take control of projects by directly managing them and assigning project managers.
-
✗ Administrative
This is not a standard PMI classification for PMOs; the three types are Supportive, Controlling, and Directive.
-
-
11 Which document is primarily used to track the source of each requirement and ensure it is tested during the product delivery phase?
Think of the artifact that 'traces' requirements from start to finish.
Requirements Traceability Matrix
The RTM links requirements to their origins and tracks them throughout the project lifecycle to ensure they are realized.
-
✗ WBS Dictionary
The WBS Dictionary provides detailed information about each work package but does not specifically track the validation of individual requirements.
-
✗ Stakeholder Register
This document identifies stakeholders and their interests but is not designed for tracking technical requirement fulfillment.
-
✗ Risk Register
The risk register documents threats and opportunities, not the functional or non-functional requirements of the product.
-
-
12 Calculate the Schedule Variance ($SV$) if the Earned Value ($EV$) is $2,400 and the Planned Value ($PV$) is $2,800.
Apply the subtraction formula that compares work actually done to work that should have been done.
$-400$
Schedule Variance is calculated as $EV - PV$, which is $2,400 - 2,800 = -400$.
-
✗ $400$
This occurs if $PV$ is subtracted from $EV$, which would incorrectly indicate that the project is ahead of schedule.
-
✗ $0.85$
This is the Schedule Performance Index ($SPI$), not the variance; variance is expressed as a currency value.
-
✗ $5,200$
This is the sum of the two values, which has no application in standard Earned Value Management calculations.
-
-
13 In a predictive project, a change request is submitted to add a new feature. What should the project manager do first?
Identify the analytical step that must occur before any decision or implementation.
Analyze the impact of the change on scope, schedule, and cost.
A project manager must evaluate the consequences of a change before presenting it to the Change Control Board for approval.
-
✗ Immediately update the Project Management Plan.
The plan should only be updated after the change has been formally reviewed and approved by the appropriate authority.
-
✗ Ask the Change Control Board to approve the change.
Submitting for approval without an impact analysis is premature and does not provide the board with necessary decision-making data.
-
✗ Implement the change to keep the customer happy.
Implementing changes without formal approval leads to scope creep and bypasses the integrated change control process.
-
-
14 An activity on the critical path has an Early Start ($ES$) of day 10. If the activity is delayed by 3 days, what happens to the project completion date?
Recall the definition of the critical path and its relationship to 'float'.
The project completion date will be delayed by 3 days.
Activities on the critical path have zero float; therefore, any delay directly translates to a delay in the overall project.
-
✗ The project completion date will remain the same.
This would only be possible if the activity had float, which critical path activities do not possess.
-
✗ The project manager can use the activity's float to absorb the delay.
Critical path activities are defined by their lack of float, meaning there is no buffer to absorb delays.
-
✗ The project completion date will be delayed by 1.5 days.
Delays on the critical path are not halved or reduced; they impact the end date on a one-to-one basis.
-
-
15 A project manager is calculating the Cost Variance ($CV$). If the Earned Value ($EV$) is $900 and the Actual Cost ($AC$) is $850, what is the result?
Subtract the actual amount spent from the value of the work performed.
$50$
Cost Variance is calculated as $EV - AC$, which is $900 - 850 = 50$.
-
✗ $-50$
This would be the result if costs were higher than the earned value, indicating an over-budget status.
-
✗ $1.06$
This is the $CPI$ ($900 / 850$), which is an efficiency ratio rather than a variance.
-
✗ $1,750$
Summing the $EV$ and $AC$ does not provide a meaningful performance metric for cost control.
-
-
16 What is the primary difference between a Project and Operations?
Think about the duration and the nature of the output (unique vs. same).
Projects are temporary and unique; operations are ongoing and repetitive.
This is the fundamental distinction provided by PMI; projects have a definitive end, whereas operations sustain the business.
-
✗ Projects have budgets, while operations do not.
Both projects and operations require financial resources and have assigned budgets to function.
-
✗ Projects are managed by PMs, while operations are managed by Sponsors.
Operations are typically managed by functional or departmental managers, not sponsors, who provide high-level project support.
-
✗ Operations are always predictive, while projects are always adaptive.
The development approach (predictive/adaptive) can be applied to projects, but operations are categorized by their repetitive nature regardless of methodology.
-
-
17 A project manager is preparing a RACI matrix. What does the 'A' in RACI stand for, and how many individuals should hold this role per task?
Identify the role that has 'the buck stops here' responsibility and its frequency.
Accountable; exactly one per task.
Accountability implies final authority; having more than one person accountable often leads to confusion in decision-making.
-
✗ Authorized; as many as needed.
The 'A' stands for Accountable, not Authorized, and it is a best practice to limit this to one person.
-
✗ Assigned; one or more per task.
The 'R' stands for Responsible (those who do the work), which is different from the Accountable role.
-
✗ Approve; only the project sponsor.
While 'A' involves final sign-off, it stands for Accountable, and the role is not limited strictly to the sponsor.
-
-
18 A project manager is evaluating the cost of quality. They spend money on training the team to prevent defects. Under which category does this cost fall?
Consider costs associated with proactive measures to ensure work is done correctly from the start.
Prevention costs
Prevention costs are incurred to keep defects out of the hands of the customer by ensuring they are not created in the first place.
-
✗ Appraisal costs
Appraisal costs relate to testing, measuring, and auditing to identify defects, not to training for prevention.
-
✗ Internal failure costs
These costs are incurred when a defect is found by the team before the product is delivered to the customer.
-
✗ External failure costs
External failure costs occur when the customer finds the defect after delivery, leading to warranties or lost reputation.
-
-
19 If an activity has a Late Start ($LS$) of day 15 and an Early Start ($ES$) of day 12, what is the $Total Float$ for this activity?
Subtract the earliest possible start day from the latest possible start day.
3 days
Total Float is calculated as $LS - ES$, which is $15 - 12 = 3$.
-
✗ 27 days
Adding the dates does not yield a slack metric or any standard project management indicator.
-
✗ 0 days
If the float were zero, the Late Start and Early Start would be the same day, indicating a critical path activity.
-
✗ $-3$ days
Negative float occurs when the project is behind, but the standard calculation results in a positive value in this scenario.
-
-
20 Which artifact is used in predictive projects to provide a detailed description of each component in the Work Breakdown Structure, including its owner and acceptance criteria?
Identify the 'companion' document that adds context to the graphical WBS tree.
WBS Dictionary
The WBS Dictionary accompanies the WBS to provide the descriptive details needed for every work package.
-
✗ Project Charter
The charter provides a high-level project overview and authority but does not contain detailed work package descriptions.
-
✗ Scope Baseline
The Scope Baseline includes the WBS and Dictionary, but the Dictionary is the specific component containing the descriptive text.
-
✗ Activity List
The activity list breaks work packages down further into tasks but does not define the WBS components themselves.
-
-
21 A project manager calculates that the Cost Performance Index ($CPI$) is $1.2$ and the Schedule Performance Index ($SPI$) is $0.7$. What is the status of the project?
Analyze the efficiency indices relative to the baseline of 1.0.
The project is under budget and behind schedule.
A $CPI > 1.0$ indicates spending efficiency (under budget), while an $SPI < 1.0$ indicates schedule delay (behind schedule).
-
✗ The project is over budget and ahead of schedule.
This correctly interprets the direction of the numbers but applies them to the wrong categories.
-
✗ The project is under budget and ahead of schedule.
This incorrectly assumes that a low $SPI$ ($0.7$) represents a fast-moving project.
-
✗ The project is over budget and behind schedule.
This ignores the cost efficiency shown by the $CPI$ being greater than one.
-
-
22 What is the primary purpose of a 'Milestone' in a predictive project schedule?
Consider the duration of a milestone and its role as a marker.
To mark a significant point or event with zero duration.
Milestones are used as reference points for progress and typically represent the completion of major deliverables.
-
✗ To act as a buffer for activities on the critical path.
Milestones have zero duration and cannot serve as buffers; buffers are specific time allocations added to paths.
-
✗ To represent the amount of effort required to complete a task.
Task durations represent effort and time; milestones are points in time that do not consume effort.
-
✗ To replace the need for a Work Breakdown Structure.
Milestones are scheduled items, whereas the WBS is a deliverable-oriented hierarchy; they serve different purposes.
-
-
23 An activity has an Early Finish ($EF$) of day 18 and a Late Finish ($LF$) of day 18. What can be concluded about this activity?
Consider what 'slack' or 'float' exists when the earliest and latest completion dates match.
The activity is on the critical path.
When the Early Finish and Late Finish are identical, the activity has zero float, which is the defining characteristic of the critical path.
-
✗ The activity has a float of 18 days.
Float is the difference between late and early dates ($18 - 18$), which is zero, not the date value itself.
-
✗ The activity is a milestone.
While a milestone could have these dates, any activity on the critical path will share this early/late finish identity regardless of its duration.
-
✗ The project is behind schedule.
Identical early and late finish dates indicate zero float, meaning the project is exactly on track, not behind.
-
-
24 According to the PMI Code of Ethics, which value requires project managers to provide accurate information and not mislead others regarding project status?
Identify the core value associated with truth-telling and transparency.
Honesty
Honesty is the ethical commitment to provide truthful information and refrain from misleading stakeholders about project performance.
-
✗ Responsibility
Responsibility refers to the ownership of decisions and actions, which includes the consequences of those actions.
-
✗ Fairness
Fairness involves being objective and impartial, particularly regarding conflicts of interest or procurement.
-
✗ Respect
Respect involves showing regard for others, their property, and their contributions to the project.
-
-
25 In a scenario where $SPI = 1.1$ and $CPI = 0.9$, which management action is most appropriate?
Determine which index indicates a performance issue that needs a corrective investigation.
Investigate why costs are higher than planned despite being ahead of schedule.
A $CPI$ below $1.0$ is a concern even if the schedule performance is good, as it indicates a cost overage.
-
✗ No action is needed because the project is ahead of schedule.
Being ahead of schedule does not negate the fact that the project is over budget, which requires management attention.
-
✗ Crash the schedule to improve the Cost Performance Index.
Crashing usually increases costs, which would further lower an already poor $CPI$.
-
✗ Celebrate a successful project that is performing well in all domains.
A $CPI$ of $0.9$ indicates a 10% cost overrun, meaning the project is not performing well in the cost domain.
-