CCNA Delivery Questions

The Daily Stand-up is a short, timeboxed Scrum event where members share progress, plans and impediments, synchronising work and surfacing blockers early. This directly satisfies the stem's purpose, enabling rapid impediment removal rather than status reporting to management.

Defining the sprint goal gives the iteration a single cohesive objective, aligning the team and guiding trade-off decisions during the sprint. It satisfies sprint planning's purpose of establishing a shared, negotiable target that focuses the team's work for the iteration.

The Product Owner owns backlog ordering and trade-offs, so routing the mid-sprint request there preserves the sprint commitment while letting value be weighed against existing work. The practitioner should not unilaterally insert scope, which would undermine the team's agreed sprint goal.

Cycle time is a team-level flow metric, so the retrospective is where the team inspects its own process data and identifies systemic causes. Discussing the three-sprint trend there engages those closest to the work, satisfying the need to find root cause before prescribing changes.

The delay is a scope-versus-schedule trade-off affecting cost, risk and value, so the decision belongs to those accountable for business outcomes. Presenting the trade-off lets stakeholders weigh the feature's worth against the two-week slip transparently.

Lead Time measures the elapsed duration from a request being made to its delivery, capturing queueing and waiting waste across the whole value stream. This end-to-end visibility satisfies the stem's requirement for metrics that expose and help mitigate delivery waste.

Backlog grooming directly restores alignment by re-ranking items against current business value, satisfying the stem's constraint that delivered features no longer match organisational priorities. Engaging stakeholders in that session ensures the revised order reflects their priorities, so subsequent iterations deliver the highest-value work first.

Automated testing catches regressions on every commit, while continuous integration merges and verifies code frequently, exposing integration defects before release. This directly addresses the stem's post-release defect volume by shifting detection earlier, satisfying the need for a repeatable quality gate rather than relying on manual end-of-cycle testing.

A sprint goal must be clear and concise so every team member can state, without ambiguity, what the sprint intends to achieve and whether the selected backlog items serve it. That shared, memorable focus guides daily trade-off decisions and underpins meaningful inspection at the sprint review.

Time-boxing the decision forces the team to converge within a fixed window, preventing endless debate. The practitioner facilitates by clarifying options, surfacing dissent and driving consensus before the timer expires, so decision paralysis yields to forward progress without sacrificing team input.

The Sprint Burndown chart plots remaining work against time within the sprint, directly showing whether the team is on track to meet the sprint goal. It satisfies the stem's requirement for tracking progress towards that goal, unlike product-level or release-level artefacts, which measure broader scope beyond the current sprint.

One Product Owner with a single unified backlog gives all three teams a shared priority order, preventing divergent roadmaps. This satisfies the coordination constraint by aligning what each team builds toward one product vision rather than competing backlogs.

Agile teams address risk continuously because each iteration surfaces new information, changing the risk profile. Risk management is embedded in ceremonies such as daily stand-ups, retrospectives and iteration reviews, satisfying the stem's requirement for ongoing identification and response rather than a single upfront phase.

Reviewing retrospective notes targets the root cause of the 20% velocity drop by surfacing systemic blockers, such as unresolved impediments or process friction, rather than reacting to the symptom. This satisfies the stem's "first" constraint: inspect before adapting, consistent with the Agile principle of reflecting and adjusting at regular intervals.

Value stream mapping exposes every step between request and delivery, revealing queues, handoffs and rework that inflate lead time. Eliminating those non-value-added activities directly shortens the end-to-end flow the stem describes, rather than optimising individual functions in isolation.

A collaborative review lets the team clarify, tighten and agree the Definition of Done so it is consistently applied. This directly addresses the stem's inconsistent application and resulting technical debt by removing ambiguity through shared ownership rather than imposing a mandate.

An MVP ships the smallest increment that lets real users test the underlying hypothesis, converting assumptions into validated learning. This produces meaningful outcomes because feedback from actual usage, not internal output metrics, determines whether the product delivers value and guides the next iteration.

WIP limits should be set around the workflow's constrained steps, because limiting work elsewhere merely shifts the queue to the bottleneck. Identifying bottlenecks first lets the practitioner cap WIP at the slowest stage, exposing the real constraint and driving improvement there rather than at unconstrained stages.

