CCNA Pkp Tools Documentation Questions

A burndown chart plots remaining work against time across the sprint, directly showing whether the team's current pace will reach zero by the sprint's end. This satisfies the stem's requirement to track remaining work and assess whether all committed stories will be completed on schedule.

Transferring risk involves shifting the financial impact of a risk to a third party, often through insurance, warranties, or contracts. By purchasing insurance, the project manager transfers the potential $80,000 loss to the insurer in exchange for a premium. This strategy is appropriate when the risk is significant but cannot be easily avoided or mitigated.

A Gantt chart displays tasks as horizontal bars along a timeline, shows dependencies between tasks, and highlights the critical path. It is ideal for tracking progress, identifying schedule risks, and communicating the project schedule to stakeholders. This tool directly supports the project manager's need to visualize task sequences and critical activities.

Benchmarking involves comparing project practices, processes, and products to those of similar projects or industry standards to identify best practices and generate ideas for improvement. It is a tool used in plan quality management to establish quality objectives and standards. In this scenario, it helps the project manager set realistic and competitive quality goals.

Cycle time measures the time it takes for a work item to move through the workflow from start to finish. By limiting WIP, the team aims to reduce cycle time and improve flow. Monitoring cycle time helps the project manager assess whether the WIP limit is effectively reducing delays and bottlenecks, leading to faster delivery.

Eight consecutive points on one side of the mean breach a run rule, signalling non-random, special cause variation even though every point sits inside the control limits. This satisfies the stem's scenario, where limit compliance alone would wrongly suggest a stable process.

A Gantt chart renders tasks as horizontal bars against a calendar timeline, draws dependency links between them, and can shade or flag critical path activities. It uniquely satisfies all three stem requirements: timeline bars, dependencies and critical path highlighting.

The risk response plan documents the agreed actions to be taken if a risk occurs, including contingency and fallback steps. For a high-probability supplier failure, this component would contain the specific mitigation or contingency actions. It is the correct place for the project manager to document and later execute the response actions described in the scenario.

A Pareto chart ranks defect categories by frequency in descending bars with a cumulative line, exposing the 80/20 concentration. This lets the project manager visually justify focusing corrective action on the few defect types causing most complaints, exactly as the audit data shows.

In a RACI matrix, A denotes Accountable: the single person who ultimately answers for the task's completion and approves the work, distinct from those merely Responsible for performing it. This satisfies the stem's requirement for the ultimately accountable role.

A Pareto chart ranks causes as bars ordered by frequency, with a cumulative line, so the vital few contributing roughly 80% of the problem stand out. This satisfies the stem's 80/20 prioritisation requirement, which a histogram or scatter diagram cannot deliver.

A network diagram maps activities as nodes with arrows showing dependencies, so the longest path through it reveals the critical path. This directly satisfies the need to visualise sequence and dependencies, unlike a Gantt chart that emphasises duration and calendar timing.

A burnup chart plots a total work scope line alongside a completed work line, exposing scope changes that a burndown chart hides. This satisfies the stem's requirement for tracking progress against a moving baseline, letting the agile team see both delivered value and any expansion of total work across the project.

A project dashboard aggregates schedule, cost, and scope metrics and displays them with red-amber-green thresholds, giving executives a single consolidated health view. This directly matches the request for one view combining performance indicators against thresholds, making it the appropriate reporting tool for this scenario.

Dividing the budget at completion by the cost performance index ($500,000 ÷ 0.8) yields $625,000, because a CPI below 1.0 signals costs are running above plan. This satisfies the stem's assumption that current cost performance continues, making it the valid estimate at completion.

Earned value of $40,000 sits below planned value of $50,000, so the schedule variance is negative and work lags. Actual cost of $45,000 exceeds earned value of $40,000, giving a negative cost variance, confirming over budget.

Ten consecutive points all above the mean constitute a non-random run, which control chart rules flag as special cause variation even though every point sits inside the control limits. It satisfies the stem's scenario of points within limits but consistently shifted.

Pareto charts derive from the Pareto principle, commonly called the 80/20 rule, which holds that roughly 80% of effects stem from 20% of causes. This underpins why the tool highlights the vital few contributors rather than treating all causes equally.

A good Definition of Done includes verifiable quality criteria such as unit tests written and passing, ensuring each increment meets agreed technical standards before it is considered complete. This prevents unfinished or untested work being counted as done.

