CCNA Project Life Cycle Questions

Regular email updates suit low-power, high-interest stakeholders because they need frequent, digestible progress information without demanding intensive engagement. Email delivers scheduled, asynchronous communication that keeps this group informed and satisfied, matching their high interest while respecting their limited influence over project decisions. More interactive methods would over-serve stakeholders who cannot affect outcomes.

CV subtracts actual cost from earned value; a negative result means costs exceed the value earned, so the project is over budget. It gives the over-budget condition as an absolute currency amount, complementing CPI's ratio-based view of the same cost performance.

The twelve-week permit lead time is a mandatory external dependency and a schedule constraint. The project manager must record it, adjust the network logic so site preparation starts after permit issuance, and then assess the resulting impact on the critical path and project finish date before deciding whether further action is needed.

Monte Carlo simulation runs repeated random sampling across probability distributions for cost and schedule variables, producing a range of possible outcomes with confidence levels. This iterative numerical modelling satisfies the quantitative risk analysis requirement to assess combined risk exposure.

Interactive communication involves real-time, multidirectional exchange of information between two or more people. Daily stand-up meetings are interactive because team members actively share updates, ask questions, and collaborate in real time. This method is most effective for ensuring shared understanding and immediate feedback among participants.

The project charter is the document 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 typically issued by the sponsor or initiating entity. In a predictive life cycle, the charter is created during Initiating and serves as the foundation for planning. This matches the sponsor's request exactly.

Norming is the stage where conflict resolution begins and shared norms are established, satisfying the stem's requirement. Members shift from competing to cooperating, agreeing on working methods and values. This contrasts with storming, where conflict peaks, and performing, where productivity depends on those norms already being settled.

Cost Variance (CV) measures cost efficiency by subtracting actual cost from earned value (CV = EV − AC). A positive CV indicates the project is under budget; a negative CV signals overspending. This directly satisfies the stem's requirement to assess cost efficiency, unlike schedule-based metrics such as SV or SPI.

The critical path method (CPM) is used to determine the longest path through a network diagram, which represents the shortest possible project duration. It helps identify critical activities that cannot be delayed without delaying the project. In this scenario, the project manager needs to find the longest path, so CPM is the correct technique. CPM also calculates float for non-critical activities.

A hybrid life cycle deliberately blends a predictive approach for fixed external milestones with iterative or incremental delivery for evolving requirements. This preserves the legally mandated dates while allowing the team to refine regulatory interpretations in short cycles, matching exactly the sponsor's request without abandoning the compliance constraints.

Specifying the method or technology for communication ensures each stakeholder receives information through an appropriate channel, such as email, meetings or a shared portal. This directly satisfies the Executing-phase need for effective stakeholder communication by defining how messages are actually transmitted, rather than leaving delivery to chance.

Once the CCB approves a change, the project manager must update the project management plan and associated baselines, such as scope, schedule, and cost. This ensures that the approved change is formally integrated and that future performance is measured against the revised baselines. Without this update, the project team would continue working with outdated plans, leading to misalignment and inaccurate reporting.

Parametric estimation applies the same unit-rate model to any quantifiable project variable, so the 100 square metres per day rate can drive either duration or cost totals. This satisfies the stem's requirement that the technique is not limited to scheduling alone.

Initiating is where the project charter is authorised and the project manager is formally assigned. This phase defines the project's high-level scope and secures organisational approval before planning begins, directly satisfying the stem's requirement for charter creation and PM appointment.

A fixed-price contract fixes the amount paid regardless of actual costs, so any overrun is absorbed by the seller. This transfers maximum cost risk to the seller, unlike cost-reimbursable or time-and-materials arrangements where the buyer bears overruns.

CPI above 1.0 means earned value exceeds actual cost, so the project is under budget; SPI below 1.0 means earned value trails planned value, so it is behind schedule. Both indices together satisfy the stem's stated values.

After final product acceptance and transition, the project manager should archive project documents and release resources. Archiving preserves historical data for future projects and audits, while releasing resources allows team members to return to functional or other assignments. These are key activities in the Close Project or Phase process. This step completes the project formally and ensures organizational assets are updated.

Avoidance eliminates the risk entirely by removing its cause. Changing project scope so the risky activity no longer exists removes the threat rather than reducing, transferring or accepting it, which is precisely what an avoid response requires.

