CCNA Project Management Concepts Questions

Archiving records and capturing lessons learned makes the project's knowledge reusable, which is precisely what the sponsor wants. Lessons learned should include what went well, what did not, and recommendations for similar future efforts, and they belong in the organizational process assets so other project managers can retrieve them. This closes the knowledge loop rather than leaving experience trapped with the departing team.

Communicating project status to stakeholders is a core project manager responsibility, satisfying the stem's requirement for direct stakeholder engagement. The project manager owns the communication plan, translating schedule, budget and risk data into status reports, and acts as the primary liaison between the delivery team and sponsors, ensuring transparency throughout the project lifecycle.

Scope creep adds unapproved features, directly expanding the agreed deliverables and work content. The scope constraint, defined by the approved scope baseline, is therefore the constraint most immediately impacted, since the change alters what the project must deliver.

The project charter is the document issued by the sponsor or initiating authority that formally authorizes the project and names the project manager with the authority to apply organizational resources. It is the recognized output of the initiation phase and the basis on which the project manager can legitimately commit resources and begin planning.

Additional features fall outside the agreed deliverables, directly expanding the project scope. With budget and deadline fixed, this unplanned work creates a triple-constraint conflict: the new requirements cannot be absorbed without either increasing cost, extending the schedule, or renegotiating what was originally committed.

In a functional organisation, authority rests with the functional manager, who controls resources, budgets and team assignments. The project manager coordinates across departments with little formal power, often acting as a coordinator or expediter rather than a true leader. This directly satisfies the stem's constraint of least project manager authority.

A balanced matrix matches the stem: the project manager holds moderate authority while functional managers retain control of resources, so team members report to both. Weak matrices give the project manager limited authority, whereas strong matrices grant high authority and dedicated resources.

Routing the request through formal change control prevents unapproved features entering the baseline, ensuring the change is assessed, documented and authorised before any work proceeds. This is the mechanism that stops scope creep rather than merely reacting to it.

NPV discounts all future cash flows to present value, so the highest NPV signals the greatest absolute value creation over the project's full life. This justifies accepting the long payback period, since the stem's constraint is long-term profitability rather than speed of recovery.

Payback period divides initial investment by annual cash flow: Project A recovers its $100,000 in roughly 3.33 years, while Project B recovers $50,000 in 2.5 years. Project B's shorter payback satisfies the selection criterion, returning capital sooner.

Frequent backlog reprioritisation driven by shifting customer needs demonstrates agile's capacity to adapt through short iterative cycles, absorbing change rather than freezing scope. This directly satisfies the stem's constraint of continuously evolving requirements, which predictive methodologies resist.

The project charter is the document issued by the sponsor or initiating authority that formally authorizes the project and names the project manager with the authority to apply organizational resources. It also records high-level requirements, success criteria, and the initial budget and milestone summary, which is why it is the artifact a new project manager reads first during initiation.

Scope creep is uncontrolled expansion of project scope, typically through unapproved additions. Adding stakeholder-requested features without formal change control bypasses the integrated change control process, which is precisely the definition of scope creep in the stem.

Payback period calculates how many periods are needed for cumulative cash inflows to equal the initial outlay, directly answering the stem's criterion of time to recover investment. It ignores cash flows after the break-even point, unlike net present value or internal rate of return.

IRR discounts all project cash flows to the rate at which net present value equals zero, so it explicitly compounds cash flows over time. That discounting mechanism is what satisfies the stem's requirement for a method incorporating the time value of money.

Predictive methodology plans the full scope upfront and executes sequential phases, suiting stable requirements and a fixed budget. Waterfall's linear structure matches the team's stated preference for clear phases, satisfying the stem's constraint of unchanging requirements.

A portfolio groups projects, programmes and operations that are not necessarily related but are collectively managed to achieve strategic organisational objectives. This matches the stem's collection of unrelated projects all pursuing the shared goal of market expansion.

When a stakeholder requests work outside the approved baseline, the disciplined response is to route it through integrated change control so scope, schedule, cost, and risk impacts are analyzed before any commitment. This protects the fixed regulatory deadline and budget ceiling while giving the sponsor a documented decision point. Only after approval should the portal be planned into the baselines.

The project sponsor owns the business case, secures funding and resources, and holds authority above the project manager's level. Escalating issues beyond the project manager's remit and providing budget align exactly with the sponsor's defined governance responsibilities.

Cost variance is earned value minus actual cost. At 50% completion, earned value is $50,000, while actual cost is $60,000, giving $50,000 − $60,000 = −$10,000. The negative result confirms the project is over budget at the six-month mark.