A Kanban board visualises workflow as columns representing stages such as 'To Do', 'In Progress', and 'Done', with cards moving between them. This matches the stem's requirement to visualise work flowing across those specific columns.

The project charter formally authorises the project by establishing the project manager’s authority to apply organisational resources, directly satisfying the stem’s requirement for a document that grants both formal approval and resource allocation power. Unlike a project scope statement, which defines deliverables and boundaries after initiation, the charter is the single binding authorisation instrument that triggers the project’s official start and legitimises resource use.

The sprint backlog is an agile artefact listing the product backlog items selected for the current sprint, plus the plan for delivering them. It satisfies the stem's requirement by being produced and maintained by the development team during sprint planning.

The project charter is the formal document that authorises the project's existence and grants the project manager authority to apply organisational resources. It satisfies the stem's requirement for both formal authorisation and resource-application authority, distinguishing it from plans or business cases.

CPI is calculated as EV ÷ AC, giving $200,000 ÷ $250,000 = 0.8. A value below 1.0 means each dollar spent delivers only 80 cents of earned value, so the project is over budget. This directly satisfies the stem's request for both the CPI figure and its cost implication.

Lessons learned are most useful when they include specific context, such as what happened, why it happened, and what the team recommends for similar situations. For a marketing campaign project, this means documenting which tactics worked, which vendors underperformed, and how to adjust timelines or budgets next time. This specificity enables future teams to apply the lessons, so this is the correct action.

A cost performance report consolidates planned budget, actual costs, and earned value information into a single view for analysis. It lets the project manager compare how much was budgeted, what was actually spent, and the value of completed work, making it the correct tool for evaluating financial performance on the construction project.

The product backlog is the ordered list of all desired work, and Jira manages it as the master requirements artefact feeding sprint planning. It satisfies the stem's requirement for an artefact used in Agile planning and tracking.

Velocity measures the average story points a team completes per sprint, directly satisfying the product owner's need to predict future performance from the 30- and 25-point sprints. Unlike cumulative flow or burndown, which track work remaining over time, velocity averages completed points across iterations, giving the forward-looking capacity forecast requested.

A Gantt chart plots activities as horizontal bars against a calendar timeline, directly satisfying the stem's requirement to show dependencies and milestones. Bar length represents duration, while linking arrows and diamond markers depict task relationships and key dates, making it the standard scheduling tool for this purpose.

The stakeholder register is the artefact that records each identified stakeholder alongside their interests, influence, and expectations, which is precisely what the stem describes. It satisfies the constraint of capturing all stakeholders and their attributes in one document, distinguishing it from the stakeholder engagement plan, which instead defines management strategies.

Reducing probability from 0.3 to 0.1 cuts expected loss from $15,000 to $5,000, saving $10,000. Subtracting the $5,000 response cost leaves a net EMV benefit of $5,000, satisfying the stem's requirement to quantify the response's net value.

The burndown chart tracks remaining work, so adding stories mid-sprint raises the remaining total even while the team completes points. Completed work of 30 story points alongside an upward trend therefore indicates scope was injected into the sprint.

The EAC of $250,000 is derived from the formula EAC = BAC / CPI, which applies when the cost performance index (CPI) is expected to remain constant for the remainder of the project. Given BAC = $200,000 and CPI = EV/AC = $80,000/$100,000 = 0.8, the calculation yields $200,000 / 0.8 = $250,000. This satisfies the constraint that the same CPI persists, reflecting no change in cost efficiency.

The issue log is the project artefact specifically designed to record, assign and track issues through to resolution, capturing owner, status and due dates. It directly satisfies the stem's requirement to record and monitor issues, unlike a risk register, which addresses uncertain future events rather than problems already occurring.

Points plotting beyond the upper control limit signal that the process is influenced by an assignable, non-random source rather than normal common cause variation. This satisfies the stem's observation of out-of-limit data, indicating special cause variation requiring investigation.

A consistent naming and versioning convention ensures team members can identify the latest approved document and trace revisions. This directly supports the goal of controlled changes and easy retrieval, and it is a foundational practice for any shared project repository where multiple contributors update artifacts over time.

SPI is calculated as EV ÷ PV, giving 0.8, which is below 1.0 and therefore signals the project is behind schedule, directly satisfying the stem's stated concern. The AC figure is irrelevant here, since SPI measures schedule efficiency only, not cost performance.

