Project Management Qualification (PMQ) Quiz 04

Correct: The integration of change control and scope management requires a systematic approach where the impact on all project constraints such as time, cost, quality, and risk is assessed before a decision is made. Once the impact is understood, a formal change request must be processed through the established governance framework. If approved, the scope baseline and the Work Breakdown Structure (WBS) must be updated to ensure the project team is working toward the most current, authorized version of the project scope. Incorrect: Updating the Work Breakdown Structure before formal approval bypasses the change control process and leads to unauthorized scope expansion. Implementing the change immediately without assessment or approval is a primary cause of scope creep and can lead to significant budget and schedule overruns. Simply rejecting the request because the baseline is locked is an inflexible approach that fails to recognize that project environments are dynamic; the purpose of change control is to manage changes effectively, not to prevent them entirely. Key Takeaway: Effective scope management relies on a robust change control process that ensures all modifications are evaluated, authorized, and documented in the project baselines.

Correct: Crashing is a schedule compression technique used to shorten the schedule duration for the least incremental cost by adding resources. In this scenario, authorizing overtime and hiring additional subcontractors are classic examples of crashing. The main drawbacks are the increase in budget and the potential for diminishing returns where adding more people leads to coordination overhead and lower individual productivity. Incorrect: Fast tracking involves taking activities that would normally be done in sequence and performing them in parallel. While the scenario mentions working simultaneously, the primary driver here is the addition of resources (overtime and new subcontractors), which characterizes crashing. Incorrect: Resource smoothing is a 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. Unlike resource leveling, smoothing does not change the critical path or the completion date. Incorrect: Lead adjustment (or adding a lead) allows an acceleration of the successor activity, but it does not inherently involve the addition of extra resources or costs like crashing does. Key Takeaway: When a project manager needs to compress a schedule by adding resources to critical path tasks, they are crashing the project, which prioritizes time over cost.

Correct: Parametric estimating involves using a statistical relationship between historical data and other variables to calculate an estimate for activity parameters such as duration or cost. In this scenario, the project manager is using a specific unit of measure (hours per rack) and multiplying it by the quantity of work to be performed, which is the hallmark of the parametric approach. Incorrect: Analogous estimating uses the total duration or cost of a previous similar project as a whole to estimate the current one; it is a top-down approach that is generally less accurate because it does not use a statistical scale. Three-point estimating uses optimistic, pessimistic, and most likely values to account for uncertainty, which was not described in the scenario. Bottom-up estimating involves breaking down the project into the smallest possible components and aggregating their individual estimates, which is a more granular and time-consuming process than the mathematical modeling shown here. Key Takeaway: Parametric estimating is most effective when there is a high degree of correlation between the variables and the historical data used to create the model is accurate.

Correct: The Program Evaluation and Review Technique (PERT) uses a weighted average (Beta distribution) to calculate the expected duration. The formula is (Optimistic + 4 x Most Likely + Pessimistic) / 6. Applying the values from the scenario: (10 + (4 x 15) + 26) / 6 = (10 + 60 + 26) / 6 = 96 / 6 = 16 days. The standard deviation for a single activity in PERT is calculated as (Pessimistic – Optimistic) / 6. Applying the values: (26 – 10) / 6 = 16 / 6 = 2.67 days. Incorrect: The option suggesting 17 days is incorrect because it uses the Triangular Distribution formula (Optimistic + Most Likely + Pessimistic) / 3, which is less common in PERT analysis as it does not weight the most likely estimate. Incorrect: The option suggesting a standard deviation of 6.53 days is incorrect because it likely uses an incorrect divisor or a variance calculation instead of the standard deviation formula. Incorrect: The option suggesting 15 days is incorrect because it only identifies the most likely estimate without performing the weighted average calculation required by PERT. Key Takeaway: PERT provides a more statistically weighted estimate than a simple average by giving four times the weight to the most likely scenario, and the standard deviation helps project managers understand the level of risk or uncertainty associated with the estimate.