The organisation's stated policy selects the project with the highest net present value, so Project A's $50,000 NPV outranks Project B's $40,000. Payback period is a secondary liquidity measure and does not override the mandated NPV criterion.

The sponsor is currently supportive but distracted, and the engagement assessment compares current engagement with the desired level. A focused conversation re-establishes the partnership, surfaces the specific decisions the project needs, and moves the sponsor back toward leading, which is the appropriate corrective action for a stakeholder whose support is drifting.

Distributed teams suffer when decisions are made verbally without a durable record. A decision log captures what was decided, by whom, when, and the rationale, while a defined escalation path prevents unresolved items from silently reopening. Written confirmation within a fixed window gives absent members a chance to raise objections before the decision is treated as final, reducing reversals and rework.

Gold plating is the team voluntarily adding unrequested features beyond the agreed scope, consuming budget and schedule without customer approval. This matches the stem exactly: extra functionality was delivered that the customer never requested, breaching scope boundaries.

The sponsor champions the project, secures funding and resources, and is accountable for realizing the business case. In most governance models the sponsor, or a change control board the sponsor chairs, approves changes to the approved budget baseline. Identifying the sponsor therefore answers the question accurately and gives the project manager the correct escalation path for a funding decision.

Testing is a project activity performed within the execution and monitoring phases, not a life-cycle phase itself. The typical life cycle comprises initiation, planning, execution, monitoring and controlling, and closure, so testing falls outside that structure.

Resource levelling adjusts start and finish dates within slack to smooth peaks in demand, reducing the day-to-day contention between functional departments and the project. It addresses the matrix constraint where the same specialists are pulled by competing priorities, easing the conflicts described in the stem.

Releasing project resources — team members, equipment and budget — happens during closing once deliverables are accepted and no further work is authorised. It confirms the project is formally wound down rather than continuing to consume organisational capacity.

The resource management plan describes how project resources are identified, acquired, and managed, and includes team development approaches, recognition and training plans, performance assessment methods, and criteria for releasing team members. Since the sponsor is asking about acquisition, training, appraisal, and release of people, this plan is the correct place to record those decisions.

Scope changes alter the approved baseline, so only the steering committee holds the authority to authorise them. This governance body owns the project charter and budget, satisfying the stem's need for the group accountable for approving modifications to project scope.

A project is a temporary endeavour undertaken to create a unique product, service, or result, which directly satisfies the stem's requirement for a defining characteristic. This uniqueness distinguishes projects from ongoing operations, which produce repetitive outputs. The constraint of delivering something novel within a defined scope and timeframe is met precisely by this attribute.

A stakeholder with high power and low interest falls into the keep satisfied quadrant; the goal is to deliver enough relevant information to prevent surprises or opposition without demanding heavy involvement. Because this department head controls funding, ignoring them risks late resistance, while overloading them with detail may be counterproductive, so targeted, concise engagement is appropriate.

A hybrid life cycle combines predictive and adaptive phases within one project, matching the stem's split: predictive requirements gathering and design, then iterative sprints for development. It satisfies the constraint that both approaches coexist sequentially, rather than the whole project following a single methodology.

Gold plating is adding unrequested features beyond scope to improve a deliverable, consuming budget and time without customer approval. This precisely matches the stem's description of extra unrequested work, unlike scope creep which stems from stakeholder requests.

In a strong matrix organization, functional managers control the people and the project manager must negotiate for their time. Presenting the approved project charter, which documents the project manager's authority, alongside the non-negotiable regulatory deadline gives the functional manager a clear basis to prioritize the assignment. This is the recognized path to securing scarce specialized resources in a matrix environment.

Agile matches the stem's evolving requirements through iterative, time-boxed sprints and a prioritised backlog that accommodates change. Daily stand-ups provide continuous coordination, unlike waterfall's sequential phases or PRINCE2's stage-gate governance. This satisfies the constraint that requirements evolve throughout the project rather than being fixed upfront.

NPV discounts all future cash inflows and outflows to present value, then subtracts the initial investment. A positive NPV signals the project adds financial value, making it a standard discounted cash-flow method for comparing and selecting candidate projects during project selection.

Communicating project status to stakeholders is a core project manager duty, satisfying the stem's requirement for primary responsibilities. The project manager owns performance reporting, translating schedule, budget and risk data into stakeholder-appropriate updates. This differs from the sponsor, who authorises and funds, and the PMO, which defines standards. Regular status communication sustains alignment and informed decision-making.