The Initiating phase produces the project charter, which formally authorises the project and names the project manager. This satisfies the stem's requirement that both the charter's creation and the manager's formal assignment occur in the same phase, before planning begins.

The project charter is produced during Initiating, where the project is formally authorised and the project manager is assigned. Approval of the charter marks the phase boundary, giving the project its mandate before planning begins.

Norming is the stage where the team resolves earlier conflicts and establishes agreed norms, cohesion and working relationships. This directly matches the stem's description of conflict resolution and norm establishment, distinguishing it from storming, which precedes it, and performing, which follows.

Expected monetary value multiplies probability by impact: 0.3 × $50,000 = $15,000. This quantifies the risk's average financial exposure, letting the project manager compare it against other risks in the matrix and prioritise responses accordingly.

Decomposing scope into a hierarchy produces the work breakdown structure, whose lowest level is the work package. The WBS organises deliverables, and work packages are the smallest components assigned and estimated, directly satisfying the stem's requirement for the lowest level of decomposition.

Analogous estimating draws on actual costs from comparable past projects, using top-down comparison to produce a rough order-of-magnitude figure. It satisfies the stem's requirement for historical data from similar projects, and suits early planning when detailed scope is unavailable and speed matters more than precision.

Storming is marked by conflict as members assert opinions and resist the emerging structure. Challenging each other's ideas reflects this friction, distinguishing it from the politeness of forming or the cohesion of norming and performing.

Lessons learned capture what went well, what did not, and recommendations for future projects. CompTIA Project+ places this activity in the Closing phase, after deliverable acceptance and before final archive. It converts tacit team experience into organizational process assets so future projects avoid repeated mistakes. Without it, the project closes administratively but the organization loses the knowledge gained.

Mitigation reduces probability or impact.

Stakeholders rated high on both power and interest demand the closest engagement because they can significantly affect project outcomes and care deeply about results. The manage-closely quadrant therefore receives frequent, detailed communication and active involvement to sustain their support.

After submitting a change request to the change control board, the project manager must wait for their decision. If approved, the project manager then updates the project management plan, including the scope, schedule, and cost baselines as needed, and communicates the change to stakeholders. This ensures the change is properly integrated and documented.

A hybrid approach keeps the predictive schedule and deadline while adding iterative reviews to absorb the new regulation. Evaluating impact first ensures the change is understood before altering the baseline, and controlled change keeps governance intact. CompTIA Project+ recognizes hybrid life cycles as appropriate when a fixed deadline coexists with evolving requirements, allowing adaptation without sacrificing regulatory documentation or the submission date.

A change control board is the formal governance body that reviews documented change requests and authorises or declines them, weighing the analysed impact on scope, schedule and cost. This satisfies the stem's requirement for the typical approval authority once the project manager has completed impact analysis.

Storming is the stage where team members challenge the project manager's authority and conflict emerges over roles and direction. This directly matches the stem's reported conflicts and authority questioning, distinguishing it from forming (polite orientation), norming (cohesion established) and performing (focus on delivery).

High power combined with high interest places the stakeholder in the grid's manage-closely quadrant, requiring active, regular engagement. Their ability to influence the project and their investment in outcomes mean their concerns must be addressed continuously to avoid disruption.

Decomposition is the technique that splits WBS deliverables into progressively smaller, manageable work packages, satisfying the stem's requirement to break deliverables down during planning. It defines the lowest-level components that can be estimated, scheduled and assigned, which is precisely what the project manager needs before basing cost and duration estimates on them.

Expected monetary value multiplies probability by impact: 0.30 × $50,000 = $15,000. This quantifies the risk's average financial exposure, letting the project manager weigh it against contingency reserves or response costs during quantitative risk analysis.

Analogous estimation uses historical cost data from comparable completed projects to derive the new estimate. With three similar past software projects available, this top-down technique is quick and appropriate, especially when detailed information is limited during early estimating.

Stakeholder communication needs must be identified first because they determine who receives information, what content, which channel and frequency. Every later element of the communication plan — the matrix, methods and schedule — derives from this analysis, so establishing needs before selecting tools satisfies the plan's foundational dependency.

An SPI of 1.2 exceeds 1.0, meaning earned value outpaces planned value, so the project is ahead of schedule. This satisfies the schedule constraint directly, independent of the CPI of 0.8, which indicates cost overrun. SPI measures schedule efficiency only, so the ahead-of-schedule conclusion holds.

