Moving team members does not address the underlying uncertainty associated with the third-party dependency or its potential effect on the release.

Immediately removing a high-value feature is premature. The team should first assess the risk and evaluate appropriate responses before changing the release scope.

Executive escalation is premature before the team has assessed the risk and considered reasonable mitigation strategies.

Increasing formal status reporting adds administrative communication but does not provide the continuous transparency and rapid information access encouraged by Agile.

Additional mandatory meetings may create unnecessary overhead and still leave information unavailable between meetings, particularly for distributed stakeholders.

Using intermediaries can slow communication and introduce filtering or misunderstanding rather than promoting direct transparency between the team and stakeholders.

MoSCoW is a valid technique, but Agile does not require one particular prioritization method simply because it is commonly used or taught.

Voting selects a preferred technique but does not necessarily improve value-based prioritization or resolve the underlying objective.

Combining several techniques introduces unnecessary complexity. Agile favors an effective and sufficiently simple approach rather than process for its own sake.

Waiting for a later formal event unnecessarily delays transparency and reduces the client's opportunity to respond to the emerging risk.

Monitoring is appropriate, but withholding the information until the risk materializes changes proactive risk management into reactive issue management.

The team should mitigate the risk, but internal mitigation does not replace transparent communication with stakeholders who may be affected.

Individual coaching may improve confidence, but it does not directly resolve the broader team-level problem of poor visibility into work progress and dependencies.

Experimentation supports learning, but this response does not address the immediate transparency and coordination problem affecting the team.

The product owner focuses primarily on product value and backlog priorities. The team should strengthen self-management rather than transfer responsibility for team coordination to the product owner.

The behavior may contribute to team misalignment, but Team Misalignment Zone is not the specific behavioral classification described by the source.

Conflict may be escalating, but this describes the situation rather than the specific behavior zone being tested.

Communication is being impaired, but Communication Breakdown Zone is not the intended classification. The described blame, defensiveness, and resistance to feedback point specifically to the Red Zone.

Incorrect. Waiting for the complete product delays feedback and increases the risk that problems or incorrect assumptions will be discovered late.

Incorrect. Agile integrates testing and validation throughout development rather than postponing testing to a separate final phase.

Incorrect. A one-time pilot may provide feedback, but it does not create the continuous feedback cycle achieved through incremental delivery.

Incorrect. Servant leadership focuses on supporting, empowering, and enabling the team rather than the continuous process-improvement cycle described here.

Incorrect. Continuous deployment concerns releasing validated software changes automatically into production, not improving the team's working process.

Incorrect. A sprint review primarily inspects the product increment with stakeholders and adapts the product backlog; this scenario focuses on process improvement following a retrospective.

Incorrect. Simple voting identifies a preferred decision but provides limited information about the degree of support or resistance among team members.

Incorrect. Silent brainstorming is primarily an idea-generation technique and does not directly measure the strength of agreement with a proposal.

Incorrect. A consensus workshop can facilitate agreement, but it is more involved than necessary when the objective is to quickly measure each participant's level of support.

Incorrect. Scheduling Scrum events does not establish the quality and completion criteria used to determine whether work is done.

Incorrect. Product Owner involvement is important, but approval of planned user stories does not create a common standard for determining whether completed work satisfies required quality criteria.

Incorrect. Individual task assignments do not establish shared completion criteria, and Agile teams are generally expected to self-manage how work is performed.

Incorrect. Centralizing communication through one project manager can create a bottleneck and reduce direct collaboration and team self-management.

Incorrect. Requiring identical frameworks and cadences does not necessarily resolve dependencies and communication problems between teams.

Incorrect. Combining all teams into one centralized team can increase complexity and undermines the benefits of maintaining effective cross-functional Agile teams.

Incorrect. Timeboxing and iterative delivery are useful Agile practices, but they do not fully explain the broader Agile approach to collaboration, adaptability, and value delivery.