Scope creep is managed through integrated change control, so the project manager must first assess how the extra features affect scope, schedule, cost and risk, then route a formal change request to the change control board for approval or rejection before any work proceeds.

When scope, time, and cost are all fixed and infeasible together, the project manager cannot unilaterally break a constraint. Escalating to the sponsor, who controls budget and can authorize trade-offs, is the appropriate action to obtain a decision on which constraint to adjust or what additional resources to provide.

An incremental life cycle delivers the solution in successive functional increments, so a working subset of high-priority network upgrades can be released early while later increments follow as funding permits. This matches the sponsor's intent to realize value within four months and to gate remaining work on budget availability. Each increment adds usable functionality to the same solution rather than producing separate unrelated products.

A CPI of 0.8 means every £1 spent delivers only £0.80 of earned value, so the project is over budget. An SPI of 1.1 means earned value exceeds planned value, so work is ahead of schedule. This option satisfies both constraints simultaneously.

Cost is one of the triple constraints, alongside scope and time, limiting what a project can deliver. Budget availability directly restricts options throughout planning and execution, satisfying the stem's requirement for a genuine project constraint.

A team charter captures the operating agreement for the group: how members communicate, make decisions, resolve disagreements, and behave toward one another. On a multi-department team with a history of friction, making these expectations explicit and agreed-upon up front reduces ambiguity that fuels conflict. It also clarifies the project manager's authority relative to functional managers, which is essential in a shared-resource environment.

The project sponsor owns the business case and executive authority, so they secure and assign resources and escalate or clear obstacles exceeding the project manager's authority. This matches the stem's requirement for someone providing resources and removing obstacles beyond the PM's control.

The project charter formally authorizes the existence of the project and gives the project manager the authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity and names the project manager. This matches the sponsor's request for the document that authorizes the project and assigns authority.

The project charter should contain clear success criteria and a high-level budget to authorize and bound the project. When these are vague, the project manager should work with the sponsor to refine and update the charter before detailed planning, ensuring the project has measurable objectives and an approved funding envelope. This prevents planning on unstable assumptions and aligns all stakeholders on what success looks like.

In a matrix organisation, functional managers retain line authority over shared staff, so the project manager negotiates resource availability rather than directing it. Authority is therefore limited and shared, matching the stem's description of resources split with functional managers.

The scope statement documents the project's deliverables, measurable product and project objectives, the boundaries of the work (what is in and out of scope), and the acceptance criteria the customer will apply. That matches every element the PM must record before breaking work into a schedule, making it the correct next artifact to produce for the portal replacement.

An announced external event that may delay the critical path is an identified risk with a known trigger window, so it belongs in the risk register with probability, impact, and a response plan. The PM can plan mitigation such as resequencing work, renting temporary power, or negotiating an alternate window. Updating the risk register keeps the analysis visible and drives proactive response rather than reactive firefighting.

Iterative approaches deliberately repeat cycles of build and feedback so that requirements are discovered and refined rather than fixed upfront. The autonomous vehicle scenario, with unproven technology and a customer wanting frequent demonstrations, aligns precisely: each prototype teaches the team something and shapes the next cycle, reducing uncertainty progressively.

The project sponsor authorises the project and supplies resources and funding, directly satisfying the stem's requirement to secure approval and champion the initiative. Unlike the project manager, who executes within delegated authority, the sponsor owns the business case and holds budgetary control, making them the role accountable for greenlighting and resourcing the mobile application development.

Risk identification and creation of the risk management plan occur during planning, where the project manager defines how risks will be identified, analysed, and responded to before execution begins. This satisfies the stem's requirement for the phase producing the risk management plan.

The traditional triple constraint comprises scope, time and cost. Time is one of those three axes, so it satisfies the stem's requirement to identify a triple-constraint component, distinct from quality, which sits outside the classic trio.

Hybrid suits a fixed deadline with evolving requirements by fixing the schedule and budget baseline predictively while iterating requirements delivery. This satisfies both stem constraints: the deadline is protected through predictive planning, and requirement volatility is absorbed by iterative elaboration rather than upfront specification.

A published regulation that invalidates a design assumption creates a change that must be evaluated for scope, schedule, cost, and compliance impact. Raising a change request and routing it through integrated change control preserves traceability, produces a documented decision, and ensures baselines are only updated after approval. This satisfies the project manager's goal of accuracy plus auditability.

