CCNA Predictive Plan Based Questions

The critical path method calculates the longest sequence of dependent activities, determining the project's shortest possible duration and identifying float. It is a core schedule development technique in predictive projects, driving duration forecasting and schedule compression decisions.

The Ishikawa diagram maps effect back to categorised causes — people, process, tools, environment — so the team can trace defect sources before they occur. For a predictive project's quality management plan, this satisfies the requirement to identify root causes proactively, rather than detecting defects later through inspection or statistical sampling.

Work performance information is a Control Quality output because the process compares deliverables against quality standards and feeds results into the Monitor and Control Project Work cycle. It satisfies the stem's requirement by capturing conformance and nonconformance data, such as validated defect repairs, which supports quality control decisions and reporting.

Project constraints — such as scope, schedule, cost, quality, risk and resource limitations — are documented in the scope statement to bound what the project will deliver. Including them satisfies the stem's requirement for a typical scope statement element in a predictive project.

Analogous estimating derives cost figures from the actual costs of comparable past projects, typically using top-down judgement. It suits early planning when detailed data is scarce, matching the stem's reference to historical data from similar projects.

The project charter is the document that formally authorises the project and grants the project manager authority to apply organisational resources to project activities. It satisfies the stem's authorisation constraint, distinguishing it from plans, which describe how work will be performed.

The forward pass is a schedule network analysis technique that calculates the early start and early finish dates for each activity by moving forward through the network from the start. It uses duration estimates and dependencies to determine the earliest possible times. This directly matches the project manager's need to determine early start and early finish dates for the renovation activities.

Variance analysis compares planned vs actual schedule.

In a predictive waterfall project, phases run sequentially with no overlapping or fast-tracking, so a two-week design delay pushes every dependent downstream phase by the same amount. The critical path lengthens by exactly two weeks, assuming no float or compression is applied later.

Sequential dependency accurately describes this chain, where each task's start is gated by its predecessor's finish (A→B→C→D). The stem's constraint is a strict finish-to-start cascade with no branching or overlap, which is precisely what a sequential relationship defines.

Qualitative risk analysis ranks identified risks by probability and impact, so it updates the risk register with each risk's urgency or priority rating. This satisfies the stem's requirement for a typical output of that process, since the register is the repository where prioritised risk information is recorded and maintained.

EMV multiplies probability by monetary impact, so 0.3 × $50,000 yields $15,000. This quantifies the risk's expected cost exposure against project objectives, giving the project manager a comparable figure for contingency reserves and risk prioritisation within the risk register.

The schedule baseline is an approved, time-phased version of the schedule, forming part of the project management plan's subsidiary plans and baselines. It satisfies the stem's requirement by being an output of schedule development that is formally incorporated into the plan, alongside scope, cost and performance measurement baselines.

The stakeholder register is an input to Plan Quality Management as it identifies stakeholders who have a specific interest in or influence over quality. For the ERP project, key stakeholders such as the finance department or IT security may have quality requirements. Understanding their needs helps the project manager define quality standards and compliance approaches, so the stakeholder register is a correct input.

When the current cost performance is expected to continue at the same rate, the estimate at completion is calculated as budget at completion divided by the cost performance index. This formula assumes that the efficiency or inefficiency observed to date will persist for the remainder of the project. It is the most common EAC formula used in earned value management for this scenario.

The project charter formally authorizes the project and the project manager, and it gives the project manager authority to apply organizational resources to project activities. In a predictive project, this authorization is essential before the project manager can commit resources to the schedule and budget. It is the document the sponsor signs to empower the project manager.

Parametric estimation multiplies the unit rate by quantity, then applies the productivity adjustment: 10 hours × 50 units = 500 hours, increased by 20% for slower new team members gives 500 × 1.2 = 600 hours. This satisfies the stem's stated productivity constraint.

A responsibility assignment matrix maps each work package or activity to the person accountable and responsible, typically using RACI notation. It is the document that makes role and responsibility assignments explicit, satisfying the need for the team to understand who does what.

