CCNA Project Life Cycle Questions

The project charter is the document that formally authorizes the existence of a project and grants the project manager the authority to apply organizational resources to project activities. It is typically issued by the sponsor or a senior manager. Without a charter, the project manager lacks formal authority, and the project may not be recognized as legitimate within the organization.

Phase closure verifies that the phase's deliverables met acceptance criteria and that the phase objective was achieved before the next phase begins. Documenting that acceptance, archiving phase records, and capturing lessons learned preserves organizational knowledge and provides the transition basis for the following phase, while leaving ongoing resources in place for continued work.

In an adaptive life cycle, new requirements are welcomed and added to the product backlog. The product owner prioritizes the backlog, and the team pulls items into iterations based on capacity and value. Introducing the requirement mid-iteration would disrupt the team's focus, so the correct action is to add it to the backlog for future consideration. This maintains the iterative process and allows for reprioritization.

Mitigate lowers the probability or impact of a risk, and cross-training directly reduces the impact of losing a key team member by ensuring others can absorb their duties. This satisfies the stem's constraint of reducing impact without eliminating the risk, unlike avoid, transfer or accept strategies.

Cost variance is EV minus AC: $50,000 − $55,000 = −$5,000. The negative result satisfies the stem's requirement to quantify cost performance, showing the project has overspent by $5,000 against the work completed. PV is irrelevant here, since CV measures actual cost efficiency, not schedule.

The Statement of Work defines the contractor's specific deliverables, scope, schedule and acceptance criteria for Activity X's specialised skill, establishing exactly what work is performed. It is the document that scopes the engagement before contractual terms are formalised.

The project charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity and includes high-level information such as objectives, success criteria, and the named project manager. This matches the scenario's need for formal authorization.

Frequency of communication specifies how often each stakeholder group receives information, satisfying the plan's need to schedule interactions. It complements details such as method, sender, and audience, ensuring stakeholders know when to expect updates rather than only what will be communicated.

Decomposing scope produces the Work Breakdown Structure, a hierarchical deliverable-oriented decomposition of total project scope. The WBS defines all work required, with lower levels representing progressively finer detail, satisfying the scope-decomposition input. It is not a schedule or activity list; those derive later from the WBS during sequencing and estimation.

The project charter formally authorises the project and records high-level objectives and constraints, giving the project manager authority to proceed. These elements define what the project must achieve and the boundaries within which it must operate.

Any change affecting the scope baseline must pass through Integrated Change Control, so the project manager's first action is documenting and submitting a formal change request. Approval by the change control board follows; implementing the change beforehand bypasses governance and invalidates the baseline.

With cost performance expected to continue, EAC equals BAC divided by the cost performance index (CPI). Here CPI is EV/AC = 120,000/130,000 ≈ 0.9231, so EAC = 200,000/0.9231 ≈ $216,667. This satisfies the stem's assumption of ongoing variance, unlike the atypical-variance formula.

In a fixed-price contract the seller agrees to deliver the defined scope for a set price, so any cost overruns from underestimated effort, resources or duration are absorbed by the seller. The buyer pays the agreed amount regardless, placing cost risk squarely on the seller.

An issue is a current condition or event with a realized impact, whereas a risk is a potential future event. The utility strike has already happened, is affecting scope and schedule immediately, and therefore belongs in the issue log. The resulting change request must then go through integrated change control for impact analysis and disposition, because it alters the approved baselines.

Norming is marked by resolving differences and developing cohesion, so members collaborate and share ideas openly. This matches the stem's observation during executing, where relationships stabilise and trust grows. Storming still involves conflict, while performing focuses on task delivery rather than relationship-building.

Multiplying the 20% probability by the $50,000 impact yields $10,000, the expected monetary value of the risk event. EMV quantifies risk exposure by weighting the impact against its likelihood, giving the project manager a defensible figure for contingency reserves and risk prioritisation.

Parametric estimation uses a statistical relationship between historical data and project variables, here cost per function point multiplied by expected function points. This satisfies the stem's constraint of deriving cost from a measurable unit rate, rather than expert judgement or bottom-up aggregation of individual work packages.

The project charter authorises the project and records the high-level budget and schedule, giving stakeholders the approved cost and timeline boundaries. Including these satisfies the charter's purpose of formally establishing scope, funding and time expectations before detailed planning begins.