Uniqueness is a defining project characteristic: every project creates a distinct product, service, or result, differentiating it from routine operations. This progressive elaboration of a novel deliverable satisfies the stem's requirement for a key project characteristic.

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 issued by the sponsor or another authority outside the project and typically records the high-level scope, objectives, and identified stakeholders. Because leadership has already assigned a sponsor and the request is for formal authorization and resource authority, this is the document the project manager must produce.

A divestiture that eliminates the business need for part of the scope and moves the deadline is a significant change to the project's baseline. The disciplined first response is to document and submit a change request describing the scope reduction and schedule compression, obtain approval, and only then update the affected baselines and subsidiary plans. This preserves traceability between the changed business need and the revised project documents.

Adding unplanned features expands scope beyond the agreed baseline, consuming schedule float and pushing delivery dates. Even with remaining budget, the team's capacity is finite, so extra work risks late completion and compresses testing time.

In a weak matrix, functional managers retain authority over assignments and priorities, so the project manager lacks formal power to commandeer staff. This directly produces limited influence over resource allocation and prioritisation, the defining constraint of the stem.

NPV discounts future cash flows to present value, giving a monetary figure for comparing initiatives. The stem asks for financial selection methods, and NPV satisfies that by quantifying profitability in currency terms, unlike scoring models or benefit measurement approaches that rank projects non-financially.

A defined change control process is essential because it specifies the path a change request takes, who evaluates it, and who has authority to approve or reject it. Without it, changes may be applied informally, which erodes the approved baseline and makes it impossible to show the sponsor how scope, schedule, and cost remain controlled.

A schedule variance triggered by an external vendor is exactly what the integrated change control process exists for. Because the delay affects an approved baseline that the project manager cannot alter unilaterally, the change request formally captures the impact, gives the CCB the information it needs to approve, reject, or defer, and keeps the baseline authoritative until a decision is recorded.

An adaptive life cycle, such as agile, is designed for high uncertainty and frequent delivery of working product. It welcomes changing requirements and uses short iterations to demonstrate value to the sponsor. This aligns with the fixed deadline, distributed team, and the sponsor's desire for frequent demonstrations.

NPV discounts all future cash inflows and outflows to present value, so projects can be ranked by absolute financial return. This satisfies the stem's requirement for a valid financial selection method, unlike scoring or weighted matrices, which are non-financial.

Stakeholders who are both highly interested and highly influential require close management, meaning active, two-way engagement and early involvement in decisions. For a regulator that can stop the project, this means proactive permit coordination and regular interaction, which is the most effective way to keep the stakeholder satisfied and protect the schedule.

Gold plating is delivering extra functionality beyond documented requirements. The developer adds a 'nice to have' feature absent from the requirements baseline, expanding scope without authorisation, which risks unplanned effort, testing burden and schedule slippage.

In a functional organisation, the functional manager controls resources and can reassign staff at will. The project manager holds little formal authority, so securing and retaining team members against competing operational demands becomes the dominant challenge described in the stem.

Self-organising teams, short iterations, frequent customer feedback and Kanban visualisation all sit within agile delivery, where scope emerges through iteration rather than being fixed upfront. This satisfies the stem's executing-phase mobile app scenario, confirming an adaptive, iterative methodology rather than a predictive one.

Implementing risk responses means executing the agreed response plans for identified risks, such as expediting a delivery at added cost or substituting a component. The PM is actively working to reduce the threat to the critical path, which is exactly this process, and the resulting cost or schedule effects would then be routed through integrated change control if baselines must change.

Predictive methodology suits this project because stable, well-understood requirements allow full scope definition upfront, enabling sequential phase planning, detailed baselines and formal change control. Its plan-driven structure minimises rework where change is unlikely, unlike adaptive approaches that assume evolving requirements and iterative discovery.

Mitigation reduces the probability or impact of a threat. By notifying the sponsor, sourcing alternate vendors, and reworking the schedule to absorb a potential slip, the manager is lowering the impact of the supplier delay while the risk is still live, which is the defining behavior of mitigation.

Agile uses iterative, incremental delivery with short feedback cycles, accommodating evolving requirements and frequent change. The stem specifies unclear requirements and expected frequent changes, and Agile satisfies that constraint by embracing change through backlog refinement rather than locking scope upfront as predictive methodologies require.

Predictive methodology suits this scenario because stable, well-defined requirements allow sequential phase planning with baselined scope, schedule and cost. Its phase-gate controls manage dependencies and approvals typical of construction, satisfying the stem's constraint that requirements are unlikely to change, unlike adaptive approaches that expect evolving scope.