The stakeholder register is a project document that identifies all stakeholders, including their roles, contact information, and other relevant details. It is used to plan stakeholder engagement and manage communications. In this scenario, the project manager needs a centralized list of stakeholders, making the stakeholder register the appropriate choice.

Planning poker has each team member privately select a card representing their story point estimate, then discuss discrepancies until convergence. This iterative reveal-and-discuss cycle produces a shared consensus estimate, directly satisfying the stem's stated purpose rather than merely averaging individual guesses.

A burndown chart plots remaining work against time across the sprint, so flat or rising lines immediately expose work not decreasing as expected. It satisfies the stem's need to visualise the remaining-work trend over the sprint duration.

The project scope statement details the project deliverables, acceptance criteria, and exclusions, which are essential for creating a precise procurement SOW. It ensures the vendor's work aligns with the project's boundaries and quality expectations. By referencing it, the project manager can clearly define what the vendor must produce and how it will be accepted.

A network diagram maps activities as nodes linked by dependency arrows, exposing the longest path through the schedule — the critical path. This directly satisfies the stem's requirement to show sequence and dependencies, which a Gantt chart's timeline bars obscure and a RACI matrix or resource histogram cannot represent at all.

A burndown chart plots remaining work against time and is used to forecast whether the team will finish the backlog by a target date. It visualizes progress and helps identify trends early. For predicting completion of an agile project, the burndown chart directly addresses the scenario's need to compare remaining work with time.

Planning poker has each team member privately choose a card showing story points, then reveal simultaneously and discuss divergent estimates until consensus forms. This matches the stem's private-selection-then-discussion sequence exactly, distinguishing it from other estimation techniques such as affinity estimating or T-shirt sizing.

The "so that..." clause captures the benefit or business value the story delivers, satisfying the user story template's third element alongside role and goal. This ensures work ties to a tangible outcome rather than a feature alone, which is precisely what the stem's key-elements requirement demands.

A milestone chart plots only zero-duration markers for phase gates and major deliverables, so senior management sees key events without the task-level detail they do not need. It directly satisfies the stem's constraint of highlighting only phase starts, ends and deliverables.

A document management system provides version control, check-in/check-out, authorship, revision history, and approval workflow for project documents. It is designed exactly for tracking who created, revised, and approved each artifact, making it the right tool for this scenario's need to monitor document status centrally.

An RFP formally solicits proposals from prospective sellers, defining requirements and evaluation criteria so the buyer can compare bids. It is a core procurement document, satisfying the stem's request for documents used when selecting vendors and awarding contracts.

Using EAC = BAC ÷ CPI suits the stem's constraint that current cost performance continues. CPI is EV ÷ AC = 90,000 ÷ 100,000 = 0.9, so EAC = 200,000 ÷ 0.9 = $222,222. This formula projects the same cost efficiency forward, unlike the atypical-variance approach.

A burnup chart plots completed work against total scope, exposing scope changes that distort a burndown. It tracks sprint progress by showing whether remaining work reflects added or removed stories, satisfying the stem's requirement for a metric measuring progress within a sprint.

The RACI matrix directly satisfies the stem's requirement for a document mapping roles and responsibilities across four defined categories: Responsible, Accountable, Consulted, and Informed. Unlike a project charter or communication plan, it assigns each task or decision to specific people using exactly these designations, making it the precise artefact described.

A Pareto chart ranks defect categories by descending frequency, applying the 80/20 principle so the few defect types causing most occurrences stand out. This directly satisfies the stem's need to prioritise corrective actions on the most frequently occurring defects.

A formal acceptance document signed by the authorized stakeholder confirms the deliverables met the agreed criteria and closes the contract. It is the standard control for releasing final payment and completing procurement closure, which is exactly what the PM needs here after the vendor finished all fixed-price deliverables.

EAC equals BAC divided by cost performance index. CPI is EV divided by AC, or $40,000 over $50,000, giving 0.8. Dividing the $100,000 BAC by 0.8 yields $125,000, satisfying the assumption that current cost performance continues.

The issue log should record each issue, assign an owner, and include a target resolution date. This ensures accountability and timely follow-up. By assigning owners and dates, the PM addresses the blocking issues directly. This is the standard practice for managing issues and aligns with the purpose of the issue log.