Shared digital Kanban boards give distributed teams a single, real-time visual source of truth, replacing physical task walls that co-location would otherwise provide. This directly satisfies the stem's distributed constraint by making work-in-progress, blockers and ownership visible asynchronously across time zones, sustaining the transparency agile communication depends on.

A dedicated enabler team or infrastructure service-level agreement removes the cross-team dependency that repeatedly blocks delivery, addressing the delays at organisational rather than team level. This satisfies the stem's requirement for an organisational-level fix rather than local workarounds.

Continuous improvement targets the process itself, not just the product, so retrospectives feed small iterative changes that compound into better delivery efficiency. This directly satisfies the stem's goal of enhancing processes and delivery efficiency over time, rather than merely fixing defects or adding features.

A Cumulative Flow Diagram plots work-in-progress per column over time, so widening bands at the QA column reveal where items accumulate and how long they wait. This exposes the bottleneck's nature and trend, which a single-cycle-time or throughput number cannot show.

The Product Owner owns backlog ordering, so routing new requests there lets them be assessed against the sprint goal rather than injected directly. This shields the team's committed capacity while keeping scope decisions with the accountable role.

WIP limits cap concurrent work, forcing the team to finish items before pulling new ones. This directly reduces the context switching described in the stem and shortens cycle time, optimising end-to-end flow across the value stream.

Global time zones prevent full synchronous overlap, so scheduling a shared core window for critical synchronisation, combined with asynchronous tools for everything else, minimises coordination delay. This directly addresses the constraint of distributed time zones while preserving alignment across the enterprise.

Facilitating a discussion lets the team examine each ceremony and remove or shorten those adding no value, directly addressing the overwhelm. This preserves agile principles while ensuring every ceremony's purpose is understood, satisfying the need to support the team without abandoning the framework.

Action items for the next sprint belong in the retrospective because the ceremony closes by converting identified improvements into owned, tracked commitments. This satisfies the stem's requirement for a typically discussed retrospective item, distinguishing it from sprint planning or daily standup content, where forward work is instead selected or coordinated.

Cost of Delay quantifies the value forfeited per unit of time a feature remains undelivered, combining revenue, time-criticality and risk reduction. The Product Owner uses it to sequence backlog items by economic impact, so delaying a high-CoD feature directly sacrifices measurable revenue or value.

Psychological safety underpins flow by letting team members surface blockers, admit mistakes and challenge process decisions without fear of reprisal. That candour shortens feedback loops and prevents work stalling silently, directly satisfying the stem's requirement for a cultural aspect that optimises flow across the delivery pipeline.

Pairing the early finisher with struggling members spreads capability across the team, reducing bottlenecks and balancing workload, which optimises flow. This satisfies the stem's goal of improving overall throughput rather than rewarding individual speed or reassigning work away from the team.

A Burndown Chart plots remaining work against time within a sprint or release, giving teams visible progress tracking. It is a widely used agile artifact, satisfying the stem's requirement for artefacts commonly employed in agile delivery.

Scrum of Scrums brings representatives from each team together regularly to surface and resolve cross-team impediments, dependencies and integration issues. This creates a formal synchronisation mechanism that satisfies the coordination requirement in scaled agile environments where many teams must align.

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small and Testable. The letter P appears nowhere in the acronym, so any option claiming P represents a genuine INVEST criterion is factually wrong. The stem's premise is therefore a deliberate trick.

Product-based funding shifts investment decisions to outcome delivery, so value-based metrics such as Net Promoter Score and Customer Acquisition Cost measure realised customer and business value rather than schedule or budget adherence, matching the stem's funding-model change.

The Definition of Done is a shared checklist of quality and completeness criteria applied to every increment, so 'done' means the same thing to developers, testers and the product owner. That shared understanding prevents incomplete work being counted as finished, which is precisely the readiness guarantee the stem asks about.

Technical debt accumulates when refactoring is perpetually deferred, so dedicating a fixed slice of each sprint's capacity to remediation ensures it is addressed continuously rather than starved by feature work. This directly satisfies the stem's constraint of slowing feature delivery by making debt reduction a planned, sustainable commitment.

A flat burn-down alongside a rising burn-up indicates work is being counted before it meets the Definition of Done. Re-baselining the burn-down to accepted stories and confirming when points are awarded restores the metric's predictive value and gives the product owner an honest release forecast, which is exactly what the scenario requires.