Correct: Finish-to-Start is the most common logical relationship where the successor activity (data analysis) cannot begin until the predecessor activity (clinical trials) has been completed. This accurately reflects the requirement that the analysis starts only after the trials end. Incorrect: Start-to-Start would imply that the data analysis could begin as soon as the clinical trials start, which contradicts the requirement that trials must finish first. Incorrect: Finish-to-Finish implies that the successor cannot finish until the predecessor finishes; while this might be true, it does not specifically control the start of the analysis phase as requested. Incorrect: Start-to-Finish is a rare dependency where the completion of a successor depends on the start of a predecessor, which is the inverse of the logical flow needed for sequential research activities. Key Takeaway: Finish-to-Start is the standard dependency for sequential tasks where one must be fully completed before the next can initiate.

Correct: The critical path is defined as the longest sequence of activities through a project network that determines the shortest possible project duration. By calculating the paths in this scenario, we find two main sequences: Path 1 (A-B-C-D-F) which equals 4 + 12 + 20 + 10 + 5 = 51 days, and Path 2 (A-B-E-F) which equals 4 + 12 + 15 + 5 = 36 days. Since Path 1 is the longest, it is the critical path. Incorrect: The option A-B-E-F with a duration of 36 days represents a non-critical path because it is shorter than the longest path, meaning the activities on this path have float. The option A-B-C-D-F with a duration of 46 days is a mathematical error that fails to correctly sum the durations of the activities on the longest path. The option A-B-C-E-F with a duration of 56 days is incorrect because it describes a sequence that does not follow the logic of the network diagram, as Activity E follows Activity B, not Activity C. Key Takeaway: Identifying the critical path requires summing all possible sequences of activities from start to finish; the sequence with the highest total duration is the critical path and has zero float.

Correct: Total Float is calculated by subtracting the Early Finish from the Late Finish (20 minus 13), which equals 7 days. This represents the amount of time an activity can be delayed from its early start without delaying the project finish date. Free Float is calculated by subtracting the Early Finish of the current activity from the Early Start of the immediate successor (16 minus 13), which equals 3 days. This represents the amount of time an activity can be delayed without delaying the early start of any successor activity. Incorrect: The option stating both are 7 days is incorrect because it assumes that Free Float is always equal to Total Float, which only happens if the successor’s Early Start is equal to the current activity’s Late Finish. The option stating both are 3 days incorrectly applies the successor constraint to the project-level float calculation. The option stating 8 days and 5 days uses incorrect mathematical logic that does not align with the standard Critical Path Method formulas. Key Takeaway: Total Float measures flexibility relative to the project completion date, while Free Float measures flexibility relative to the next logical activity in the sequence.

Correct: The most effective communication strategy involves tailoring the level of detail to the audience. Executive stakeholders typically require a milestone chart because it provides a high-level summary of significant events, key deliverables, and critical dates without the clutter of individual tasks. Conversely, technical teams require a detailed Gantt chart to understand the specific timing of tasks, the duration of activities, and the complex dependencies between work packages. Incorrect: Presenting a detailed Gantt chart to executives often leads to information overload and distracts from strategic decision-making, while a milestone chart alone is insufficient for technical leads who need to manage the flow of daily work. Using a network diagram for executives is generally inappropriate as it is a technical tool for logic analysis rather than a status reporting tool. Providing only summary bars to technical leads would prevent them from seeing the specific task-level data they need to execute the project. Key Takeaway: Milestone charts are best for high-level reporting of major progress points, while Gantt charts are essential for managing the detailed schedule, dependencies, and resource timing at the execution level.

Correct: Finish-to-Finish with a 5-day lag is the correct choice because the scenario specifies that the completion of the successor (Activity B) is dependent on the completion of the predecessor (Activity A). A lag is an added delay between activities, which in this case is the 5 days required for stabilization after the integration is finished. Incorrect: Finish-to-Start with a 5-day lag is incorrect because this would mean that the testing phase cannot even begin until 5 days after the integration is finished, whereas the scenario specifically links the completion dates of the two activities. Incorrect: Start-to-Finish with a 5-day lead is incorrect because this relationship implies that the successor cannot finish until the predecessor starts, which is a rare logical link and does not fit the scenario of two finishing points being linked. Incorrect: Finish-to-Finish with a 5-day lead is incorrect because a lead represents an acceleration of the successor activity, meaning it would finish 5 days before the predecessor finishes, which contradicts the requirement for a 5-day delay. Key Takeaway: In the Precedence Diagramming Method, the Finish-to-Finish relationship is used when the completion of the successor depends on the completion of the predecessor, and lags are used to insert mandatory waiting time between these logical points.