The schedule management plan is a subsidiary component of the project management plan, describing how the schedule is developed, monitored and controlled. Project documents, by contrast, include items such as the schedule baseline's supporting activity lists and duration estimates.

Activity attributes are a documented output of Define Activities, extending the activity list with details such as predecessor relationships, leads and lags, resource requirements and imposed dates. They satisfy the stem's requirement for a Define Activities output rather than an input or tool.

The stakeholder register identifies everyone with an interest in the project, supplying the perspectives needed to surface risks during identification. It satisfies the input requirement by revealing external and internal parties whose objectives, concerns or influence may generate project threats and opportunities.

The lessons learned register is the living document updated throughout the project to capture knowledge gained during each phase. Recording these entries at phase closure lets the project manager feed validated insights into later phases, satisfying the stem's requirement to preserve lessons for future work rather than waiting until project closure.

The activity list is the primary output of Define Activities, enumerating all scheduled activities required to complete the project work. It satisfies the process output requirement by documenting activities that feed subsequent sequencing and estimation processes.

Lead time allows a successor task to begin before its predecessor completes, overlapping the two by two days. This satisfies the schedule constraint described in the stem, where the task starts early rather than waiting. It contrasts with lag, which imposes a delay between activities.

The project charter is the document that formally authorises the project's existence and grants the project manager authority to apply organisational resources to project activities. It is issued by the sponsor, satisfying the stem's requirement for formal authorisation and resource authority.

Used to compare actual vs planned.

A control chart plots data over time with control limits to distinguish common cause variation from special cause variation. It reveals whether a process is stable and highlights unusual patterns such as trends or points outside limits. This directly matches the need to assess process stability and detect anomalies in defect counts.

The WBS decomposes scope downward until reaching work packages, the lowest-level components where cost and duration can be reliably estimated and work assigned. This satisfies the structural characteristic that work packages sit at the bottom of the hierarchy.

Purchasing insurance transfers the financial consequence of the risk to a third party, satisfying the high-probability, high-impact threat in this predictive construction project. Unlike mitigation, which reduces probability or impact, transfer shifts ownership of the loss to the insurer while the risk itself remains.

Analogous estimating uses historical data from comparable past projects to estimate current costs, typically at a summary level. It satisfies the predictive approach's need for a top-down, less detailed technique when limited information exists, though it is less accurate than bottom-up methods.

In a predictive project, the approved scope baseline can only change through integrated change control. Documenting the cost and schedule impact, informing the stakeholder, and submitting a formal change request to the change control board respects that authority rather than unilaterally altering scope.

Purchasing insurance shifts the financial consequence of the risk to a third party, which is the defining mechanism of transfer. It satisfies the stem's constraint of a high-impact, low-probability threat, where avoidance is impractical and mitigation cannot reduce the loss exposure itself. The risk remains, but its ownership moves to the insurer.

This directly addresses the root cause and aims to recover the schedule.

Monitoring and Controlling tracks, reviews and regulates project performance against the plan, comparing actual progress with baselines and initiating change requests. It spans execution, giving the predictive project its mechanism for measuring deliverable progress and correcting deviations.

The project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is a key input to the Develop Project Charter process and is essential for initiating a predictive project. This directly matches the scenario's requirement.

Schedule compression analysis evaluates crashing and fast-tracking against the critical path, directly addressing the two-day slippage while protecting the project end date. It is the prescribed first response because it quantifies viable recovery options before committing resources, satisfying the stem's requirement to recover the schedule without prematurely altering scope or baseline.

Root cause analysis identifies why documentation and testing non-conformances arose, then corrective actions eliminate the source rather than the symptom. This satisfies the regulatory compliance requirement while preventing recurrence, and targeted fixes limit schedule impact better than halting work.

Work packages represent the lowest WBS level and describe deliverables, not scheduled work. The next step decomposes each work package into activities, which then feed schedule development. This satisfies the stem's request for the step immediately following work package identification.