Incorrect. Agile does not eliminate planning. Planning occurs continuously and is adapted as new information and changing requirements emerge.

Incorrect. Examples from previous projects may help stakeholder understanding, but they do not directly explain the principles that enable Agile teams to maintain control and deliver value.

Incorrect. Agile teams maintain alignment around a shared vision, but they do not use the vision to avoid necessary changes driven by feedback and learning.

Incorrect. Velocity can support planning, but maintaining a particular velocity is not the objective when customer feedback indicates that adaptation is needed.

Incorrect. Agile planning is adaptive. Teams should not follow an iteration plan rigidly when learning and customer feedback indicate that changes are necessary.

Incorrect. Reducing workload may ultimately be appropriate, but making the decision unilaterally does not address the client's expectations or promote collaborative alignment.

Incorrect. The project manager should not wait for a formal complaint. Regular overtime, declining energy, and evidence of excessive workload are already indicators that intervention is needed.

Incorrect. A private discussion with the team could provide useful information, but it does not address the client's expectations. The stronger response is transparent collaboration between the affected parties.

Incorrect. The sprint backlog contains detailed work selected for a specific sprint and is focused on short-term execution rather than communicating the broader future direction of the product.

Incorrect. A release burndown chart is primarily used to monitor remaining work and progress toward a release, not to communicate the high-level future direction of the product.

Incorrect. A product increment represents completed usable value and therefore describes what has been delivered rather than the anticipated direction of future development.

Incorrect. Process optimization can improve performance, but the scenario emphasizes that people-related factors have a substantially greater influence.

Incorrect. Tools can support a team, but they do not necessarily compensate for deficiencies in capability, experience, communication, or collaboration.

Incorrect. The scenario does not indicate that automation efficiency is the primary factor influencing software project cost or success.

Incorrect. Independent ranking reduces collaboration and does not directly create alignment among competing stakeholder groups.

Incorrect. MoSCoW is a valid prioritization technique, but the scenario specifically emphasizes broad stakeholder participation and collaborative prioritization.

Incorrect. Implementation cost alone should not determine backlog priority; value and stakeholder needs must also be considered.

Incorrect. Conflict resolution is relevant to the situation, but the scenario specifically emphasizes evaluating trade-offs and reaching a mutually acceptable agreement.

Incorrect. Active listening supports the discussion, but it is only one element of the broader skill being demonstrated.

Incorrect. Facilitation helps structure collaborative discussions, but the defining element here is working through competing positions and trade-offs toward an agreement.

Incorrect. Extending the stand-up increases meeting time but does not provide continuous visibility into workflow and blockers.

Incorrect. Additional meetings create communication overhead instead of addressing the lack of continuous workflow visibility.

Incorrect. Centralizing status reporting with one team member reduces transparency and creates unnecessary reporting overhead.

Incorrect. Generate Insights occurs after information has been gathered and focuses on identifying patterns, causes, and meaning.

Incorrect. Gather Data focuses on collecting facts, observations, and perspectives about what occurred during the iteration.

Incorrect. Decide What to Do occurs later in the retrospective when the team selects specific improvement actions.

Incorrect. The scenario does not indicate that completed software is continuously deployed to production.

Incorrect. Agile teams are expected to adapt and self-manage rather than simply follow a centrally imposed sprint plan.

Incorrect. Stakeholders provide input and feedback, but the scenario emphasizes the team's autonomy rather than stakeholder control.

Incorrect. Variance analysis compares actual results against a baseline, target, or expected value rather than primarily examining patterns over time.

Incorrect. A lagging metric reports outcomes that have already occurred; the scenario specifically describes analyzing patterns to anticipate future performance.

Incorrect. Root cause analysis investigates why a problem occurred, whereas this scenario focuses on identifying patterns in quantitative performance metrics.

Incorrect. Tasks and documentation can support delivery, but completing them does not necessarily demonstrate that usable value has been delivered.

Incorrect. Burn-down charts are useful tracking tools, but achieving a burn-down target without producing functional outcomes is not the primary measure of progress.