With EV $45,000 below PV $50,000, the schedule variance is negative, so the project trails the baseline. EV $45,000 below AC $55,000 yields a negative cost variance, meaning more was spent than earned. Both CPI and SPI sit under 1.0.

Dividing budget at completion by cost performance index ($200,000 ÷ ($120,000 ÷ $130,000)) yields $216,667. This satisfies the stem's constraint that the project continues at its current cost efficiency, so EAC is BAC ÷ CPI rather than a bottom-up re-estimate.

The change log is used to record the status of change requests, including their approval or rejection, and the associated impacts on scope, schedule, and cost. Documenting the approved reporting module addition here provides a clear audit trail and updates the project baseline, which is exactly what the scenario requires.

The project charter is the formal authorisation document that names the project manager and grants them authority to apply organisational resources. It satisfies the stem's requirement for both formal authorisation and assignment of the project manager, distinguishing it from the project management plan.

Schedule variance is calculated as earned value minus planned value; a negative result means less work was completed than planned at that point. An SV of -$5,000 therefore indicates the project is behind schedule, not over budget.

The product backlog is the prioritised, emergent list of features, enhancements and bug fixes not yet scheduled into a sprint, owned and ordered by the product owner. It satisfies the stem's description of an unscheduled, product-owner-prioritised list.

A point beyond the upper control limit signals special cause variation, meaning the process is not behaving predictably. Control charts exist to trigger exactly this response, so the project manager must investigate the assignable cause before deciding whether the process needs correction.

Using the typical CPI assumption, EAC equals BAC divided by CPI. Here CPI is EV/AC, or $120,000/$150,000 = 0.8, so EAC is $200,000/0.8 = $250,000. This satisfies the stem's requirement to forecast the final cost using typical performance.

The schedule management plan is a subsidiary plan defining how the schedule is developed, monitored and controlled, so it forms part of the project management plan. It satisfies the stem by being a component document rather than a standalone project artefact.

The scope management plan describes how the project scope will be defined, validated, and controlled. It is a core subsidiary plan that ensures all required work and only the required work is included. For a construction project, it prevents scope creep and provides the framework for managing changes to the building specifications and deliverables.

A Gantt chart plots tasks as horizontal bars against a calendar timeline, with dependency links between bars and milestone markers at key dates. This satisfies every element the stem requires: horizontal bars, timeline, dependencies and milestones.

A signed acceptance certificate documents that the customer or sponsor formally accepts the project deliverables, which is required before final payment and closure. In this construction scenario, it confirms that the work meets contractual requirements and that the buyer agrees the project is complete. Without this document, the project manager cannot prove formal acceptance, so it is one of the correct documents to review.

Kanban boards use columns representing workflow states, such as 'To Do', 'In Progress' and 'Done', with cards moving between them. This matches the tool described, satisfying the stem's requirement to identify the board type visualising workflow stages.

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. The indices measure cost and schedule efficiency on independent axes.

The sprint backlog is the agile artifact holding the product backlog items selected for the current sprint, plus the team's plan for delivering them. It satisfies the stem's need to manage work at the iteration level, unlike traditional schedules or work breakdown structures.

Multiplying probability by impact gives the expected monetary value: 0.3 × $50,000 = $15,000. This quantifies the risk's average financial exposure, satisfying the register's requirement to express each risk in monetary terms for comparison and contingency budgeting.

A Kanban board visualises workflow by splitting work items into columns representing process stages, exactly matching the 'To Do', 'In Progress', and 'Done' layout described. It tracks user stories, epics, and bugs as cards moving between those columns, satisfying the stem's sprint-tracking and column-view constraints.

The project charter formally authorises the project's existence and explicitly identifies the assigned project manager, conferring authority to proceed. It satisfies both constraints in the stem, whereas subsidiary documents such as the project management plan assume authorisation already exists.

An instant messaging and persistent chat platform supports real-time collaboration by allowing quick questions, clarifications, and decisions across time zones, with searchable history. It addresses the real-time communication need in the scenario. Combined with a version-controlled repository, it forms a practical toolset for a distributed team's communication plan.

Activities on the critical path have zero total float, meaning any delay directly extends the project's finish date. This zero-float property is precisely what defines the longest-duration sequence through the network diagram, satisfying the stem's requirement to identify critical path characteristics.