Once the CCB approves a change, the project manager must ensure affected parties know what is changing, when and why, so they can adjust plans and expectations. Communicating to stakeholders maintains transparency and prevents work being performed against superseded baselines.

Analogous estimating uses historical data from a comparable past project, scaled by parameters such as size, to produce a top-down estimate. This directly satisfies the stem's constraint of adjusting a similar previous project's costs for size differences, making it the appropriate technique here.

Analogous estimating derives duration or cost from historical data of comparable past projects, scaled for known differences. This matches the stem's requirement precisely, distinguishing it from parametric modelling, which uses statistical relationships between variables, and bottom-up estimating, which aggregates component-level detail.

Charter approval formally authorizes the project and transitions it into the Planning process group. The immediate next step is developing the project management plan, which integrates scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder plans, and then securing approval of the scope, schedule, and cost baselines before execution work is released to the team.

A WBS decomposes the total project scope into progressively smaller, manageable deliverables, forming the foundation for estimating, scheduling and assigning responsibility. This hierarchical decomposition directly satisfies the stem's requirement to define the primary purpose, since scope breakdown — not scheduling or resourcing — is the WBS's defining function in project planning.

Analogous estimation uses historical data from a comparable past project as the basis, then adjusts for known differences. This top-down technique suits the scenario because the new project closely resembles the previous one, making prior cost a reliable anchor.

The WBS decomposes total project scope hierarchically, with each descending level giving progressively finer detail of deliverables and work packages. This matches the stem's description of scope decomposition, forming the basis for estimating, scheduling and cost control.

An RFP formally solicits proposals from potential sellers, detailing requirements so vendors respond with solutions and pricing. It fits this procurement phase, unlike an RFI which gathers information, or an IFB which invites bids against fixed specifications.

Finish-to-Start means the successor activity cannot begin until the predecessor activity has completed, which is exactly the constraint described. The other dependency types (Start-to-Start, Finish-to-Finish, Start-to-Finish) permit overlapping or different timing relationships, so they do not match the stem.

Releasing project resources satisfies the closure requirement to disband the team and free allocated staff, equipment and budget once deliverables are accepted. Closure formally ends the project, so releasing resources prevents unnecessary cost accrual and confirms no further work is authorised. This activity belongs to the closing process group, not execution or monitoring.

The charter authorises the project and records its purpose plus high-level scope, giving the sponsor's formal approval and boundaries before detailed planning begins. These elements are foundational inclusions rather than detailed schedules or risk registers.

The forward pass calculates the earliest start and finish dates for each activity by moving from the project start through the network, using activity durations and dependencies. The result identifies the earliest possible project completion date. This is exactly what the project manager needs to determine the earliest finish.

Avoidance eliminates the threat entirely by changing the project scope or approach so the risk no longer exists, which suits high-probability, high-impact risks. Mitigate only reduces impact or likelihood, transfer shifts financial exposure to a third party, and accept retains the risk, so none eliminate the threat.

Storming is the stage where conflict and power struggles surface as members assert individual positions and challenge leadership. Tuckman places this immediately after forming, before norms and roles stabilise. The stem's explicit conflict and power struggles therefore map directly onto storming, not norming or performing.

Execution should not begin until the project management plan is approved by the sponsor or governance authority. Formal approval confirms that scope, schedule, cost, and other baselines are accepted and that the project manager is authorized to proceed. Without this approval, the team could start work against an unapproved plan.

A request for quotation asks vendors to price a specific, already-defined product, satisfying the stem's requirement for a document seeking price only. It differs from an RFP, which solicits solution proposals, and an RFI, which gathers capability information.

Archiving project documents preserves the project's records for audit, compliance and future reference, satisfying the closing requirement to finalise and retain artefacts. Unlike ongoing execution activities, archival formally transfers knowledge out of the active project and into organisational repositories, confirming the project is complete and releasing the team from further obligations.

A fixed-price contract sets a total price of $100,000 agreed upfront, so the vendor bears cost overruns and the buyer pays that sum regardless of actual costs incurred. This matches the stem's fixed price independent of real expenditure.

Correct: Avoid involves eliminating the risk.

Conducting a lessons learned session is a key activity in the Closing phase. It captures what went well, what did not, and recommendations for future projects. Since the product has been accepted, the project manager should gather the team and stakeholders to document lessons learned before releasing resources. This helps organizational process assets and improves future project performance.