Incorrect. Schedule percentage completion focuses on planned activity completion rather than actual delivery of usable customer value.

Incorrect. Simplicity focuses on creating the simplest effective solution and avoiding unnecessary complexity.

Incorrect. Feedback is an important XP value, but the central issue here is the developer being afraid to raise a known concern.

Incorrect. Communication supports collaboration, but this situation specifically requires the courage to communicate potentially uncomfortable information.

Incorrect. Separating developers from business stakeholders reduces collaboration and can delay important feedback.

Incorrect. Weekly reports create slower feedback cycles and do not replace frequent collaboration between business and development participants.

Incorrect. A liaison introduces an unnecessary communication layer that can slow or distort feedback between the people doing the work and the business stakeholders.

Incorrect. Agile does not eliminate planning. It favors adaptive and iterative planning that can respond to new information.

Incorrect. Freezing future work prevents the team from adapting to changing needs and priorities.

Incorrect. Requiring all changes to follow a formal sponsor-driven change control process reflects a more predictive approach and limits Agile adaptation.

Incorrect. The size of the product backlog does not directly address excessive work currently in progress.

Incorrect. Analyzing delays can be useful, but it does not directly address the immediate excessive-WIP problem.

Incorrect. Extending the sprint treats the symptom rather than improving workflow and limiting excessive work in progress.

Incorrect. Iterative and incremental approaches do not necessarily operate with fixed requirements and are designed to support learning and adaptation.

Incorrect. Team size and organizational maturity may influence the selected approach, but they do not define the fundamental differences between predictive, iterative, and incremental development.

Incorrect. Iterative development emphasizes repeated refinement, while incremental development emphasizes delivering usable portions of the solution progressively.

Incorrect. A wireframe primarily visualizes the user interface rather than the broader interactions between users and system functionality.

Incorrect. A data-flow diagram focuses on data processing and technical flows rather than how end users interact with the system.

Incorrect. A prioritized user-story list communicates ordering but does not visually represent how users interact with the overall system.

Incorrect. MoSCoW is a prioritization technique used to categorize requirements or features according to their relative importance.

Incorrect. INVEST provides criteria for evaluating the quality of user stories rather than defining improvement goals.

Incorrect. The Definition of Done establishes the conditions that work must satisfy before it is considered complete.

Incorrect. Pair programming improves collaboration, knowledge sharing, and code quality, but it does not directly address excessive working hours or burnout.

Incorrect. Refactoring improves the internal structure and maintainability of code without changing its external behavior.

Incorrect. Test-driven development improves software quality by creating tests before implementation, but it does not directly address sustainable working hours.

Incorrect. Story mapping organizes user stories around the user journey and helps visualize product functionality, but the scenario specifically prioritizes features based on economic value.

Incorrect. Risk-based prioritization ranks work according to uncertainty, exposure, or risk rather than expected return on investment.

Incorrect. Progressive elaboration develops greater detail as more information becomes available; it is not primarily a value-ranking technique.

Incorrect. The Product Owner prioritizes value and manages the Product Backlog but does not assign the developers daily tasks.

Incorrect. The ScrumMaster facilitates Scrum and helps remove impediments but does not direct the team's daily work.

Incorrect. Scrum does not rely on the Product Owner and ScrumMaster assigning work to individual developers.

Incorrect. Five story points per day is the team's throughput, not the expected cycle time.

Incorrect. At five story points per day, ten days would complete only fifty story points.

Incorrect. Sixty represents the size of the feature in story points, not the number of days required.

Incorrect. Gathering data focuses on collecting information about what happened during the iteration rather than selecting specific improvement actions.

Incorrect. Generating insights focuses on understanding patterns, causes, and why events occurred rather than selecting concrete improvement actions.

Incorrect. Closing the retrospective concludes the session and does not represent identifying the improvement actions shown in the scenario.