Correct: Fast tracking is a schedule compression technique where activities or phases normally performed in sequence are performed in parallel for at least a portion of their duration. Since the project sponsor has refused additional budget, fast tracking is the most appropriate choice because it typically does not involve extra costs, though it does increase project risk and the potential for rework. Incorrect: Crashing involves adding resources to the project to shorten the duration for the least incremental cost. This technique is unsuitable here because it always increases project costs, which violates the sponsor’s constraint. Incorrect: Resource leveling is a resource optimization technique that adjusts start and finish dates based on resource constraints. It usually results in an increased project duration rather than a compressed one. Incorrect: Scope reduction involves removing deliverables or requirements to save time. While this might shorten the schedule, it is a change to the project’s baseline scope rather than a schedule compression technique like fast tracking or crashing, and it may not be permissible under regulatory requirements. Key Takeaway: When schedule compression is required without additional funding, fast tracking is the primary technique used, provided the project team can manage the increased risk of overlapping tasks.

Correct: Resource leveling is the appropriate technique when resource limits are the primary constraint. It involves adjusting start and finish dates based on resource availability. Because the resource is limited to one crane and the activities are concurrent, leveling will move one activity to start after the other, which often extends the project duration and changes the critical path. Incorrect: Resource smoothing is used when the time constraint is the priority; it only adjusts activities within their available float and cannot resolve a conflict where the total resource demand exceeds the limit throughout the required period. Crashing is incorrect because it involves adding resources to shorten the schedule, which violates the scenario’s constraint of a fixed budget and a single available crane. Fast tracking is incorrect because it involves overlapping activities to shorten the duration, which would actually worsen the resource conflict by requiring two cranes simultaneously instead of one. Key Takeaway: Resource leveling is a resource-constrained scheduling technique that prioritizes resource limits over schedule dates, whereas resource smoothing is a time-constrained technique that prioritizes the end date over resource optimization.

Correct: Resource smoothing is a technique used when the project duration is fixed (time-limited). It involves rescheduling activities within their total float so that resource requirements do not exceed specific limits or to simply reduce the fluctuations in demand. Since the scenario mentions a fixed completion date and available float, delaying non-critical tasks is the appropriate smoothing action. Incorrect: Delaying the project completion date describes resource leveling, which is used when resources are limited and the schedule must be extended to accommodate them. Incorrect: Fast-tracking is a schedule compression technique used to shorten the project duration, not to smooth resource demand. Incorrect: Crashing involves adding resources to shorten the schedule, which typically increases costs and does not address the goal of minimizing fluctuations in the existing resource pool. Key Takeaway: Resource smoothing is time-limited and utilizes float to balance demand, whereas resource leveling is resource-limited and may extend the project end date. Neither technique should be confused with schedule compression methods like crashing or fast-tracking.

Correct: A lag is a directed delay in the logical relationship between two activities. In this scenario, the cabling (successor) must wait for a period of time after the rack installation (predecessor) is completed. A Finish-to-Start relationship with a 2-day lag ensures that the successor activity starts exactly 2 days after the predecessor finishes, accounting for the mandatory inspection period. Incorrect: Applying a Finish-to-Start relationship with a 2-day lead would mean that the cabling starts 2 days before the rack installation is even finished, which contradicts the requirement that the racks must be fully installed first. Incorrect: A Start-to-Start relationship with a 2-day lag would mean the cabling could start 2 days after the rack installation begins. If the rack installation takes 5 days, the cabling would start while the racks are still being moved, which is incorrect. Incorrect: A Finish-to-Finish relationship with a 2-day lag would only mandate that the cabling finishes 2 days after the racks finish. This does not properly constrain the start date of the cabling, which is the primary concern for the safety inspection. Key Takeaway: Lag represents a required delay between activities, while lead represents an acceleration or overlap. Finish-to-Start with lag is the standard way to model waiting periods for external dependencies like inspections or curing times.