Planning Poker applies wideband Delphi with simultaneous card revelation, so individual estimates are not anchored by senior voices. This directly addresses the team's difficulty sizing tasks by exposing divergent assumptions, forcing discussion until consensus, and producing faster relative estimates than open debate.

A daily Scrum of Scrums gives cross-team representatives a recurring forum to surface, track and resolve inter-team dependencies before they block delivery. This provides the coordination cadence four teams need, which single-team events cannot supply.

Smaller, similarly sized work items reduce variability in cycle time and make flow more predictable. When items are too large or inconsistent in size, they clog the system and make forecasting difficult. Breaking them down enables smoother pull through the workflow and supports better WIP management, directly addressing the root cause of unpredictability.

Automated deployment moves validated builds into environments without manual intervention, removing handoff delays and human error. This keeps the pipeline flowing continuously from commit to release, satisfying the requirement for a healthy, continuous delivery pipeline.

Scrum of Scrums directly addresses cross-team dependency synchronisation by having each team's representative report progress, impediments and upcoming inter-team dependencies. This satisfies the stem's multi-team coordination constraint, unlike single-team ceremonies such as daily stand-ups, which cannot surface or resolve dependencies spanning several cross-functional teams.

Cross-functional teams aligned to value streams own a complete slice of delivery, removing handoffs and queueing between silos. This directly optimises end-to-end flow because dependencies and wait states shrink, letting work move continuously from idea to customer rather than pausing at departmental boundaries.

The gap stems from building the wrong thing, not from poor execution. By bringing stakeholders together to articulate the outcomes they need, the team can re-align the backlog to deliver value rather than output. This directly addresses the root cause and ensures future increments are measured against business results, not just acceptance tests.

Re-evaluating the backlog with the Product Owner against current business value and ROI criteria reorders work by present market worth, not historical momentum. This directly corrects the mismatch between delivered features and organisational priorities, satisfying the stem's alignment constraint.

The sprint review inspects the completed increment with stakeholders, then adapts the product backlog based on their feedback. This satisfies the empirical inspect-and-adapt requirement at the product level, distinct from the retrospective's focus on process.

The practitioner's role is to remove impediments and enable the team to self-organize. By making the issue transparent and guiding the team through impact assessment, the team can decide whether to descope, spike, or escalate. This preserves commitment realism and sustainable pace while addressing the technical problem collaboratively.

The Scrum Master serves the team by removing impediments, coaching agile practises and shielding it from external disruption, directly enabling self-organisation. This facilitation role is fundamental because without it the team's process discipline and continuous improvement stall, undermining the collaborative cadence the scenario demands.

Divergence between local and pipeline environments is the leading cause of this pattern. Aligning them removes the environmental variable, and treating failures as stop-the-line prevents broken builds from accumulating. Together these make the pipeline a trustworthy signal, which is what shortens the delay between commit and deployable increment.

A technical blocker preventing a high-priority feature needs the practitioner to facilitate team discussion of alternatives, escalating only if the team cannot resolve it. This keeps ownership with the team while ensuring impediments are surfaced, satisfying the sprint planning constraint.

Large features delay feedback and obscure value delivery. Splitting epics into smaller, investable user stories shortens the feedback loop, letting the team deliver and validate increments frequently, directly addressing the stem's root cause of oversized features.

Respecting the WIP limit means the fourth item should not enter 'Testing'. Rather than idle, the developer should swarm on the blocked work or resolve the third-party dependency, restoring flow and preventing the bottleneck from worsening.

MoSCoW sorts backlog items into Must, Should, Could and Won't categories, forcing explicit trade-offs against organisational goals. Must-haves map to non-negotiable business objectives, so prioritisation reflects value and constraints rather than arbitrary ordering, satisfying the requirement to align the backlog with organisational goals.

Strict WIP limits cap concurrent work per person or column, forcing completion before pulling new items. This directly reduces context switching by preventing the multi-tasking that fragments focus, satisfying the stem's constraint of minimising task-switching overhead across the team.

Measures the time to complete a single unit of work.