A network diagram maps activity dependencies, showing which tasks must precede others and where parallel paths exist. This directly satisfies the stem's requirement to determine sequence, unlike a Gantt chart (which displays duration and schedule) or a work breakdown diagram (which decomposes scope). It exposes the critical path through the logical order of activities.

Decomposition subdivides project deliverables into progressively smaller, manageable work packages until each can be estimated, scheduled and assigned. It is the specific technique that produces the lowest-level WBS components, resolving the team's difficulty defining adequately sized work packages.

Once the scope baseline is approved, new features cannot be added informally; the request must enter Perform Integrated Change Control, where it is documented, evaluated and approved or rejected. This satisfies the governance constraint protecting the approved baseline.

Bottom-up estimating aggregates detailed estimates prepared for each work package or activity, producing the greatest accuracy and supporting the work breakdown structure. It suits this scenario because the project manager requires high accuracy at work-package level rather than the rough order-of-magnitude figures of analogous or parametric methods.

The estimate at completion (EAC) using BAC / CPI assumes that the current cost performance will continue at the same rate for the remainder of the project. Here, CPI = EV / AC = (40% of $500,000) / $220,000 = $200,000 / $220,000 ≈ 0.909. EAC = $500,000 / 0.909 ≈ $550,000. This forecast is appropriate when the project manager expects the same cost efficiency trend to persist, making it the correct choice for the scenario.

Analogous estimating uses historical data from comparable past projects to derive cost figures, which suits a predictive lifecycle with limited detail. It satisfies the stem's constraint of available historical data from similar projects, delivering a quick top-down estimate, though less accurate than bottom-up or parametric methods.

The WBS decomposes the total project scope into deliverables, so any missing deliverable indicates an incomplete WBS. Reviewing and correcting it ensures every required output is captured before the schedule is baselined, closing the gap at its source rather than patching the schedule.

Any scope addition altering cost must pass through integrated change control before work begins. The change control board evaluates, approves or rejects the request and authorises corresponding baseline updates. Proceeding without approval bypasses governance, regardless of critical path impact.

A CPI below 1.0 means earned value is less than actual cost, so the project is spending more than planned and is over budget. An SPI below 1.0 means earned value lags planned value, so the project is behind schedule.

Assessing the change's effect on scope, schedule, cost, and risk before any decision gives the sponsor and change control board the data needed to approve, reject, or defer. This satisfies the predictive constraint of controlling changes through integrated change control.

The critical path method (CPM) is a schedule network analysis technique used to determine the total duration of a project by identifying the longest path of dependent activities. It calculates early start, early finish, late start, and late finish dates, and identifies the critical path, which determines the shortest possible project duration. In this scenario, the project manager needs to analyze activity sequences and dependencies to find the total duration, making CPM the appropriate technique.

The schedule baseline is an approved version of the schedule model, forming part of the project management plan's baselines along with scope and cost. It provides the fixed reference against which schedule performance is measured and variances tracked.

The work package is the lowest WBS level, where deliverables are decomposed enough to assign, estimate cost and duration, and schedule. It satisfies the stem's estimating and scheduling basis because effort and resources can be quantified per package.

Crashing shortens the critical path by adding resources, directly targeting the schedule constraint the stem identifies. Because only critical path activities govern total project duration, compressing them yields immediate schedule reduction, though it typically increases cost and risk. This satisfies the stem's requirement for a valid compression technique applicable to critical path activities.

PDM establishes logical relationships between activities using nodes and precedence links such as finish-to-start, start-to-start, finish-to-finish and start-to-finish. It directly documents dependencies, satisfying the requirement to identify and record logical relationships among activities during schedule creation.

Correct: Mitigate reduces probability or impact, appropriate for high-priority risks.

Activity attributes are a documented output of Define Activities, recording details such as activity identifiers, codes, dependencies and resource requirements. They extend the activity list and feed subsequent schedule development processes, satisfying the stem's requirement for a genuine Define Activities output.

Scope changes affecting budget and schedule must pass through integrated change control. Submitting a change request to the change control board first ensures the request is formally evaluated, approved, or rejected before any baselines are modified, preserving the project's approved scope, cost, and schedule.