Obtaining formal acceptance from the sponsor satisfies the closing requirement to confirm deliverables meet agreed criteria before releasing resources. This sign-off transfers ownership to the business and authorises final payment, providing the documented closure evidence that project closing demands.

Using the cost performance index (CPI) to extrapolate future spending satisfies the stem's constraint that the project continues at the same cost efficiency. CPI is EV ÷ AC = 60,000 ÷ 80,000 = 0.75, so EAC = BAC ÷ CPI = 200,000 ÷ 0.75 = $266,667.

The risk register is the artefact that logs each identified risk alongside its probability, impact and agreed response strategy. It satisfies the stem directly, unlike a risk management plan, which describes approach rather than listing individual risks.

Communication needs establish what information each stakeholder requires, forming the content dimension of the communication plan. Addressing this per stakeholder ensures relevant, timely updates and satisfies the stem's requirement to consider factors tailored to each individual or group.

Before approving, rejecting or deferring the request, the project manager must assess how it affects scope, schedule, cost, risk and quality. Impact analysis produces the evidence the change control board needs, so it precedes any decision or baseline update.

High-power, low-interest stakeholders require sufficient engagement to prevent them from becoming blockers, yet without overwhelming them with operational detail. Periodic high-level updates satisfy this by maintaining awareness and confidence while conserving their attention. This matches the power/interest grid's "keep satisfied" quadrant, which prioritises concise, strategic communication over frequent granular reporting.

CPI is EV divided by AC, giving 50,000/60,000 = 0.83. Any value below 1.0 means earned value trails actual cost, so the project has spent more than the work delivered is worth — over budget.

A work breakdown structure decomposes scope into deliverables, not activities, so each element must represent a tangible output the project produces. This satisfies the best-practice constraint that WBS nodes define what will be delivered, enabling accurate scope, cost and acceptance criteria assignment.

Dividing earned value by actual cost ($40,000 ÷ $45,000) yields 0.89, satisfying the stem's request for the cost performance index. A CPI below 1.0 signals the project is over budget for the work completed, since each dollar spent returns only 89 cents of earned value.

Once the CCB approves a change, the project manager proceeds with implementation and formally updates the affected baselines to reflect the approved scope, schedule or cost. Recording the revised baselines preserves the integrity of future variance analysis and performance measurement against the newly authorised plan.

Keeping these stakeholders satisfied directly addresses their high power and low interest by maintaining engagement without overloading them with detail. This prevents them from becoming disengaged and later using their authority to block or derail the project, which is the specific risk the power/interest grid's "keep satisfied" quadrant is designed to mitigate.

CCB approval authorises the change, so the next action is executing the approved work and revising the affected project baselines—scope, schedule and cost—to reflect it. Baselines must be updated so subsequent performance measurement and variance analysis compare against the approved revised plan.

Qualitative risk analysis involves assessing the probability and impact of each identified risk, often using a probability and impact matrix, to assign a priority level. This helps the project manager focus on high-priority risks given limited budget and schedule. The risk matrix provides a structured, consistent way to rank risks for response planning without requiring detailed quantitative data.

By definition, activities on the critical path have zero total float; any delay directly extends the project duration. The durations of 5, 3 and 4 days sum to the critical path length, and none of these activities can slip without delaying completion.

EMV multiplies probability by monetary impact: 0.20 × $50,000 = $10,000. This quantifies the risk's expected cost exposure, satisfying the calculation the stem requests and providing a comparable figure for prioritisation against other identified risks.

All changes, including mandatory regulatory ones, should be documented in a change request and analyzed for impact before approval. This lets the change control board or sponsor decide how to proceed with full knowledge of effects on baselines and resources. It preserves the integrity of the plan while ensuring compliance is addressed through the proper channel.

With CPI calculated as EV divided by AC, $120,000 ÷ $110,000 gives 1.09, indicating the project is under budget for every dollar spent. This satisfies the stem's requirement to derive cost efficiency from the given earned value, planned value and actual cost figures.

Lessons learned captures what worked and what did not, plus recommendations, so subsequent projects can reuse successful approaches and avoid repeating mistakes. That forward-looking knowledge transfer is its primary purpose during closing, not apportioning blame or documenting the current project's budget.