Correct: The schedule baseline is the approved version of the schedule that provides a benchmark for measuring project performance. It is essential for calculating variances and determining if the project is ahead of or behind schedule. When a significant scope change occurs, the baseline must be updated through formal change control to ensure that performance measurement remains relevant and accurate. Incorrect: Allowing team leads to adjust dates without formal control undermines the integrity of the baseline and makes performance measurement impossible because the reference point is constantly moving. Incorrect: Using only a live schedule without a baseline prevents the project manager from identifying deviations from the original plan, as there is no fixed point for comparison. Incorrect: Locking the schedule and refusing to update it for approved scope changes results in a baseline that no longer reflects the project reality, leading to misleading performance data and poor decision-making. Key Takeaway: A schedule baseline is a vital tool for monitoring and control that must be protected by formal change management to remain a valid reference point throughout the project lifecycle.

Correct: Resource smoothing is the specific technique used when the project’s end date is a fixed constraint. It involves adjusting the activities of a schedule such that the requirements for resources do not exceed certain predefined resource limits. In smoothing, unlike leveling, the project’s critical path is not delayed, and activities are only rescheduled within their available float. Incorrect: Resource leveling is used when resource limits are the primary constraint. This technique often results in the project’s original end date being extended because activities are delayed beyond their float to match resource availability. Incorrect: The resource breakdown structure is a hierarchical tool used to categorize and identify resources by type and category; it is a planning document rather than an optimization technique for resolving over-allocation. Incorrect: Fast tracking is a schedule compression technique where activities that would normally be done in sequence are performed in parallel. This typically increases resource demand and risk rather than resolving a resource over-allocation issue. Key Takeaway: Choose resource smoothing when the schedule is the priority and resource leveling when resource availability is the priority.

Correct: In project management, resource identification involves determining what is needed to complete the work. Human resources are categorized by their skills, experience, and competencies to ensure the right people are assigned to the right tasks. Physical resources, such as equipment, materials, and facilities, are categorized by their technical specifications, quality requirements, and the quantities needed. Incorrect: Categorizing resources solely by cost and depreciation focuses on accounting and financial reporting rather than the functional identification needed for project execution. Incorrect: Classifying all resources as consumables is inaccurate because human resources are not consumed in the same way as materials like fuel or stationery, and equipment often has residual value. Incorrect: Grouping by department or storage location describes organizational or logistical structures but does not address the fundamental identification of the resource capabilities or specifications required to meet project objectives. Key Takeaway: Effective resource management requires a clear distinction between human resources (defined by capability) and physical resources (defined by specification) to ensure the project has the necessary means to achieve its outputs.

Correct: The Responsibility Assignment Matrix (RAM) is the most effective tool for mapping work packages from the Work Breakdown Structure to the project team members. A common version is the RACI chart, which explicitly defines who is Responsible, Accountable, Consulted, and Informed for each task, thereby eliminating confusion over authority and task ownership. Incorrect: The Resource Breakdown Structure (RBS) is a hierarchical list of resources categorized by type and category; while it helps in identifying what resources are available, it does not assign specific accountability for work packages. Incorrect: A Resource Histogram is a tool used to visualize resource allocation over time to identify periods of over-allocation or under-utilization, but it does not define roles or responsibilities. Incorrect: Resource Leveling is a technique used to adjust the project schedule to address resource constraints by balancing demand with supply, rather than a tool for defining accountability. Key Takeaway: To ensure clear accountability and avoid role confusion, project managers use a Responsibility Assignment Matrix (RAM) to link the work (WBS) with the people (OBS). Only one person should be marked as Accountable for any single task to ensure clear ownership. No asterisks were used in this explanation as requested.