Total float is the schedule buffer a non-critical activity can consume before it delays the project finish. Five days of slip fits within that float, so the end date is unaffected and the critical path is unchanged.

The scope management plan describes how completed deliverables will be formally accepted, often through a verification process. This ensures that deliverables meet requirements before acceptance and helps prevent disputes. It is a key element because it defines the validation and control mechanisms for scope.

Decomposition breaks the project scope into progressively smaller, manageable work packages, ensuring every deliverable is captured at the lowest level. This directly satisfies the stem's requirement that all deliverables be identified, since the WBS is built by subdividing scope until each component is defined and verifiable.

Even when the impact sits inside contingency reserves, a predictive project routes scope changes through integrated change control. The change request must reach the CCB for review and approval before the project manager can adjust the baselines or release reserve funds.

Crashing adds resources to a critical-path task to shorten duration, directly addressing Task X's two-week slip. With zero float and successors Y and Z also critical, any delay propagates to the project end date, so compressing Task X is the targeted recovery action, accepting the added cost crashing entails.

The schedule baseline is an approved version of the schedule model, forming part of the project management plan's schedule management plan outputs. It satisfies the stem's predictive constraint by providing the fixed time reference against which project performance is measured and change requests assessed, rather than a living backlog artefact used in adaptive approaches.

The schedule baseline is an approved version of the schedule model and is a component of the project management plan. It is used to compare actual performance against the plan. For an ERP implementation with multiple phases, the schedule baseline provides the reference for measuring schedule variance and controlling the timeline. It is one of the three baselines included in the plan.

Both indices fall below 1.0, so the project is spending more than planned and progressing slower than planned. CPI of 0.85 means only 85 pence of value is earned per pound spent, while SPI of 0.90 confirms schedule slippage. This directly satisfies the stem's requirement to conclude on cost and schedule status.

The scope baseline is the primary output of Create WBS, comprising the approved scope statement, the WBS itself, and the WBS dictionary. It satisfies the stem's need to identify all required work by formally baselining the decomposed deliverables, which later guide scope verification and control.

A mandatory dependency is one required by the nature of the work or a contractual obligation, such as foundation work physically needing completion before framing. This is inherent to the construction sequence, not a discretionary choice by the team.

The project statement of work is a narrative description of products, services, or results to be delivered by the project. It provides the business need, scope description, and strategic plan. For a project charter, it is a key input because it defines the project's purpose and boundaries, enabling the sponsor to authorize the project formally.

Following change control ensures the defect's scope, schedule and cost impacts are formally assessed before corrective action, satisfying the predictive methodology's constraint that baseline changes require approved change requests. With only 5 days' buffer against 10 days' rework, this evaluation determines whether to escalate, re-baseline or fast-track.

The WBS hierarchically decomposes total project scope into deliverables and work packages, giving the structured framework detailed planning requires. Unlike activity lists or network diagrams, it defines scope boundaries rather than schedules, satisfying the stem's need to break scope into manageable components before estimating, assigning responsibility, or controlling change.

Cost variance is EV minus AC, so $45,000 − $50,000 = −$5,000. The negative sign satisfies the stem's cost performance review: the project has spent more than the value earned, indicating an overrun of $5,000 against the actual cost constraint.

Define Scope produces the detailed project and product description, plus the scope statement, by elaborating on the deliverables and boundaries recorded during initiation. It directly satisfies the stem's demand for a more precise scope during planning, distinguishing it from Collect Requirements, which gathers stakeholder needs rather than documenting the project and product description itself.

Scope changes affecting budget and schedule must pass through integrated change control before any work proceeds. Submitting the request to the change control board documents the impact assessment and obtains formal approval, satisfying the governance requirement that no baselined scope, cost or schedule is altered unapproved.

The work breakdown structure (WBS) is 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. It organizes all work into manageable components, typically down to work packages. This directly matches the sponsor's request for a document that lists all work in a hierarchical decomposition.