A phase-end review validates that the phase achieved its objectives and satisfies the defined exit criteria before the next phase is authorized. This gives the sponsor evidence-based assurance and a formal decision point for continued funding. It aligns with the predictive life cycle's use of phase gates to control risk and investment progressively.

Analogous estimation derives cost from a comparable historical project, adjusting for size and complexity differences. Using the previous $500,000 project as the basis and scaling to $600,000 matches this top-down technique, which relies on expert judgement rather than detailed bottom-up breakdowns.

The schedule baseline is an approved version of the schedule model and is a key component of the project management plan. It is used to measure project performance and is part of the overall project management plan. It provides a fixed reference point for comparing actual progress against planned progress.

CPI equals EV divided by AC, giving 50,000/60,000 = 0.83. A value below 1.0 means each dollar spent delivers only 83 cents of earned value, so the project is running over budget against the stem's figures.

CPI is calculated as EV ÷ AC, giving $50,000 ÷ $55,000 = 0.91. A CPI below 1.0 means each dollar spent delivers less earned value than planned, so the project is over budget. This satisfies the stem's request for both the index and its cost implication.

The charter formally authorizes the project and names the project manager, specifying the level of authority to apply resources to project activities. Without documented authority, the project manager cannot commit organizational resources effectively. This element is essential for the project manager to lead and make decisions on behalf of the sponsor.

High-level scope defines what the project will and will not deliver, establishing its boundaries. Including it in the charter authorises the project manager to proceed while clarifying what falls inside and outside the project's remit, which is exactly the boundary-defining element requested.

Total float equals the difference between the critical path duration and the activity's longest path. Both paths total nine days and both have zero float, so Path A is also critical; any activity on it therefore has zero days of scheduling flexibility.

PERT weights the most likely estimate four times: (5 + 4×8 + 13) ÷ 6 = 50 ÷ 6 = 8.33 days. This expected duration replaces the single-point estimate for activity X on the critical path.

Activity B starts after A finishes, so B begins on day 4 and runs to day 8. The start-to-start relationship with a 2-day lag lets C begin two days after B starts: day 4 plus 2 equals day 6. Day 6 is therefore the earliest start.

Even for a cancelled project, the project manager must first verify which deliverables were completed and accepted, and document the current state of work. This provides the factual basis for closing activities, including final reporting, lessons learned, and resource release. Without this verification, the project manager cannot accurately report what was delivered or justify the closure to the sponsor and stakeholders.

Even a cancelled project must undergo administrative closure to finalize contracts, release team members, document lessons learned, and archive records. This produces the organizational process assets and historical information the performing organization needs, and it is the only activity that formally ends the project regardless of whether deliverables were completed.

Multiplying the 30% probability by the $50,000 impact yields an expected monetary value of $15,000, quantifying the risk's average financial exposure for the project budget. This directly satisfies the stem's requirement to calculate EMV from the given probability and impact figures.

During Storming, differing working styles and opinions surface, producing disagreements and competition among members. This interpersonal conflict is the defining trait the stem asks for, separating Storming from the collaboration of Norming and the productivity of Performing.

Archiving project documents preserves the historical record, lessons learned and audit evidence after closure. It is a recognised closing activity because it secures artefacts for future reference and compliance, satisfying the stem's requirement for activities typically performed during project closing.

The project manager should first address the team directly to understand the root cause and reinforce expectations. A meeting allows for open communication, clarification of standards, and identification of any training gaps. This aligns with the Executing phase's focus on team development and quality assurance. If the issue persists, more formal actions like process adjustments or performance management can follow.

Formal acceptance is the closing process where the customer or sponsor signs off that deliverables satisfy documented requirements, converting provisional output into accepted product. It directly satisfies the stem's demand for obtaining formal acceptance during project closing.

Closing is the process group where the project manager obtains formal sign-off that deliverables meet acceptance criteria, then archives project documentation and releases resources. It directly satisfies the stem's requirement for formal acceptance and document archiving, which no other process group performs.

A constraint is a limiting factor that restricts the project team's options, such as a fixed budget, a hard deadline, or a mandated change freeze. The production change freeze is an externally imposed restriction on when migration activities can occur, so it directly limits scheduling options. CompTIA Project+ treats such imposed limitations as constraints that must be documented and factored into the schedule and risk planning.