Correct: Analyzing the schedule for workarounds and seeking alternatives is the most proactive way to manage physical resource constraints. By identifying tasks that are not dependent on the delayed equipment, the project manager can maintain momentum and minimize the impact on the overall timeline without immediately resorting to schedule extensions or excessive costs. Incorrect: Submitting a formal change request to extend the date is premature. A project manager should first attempt to mitigate the delay through resource leveling, smoothing, or re-sequencing before requesting a baseline change. Incorrect: Canceling the order and purchasing from a new vendor without a cost-benefit analysis or confirmation of lead times could lead to even greater delays and significant budget overruns, making it an irresponsible first step. Incorrect: Reallocating specialized technicians to administrative tasks is a poor use of human resources and does not address the physical resource gap. It focuses on keeping people busy rather than progressing the project’s critical objectives. Key Takeaway: Effective physical resource management involves proactive problem-solving, schedule flexibility, and the exploration of alternatives to maintain the project’s critical path when faced with supply chain disruptions.

Correct: When resources are over-allocated on the critical path and the project end date is fixed, the project manager must increase the resource supply to meet the demand. This can be achieved by hiring contractors, authorizing overtime, or reassigning qualified personnel from other areas. Since there is no float on the critical path, the capacity must be increased to meet the demand without changing the schedule. Incorrect: Applying resource leveling involves moving tasks to resolve resource conflicts, which often results in a delay to the project completion date. This contradicts the sponsor mandate to keep the end date fixed. Incorrect: Resource smoothing is a technique used to even out resource demand by utilizing the float of non-critical activities. Because the activities in this scenario are on the critical path, they have zero float, making resource smoothing an impossible option. Incorrect: Reducing the scope might solve the resource issue but is a drastic measure that changes the project deliverables and objectives. It is generally considered a last resort after resource acquisition strategies have been exhausted. Key Takeaway: Resource histograms identify periods of over-allocation. If the over-allocated tasks are on the critical path and the end date is fixed, the project manager must focus on increasing resource capacity rather than rescheduling tasks.

Correct: In a multi-project environment where resources are shared and scarce, conflicts should be resolved by looking at the broader organizational strategy. The Project Management Office (PMO) or a portfolio steering committee has the authority and visibility to determine which project provides the highest value or carries the highest risk, allowing them to allocate the resource where it is most needed. Incorrect: Implementing a resource leveling strategy by splitting time often results in task switching costs, where the resource loses productivity moving between different contexts, potentially causing both projects to miss their deadlines. Incorrect: Instructing a resource to work excessive overtime is an unsustainable solution that increases the risk of human error and burnout, which is particularly dangerous in high-stakes areas like cybersecurity. Incorrect: Unilaterally adjusting a project schedule without consulting the sponsor or assessing the impact on the business case is a failure of change control and ignores the possibility that the infrastructure project might actually be the higher priority. Key Takeaway: Resource scarcity across multiple projects requires a governance-led approach to ensure that resource allocation aligns with the organization’s strategic priorities rather than individual project preferences.

Correct: The most effective first step is to perform a gap analysis using a competency framework. This allows the project manager to objectively compare the specific skills required for the project tasks against the current proficiency levels of the team. This structured approach ensures that any interventions, such as training or recruitment, are targeted and cost-effective. Incorrect: Reviewing past performance appraisals is insufficient because high general productivity does not equate to having the specific technical competencies required for a new technology. Incorrect: Initiating a recruitment drive before identifying the specific gaps is premature and may lead to unnecessary costs or hiring the wrong profiles. Incorrect: Scheduling a mandatory training program for the entire team without a gap analysis is inefficient, as it may cover topics some members already know while failing to address the specific technical needs of the integration phase. Key Takeaway: Competency frameworks provide a standardized benchmark for assessing skills, enabling project managers to identify and bridge specific gaps through targeted development or resource acquisition.

Correct: The scenario describes the Storming stage, which is characterized by conflict, competition for status, and questioning of authority or processes as team members begin to realize the reality of the work and their relationships with others. In this stage, the project manager must act as a coach, helping the team navigate disagreements and ensuring that roles and responsibilities are clearly understood. Incorrect: Forming is the initial stage where team members are generally polite, observant, and looking for guidance; the scenario describes active friction which occurs later. Norming is the stage where the team begins to resolve their differences, appreciate colleague strengths, and develop a cohesive way of working; the scenario shows the team is still in the conflict phase. Performing is the stage where the team is highly functional, autonomous, and focused on achieving goals with minimal intervention; the current team dynamics are too volatile for this stage. Key Takeaway: The Storming stage is a critical period where the project manager must transition from a directing style to a coaching style to help the team move toward stability and productivity.