Oversized items break the sprint's forecast reliability, so splitting them into smaller INVEST-compliant stories restores estimability and flow. The Scrum Master facilitates this by coaching the Product Owner to decompose work, keeping each slice independently valuable and completable within the sprint, matching historical velocity.

If the team repeatedly misses the Definition of Done, the criterion itself may be unrealistic or ambiguous, so reviewing and refining it addresses the root constraint. This keeps the standard meaningful while making it achievable, directly resolving the consistent failure described in the stem.

Velocity measures story points completed per iteration, directly quantifying the team's throughput. For assessing consistency of value delivery across iterations, its iteration-by-iteration trend reveals variability that cumulative metrics hide. PMI-ACP treats velocity as the standard empirical measure of predictable delivery capacity, satisfying the stem's requirement for per-iteration consistency.

A dependency board makes upstream and downstream blockers visible, so the team can sequence work around external constraints instead of absorbing idle time. Visualising impacts enables earlier escalation and pull-based coordination, restoring the consistent cadence that external dependencies had disrupted.

Embedding verification into the Definition of Done and generating evidence automatically makes compliance a byproduct of normal work rather than a separate phase. The team keeps its two-week cadence, the regulator receives consistent auditable records, and verification becomes faster and more reliable than a manual end-of-cycle review would be.

Archiving or deleting low-priority items that are unlikely to be built shrinks the backlog to a manageable, decision-ready size. It removes stale entries that distort prioritisation and inflate refinement effort, keeping the remaining items ordered and genuinely actionable.

Improving estimation accuracy and actively managing capacity addresses the root cause of missed sprint goals: unreliable forecasts and overcommitment. By calibrating estimates against historical velocity and limiting work in progress to true available capacity, the team commits to achievable goals and delivery reliability rises.

Surfacing the impediment makes it transparent and actionable, while a stub or contract test lets the team verify its own integration logic without the live gateway. This preserves flow, keeps the increment potentially shippable, and positions the team to swap in the real endpoint quickly once the vendor is ready, which is the smallest effective first step.

Automated build and testing pipelines remove the manual verification bottleneck that makes monthly releases feasible, enabling code to be validated and deployed on demand. This directly satisfies the continuous delivery constraint: every change must be releasable to production at any time, which requires repeatable, automated quality gates rather than scheduled manual testing cycles.

A Kanban board maps each workflow stage as a column, exposing where work items accumulate and stall. By applying work-in-progress limits per column, it directly reveals the bottleneck stage constraining throughput, satisfying the need to identify flow constraints visually rather than tracking effort or dependencies.

A widening band between 'In Progress' and 'Done' on a cumulative flow diagram directly signals accumulating work-in-progress, meaning items enter the active state faster than they exit. This vertical expansion of the in-progress band is the standard CFD indicator of a downstream bottleneck constraining throughput, exactly the constraint the stem describes.

The practitioner's role is to surface the impact of the priority shift, not to accept or reject it. Helping the Product Owner assess consequences and reorder the product backlog keeps prioritisation with the PO, satisfying the constraint that scope decisions remain a product-ownership responsibility rather than a team or stakeholder one.

Mid-iteration scope injection is a classic source of flow degradation because it forces context switching and leaves multiple items partially done. Agreeing that the team completes its committed work before accepting new items limits work in progress, shortens cycle time, and gives the product owner a predictable channel for new requests in the next planning event.

'Start, Stop, Continue' gives every member a structured, low-risk prompt to voice observations across three dimensions, surfacing improvement actions without blame. This directly raises participation and psychological safety, satisfying the goal of improving team engagement during the retrospective.

A Scrum of Scrums directly satisfies the cross-team coordination constraint by having each team's representative surface dependencies, integration blockers and inter-team risks in a recurring forum. This scales agile communication across the five teams without adding a command-and-control layer, preserving team autonomy while optimising end-to-end delivery flow.

INVEST criteria—Independent, Negotiable, Valuable, Estimable, Small, Testable—provide the concrete quality checklist a user story must satisfy. This directly answers the stem's demand for a key component of a good user story, since INVEST defines the attributes separating well-formed stories from vague requirements.

Value-based prioritisation ranks backlog items by delivered business value, ensuring limited agile capacity flows to the highest-return work first. This satisfies the alignment constraint by tying day-to-day iteration selection directly to organisational priorities rather than effort, seniority or technical preference.