Incorrect. Stakeholder alignment may be useful, but it does not address the team's most immediate impediments.

Incorrect. Resolving the technical blocker is important, but this addresses only one of the two immediate problems affecting the team.

Incorrect. Protecting the team from interruptions is important, but this option leaves the technical blocker unresolved.

Incorrect. Reallocating resources assumes insufficient testing capacity is the cause before the actual bottleneck has been investigated.

Incorrect. Increasing sprint duration does not address the underlying cause of work accumulating in testing.

Incorrect. Slowing or stopping development may temporarily reduce incoming work but does not identify or resolve the underlying testing bottleneck.

Incorrect. A daily stand-up coordinates current work and identifies impediments rather than reviewing the completed sprint for process improvements.

Incorrect. A sprint review primarily inspects the product increment and gathers stakeholder feedback rather than focusing on improving the team's working process.

Incorrect. A pre-mortem anticipates possible future failures rather than reflecting on a completed iteration.

Incorrect. Agile does not eliminate documentation. Necessary and valuable documentation should still be created.

Incorrect. Requiring all detailed documentation before development resembles an upfront predictive approach and reduces adaptability.

Incorrect. Agile does not place comprehensive documentation above delivery of a valuable working product.

Incorrect. Planning occurs before implementation when the team determines what and how to deliver.

Incorrect. Learning uses insights obtained from evaluation to adapt and improve future work.

Incorrect. Development has already occurred because the feature has been implemented.

Incorrect. A process control chart monitors process stability and variation rather than mapping the end-to-end flow of work.

Incorrect. A burnup chart tracks completed work against the total amount of work or scope.

Incorrect. A value-based prioritization matrix supports prioritization based on value rather than identifying waste and delays in a workflow.

Incorrect. Stakeholder feedback should be evaluated and prioritized before implementation rather than automatically implemented.

Incorrect. Valuable feedback should be captured and considered instead of being ignored or unnecessarily deferred.

Incorrect. Requiring formal change requests is generally associated with predictive change control and can unnecessarily restrict Agile feedback.

Incorrect. A sprint review primarily inspects the product increment and gathers stakeholder feedback.

Incorrect. Release planning focuses on broader release objectives and delivery planning rather than reflecting on team performance.

Incorrect. Sprint planning determines the work and objectives for the upcoming sprint.

Incorrect. Prune the Product Tree is primarily used to explore and prioritize product features.

Incorrect. Remember the Future asks participants to imagine a successful future state and identify what would be required to achieve it.

Incorrect. Boat Mapping is not the collaboration game described by the wind-and-anchor retrospective metaphor.

Incorrect. Agile does not require the entire backlog to be cleared before valuable new features can be considered.

Incorrect. Formal change control is not the best technique for categorizing Agile features according to customer satisfaction.

Incorrect. Prioritizing innovation while basic functionality remains unreliable can neglect essential customer needs.

Incorrect. Agile favors empowered and collaborative teams rather than centralized task control.

Incorrect. The Product Owner prioritizes value and backlog items but does not assign all development tasks.

Incorrect. Agile emphasizes collaboration and adaptability rather than rigid hierarchical task assignments.

Incorrect. Agile favors adaptation and frequent feedback rather than rigid adherence to a fixed process.

Incorrect. Agile encourages continuous customer and stakeholder engagement throughout delivery.

Incorrect. Agile aims to deliver usable value early and incrementally rather than waiting until project completion.

Incorrect. Innovation should support validated customer or business value rather than introduce unnecessary work.

Incorrect. Developing both features increases work and can delay delivery of the customer's prioritized requirement.

Incorrect. Additional functionality does not automatically create customer value and may constitute gold plating and waste.

Incorrect. Documentation alone does not provide the same level of shared understanding and ownership as collaborative alignment.

Incorrect. Continuing development without clarity about the product purpose can create misalignment, rework, and waste.

Incorrect. Establishing a shared product vision should involve the relevant stakeholders and team rather than being delegated to one individual.