Correct: The Completer Finisher is essential at the end of a project or task to polish and perfect the work. They are characterized by their attention to detail, their ability to spot minor errors, and their drive to ensure that the project is completed to the highest standard and on time. In this scenario, the lack of focus on final polish and inconsistent documentation are classic signs that this role is missing. Incorrect: The Plant is the role responsible for generating original ideas and solving difficult problems through creativity. Since the team has already successfully moved through the design phase with innovative solutions, this role is likely already well-represented. Incorrect: The Resource Investigator focuses on exploring opportunities, networking, and bringing in external information or resources. The scenario describes internal quality control issues rather than a lack of external engagement or resources. Incorrect: The Monitor Evaluator provides a logical, eye-for-detail approach to analyzing options and making impartial judgments. While they are good at seeing the big picture and evaluating feasibility, they are less focused on the final polishing and finishing tasks compared to the Completer Finisher. Key Takeaway: Building a balanced team requires recognizing that different phases of a project lifecycle demand different Belbin roles; the closing phase specifically requires the meticulous nature of the Completer Finisher to ensure quality and compliance.

Correct: According to Herzberg’s Two-Factor Theory, factors such as salary, working conditions, and job security are hygiene factors. While their absence causes dissatisfaction, their presence does not provide long-term motivation. To truly motivate a team, a project manager must focus on motivators, which include responsibility, the work itself, recognition, and opportunities for personal growth. Delegating responsibility and providing growth opportunities directly addresses these motivators. Incorrect: Increasing base salary and improving the office environment are hygiene factors. While these may prevent dissatisfaction, Herzberg argues they do not lead to higher levels of motivation once a baseline is met. Incorrect: Clarifying reporting lines and job descriptions are also hygiene factors related to company policy and administration. These help prevent confusion and dissatisfaction but do not act as positive motivators for performance. Incorrect: Linking effort to performance and rewards is the core of Vroom’s Expectancy Theory, not Herzberg’s Two-Factor Theory. While effective in its own right, it does not align with the specific theoretical framework requested in the scenario. Key Takeaway: To move beyond mere satisfaction and achieve true motivation, project managers must look past hygiene factors like pay and conditions and instead provide team members with meaningful work, recognition, and autonomy.

Correct: The Participating or Supporting style is the most appropriate choice when a team has high competence but variable or low commitment and confidence, often referred to as Maturity Level 3. In this scenario, the team is technically capable but has lost morale due to a specific hurdle. The project manager should focus on relationship-oriented behaviors, such as listening and facilitating, to help the team regain their confidence and reach a collective solution. Incorrect: The Telling or Directing style is intended for teams with low competence and low commitment; applying it to a highly skilled team would be seen as micromanagement and would likely decrease morale further. Incorrect: The Selling or Coaching style is best suited for teams with some competence but high commitment who still need direction; here, the team already possesses the skills but lacks the psychological drive to proceed. Incorrect: The Delegating style is reserved for teams with both high competence and high commitment. While the team is skilled, their current state of uncertainty and low morale means they require more support than a pure delegation approach provides. Key Takeaway: Effective project leadership requires matching the level of task and relationship behavior to the specific maturity and psychological state of the team at a given moment.

Correct: Coaching is the most appropriate technique here because it is task-oriented and focused on improving specific skills or performance levels within a relatively short timeframe to achieve immediate goals. The scenario specifies a three-week period and a focus on a specific software tool, which aligns with the coaching methodology. Incorrect: Mentoring is incorrect because it is typically a long-term, relationship-driven process focused on the individual’s overall career growth rather than a specific technical skill needed for a current task. Incorrect: Facilitating is incorrect because it is a technique used to help a group of people work together more effectively or reach a common goal, rather than focusing on one-on-one skill development. Incorrect: Counseling is incorrect because it is a supportive technique used to help individuals deal with personal problems or emotional issues that affect their work, which is not the case in this scenario. Key Takeaway: Coaching is used for short-term, task-specific skill enhancement, whereas mentoring is used for long-term, holistic professional development.

Correct: Effective performance management relies on timely, specific, and private feedback. By addressing the issue directly and privately, the Project Manager maintains the individual’s dignity while focusing on factual performance data (the missed milestones). A two-way conversation allows the manager to identify root causes—such as personal issues, resource constraints, or technical blockers—and fosters a collaborative environment for improvement. Incorrect: Highlighting performance issues in a project board meeting or any public forum is unprofessional and likely to damage morale and trust. Incorrect: Waiting for a formal annual review violates the principle that feedback should be timely; delaying the conversation prevents the team member from making necessary adjustments and risks further project slippage. Incorrect: Reassigning tasks without a prior discussion avoids the management responsibility of addressing the behavior and can lead to resentment or further disengagement from the team member. Key Takeaway: Constructive feedback should be behavior-focused, delivered in a private setting, and aimed at collaborative problem-solving to restore performance levels.

Correct: The Cost Performance Index (CPI) is calculated by dividing the Earned Value (EV) by the Actual Cost (AC). In this scenario, £250,000 divided by £275,000 equals approximately 0.91. A CPI value of less than 1.0 indicates that for every pound spent, the project is only receiving 91 pence of value, meaning the project is over budget. Incorrect: The value of 1.10 is incorrect because it results from dividing Actual Cost by Earned Value, which is the inverse of the correct formula. A value over 1.0 would suggest the project is under budget. Incorrect: The value of 0.83 represents the Schedule Performance Index (SPI), which is calculated as Earned Value divided by Planned Value (£250,000 / £300,000). While this shows the project is behind schedule, it does not represent the cost performance. Incorrect: While the CPI calculation of 0.91 is correct, the interpretation that the project is ahead of schedule is false. The SPI of 0.83 indicates the project is actually behind schedule. Key Takeaway: CPI is a measure of cost efficiency. A CPI of 1.0 means the project is exactly on budget, greater than 1.0 means under budget, and less than 1.0 means over budget.

Correct: Top-down estimation is most appropriate during the early stages of a project when limited information is available. It uses historical data or expert judgment to provide a quick, high-level figure suitable for feasibility studies. Bottom-up estimation is used once the project is detailed in a Work Breakdown Structure, as it involves estimating individual tasks and aggregating them to provide the highest level of accuracy for the budget baseline. Incorrect: Bottom-up estimation for the initial concept phase is incorrect because the detailed information required for this method is not yet available during the feasibility stage. Top-down estimation for the project management plan is incorrect because it lacks the necessary detail and accuracy required for a formal budget baseline. Incorrect: Parametric estimation for the initial concept phase and analogous estimation for the project management plan is incorrect because analogous estimation is a top-down technique that is less accurate than bottom-up, making it unsuitable for a final project management plan baseline. Incorrect: Three-point estimation for the initial concept phase and top-down estimation for the project management plan is incorrect because while three-point estimation can be used at various stages to manage uncertainty, using top-down estimation for the final plan does not provide the granular accuracy needed for effective project control and monitoring. Key Takeaway: Use top-down methods for speed and early-stage feasibility when details are scarce, and bottom-up methods for accuracy and detailed baseline establishment once the WBS is defined.

Correct: The cost baseline is the authorized, time-phased budget used to measure and monitor cost performance. It includes the project’s estimated costs and the contingency reserves (for known unknowns) but specifically excludes management reserves (for unknown unknowns). Management reserves are added to the cost baseline to determine the total project budget. Incorrect: The statement that the cost baseline includes management reserves is incorrect because management reserves are not part of the performance measurement baseline; they are held for unforeseen changes and require specific approval to be used. Incorrect: Excluding contingency reserves from the baseline is incorrect because contingency reserves are part of the budget allocated for identified risks and are essential for accurate performance measurement. Incorrect: Describing the baseline as a document that includes management reserves for the project manager’s discretionary use is incorrect; the baseline is subject to change control, and management reserves are typically outside the project manager’s direct control until authorized. Key Takeaway: The cost baseline is the performance measurement baseline that includes contingency reserves but excludes management reserves.