100 Free PMI-ACP Practice Questions and Answers
100 questions for the PMI-ACP exam, each answer explained. Watch it here, try the questions yourself, or read the transcript.
Questions in this video
Tap an answer to see why it is right or wrong. Tap it again to reset.
Question 1 Play from 00:00
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Acknowledging the list and sharing it with management produces no actual improvement.
Not this one. Try another answer.
Why B is wrong
Implementing everything at once overwhelms the team and makes it hard to see which change helped.
Right, C is the answer.
Why C is right
Even when every idea is beneficial, a team cannot absorb many changes at once without losing focus and capacity for delivery. The agile coach should help the team select the one or two improvements expected to have the greatest impact and commit to implementing them right away, often by adding them to the next sprint backlog. The team can then inspect the results at the next retrospective and pick further items, making continuous improvement steady and measurable.
Not this one. Try another answer.
Why D is wrong
Complexity is not the selection criterion, and starting with the hardest change risks stalling improvement.
Question 2 Play from 02:06
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Writing complete test cases before a story even enters the backlog is premature, front-loaded work that conflicts with progressive refinement.
Not this one. Try another answer.
Why B is wrong
Defining detailed business requirements up front is a predictive approach that replaces collaboration with documentation.
Right, C is the answer.
Why C is right
A user story is a placeholder for a conversation, not a full specification. When the team is unsure about the acceptance criteria and level of detail during backlog refinement, the agile practitioner should guide everyone toward stories with just enough detail to start, so that understanding grows through continuous collaboration between the developers and the product owner. Details are added progressively as the story approaches implementation, which avoids waste from premature specification and keeps the team able to respond to what it learns.
Not this one. Try another answer.
Why D is wrong
Loading the acceptance criteria with test scenarios does not resolve the confusion about how much detail a story needs and pushes toward excessive up-front specification.
Question 3 Play from 04:30
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Requesting more resources from management is unnecessary when the team already has slack and the cause of the stress has not been explored.
Not this one. Try another answer.
Why B is wrong
Raising one member's stress at the daily stand-up turns a personal well-being concern into a public status item before the leader understands it.
Right, C is the answer.
Why C is right
A team member who is stressed by a heavy workload needs support, and a servant leader responds by meeting with that person directly. A personal conversation shows care for the member's well-being, gives the leader a clear understanding of what is driving the stress, and lets the two of them brainstorm practical ways to manage the work, such as reprioritizing tasks, asking teammates for help, or limiting work in progress. This approach protects sustainable pace and psychological safety without exposing the member's difficulties in front of the whole team.
Not this one. Try another answer.
Why D is wrong
Tracking one person's tasks in a separate backlog adds overhead, reduces transparency, and singles the member out.
Question 4 Play from 06:50
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Including stakeholders in one planning meeting is a one-time touchpoint and does not cover the ongoing detailing of requirements.
Not this one. Try another answer.
Why B is wrong
An earlier demo would detect the gap sooner but would not prevent it, since the stakeholders would still be absent from requirements work.
Not this one. Try another answer.
Why C is wrong
Formal sign-off freezes requirements on paper and does not ensure the right stakeholders contributed or that needs stay current.
Right, D is the answer.
Why D is right
Missing requirements surfaced because some key stakeholders were left out while requirements were being detailed. Agile requirements are elaborated progressively, just in time, so stakeholder engagement must be continuous rather than a single event. Identifying all key stakeholders and engaging them periodically, for example in backlog refinement, story workshops and sprint reviews, ensures their needs are captured as stories are detailed and gives frequent chances to catch gaps early. This steady collaboration is what prevents late surprises when the increment is shown.
Question 5 Play from 09:14
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A team-building activity may lift spirits briefly but leaves the repetitive work that causes low motivation unchanged.
Right, B is the answer.
Why B is right
Subject matter experts who perform the same repetitive tasks lose motivation because their work offers little variety, learning, or mastery. Having team members work in pairs lets the experts share their knowledge and pick up new skills from colleagues, which adds variety to their work and spreads expertise across the team. This builds cross-functional, T-shaped skills, reduces dependence on single specialists, and lets the repetitive work be shared, all of which address the motivation problem directly while improving the team's resilience.
Not this one. Try another answer.
Why C is wrong
Value stream analysis targets waste and delays in the process, not the lack of variety and growth that is lowering motivation.
Not this one. Try another answer.
Why D is wrong
Adding resources does not change the nature of the work and makes the repetitive tasks no more engaging.
Question 6 Play from 11:28
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Escalating to the sponsor bypasses the team and signals a lack of trust in its ability to self-organize.
Not this one. Try another answer.
Why B is wrong
Removing stories distorts the velocity figure without addressing why the team is disengaged.
Not this one. Try another answer.
Why C is wrong
A daily standup is a short planning event for the day and is not designed for exploring morale and root causes.
Right, D is the answer.
Why D is right
Disengagement and falling velocity are signs that something in the way the team works needs attention. A retrospective gives the team a safe, facilitated space to discuss what is affecting motivation, find root causes and agree on improvements it owns. Retrospectives do not have to wait for the end of an iteration; a team can hold one whenever it appears stuck. Facilitating this conversation reflects servant leadership because the practitioner helps the team solve its own problem instead of imposing a fix.
Question 7 Play from 13:28
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The retrospective is the right place for the team to inspect its way of working and agree on improvements. Pair programming, an XP practice, pairs the inexperienced engineer with a more experienced colleague, so knowledge transfers quickly, defects are caught as code is written and the whole team becomes more capable. It addresses the root cause, a skill gap, rather than the symptom, and it reflects collective ownership because the team solves the problem together instead of isolating one person. Over the following iterations velocity should recover as the engineer gains experience.
Not this one. Try another answer.
Why B is wrong
Reprioritizing user stories does nothing about the skill gap, and backlog order belongs to the product owner rather than the retrospective.
Not this one. Try another answer.
Why C is wrong
Re-estimating story points changes the numbers on the plan but does not improve the engineer's capability.
Not this one. Try another answer.
Why D is wrong
Steering easy work to one person limits learning, weakens collective ownership and leaves the gap in place.
Question 8 Play from 15:44
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Discouraging the investigation stifles learning and contradicts the agile emphasis on adapting the approach.
Not this one. Try another answer.
Why B is wrong
Design findings feed the work in progress, and the retrospective is focused on process improvement rather than design results.
Not this one. Try another answer.
Why C is wrong
Demanding a fully developed experiment defeats the purpose of a spike, which is a small, quick investigation.
Right, D is the answer.
Why D is right
Agile teams improve by experimenting and learning quickly. When a team member wants to explore an alternative design, the scrum master should encourage a timeboxed spike or experiment and help the whole team understand how such investigations reduce uncertainty and support continuous improvement. Developers decide how to do their work, so permission is not really the scrum master's to grant; the scrum master's role is to coach and to foster a culture in which trying new approaches is welcomed and the results are shared.
Question 9 Play from 18:14
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Demanding reviews from the product owner is adversarial and ignores ongoing collaboration and refinement of the backlog.
Right, B is the answer.
Why B is right
Agile teams welcome changing requirements, even late, and handle them by working closely with the product owner throughout delivery. Continuous backlog refinement lets incoming change requests be clarified, sized, and ordered by value, while frequent product reviews show customers working increments and gather feedback early. Many changes are absorbed before release instead of piling up afterward, and the team keeps delivering the most valuable items under pressure. Collaboration and short feedback loops are the agile answer to expected change, not tighter upfront control.
Not this one. Try another answer.
Why C is wrong
Detailed upfront specifications assume requirements are fixed, which conflicts with the expected flow of change.
Not this one. Try another answer.
Why D is wrong
Committing to fixed specifications locks in scope that the product owner already expects customers to change.
Question 10 Play from 20:35
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
The iteration retrospective is for the team to improve its own way of working, not to analyze the efficiency of the customer's process activities.
Right, B is the answer.
Why B is right
Determining the efficiency of a set of process activities is the purpose of value stream analysis, a Lean technique. Mapping the value stream shows each step, the time spent adding value and the time spent waiting, so the team can calculate process efficiency, spot delays, handoffs and other waste, and recommend improvements. Reviewing the process value stream therefore gives the customer a direct, evidence-based answer instead of a general discussion, and it can be done now rather than waiting for a scheduled event.
Not this one. Try another answer.
Why C is wrong
Assessing story value helps order the backlog but does not measure how efficiently a process performs.
Not this one. Try another answer.
Why D is wrong
The sprint review inspects the increment and gathers feedback on the product, not a detailed analysis of process efficiency.
Show all 100 questionsShow fewer questions
Question 11 Play from 22:44
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The stakeholders found that completed work did not address their most pressing needs, which means the team built lower-value items first. Before committing to iteration work, the product backlog should be refined and reordered with the product owner and stakeholders so that the highest-value, most urgent requirements are at the top. The team then plans the iteration from those items. Regular reprioritization keeps delivery aligned with current business needs, which change over time.
Not this one. Try another answer.
Why B is wrong
Keeping requirements stable during the iteration does not ensure that the right requirements were chosen.
Not this one. Try another answer.
Why C is wrong
When an item was created has no bearing on its value, so focusing on newer items does not solve the problem.
Not this one. Try another answer.
Why D is wrong
Delivering features instead of components does not prevent the problem, because features can still be the wrong ones if they are not prioritized by value.
Question 12 Play from 24:58
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Periodic cross-organizational meetings add some coordination but leave the gap open between meetings, so issues still surface late.
Not this one. Try another answer.
Why B is wrong
Merging the teams is a disruptive structural change that the situation does not require, since each team already performs well.
Not this one. Try another answer.
Why C is wrong
Writing stories from full technical specifications is a document-heavy approach that does not create the ongoing collaboration the teams lack.
Right, D is the answer.
Why D is right
Both teams perform well on their own, so the integration problems point to a communication gap between them. Co-locating the teams lets members overhear conversations, ask questions as they arise and notice interface mismatches immediately, which is the osmotic communication agile teams rely on. Continuous, informal face-to-face contact surfaces integration concerns as the work is done rather than at hand-off, which is far more effective than occasional formal meetings and fits the agile principle that face-to-face conversation is the most efficient way to convey information.
Question 13 Play from 27:16
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A shared vision and sprint goal describe intent and direction, not daily progress or activity.
Not this one. Try another answer.
Why B is wrong
A release burnup chart tracks completed scope across many iterations rather than daily activity within one.
Not this one. Try another answer.
Why C is wrong
Velocity metrics summarize completed work per iteration and are used for forecasting, not daily status.
Right, D is the answer.
Why D is right
An iteration burndown chart plots the work remaining in the current iteration against the days of the iteration and is updated daily. It is an information radiator that shows stakeholders, at a glance, whether the team is on track to finish the iteration's work and how effort is being consumed day by day. That daily granularity matches the need to report on daily resource and project activities. Other tools describe direction, long-term release progress or historical trends rather than what is happening within the current iteration each day.
Question 14 Play from 29:09
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A release breakdown shows how scope is planned across releases, not the actual progress inspected against a working increment.
Right, B is the answer.
Why B is right
The sprint review is the Scrum event designed for stakeholders. The Scrum Team presents the results of its work to key stakeholders, the increment is inspected, and progress toward the product goal is discussed, with the product backlog adjusted as needed. Inviting the new stakeholder gives them a direct view of what has been done, what remains and how plans are adapting, along with the chance to ask questions and give feedback to the people doing the work. It also starts the regular stakeholder engagement that agile delivery depends on.
Not this one. Try another answer.
Why C is wrong
Progress radiators show charts without the conversation and inspection of working product a new stakeholder needs to understand status.
Not this one. Try another answer.
Why D is wrong
Sprint planning is where the Scrum Team plans the coming sprint and is not the place to brief a stakeholder on overall status.
Question 15 Play from 31:21
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Emailing and waiting replaces collaboration with a slow handoff and may leave the story unclear.
Not this one. Try another answer.
Why B is wrong
The product owner, not the team alone, is accountable for clarifying what the story requires.
Right, C is the answer.
Why C is right
Backlog refinement, often called story grooming, is the ongoing activity in which the product owner and the developers add detail, acceptance criteria and estimates to upcoming product backlog items so they are ready for sprint planning. When a story needs more detail before planning, the scrum master should schedule a grooming session with the product owner and the team. The conversation clarifies the story, answers questions and ensures the team can plan the work with confidence.
Not this one. Try another answer.
Why D is wrong
Planning poker estimates a story but does not supply the missing details about it.
Question 16 Play from 33:21
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A RACI chart maps roles and accountability but does not explain the risks or their impact.
Not this one. Try another answer.
Why B is wrong
A Gantt chart with slack is a schedule tool and does not communicate specific risks or their impact.
Not this one. Try another answer.
Why C is wrong
A communications management plan defines who communicates what, not an understandable view of the risks themselves.
Right, D is the answer.
Why D is right
A risk burndown chart is an information radiator that plots the total risk exposure (typically probability multiplied by impact for each risk) over time. It makes the project risks and their potential impact visible in a simple, graphical form that every team member can read at a glance, and it shows how the team's risk response work is reducing exposure sprint by sprint. That visibility helps the team member understand both what the risks are and how much they matter, which is exactly the communication need described.
Question 17 Play from 35:35
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Stopping the iteration is a drastic disruption to delivery for a process issue that can wait for the retrospective.
Not this one. Try another answer.
Why B is wrong
Planning focuses on what work to take on next, while process improvement belongs in the retrospective.
Right, C is the answer.
Why C is right
Inconsistent defect information is a process problem within the team's own way of working, and the retrospective is the event designed for inspecting and adapting the process. At the next retrospective the team can generate insights into why defect reports vary, agree on what information a defect must contain, and own the resulting change. Because the team decides the improvement itself, it is more likely to be adopted and sustained than a rule imposed from outside.
Not this one. Try another answer.
Why D is wrong
Placing corrective actions in the backlog for the team to execute presumes the solution instead of letting the team inspect and agree on it.
Question 18 Play from 37:59
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The problems concern how the team and the product owner work together: task direction that distracts team members and slow answers on backlog prioritization. The iteration retrospective is the event designed for inspecting people, relationships, processes, and tools, and the product owner takes part as a member of the team. Raising both issues there lets everyone discuss the impact openly, clarify expectations about who manages tasks and how quickly prioritization questions are answered, and agree on concrete improvements together. Solutions the whole team agrees on are more likely to stick than a fix imposed by one person.
Not this one. Try another answer.
Why B is wrong
Agile teams manage their own tasks, so directing tasks is not the project manager's job either.
Not this one. Try another answer.
Why C is wrong
A private discussion with the product owner leaves the team out of agreeing how it wants to work with the product owner.
Not this one. Try another answer.
Why D is wrong
Extra hours are not sustainable and do not correct the product owner's misplaced focus.
Question 19 Play from 40:13
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Feature-driven development centers on feature design and ownership roles, not WIP control.
Not this one. Try another answer.
Why B is wrong
Extreme Programming emphasizes engineering practices such as pairing and test-driven development rather than WIP limits.
Not this one. Try another answer.
Why C is wrong
Scrum adds defined roles, events and artifacts, which is more overhead than management wants, and does not use explicit WIP limits.
Right, D is the answer.
Why D is right
Kanban is a lightweight method that can be applied to existing processes with minimal overhead, since it prescribes no new roles or mandatory ceremonies. Its core practices are visualizing work and limiting work in process (WIP), which give teams direct control over how much work is underway and expose queues and bottlenecks. Managing flow this way reduces waste such as partially done work and waiting, matching management's goals for the transformation.
Question 20 Play from 42:10
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Running regression tests on legacy functionality does not prepare the team to build the new stories.
Not this one. Try another answer.
Why B is wrong
The customer helps define acceptance tests, but asking the customer to write them alone hands off work the team should lead collaboratively before coding.
Not this one. Try another answer.
Why C is wrong
Coding before the tests exist removes the clear target that test-first development provides.
Right, D is the answer.
Why D is right
With clear, detailed requirements agreed, the next step in a test-first approach such as acceptance test-driven development or behavior-driven development is to write the tests that define when each story is correctly built. These acceptance tests turn the requirements into concrete, verifiable examples, confirm shared understanding with the customer, guide the coding and support the definition of done. Writing them before development begins reduces defects and rework because everyone knows exactly what done looks like for each story.
Question 21 Play from 44:23
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Raising the member's impediments publicly before trust exists puts them on the spot and deepens the reluctance.
Not this one. Try another answer.
Why B is wrong
Promising that input is valued and then staging a demonstration in a group meeting still exposes a reluctant member before trust has been built.
Not this one. Try another answer.
Why C is wrong
Handing the member to a senior leader adds hierarchy and focuses on productivity rather than on the member's trust and impediments.
Right, D is the answer.
Why D is right
The new member is reluctant to communicate because of poor experiences on a previous team, so trust must be rebuilt before the member will speak freely in a group. A servant leader meets privately with the member, listens, and works with them to address any impediments they face. A one-on-one setting removes the pressure of an audience, shows that the leader genuinely cares about the member's concerns, and demonstrates through action that raising impediments leads to help. That foundation of trust allows the member to integrate into the mature team over time.
Question 22 Play from 46:39
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The conflict is about whether a deliverable is complete, which is exactly what the definition of done (DoD) settles. The agile leader should facilitate team agreement on a shared DoD as part of team chartering, the working agreements the team establishes and can revisit at any point. A clear, agreed DoD removes ambiguity about completion, resolves the present dispute on objective grounds and prevents the same argument from recurring on later deliverables.
Not this one. Try another answer.
Why B is wrong
Motivating the team during storming does not resolve the underlying disagreement about what done means.
Not this one. Try another answer.
Why C is wrong
Clearer user stories help understanding of scope but do not establish the shared quality standard for completion.
Not this one. Try another answer.
Why D is wrong
Splitting epics improves story size and clarity but does not define when a deliverable is done.
Question 23 Play from 48:49
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Team capacity is useful only once the size of the backlog work is known, so it follows estimation.
Not this one. Try another answer.
Why B is wrong
Determining how much work can be delivered requires sized backlog items and a velocity, so it comes later.
Not this one. Try another answer.
Why C is wrong
Fitting work into the next iteration is an iteration planning activity that depends on estimated backlog items.
Right, D is the answer.
Why D is right
With scope and acceptance criteria defined and a release target at the end of the next quarter, the team is doing release planning. The first planning step is to estimate the product backlog items, usually in story points, so the total size of the release is known. Only then can the team apply its velocity to judge how much work fits in the release and in each iteration. Without sized backlog items, capacity figures have nothing to be compared against and any forecast of the release date would be a guess.
Question 24 Play from 50:43
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Budget influence matters, but it is a narrower impact than blocking the project's goals.
Right, B is the answer.
Why B is right
Stakeholders are prioritized by their power to influence the project and the size of the impact they can have. The stakeholder who can prevent the project from achieving its goals can have the greatest impact of all, because the goals are the reason the project exists and the source of its value. Budget overruns and delays are serious, but they are narrower than outright failure to reach the objectives. This stakeholder needs the closest engagement: understanding their concerns early, keeping them informed and involving them in key decisions.
Not this one. Try another answer.
Why C is wrong
A stakeholder who can cause delays affects the timeline but not, by themselves, whether the goals are achieved.
Not this one. Try another answer.
Why D is wrong
A friendly stakeholder who helps with the list has little influence over the project's outcome.
Question 25 Play from 52:45
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Psychological safety is essential for an effective retrospective, and signs of conflict make it more important to set the stage carefully. Reviewing the team's established ground rules at the start reminds everyone of the behaviors they agreed to, such as listening without interrupting, focusing on issues rather than people and assuming good intent. This frames the discussion, creates an open and safe environment and allows the conflict to be addressed constructively during the retrospective.
Not this one. Try another answer.
Why B is wrong
Questioning individuals about the cause beforehand can feel like an interrogation and raise tension.
Not this one. Try another answer.
Why C is wrong
Pressing on with work ignores the conflict and does nothing to create a safe environment.
Not this one. Try another answer.
Why D is wrong
Taking a team matter to the product owner and stakeholders bypasses the team and reduces trust.
Question 26 Play from 54:47
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Resolving the disagreement for the team is directive and undermines self-organization; servant leaders facilitate rather than decide.
Right, B is the answer.
Why B is right
A newly formed team is expected to go through a storming stage as members learn to work together. The scrum master supports self-organization by encouraging the team to keep working through its disagreements, coaching and facilitating where helpful but not taking over. Resolving their own differences builds trust, shared working agreements, and ownership of how they plan the sprint, helping the team progress toward norming and performing.
Not this one. Try another answer.
Why C is wrong
Telling the team the correct course of action removes their ownership of how they work.
Not this one. Try another answer.
Why D is wrong
Removing members is a drastic, punitive step that ignores normal team development.
Question 27 Play from 56:48
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Focusing on ceremonies and methods teaches the mechanics of agile without the underlying values that resolve differing agendas.
Not this one. Try another answer.
Why B is wrong
Performance and chain of command reflect a hierarchical, command-and-control approach that conflicts with agile self-organization.
Not this one. Try another answer.
Why C is wrong
Deliverables, procedures and features are product and process details rather than the core principles and values of agile.
Right, D is the answer.
Why D is right
A team whose members follow their own agendas needs a common foundation, and the core of agile is a mindset rather than a set of rituals. Emphasizing collaboration, the delivery of customer value and a shared mindset aligns everyone with the Agile Manifesto values and principles, such as individuals and interactions and customer collaboration. Once the team shares these values, the specific practices make sense and members can work toward a common goal instead of their individual habits.
Question 28 Play from 58:59
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Once the product owner has placed the priority stories into the iteration backlog, the developers self-organize to work out how the stories will be delivered. They break each story into tasks together, discuss approach and dependencies, and let members pull work according to skills and capacity. Self-organization is the agile expectation for a team at any stage, including a newly formed one, and it builds shared ownership of the iteration plan. No outside party assigns tasks, and the planning meeting already has the people it needs.
Not this one. Try another answer.
Why B is wrong
Assigning tasks to each person is command and control and replaces the team pulling work collectively.
Not this one. Try another answer.
Why C is wrong
Clarifying needs comes through the product owner in refinement and planning, and it is not the first step in defining tasks.
Not this one. Try another answer.
Why D is wrong
The scrum master role is established before planning, and identifying it does nothing to define the tasks.
Question 29 Play from 1:00:57
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
The customer is represented by the product owner and is not needed to work through technical implementation needs.
Not this one. Try another answer.
Why B is wrong
Key stakeholders do not do the work, and leaving out the core team removes the people who must plan the technical solution.
Not this one. Try another answer.
Why C is wrong
The customer and sponsor cannot plan the technical work, and this pairing omits both the team and the product owner.
Right, D is the answer.
Why D is right
A meeting at the start of the sprint to work through what a story needs should include the people doing the work and the person who can clarify it. The core team members contribute the technical knowledge and plan how to build the database feature, while the product owner explains the intent, value and acceptance criteria and answers questions about scope. Bringing the team and product owner together creates a shared understanding of the requirement without involving people who add little to the technical discussion.
Question 30 Play from 1:02:48
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Estimates belong to the developers who will do the work, not to the scrum master, so this undermines team ownership and accuracy.
Not this one. Try another answer.
Why B is wrong
Velocity cannot be applied to stories that have not yet been sized, so selecting stories by velocity skips a necessary step.
Right, C is the answer.
Why C is right
The product owner has just presented new epics and stories, so the work has not yet been sized. To answer the sponsor's question about delivery, the developers should first hold an estimation session (for example, relative sizing with planning poker) to estimate the stories. Once the stories carry estimates, the established team can apply its known velocity to forecast how many iterations the features will take and give the sponsor a realistic, evidence-based range. Estimates come from the people doing the work, which keeps the forecast credible and builds commitment to the release plan.
Not this one. Try another answer.
Why D is wrong
Historical project completion data does not describe the size of these new epics, so it cannot answer when these specific features will be delivered.
Question 31 Play from 1:05:04
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Estimating only functional requirements ignores the non-functional requirement that must be delivered.
Not this one. Try another answer.
Why B is wrong
Adding people does not change capacity quickly and new members usually slow the team at first.
Not this one. Try another answer.
Why C is wrong
Referring the issue onward leaves the work too large; the team should first split it into deliverable parts.
Right, D is the answer.
Why D is right
When an important piece of work is too large for the sprint, the agile response is to split it rather than force it in or drop it. The team can break the non-functional requirement into smaller, independently verifiable parts, for example by component, threshold or scenario, and deliver the parts that fit within the sprint capacity while ordering the remainder for following sprints with the product owner. This keeps commitments realistic, lets the team make real progress on the requirement now and preserves a sustainable pace.
Question 32 Play from 1:07:08
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Avoidance leaves the frustration unresolved and lets the disengagement continue.
Not this one. Try another answer.
Why B is wrong
Forcing imposes a win-lose outcome that may gain attendance but harms trust and commitment.
Not this one. Try another answer.
Why C is wrong
Accommodation gives in to the designer's preference and ignores the team's legitimate concern.
Right, D is the answer.
Why D is right
The designer skips most meetings and the team is frustrated, so the conflict concerns both the designer's needs and the team's need for engagement. Collaborating, also called problem solving, brings everyone together to discuss the underlying concerns openly, such as which meetings the designer finds valuable and what the team needs from them. It aims for a solution all parties commit to, preserves relationships, and reinforces shared ownership, which makes it the most effective and lasting method here.
Question 33 Play from 1:09:02
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Agile teams provide stakeholders with transparent, self-service access to project information through information radiators such as dashboards and burn charts. When a new stakeholder lacks the financial data they need, the product owner can work with the scrum master to give them access to the relevant radiator, which already displays the information. This answers the need quickly, keeps the data consistent for everyone, and avoids pulling developers away from their work to produce custom reports.
Not this one. Try another answer.
Why B is wrong
Sprint planning is for the scrum team to plan the sprint, not a forum for stakeholder questions about finances.
Not this one. Try another answer.
Why C is wrong
Asking the team to compile data in the next iteration delays the stakeholder and diverts developers from product work.
Not this one. Try another answer.
Why D is wrong
Redirecting the stakeholder to the team interrupts developers and does not create lasting access to the information.
Question 34 Play from 1:11:13
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Handing testing to a separate team breaks cross-functionality and produces work that is not done or shippable.
Not this one. Try another answer.
Why B is wrong
Dashboards improve visibility but do not themselves deliver product value to customers.
Right, C is the answer.
Why C is right
Agile teams deliver value by frequently producing working, usable increments. Working closely with the product owner, who orders the product backlog by value, the team turns the highest-value backlog items into potentially shippable increments that meet the definition of done. Each increment can be reviewed, released and used, which provides early value, generates feedback and lets the product evolve toward what customers actually need. That is the most direct way for the teams to increase value delivery.
Not this one. Try another answer.
Why D is wrong
Meeting deadlines and sharing budgets is a plan-driven focus on constraints, not on delivering value incrementally.
Question 35 Play from 1:13:25
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Capacity and competence profiles are internal team information and do not keep stakeholders up to date on progress.
Not this one. Try another answer.
Why B is wrong
A list of tools is static detail that tells stakeholders nothing about frequent progress updates.
Not this one. Try another answer.
Why C is wrong
A list of open technical issues is a narrow team-level view, not a full picture of project status.
Right, D is the answer.
Why D is right
Information radiators, such as burnup and burndown charts, task boards and release progress displays, show the project's current status in a form that is easy to take in at a glance. Including up-to-date radiators in an extended stakeholder report gives every current and future stakeholder the same transparent, frequently refreshed view of progress, so they can follow the frequent updates without needing extra explanation. This supports the transparency and stakeholder engagement that agile depends on.
Question 36 Play from 1:15:19
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A spike targets technical uncertainty, while the problem here is unclear functional behavior that the customer cannot yet explain.
Not this one. Try another answer.
Why B is wrong
An iteration 0 is setup work at the start of a project and is a heavier response than needed for clarifying one feature.
Not this one. Try another answer.
Why C is wrong
Decomposing the feature into stories requires an understanding of the functionality that the customer has not yet been able to provide.
Right, D is the answer.
Why D is right
When a customer cannot fully describe how a feature should work, agile teams do not demand a complete specification up front. Instead, the agile project manager facilitates a just-in-time exploration in which the customer and the team examine the functionality together close to when it will be built, using conversations, examples, sketches or quick prototypes. Requirements emerge through this collaboration, and the details are discovered at the last responsible moment, when the most information is available and the cost of change is lowest.
Question 37 Play from 1:17:40
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Velocity from previous projects reflects different teams, work and contexts, so it does not represent this new team's capability.
Not this one. Try another answer.
Why B is wrong
Averaging individual opinions produces a guess rather than a measure, since velocity comes from what the team actually completes.
Not this one. Try another answer.
Why C is wrong
A sponsor cannot supply a team's velocity, and imposing a figure from outside undermines the team's ownership of its estimates.
Right, D is the answer.
Why D is right
Velocity is an empirical measure of what a specific team actually completes in a sprint, so a newly formed team has no velocity yet. The scrum master should explain this to the product owner and help the team run several sprints, after which an average of the completed points gives a reliable velocity for forecasting. Until then, the team can forecast each sprint from its capacity, but any number given now would be a guess, and setting expectations on it would risk disappointment and loss of trust.
Question 38 Play from 1:19:59
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Planned percent complete reports schedule progress but does not reduce investment risk.
Right, B is the answer.
Why B is right
Stakeholders worried about failure on a large investment are reassured when value and learning arrive early. Planning the product as many small minimally marketable features, each the smallest set of functionality that delivers recognizable value to customers, allows incremental release and earlier returns. Each delivery validates assumptions and gives the stakeholders a decision point to continue, change direction or stop, so the investment is exposed in smaller steps and the risk of total failure is reduced.
Not this one. Try another answer.
Why C is wrong
Story points are a relative sizing unit and do not reassure stakeholders about failure.
Not this one. Try another answer.
Why D is wrong
Earned value measures performance against plan after work starts and does not reduce the risk of the investment.
Question 39 Play from 1:22:14
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Reinforcing existing processes assumes they are sound and skips understanding why the mistake happened.
Not this one. Try another answer.
Why B is wrong
Mandating peer reviews imposes a fix without diagnosis and bypasses the team's own improvement decisions.
Right, C is the answer.
Why C is right
The scrum master should treat the mistake as a learning opportunity rather than a matter of blame. Facilitating a retrospective lets the team examine what happened, find root causes in the process or environment and agree on improvement actions. This supports psychological safety, so people feel able to surface problems, and turns the mistake into continuous improvement for the whole team.
Not this one. Try another answer.
Why D is wrong
Rewarding low error counts encourages hiding mistakes and undermines psychological safety.
Question 40 Play from 1:24:04
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Technical debt is real work that competes for the same capacity as new features, so it should be made visible in the product backlog. The team adds the code cleanup items to the product backlog, explains their impact on quality, risk, and future velocity, and asks the product owner to prioritize them. This respects the product owner's accountability for ordering the backlog while giving the developers a transparent way to advocate for paying down debt. The prioritized cleanup work can then be pulled into upcoming iterations during planning.
Not this one. Try another answer.
Why B is wrong
Placing cleanup work directly into the iteration bypasses backlog ordering, and the product owner is not the person to clarify technical cleanup tasks.
Not this one. Try another answer.
Why C is wrong
Nothing justifies cancelling the current iteration, which is a drastic step reserved for when its goal becomes obsolete.
Not this one. Try another answer.
Why D is wrong
A separate release backlog fragments the work, and the product owner is not responsible for producing technical documentation about the debt.
Question 41 Play from 1:26:33
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Sorting by story points orders the backlog by size, which has no connection to value.
Right, B is the answer.
Why B is right
Value-driven delivery is the main principle for ordering a product backlog: the features that deliver the most value to customers and the business come first. The agile practitioner should coach the product owner to rank items by business value, weighing risk, dependencies and cost against that value with techniques such as MoSCoW or relative value scoring. Putting the highest-value work first maximizes return early, gives stakeholders useful increments sooner, and means that if the project ends early, the most important work has already been done.
Not this one. Try another answer.
Why C is wrong
Risk is one factor to weigh, but releasing whatever is riskiest first ignores the value it delivers.
Not this one. Try another answer.
Why D is wrong
Defining a minimum viable product applies to a launch decision and does not give a method for ordering an existing backlog.
Question 42 Play from 1:28:50
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Starting a backlog item without consulting the product owner risks working on something that is not the highest priority.
Not this one. Try another answer.
Why B is wrong
The scrum master does not order the backlog or choose work for the team.
Right, C is the answer.
Why C is right
The product owner is accountable for the product backlog and its ordering, so when the team finishes the sprint goal early, it should go to the product owner to identify the next item to work on. The developers and the product owner then agree on what can realistically be added to the sprint. This keeps the most valuable work flowing and respects the roles: the product owner decides what is most valuable next, while the developers decide how much they can take on.
Not this one. Try another answer.
Why D is wrong
Deciding jointly with the scrum master still leaves out the product owner, who owns the backlog order.
Question 43 Play from 1:30:46
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Seeking one-time agreement on all requirements with every stakeholder is a big-upfront approach and does not keep understanding aligned as work proceeds.
Not this one. Try another answer.
Why B is wrong
Planning only every four iterations reduces the frequency of alignment and lets misunderstandings grow between planning points.
Right, C is the answer.
Why C is right
Misunderstandings between the team and business stakeholders are best removed through frequent inspection of working product. At each sprint review the team demonstrates the increment and stakeholders give feedback, and using that feedback when planning the next sprint shows stakeholders that their input shapes the work. Over successive sprints this feedback loop converges the team's and the stakeholders' understanding of what completing each epic requires, replacing assumptions with evidence from the actual product.
Not this one. Try another answer.
Why D is wrong
Stating the reasons for the project in a contract does not create the ongoing collaboration needed to resolve disagreements about the epics.
Question 44 Play from 1:32:50
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
DISC is a behavioral assessment model describing four styles: dominance, influence, steadiness and conscientiousness. Using it with each team member helps the agile leader understand individual personalities, communication preferences and motivators, which can explain why someone has become quiet and disengaged. The leader can then adapt how they engage that person and help the team understand one another, supporting collaboration and psychological safety.
Not this one. Try another answer.
Why B is wrong
MoSCoW is a requirements prioritization technique and reveals nothing about personalities or motivators.
Not this one. Try another answer.
Why C is wrong
A SAFe coach supports scaling agile across teams and is not a means of identifying individual personalities.
Not this one. Try another answer.
Why D is wrong
Big design up front is a design approach and has nothing to do with understanding team members.
Question 45 Play from 1:34:50
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Scrum master is a specific Scrum accountability, while the advice describes a leadership approach applicable to any project manager.
Not this one. Try another answer.
Why B is wrong
A people manager handles line responsibilities such as staffing and appraisals, not the team-serving stance described.
Right, C is the answer.
Why C is right
Servant leadership is the practice of leading by serving the team: understanding its needs, supporting its growth, and removing obstacles so it can deliver. The coach's advice to continuously improve support for the team and clear impediments describes exactly this leadership style. In agile environments, project managers are encouraged to adopt servant leadership rather than command-and-control behavior, focusing on enabling self-organizing teams to do their best work.
Not this one. Try another answer.
Why D is wrong
Squad leader is not a standard agile role and does not capture leading through service.
Question 46 Play from 1:36:40
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
High-risk and high-value features are tackled first to deliver value and reduce uncertainty early, not deferred.
Not this one. Try another answer.
Why B is wrong
High-risk and low-value features are avoided altogether rather than simply scheduled for a later iteration.
Right, C is the answer.
Why C is right
In the value and risk prioritization model, high-value and high-risk features are done first, so the team delivers important functionality while retiring risk early. High-value and low-risk features come next. Low-value and low-risk features are done last, so these are the items the team defers to later iterations, and some may never be needed. Low-value and high-risk features fall into a separate category: they are avoided, because they bring risk without enough benefit to justify it.
Not this one. Try another answer.
Why D is wrong
Low-risk and high-value features deliver significant value with little uncertainty, so they are scheduled early.
Question 47 Play from 1:38:31
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
A story is done only when it meets its acceptance criteria and delivers what the customer needs. When the customer representative shows during the review that the story does not satisfy the scope of work, declaring it complete would misreport progress and ignore valid customer feedback. The honest and transparent response is to treat the story as incomplete, return it to the product backlog and have the product owner prioritize the remaining work, typically for the next sprint. This keeps velocity and progress reporting accurate and keeps the customer engaged in defining value.
Not this one. Try another answer.
Why B is wrong
The product owner represents the customer and cannot override clear evidence that the agreed scope has not been met.
Not this one. Try another answer.
Why C is wrong
Discarding the story hides unfinished work and loses the history and effort already invested in it.
Not this one. Try another answer.
Why D is wrong
The team finishing its tasks does not make the story complete when the customer shows the scope is not satisfied.
Question 48 Play from 1:40:44
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Better testing skills improve quality but do not clarify how the features should work.
Not this one. Try another answer.
Why B is wrong
More planning sessions rely on speculation instead of real user feedback.
Not this one. Try another answer.
Why C is wrong
Predictive approaches suit stable, well-understood requirements, not high uncertainty.
Right, D is the answer.
Why D is right
When the goals are clear but how certain features should work is uncertain, the best way to reduce uncertainty is to learn from users quickly. A prototype lets users see and try the proposed behavior so the product owner can gather feedback, validate assumptions and refine the product backlog before the team invests heavily in full development. This applies validated learning and short feedback loops, which suit high-uncertainty environments far better than more planning or analysis.
Question 49 Play from 1:42:52
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Small user stories are the main lever for predictable flow. They are easier to understand and estimate, move through the workflow quickly and carry less hidden risk, so cycle times become shorter and less variable. Finishing small items often creates a steady stream of completed work, faster feedback and more reliable forecasts. Large items, by contrast, block work in progress, cause uneven throughput and make forecasts unreliable.
Not this one. Try another answer.
Why B is wrong
Simple acceptance criteria may hide necessary conditions and do not by themselves smooth the flow of work.
Not this one. Try another answer.
Why C is wrong
Lean features is not an established agile practice for creating flow, and features are usually too large to flow smoothly.
Not this one. Try another answer.
Why D is wrong
Keeping the backlog lean reduces waste in refinement but does not make the flow of work through the team predictable.
Question 50 Play from 1:44:36
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Story size is estimated with techniques such as story points, planning poker or affinity estimating.
Right, B is the answer.
Why B is right
MoSCoW is a prioritization technique that sorts requirements or user stories into must have, should have, could have and will not have this time. Teams and product owners use it to agree which items are essential for a release or time box and which can be deferred, making value-based trade-offs explicit when time or capacity is limited. It says nothing about the size of an item or the progress made on it.
Not this one. Try another answer.
Why C is wrong
Product validation relies on customer feedback, demonstrations and acceptance testing.
Not this one. Try another answer.
Why D is wrong
Progress is tracked with burndown or burnup charts, task boards and other information radiators.
Question 51 Play from 1:46:13
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Recurring problems across iterations call for inspection and adaptation, which is exactly what retrospectives provide. Holding retrospectives frequently gives the team a regular, safe forum to examine why the same issues keep appearing, evaluate the suggestions team members already have, and agree on concrete improvement actions. Sharing responsibility for making the changes builds collective ownership, so improvements are actually carried out and followed up rather than left to one person. This reflects the agile principle that at regular intervals the team reflects on how to become more effective and adjusts its behavior accordingly.
Not this one. Try another answer.
Why B is wrong
Accepting recurring problems as inevitable and simply working harder ignores continuous improvement and risks an unsustainable pace.
Not this one. Try another answer.
Why C is wrong
Discussing feedback privately with the product owner removes transparency and takes the improvement decision away from the self-organizing team.
Not this one. Try another answer.
Why D is wrong
Nothing indicates a trust problem, and a team-building exercise does not address the specific process issues the team keeps encountering.
Question 52 Play from 1:48:43
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Agile welcomes changing requirements, even late, to deliver customer advantage. The product owner is accountable for maximizing value and owns the product backlog, so when market conditions change they should explain the business need to the team, so everyone understands why the change matters, and refine the product backlog to reflect the new features and their order. Plans for later sprints are adapted through the backlog, which keeps the team aligned with the product goal and the market.
Not this one. Try another answer.
Why B is wrong
Delegating the change discussion to the team abdicates the product owner's responsibility for the product backlog.
Not this one. Try another answer.
Why C is wrong
Prioritization belongs to the product owner, not to a meeting with a team lead.
Not this one. Try another answer.
Why D is wrong
The product owner seeks input from the team but remains accountable for backlog order, so prioritizing with the team is not the product owner's own action.
Question 53 Play from 1:50:56
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Labeling the chores low priority overrides the team's input and ignores the efficiency gains, and the coach does not own backlog order.
Not this one. Try another answer.
Why B is wrong
Handing the chores to another team removes them from the people who understand and benefit from them and does not resolve the prioritization question.
Not this one. Try another answer.
Why C is wrong
Escalating to a steering committee is unnecessary when the product owner and team can resolve the trade-off themselves through collaboration.
Right, D is the answer.
Why D is right
The conflict is a prioritization question between a vital requirement and improvement chores that would raise the team's productivity. The product owner is accountable for ordering the backlog, and the developers understand the cost and benefit of the chores, so the agile coach should facilitate a conversation in which both sides share their information and reach a transparent decision. This respects each role, lets the team explain how the chores increase future capacity, and lets the product owner weigh that long-term gain against the immediate business value of the requirement.
Question 54 Play from 1:53:24
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
When the risk profile exceeds the tolerance threshold, the team must reduce exposure proactively. In agile, risk responses are handled as work: mitigation tasks are added to the backlog, forming a risk-adjusted backlog, and the product owner orders them alongside features based on value and risk reduction. Prioritizing them into the current and upcoming sprints makes the response visible and ensures it is actually delivered, and progress can be tracked with tools such as a risk burndown chart.
Not this one. Try another answer.
Why B is wrong
Padding every requirement with time is not a targeted response, and it hides the mitigation work instead of making it visible and prioritized.
Not this one. Try another answer.
Why C is wrong
A fixed capacity reserve is arbitrary and does not identify or order the specific actions needed to bring the risks back within tolerance.
Not this one. Try another answer.
Why D is wrong
Waiting for risks to become issues abandons proactive risk management when exposure is already beyond tolerance.
Question 55 Play from 1:55:46
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A meeting to find out why risks are not followed up investigates blame rather than making risk status visible.
Not this one. Try another answer.
Why B is wrong
Reviewing executed tasks looks backward and does not keep risk status continuously visible.
Right, C is the answer.
Why C is right
Making risks visible is the agile way to ensure they are followed up. Displaying the risks, assumptions, issues and dependencies (RAID) log as an information radiator shows the status of the major risks to everyone at all times, so the team sees which threats to the release date are unaddressed and who owns them. This transparency prompts the team to act on risks during its normal work and events, such as the daily standup, without the project manager having to chase individuals.
Not this one. Try another answer.
Why D is wrong
Dedicating a whole sprint to risk follow-up delays value delivery and treats risk management as a separate phase.
Question 56 Play from 1:58:10
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Pushing ahead with implementation while the technical approach is unresolved invites rework and quality problems.
Right, B is the answer.
Why B is right
A spike is a short, time-boxed piece of research or prototyping used to reduce technical uncertainty before committing to an approach. When a technical challenge is delaying a story, the scrum master should coach the team to run a spike so it can explore options, learn quickly and settle the technical approach. The outcome of the spike lets the team implement the story with confidence and produce better estimates, which reduces the risk of rework and wasted effort from pushing ahead on an unproven design.
Not this one. Try another answer.
Why C is wrong
Handing the story to another team creates a dependency and prevents this team from building its own capability.
Not this one. Try another answer.
Why D is wrong
Deprioritizing the story and waiting does nothing to resolve the uncertainty, which only the team's investigation will reduce.
Question 57 Play from 2:00:26
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
A limit on concurrent users is a technical constraint, and the developers are the people best placed to investigate it. In keeping with self-organization, the team should take the concern raised at the daily stand-up and conduct focused research, often as a time-boxed spike, to understand the limitation and find a viable solution. This produces facts rather than guesses, lets the team bring concrete options and their trade-offs to the product owner, and resolves the risk early before more work is built on the technology.
Not this one. Try another answer.
Why B is wrong
Replacing the technology is a large, premature decision made before the team has investigated the limitation or its options.
Not this one. Try another answer.
Why C is wrong
Customers are not the right people to resolve a technical constraint, and going to them directly bypasses the product owner.
Not this one. Try another answer.
Why D is wrong
Discussing requirements with the product owner does not tell the team whether the technology can be made to work, so the constraint stays unresolved.
Question 58 Play from 2:02:40
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Routing the issue through a project manager bypasses the scrum team, which owns its own improvement.
Not this one. Try another answer.
Why B is wrong
Guidelines written by the scrum master are imposed on the team rather than created and owned by it.
Right, C is the answer.
Why C is right
The underestimated story has already been handled within the sprint by decomposing the work and returning items to the backlog. The next step for the scrum master is to help the team learn from it: in the sprint retrospective, the scrum master facilitates a discussion of why the complexity was missed, such as unclear stories or insufficient refinement, and the team creates its own action plan to avoid a repeat. This keeps improvement in the team's hands and turns the event into lasting learning.
Not this one. Try another answer.
Why D is wrong
Stepping back entirely abandons the scrum master's role of facilitating the team's inspection and adaptation.
Question 59 Play from 2:04:57
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Networking builds professional contacts outside the team and does not address sensitivity to team diversity.
Right, B is the answer.
Why B is right
Social awareness, a component of emotional intelligence, is the ability to perceive and understand the feelings, needs and perspectives of others, including people of different ages, cultures, genders, personalities and backgrounds. When planning a team-building event for a diverse team, the leader needs this skill to choose activities that are inclusive and comfortable for everyone and that build trust rather than alienating some members. Sensitivity to these differences is what makes the event effective at bringing the team together.
Not this one. Try another answer.
Why C is wrong
Communication matters in every situation, but it does not specifically address understanding diverse needs and perspectives.
Not this one. Try another answer.
Why D is wrong
Leadership is a broad capability and does not name the specific skill of reading and respecting differences among people.
Question 60 Play from 2:06:53
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Escalating to the scrum master is unnecessary when the product owner can address the stakeholder directly.
Not this one. Try another answer.
Why B is wrong
A more rigorous change governance slows responsiveness and runs against agile principles.
Right, C is the answer.
Why C is right
Agile approaches welcome changing requirements, even late in development, because they help the customer gain a competitive advantage. A stakeholder who is uncomfortable with frequent change may expect a traditional, fixed-scope approach. The product owner should coach the stakeholder on agile principles, explaining how short iterations, continuous prioritization of the product backlog, and frequent feedback keep the product aligned with the most valuable needs and manage the effect of change.
Not this one. Try another answer.
Why D is wrong
Limiting scope changes discards the value of adapting to new information.
Question 61 Play from 2:08:42
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Adding more people does not stop the key resource from multitasking and creates onboarding overhead of its own.
Not this one. Try another answer.
Why B is wrong
Time management training puts the burden on the individual while the structural multitasking problem remains.
Right, C is the answer.
Why C is right
Constant switching between projects causes heavy context-switching losses, slows every project the person works on and leads to overload and burnout. Agile favors stable, dedicated team members who focus on one body of work, which keeps flow and velocity predictable. Because resource allocation across projects is an organizational decision, the agile project leader should work with management to make the key resource available to one project at a time. This removes the impediment at its root instead of treating its symptoms.
Not this one. Try another answer.
Why D is wrong
Letting the switching continue keeps the overload and context-switching waste that are already hurting the work.
Question 62 Play from 2:10:53
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Frequent integration is a beneficial agile practice that reduces risk rather than creating it.
Right, B is the answer.
Why B is right
Agile relies heavily on conversation to build shared understanding of user stories, with the story card serving as a reminder for a discussion rather than a full specification. When team members are distributed, those informal conversations happen less often, so members may interpret stories differently. This lack of shared knowledge of user stories leads to misaligned work, rework and defects, making it a key risk for distributed agile teams that must be offset with deliberate communication and refinement practices.
Not this one. Try another answer.
Why C is wrong
Teaching agile in several locations is a logistical matter, not a core delivery risk.
Not this one. Try another answer.
Why D is wrong
Agile defines clear team roles, and distribution does not inherently make the team structure unclear.
Question 63 Play from 2:12:45
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
A recurring bottleneck caused by only two database engineers shows the team is not cross-functional enough for its work. Proposing that other developers train in database skills builds T-shaped team members who can share the load, reduces dependency on specialists and increases the team's flow and resilience. The issue has already surfaced in several retrospectives, so it is time to act on the root cause rather than wait or reduce delivery.
Not this one. Try another answer.
Why B is wrong
The bottleneck has already been confirmed over several retrospectives, so further waiting only prolongs it.
Not this one. Try another answer.
Why C is wrong
Planning fewer stories treats the symptom and lowers delivery without removing the skill dependency.
Not this one. Try another answer.
Why D is wrong
Removing valuable stories because of a team skill gap sacrifices customer value instead of fixing the team's capability.
Question 64 Play from 2:14:58
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Planning is a working session for the scrum team to forecast and plan the sprint, not an event aimed at stakeholders.
Not this one. Try another answer.
Why B is wrong
The daily scrum is a short event for the developers to inspect progress and adapt their plan, not a stakeholder forum.
Right, C is the answer.
Why C is right
The sprint demo, or sprint review, is the event designed for stakeholders. The scrum team shows the increment, and stakeholders discuss progress, give feedback and help adapt the product backlog. For an IT director who oversees several initiatives and is not involved in the details, the review offers a concise view of real progress and a direct chance to influence direction without taking part in the team's working sessions.
Not this one. Try another answer.
Why D is wrong
The retrospective is for the scrum team to examine its own way of working, and outside attendees can reduce psychological safety.
Question 65 Play from 2:16:49
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
More emails can simply reflect adjustment to distributed work and do not by themselves show poor teamwork.
Right, B is the answer.
Why B is right
Agile depends on short, frequent feedback loops between team members and with the customer. When a team is not collaborating well across locations, questions wait for answers, reviews stall and handoffs slow down, so the time needed to get feedback grows. A lengthening feedback cycle is therefore a clear signal that communication and collaboration are breaking down, and it directly reduces the team's ability to inspect and adapt. It is an observable symptom the team can discuss in a retrospective and address with better tools, overlapping hours or working agreements.
Not this one. Try another answer.
Why C is wrong
Rising velocity after adding the new members suggests the team is delivering more, not that it is struggling.
Not this one. Try another answer.
Why D is wrong
Asking to move meetings for time zones is a normal, healthy adjustment for a distributed team.
Question 66 Play from 2:19:08
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Agile adoption succeeds only when leadership supports it, because executives set the priorities, funding, governance and reward systems teams work within. Executive sponsorship is a key condition for an agile transformation. By presenting the advantages of agile principles and processes to the executive team and obtaining their buy-in, the CIO secures visible, consistent support from the top. Managers can then remove organizational obstacles, and the team sees that the change is backed and lasting, which eases their reservations and aligns them with the new way of working.
Not this one. Try another answer.
Why B is wrong
A memo mandating agile imposes the change from the top and tends to deepen resistance.
Not this one. Try another answer.
Why C is wrong
Running agile as an experiment without leadership backing leaves the team unsure the change will last and without support to remove organizational obstacles.
Not this one. Try another answer.
Why D is wrong
Compulsory training with an order to comply relies on mandate rather than building genuine team alignment.
Question 67 Play from 2:21:37
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Pointing out the team's choice sounds defensive and does not fix the communication gap the product owner raised.
Right, B is the answer.
Why B is right
The product owner's complaint is about status communication, not prioritization or requirement clarity. Agile teams communicate status through information radiators such as the task board, burndown chart, and product backlog view, which are highly visible and always current. The scrum master should make sure the product owner knows where this information lives and reviews it regularly, so that the status of every requirement is visible without waiting for someone to report it. This reinforces transparency and helps the product owner manage the backlog with accurate information.
Not this one. Try another answer.
Why C is wrong
A satisfaction histogram measures team or stakeholder satisfaction and says nothing about requirement status.
Not this one. Try another answer.
Why D is wrong
Requirement clarification is not the issue raised, and deflecting responsibility damages collaboration.
Question 68 Play from 2:23:54
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Stakeholder engagement matters because stakeholders help shape and share the vision of what the project must achieve. When they collaborate with the team in establishing that vision, everyone works toward the same goals, priorities reflect real business needs and feedback throughout the project stays aligned with expected outcomes. This shared vision underpins every later activity, from backlog ordering to acceptance, which is why engagement is central to project success in an agile approach.
Not this one. Try another answer.
Why B is wrong
Acceptance criteria are one narrow contribution, worked out with the product owner, not the reason engagement drives success.
Not this one. Try another answer.
Why C is wrong
Implementation methods belong to the development team, not to stakeholders.
Not this one. Try another answer.
Why D is wrong
Evaluating the development team's performance is not the purpose of stakeholder engagement.
Question 69 Play from 2:25:50
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Re-estimating the whole project is premature before anyone has decided whether the changes should be made.
Not this one. Try another answer.
Why B is wrong
Rejecting the changes outright ignores potential value and takes the decision away from the product owner.
Not this one. Try another answer.
Why C is wrong
Absorbing as many changes as possible without a prioritization decision invites scope creep and overcommitment.
Right, D is the answer.
Why D is right
The product owner is accountable for maximizing product value and for the content and order of the product backlog. When the team proposes changes that add value but also add work and affect the schedule, the agile project leader should bring them to the product owner, who weighs the added value against the cost and schedule impact and decides whether and when to include them. This keeps scope decisions with the role that owns them and keeps the team focused on the highest-value work.
Question 70 Play from 2:27:47
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Feedback on completed stories arrives after the work is done and reacts to results rather than defining the objectives up front.
Not this one. Try another answer.
Why B is wrong
How features are implemented is decided by the developers, not by stakeholders.
Not this one. Try another answer.
Why C is wrong
Stakeholders can propose features, but the product owner decides the content and order of the product backlog.
Right, D is the answer.
Why D is right
Acceptance criteria state the conditions a user story must satisfy to be accepted, so they are the most direct way for stakeholders to make sure their objectives are built into the product. By contributing to or writing acceptance criteria with the product owner, stakeholders express what success looks like before development starts, the team gains a clear target for design and testing, and the story is verified against those conditions when it is completed. This links stakeholder expectations to delivery throughout the iteration, not only at the end.
Question 71 Play from 2:29:50
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Planned overtime breaks sustainable pace and hides the planning problem instead of fixing it.
Not this one. Try another answer.
Why B is wrong
Velocity reflects work actually completed, and raising it on demand is not something a team can simply choose to do.
Right, C is the answer.
Why C is right
A sprint is a fixed timebox, so the team does not stretch it by a week or overload itself to rescue the plan. It works with the product owner on what can still be completed, returns unfinished work to the product backlog and treats the shortfall as learning. Identifying why it overcommitted, whether through estimation errors, hidden complexity or ignoring past velocity, and agreeing on improvement actions in the sprint retrospective lets the next sprint be planned realistically and sustains a predictable pace.
Not this one. Try another answer.
Why D is wrong
Adding people mid-sprint brings onboarding overhead and rarely speeds up delivery in the short term.
Question 72 Play from 2:32:07
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
A value stream map is a Lean tool that charts every step required to deliver value, from request to delivery, and records both the time spent adding value and the time spent waiting between steps. By making handoffs, queues and delays explicit, it shows where non-value-adding activity occurs and where the process can be simplified. That makes it the right tool for a team specifically seeking to identify and reduce unnecessary handovers and delays across its workflow.
Not this one. Try another answer.
Why B is wrong
A risk burndown chart tracks risk exposure over time and does not reveal handovers or waiting time.
Not this one. Try another answer.
Why C is wrong
A kanban board visualizes current work states but does not analyze end-to-end handoffs and delays.
Not this one. Try another answer.
Why D is wrong
A cumulative flow diagram shows work quantities by state over time, not the specific handovers between process steps.
Question 73 Play from 2:34:05
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Value stream mapping is the Lean technique that captures the full sequence of steps needed to deliver value to the customer, together with the activities, handoffs and waiting time involved in carrying them out. By mapping the current state, the team distinguishes value-adding steps from waste such as delays and rework, and then designs a future state with a smoother, faster flow. It is a primary Lean tool for identifying and eliminating waste across a process.
Not this one. Try another answer.
Why B is wrong
Long-term Lean planning is not a defined Lean technique for mapping the steps that deliver value.
Not this one. Try another answer.
Why C is wrong
Business process modeling documents workflows generally but does not focus on value and waste in the Lean sense.
Not this one. Try another answer.
Why D is wrong
Planning poker is a relative estimation technique and does not map a delivery process.
Question 74 Play from 2:35:52
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Taking the majority vote skips the discussion that could reveal important information about the story.
Not this one. Try another answer.
Why B is wrong
Deferring the story delays planning without resolving the small difference in understanding.
Right, C is the answer.
Why C is right
Relative estimation techniques such as planning poker aim for consensus, and the value of a differing estimate lies in the conversation it starts. The team member who voted five may see a simpler approach, or the others may know about complexity that this person has missed. The team should discuss the reasoning behind the differing estimate and, if needed, vote again until it converges on a value everyone accepts. This shared understanding of the story is often more valuable than the number itself.
Not this one. Try another answer.
Why D is wrong
Estimates belong to the people doing the work, not to the customer.
Question 75 Play from 2:38:04
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Transferring the member removes valuable expertise from the team without trying to engage them first.
Not this one. Try another answer.
Why B is wrong
A performance evaluation treats an engagement concern as a performance problem and damages trust.
Right, C is the answer.
Why C is right
In a self-organizing team, members decide together how to use each other's skills. The agile practitioner should encourage the team to involve the senior member in more activities, such as complex stories, design discussions, pairing and mentoring. This puts the member's experience to work, raises engagement and increases the capability of the whole team. The practitioner acts as a coach who helps the team solve the issue internally rather than moving people or escalating.
Not this one. Try another answer.
Why D is wrong
Handing the issue to the functional manager bypasses the team's ability to self-organize.
Question 76 Play from 2:40:06
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Dismissing the team member punishes the person for an organizational conflict and does not remove the cause.
Right, B is the answer.
Why B is right
Competing assignments from a functional manager are an impediment that the team member cannot easily resolve alone. The scrum master removes impediments and works across organizational boundaries, so the right step is a collaborative conversation with the functional manager to understand the competing demands, explain the effect on the team's commitments, and agree on how the team member's availability will be handled. Direct, respectful dialogue usually resolves the conflict and preserves a relationship the team will continue to need.
Not this one. Try another answer.
Why C is wrong
Reporting to the sponsor escalates before any attempt at direct resolution and damages trust.
Not this one. Try another answer.
Why D is wrong
Making demands is confrontational and less effective than collaborative problem solving.
Question 77 Play from 2:42:03
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Agile teams keep progress visible at all times through information radiators such as a task board, burndown chart or Kanban board. These displays show the current state of the iteration in real time, so a customer representative asking midway through the iteration can see exactly where the work stands without waiting for a formal report or a scheduled event. Sharing the information radiator supports transparency, requires no extra reporting effort and gives the most up-to-date view of progress.
Not this one. Try another answer.
Why B is wrong
A release plan shows intended timing at a high level, not the current progress within the iteration.
Not this one. Try another answer.
Why C is wrong
The retrospective is the team's event for improving its process and is not the place to give a customer a progress update.
Not this one. Try another answer.
Why D is wrong
A project report is a static snapshot that may already be outdated and adds documentation overhead compared with a live radiator.
Question 78 Play from 2:44:04
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Merely noting the changes records the restructure but does nothing to learn what the new stakeholders need from the project.
Right, B is the answer.
Why B is right
Stakeholder analysis is not a one-time activity. When an organizational restructure redefines key roles, the people who hold influence, interest, and requirements may have changed, so the team should engage the affected stakeholders directly and hold two-way conversations to refresh the analysis. Direct engagement uncovers new needs, concerns, and expectations that an organization chart cannot reveal, and it builds the collaborative relationships that agile delivery depends on. Updating the analysis in this way keeps the product backlog and engagement approach aligned with the people who now shape the outcome.
Not this one. Try another answer.
Why C is wrong
Emailing the vision is one-way communication that leaves it to recipients to decide their involvement and rarely surfaces real requirements.
Not this one. Try another answer.
Why D is wrong
A list of redefined roles shows the new structure but captures none of the interests, expectations, or requirements of the people in those roles.
Question 79 Play from 2:46:36
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Following a fixed schedule created at the start ignores the changing conditions and prevents the team from adapting.
Right, B is the answer.
Why B is right
In a volatile environment shaped by competition, rising customer expectations and new technology, a team must inspect and adapt frequently. Regular retrospectives give the team a structured cadence to reflect on what is working, identify what should change and agree on concrete improvement actions. Having team members commit to specific, owned actions turns those discussions into real change, and reviewing the actions at the next retrospective closes the loop. This steady cycle of reflection and commitment lets the team keep improving how it delivers value as conditions shift.
Not this one. Try another answer.
Why C is wrong
Trusting individual choices without a shared reflection and commitment process leaves improvements uncoordinated and easy to drop.
Not this one. Try another answer.
Why D is wrong
Tightly coupled code makes the product harder to change, which works against adapting to a fast-moving market.
Question 80 Play from 2:49:04
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Limiting changes to acceptance criteria may leave other gaps in the stories and excludes the team from the conversation.
Not this one. Try another answer.
Why B is wrong
Retrospectives improve the process rather than refine backlog items, and instructing the team is not facilitation.
Right, C is the answer.
Why C is right
A user story is a placeholder for a conversation, and missing detail is resolved by bringing people together to talk. A user story workshop gathers the team, the product owner and relevant stakeholders to discuss the stories, clarify intent, split large items and agree on acceptance criteria. The practitioner facilitates rather than directs, so shared understanding is built collaboratively and the team gains the detail it needs before committing to the work. This also improves how future stories are written.
Not this one. Try another answer.
Why D is wrong
Reporting the product owner to a manager escalates prematurely and damages collaboration.
Question 81 Play from 2:51:10
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Adding an engineer is premature before the team has even explored the component and may not be needed.
Not this one. Try another answer.
Why B is wrong
Technical investigation belongs to the developers, not the product owner.
Right, C is the answer.
Why C is right
The team faces technical uncertainty about a component it has never used, and integration is coming soon. A spike is a timeboxed investigation that lets the team build knowledge, reduce risk and improve its estimates before committing to the integration work. Because the product owner orders the backlog, the team asks the product owner to include the spike in the next iteration, keeping the work visible and prioritized while the developers perform the investigation themselves.
Not this one. Try another answer.
Why D is wrong
Swapping the component to avoid learning ignores the solution's need and the decision already made to integrate it.
Question 82 Play from 2:53:27
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
An agile coach is a servant leader whose purpose is to serve the team and help its members grow. Modeling agile principles and behaviors shows the team what the mindset looks like in practice. Self-awareness helps the coach notice their own reactions and biases, and being present allows them to listen fully. Together these let the coach truly hear the team, respond to its real needs and help people develop their strengths individually and as a team, which leads to empowered, self-organizing teams.
Not this one. Try another answer.
Why B is wrong
Convincing people what to do is directive persuasion, the opposite of the coaching stance of listening and serving.
Not this one. Try another answer.
Why C is wrong
Disguising command and control is manipulative and contradicts the transparency and servant leadership a coach must model.
Not this one. Try another answer.
Why D is wrong
Understanding team dynamics is a means the coach uses, while the reason for these behaviors is to listen to, serve and grow the people on the team.
Question 83 Play from 2:55:35
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Weekly status reports add overhead and rarely capture the practical lessons that would solve problems like this one.
Not this one. Try another answer.
Why B is wrong
Sending the team off alone ignores existing knowledge and repeats the waste of solving a solved problem.
Right, C is the answer.
Why C is right
The team is losing time solving a problem that another team has already solved, which is waste caused by knowledge that never left the team that learned it. The agile practitioner should collaborate with the team to create a way of spreading team knowledge across the company, such as communities of practice, shared wikis, cross-team demos or open retrospective outcomes. Working with the team keeps ownership with the people who will use the solution and turns a one-off gap into lasting organizational learning, supporting continuous improvement beyond a single team.
Not this one. Try another answer.
Why D is wrong
Hiring an external expert is costly and unnecessary when the team can build a fitting knowledge-sharing approach itself.
Question 84 Play from 2:57:51
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
A servant leader supports the team by clearing obstacles so the team can do its best work. When progress is slower than planned, the coach works with the team to identify what is slowing it down, such as dependencies, waiting time, tooling problems or outside interruptions, and helps remove those impediments. This addresses the cause of the slowdown while leaving the team in charge of how it organizes and plans its own work.
Not this one. Try another answer.
Why B is wrong
Adjusting the work plan treats the symptom and does not address what is causing the slowdown.
Not this one. Try another answer.
Why C is wrong
Adding resources rarely fixes a slowdown quickly and is not the coach's first response before the cause is understood.
Not this one. Try another answer.
Why D is wrong
Command and control contradicts servant leadership and undermines team self-organization.
Question 85 Play from 2:59:52
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Covering the board defeats its purpose as an information radiator and signals secrecy.
Not this one. Try another answer.
Why B is wrong
A kanban board visualizes workflow for the team and is not mainly a tool for assigning ownership of completed work.
Right, C is the answer.
Why C is right
A kanban board is an information radiator placed in a visible location on purpose. The project manager should explain to the executive that the board helps the team manage and complete its work and that its visibility makes progress, bottlenecks and unfinished work transparent to everyone. Transparency allows problems to be seen and addressed early, so hiding the board would remove one of its main benefits for the team and the organization.
Not this one. Try another answer.
Why D is wrong
Hiding the board removes transparency and the shared visibility the team relies on.
Question 86 Play from 3:02:07
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The team has some test automation skills, just not enough of them. A self-organizing, cross-functional team addresses this by cross-training other members in the automation framework, for example by pairing with those who already know it. This broadens capacity in the scarce skill, removes the bottleneck, encourages generalizing specialists and keeps the quality benefits of automated testing, all without waiting for outside help.
Not this one. Try another answer.
Why B is wrong
The product owner does not staff the team, and adding people is slow and ignores the skills already present.
Not this one. Try another answer.
Why C is wrong
Waiting for funds delays the solution indefinitely and develops only one person.
Not this one. Try another answer.
Why D is wrong
Abandoning automation sacrifices quality and long-term efficiency instead of building the needed skill.
Question 87 Play from 3:04:13
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The disagreement is about whether to deliver short-term business value through a solution that does not serve the customer in the long term. The team should resolve it by returning to the agile values and principles and to its own team values, such as customer satisfaction through valuable software, continuous attention to technical excellence and sustainable development. These shared values give the team a common basis for weighing the trade-off and reaching a decision together rather than leaving the disagreement unresolved.
Not this one. Try another answer.
Why B is wrong
A contract sets terms but does not help the team weigh short-term value against the long-term solution.
Not this one. Try another answer.
Why C is wrong
The priority list shows order, not how to balance immediate value against long-term quality.
Not this one. Try another answer.
Why D is wrong
Handing the problem off avoids the team discussion needed to resolve its own disagreement.
Question 88 Play from 3:06:10
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Agile teams aim to be cross-functional so that they can deliver finished work without waiting on external specialists. The team member has identified a concrete dependency that is slowing the team and has proposed a practical remedy. Supporting that request by sending the team member to database administrator training builds the team's capability, develops a generalizing specialist, and removes a source of delay. A servant leader enables the growth that team members ask for when it clearly helps the team deliver value.
Not this one. Try another answer.
Why B is wrong
Asking the outside specialists does not reduce the dependency that is hurting velocity.
Not this one. Try another answer.
Why C is wrong
Holding the training until the team confirms a problem already identified adds delay and second-guesses the team member's insight.
Not this one. Try another answer.
Why D is wrong
Waiting for the whole team to attend is unnecessary and prolongs the dependency on outside specialists.
Question 89 Play from 3:08:14
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Deferring the regulatory changes to a second release would ship a safety video that is already noncompliant.
Not this one. Try another answer.
Why B is wrong
Refusing to change during the release contradicts the agile principle of welcoming changing requirements.
Right, C is the answer.
Why C is right
Agile welcomes changing requirements, even late in development, for the customer's competitive advantage. When regulations are expected to shift before release, the best protection is to build the training video in small, independent increments that can be revised quickly once the new rules are known. Short iterations and frequent feedback keep the cost of change low, so the team can adjust content late without large rework and still release a product that complies with the regulations in force at release.
Not this one. Try another answer.
Why D is wrong
Monitoring discussions alone does not make the product able to absorb the change when it arrives.
Question 90 Play from 3:10:35
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Daily status emails are one-way push communication and do not build a comprehensive understanding of the project.
Not this one. Try another answer.
Why B is wrong
The daily scrum is a short planning event for the developers and shows day-to-day task progress, not the broad project picture.
Right, C is the answer.
Why C is right
A stakeholder who lacks a comprehensive understanding of the project needs a richer, two-way conversation, not more one-way data. Agile favors face-to-face, interactive communication because it lets people ask questions, surface assumptions and build a shared picture of the vision, goals and scope. Interactive sessions such as brainstorming or collaborative workshops engage the stakeholder directly, reveal what they do not yet understand and give them a voice in shaping the work, which builds both understanding and commitment far more effectively than reports or status meetings.
Not this one. Try another answer.
Why D is wrong
Building the backlog first and asking for feedback afterward delays engagement and does not address the current lack of understanding.
Question 91 Play from 3:12:49
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Moving the task to someone else is the scrum master assigning work, which undermines both the member and the team's self-organization.
Not this one. Try another answer.
Why B is wrong
Putting one person's delay before the whole team before speaking with them can embarrass the member and damage psychological safety.
Right, C is the answer.
Why C is right
When one team member falls behind, a servant leader first supports that person rather than exposing or bypassing them. A private conversation offering encouragement protects psychological safety, shows that the scrum master is on the member's side, and gives the member room to mention any obstacle that the scrum master can then help remove. This approach motivates the individual to meet the commitments they made to the team while preserving their dignity and the trust within the team. Public or directive responses risk embarrassing the member and discouraging openness in the future.
Not this one. Try another answer.
Why D is wrong
Notifying the product owner escalates a minor individual matter that the scrum master can support directly.
Question 92 Play from 3:14:51
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Replacing the team member is a heavy, punitive step that skips coaching and harms trust.
Not this one. Try another answer.
Why B is wrong
Self-organization means the whole team decides together, not that one member dominates unchecked.
Right, C is the answer.
Why C is right
When one person dominates decisions, the team loses the diverse perspectives that make self-organization work, and quieter members may stop contributing. A coach handles this through facilitation, not authority: asking probing, open questions of the other team members invites their views and makes healthy dissent safe. This builds psychological safety and leads to more balanced, better-informed decisions while still leaving the decision-making with the team. The dominant member is not punished; the group simply learns to hear more voices.
Not this one. Try another answer.
Why D is wrong
Waiting for velocity to drop is reactive and lets an unhealthy dynamic settle in first.
Question 93 Play from 3:16:57
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Refinement with the team does not address the need here, because writing and sizing stories does not tell the product owner what stakeholders value most.
Not this one. Try another answer.
Why B is wrong
Story points measure size or effort rather than value, so ordering by the largest estimates does not deliver the most value first.
Right, C is the answer.
Why C is right
In a high-visibility, fast-moving project, priorities shift quickly, and the product owner's core accountability is maximizing value through the ordering of the product backlog. Seeking regular input from stakeholders and reflecting that input in backlog priorities keeps the backlog aligned with business needs as they evolve, and it lets the product owner manage a time-consuming backlog by focusing effort on what matters most. Frequent stakeholder collaboration also builds trust and transparency, which is especially important when many people are watching the outcome.
Not this one. Try another answer.
Why D is wrong
Monthly progress reviews are too infrequent for a fast-moving project and focus on status rather than on shaping backlog priorities.
Question 94 Play from 3:19:26
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
The disagreement shows that the team and the product owner hold different views of what complete means. The definition of done creates a shared understanding of the quality standards an increment must meet, and testing is normally an essential part of it. The agile practitioner should facilitate a conversation in which the team and the product owner agree on an explicit definition of done that includes testing. Work that does not meet it is not done and returns to the product backlog, and future disputes of this kind are prevented.
Not this one. Try another answer.
Why B is wrong
The sponsor does not decide completion criteria, and escalating avoids the collaboration the situation needs.
Not this one. Try another answer.
Why C is wrong
Scheduling another review treats the symptom and leaves the underlying disagreement about done unresolved.
Not this one. Try another answer.
Why D is wrong
Testing is part of finishing the work, not a separate backlog item for the product owner to prioritize.
Question 95 Play from 3:21:36
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A change management team is not responsible for backlog prioritization and would add an unnecessary layer between stakeholders and the team.
Not this one. Try another answer.
Why B is wrong
Letting stakeholders build and order the backlog alone excludes the team's input on effort, risk and dependencies.
Right, C is the answer.
Why C is right
Alignment with stakeholder priorities comes from collaboration: the team discusses and prioritizes the backlog while actively factoring in stakeholder input. This keeps stakeholders engaged and ensures their needs shape the order of work, while the team brings its knowledge of effort, risk and dependencies to the decision. Combining both perspectives, with the product owner guiding value-based ordering, produces a backlog that reflects business value and remains realistic to deliver.
Not this one. Try another answer.
Why D is wrong
Excluding stakeholders from prioritization is the opposite of ensuring alignment with their priorities.
Question 96 Play from 3:23:52
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
A work breakdown structure is a predictive planning tool and does not express customer value priorities for an iteration.
Not this one. Try another answer.
Why B is wrong
Full descriptions and cost estimates for every feature are excessive up-front detail and do not show what matters most.
Right, C is the answer.
Why C is right
In agile planning the product owner works with the customer on a prioritized list of desired features and functions, which is effectively the ordered product backlog. Having the customer review and approve that priority order ensures that the upcoming iteration delivers the highest-value items first. It keeps the customer collaborating on value decisions while leaving the developers to plan how much they can take on and how to build it.
Not this one. Try another answer.
Why D is wrong
A comprehensive schedule is predictive planning, and the iteration content is set by value priority, not a fixed schedule.
Question 97 Play from 3:25:51
Tap an answer. The reason for that answer shows here.
Right, A is the answer.
Why A is right
Security firewalls are new work, and in agile all work the product needs is made transparent in the product backlog. Team members support the product owner by capturing the new security features as backlog items so they can be refined, estimated and prioritized against the rest of the work. Once the items are visible in the backlog, the product owner can order them by value and risk, and the team can plan them into upcoming iterations instead of leaving the request as an informal wish that might be forgotten.
Not this one. Try another answer.
Why B is wrong
A spike researches how to build something, but the immediate need is to capture the requested work so it can be prioritized.
Not this one. Try another answer.
Why C is wrong
Asking where the product will be used does not turn the security request into work the team can plan and deliver.
Not this one. Try another answer.
Why D is wrong
Questioning whether the product owner can define the security level does not move the request into the backlog where it can be refined and prioritized.
Question 98 Play from 3:28:01
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Stopping planning early leaves capacity unused and is not the practitioner's decision to force on the team.
Not this one. Try another answer.
Why B is wrong
Picking technically minimal tasks ignores business priority and may deliver little value.
Right, C is the answer.
Why C is right
Once most of the expected story points are identified, the remaining capacity should be filled with the next items in priority order. The agile practitioner helps the team refer to the remaining prioritized backlog items and select those that fit the available capacity, so the iteration continues to deliver the highest value work. The ordered product backlog, maintained by the product owner, is the authoritative guide to what comes next.
Not this one. Try another answer.
Why D is wrong
Choosing the smallest items simply because they fit ignores the priority order and can displace more valuable work.
Question 99 Play from 3:30:00
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Risk management deals with uncertain future events, while the delays are a current problem that needs causal analysis.
Not this one. Try another answer.
Why B is wrong
Variance and trend analysis shows how far performance deviates from plan and how it changes over time, but it does not explain why the delays occur.
Not this one. Try another answer.
Why C is wrong
The Kano model classifies features by their effect on customer satisfaction and does not analyze process delays.
Right, D is the answer.
Why D is right
The team already knows the symptom: long delays between product completion and release for validation and testing. To understand the issues behind it, the team needs root cause analysis, and a fishbone (Ishikawa) diagram is built for this. It organizes possible causes into categories such as people, process, tools and environment, helping the team move beyond the symptom to the underlying factors that create the delay. Once the causes are understood, the team can target improvements that shorten the time to market.
Question 100 Play from 3:32:02
Tap an answer. The reason for that answer shows here.
Not this one. Try another answer.
Why A is wrong
Going to the product owner's manager skips direct conversation and turns a coaching need into an escalation.
Right, B is the answer.
Why B is right
A servant leader addresses problems directly, respectfully and early. The agile practitioner should share the root-cause findings with the product owner and offer to facilitate conversations with the team, for example through backlog refinement sessions, story workshops or agreed acceptance criteria. This respects the product owner's role, coaches toward better communication and restores shared understanding of requirements quickly, which matters because defects are already rising late in the project. Collaboration and facilitation come before escalation, and they keep trust intact within the team.
Not this one. Try another answer.
Why C is wrong
Delegating the message to a team member delays action and avoids the practitioner's own responsibility to coach.
Not this one. Try another answer.
Why D is wrong
Escalating to the sponsor is premature when direct facilitation with the product owner has not been tried.
Transcript
Play from 00:00 Question 1. During a retrospective meeting, a team develops a large list of initiatives. All will have a positive impact and improve team performance. What should the agile coach do next? Here are the options. Option A. Positively acknowledge the list and share it with management. Option B. Immediately have the team implement the initiatives. Option C. Help the team choose one or two initiatives for immediate implementation. Option D. Ask the team to choose and implement the most complex initiative. Pause the video now if you want time to think about the answer.
The correct answer is C. Help the team choose one or two initiatives for immediate implementation. Even when every idea is beneficial, a team cannot absorb many changes at once without losing focus and capacity for delivery. The agile coach should help the team select the one or two improvements expected to have the greatest impact and commit to implementing them right away, often by adding them to the next sprint backlog. The team can then inspect the results at the next retrospective and pick further items, making continuous improvement steady and measurable. Now, why are the other options incorrect? Option A is incorrect. Acknowledging the list and sharing it with management produces no actual improvement. Option B is incorrect. Implementing everything at once overwhelms the team and makes it hard to see which change helped. Option D is incorrect. Complexity is not the selection criterion, and starting with the hardest change risks stalling improvement. Therefore, C, Help the team choose one or two initiatives for immediate implementation, is the correct answer.
Play from 02:06 Question 2. The team is refining user stories during the backlog grooming session and is confused about the acceptance criteria and level of details. What should the agile practitioner do? Here are the options. Option A. Complete the test cases before creating the story in the backlog. Option B. Define the detailed business requirements so that the team can continue with development. Option C. Define the user stories with just enough details so the team can collaborate continuously. Option D. Ensure the acceptance criteria includes testing scenarios, so the team can do thorough testing. Pause the video now if you want time to think about the answer.
The correct answer is C. Define the user stories with just enough details so the team can collaborate continuously. A user story is a placeholder for a conversation, not a full specification. When the team is unsure about the acceptance criteria and level of detail during backlog refinement, the agile practitioner should guide everyone toward stories with just enough detail to start, so that understanding grows through continuous collaboration between the developers and the product owner. Details are added progressively as the story approaches implementation, which avoids waste from premature specification and keeps the team able to respond to what it learns. Now, why are the other options incorrect? Option A is incorrect. Writing complete test cases before a story even enters the backlog is premature, front-loaded work that conflicts with progressive refinement. Option B is incorrect. Defining detailed business requirements up front is a predictive approach that replaces collaboration with documentation. Option D is incorrect. Loading the acceptance criteria with test scenarios does not resolve the confusion about how much detail a story needs and pushes toward excessive up-front specification. Therefore, C, Define the user stories with just enough details so the team can collaborate continuously, is the correct answer.
Play from 04:30 Question 3. A team member is stressed due to a heavy workload, while other team members have some slack in their schedules. How should the team lead address this? Here are the options. Option A. Inform management, and suggest that additional resources may be required. Option B. Discuss the issue with the team in the daily stand up meetings. Option C. Meet personally with the stressed team member to brainstorm ways to better manage their time. Option D. Begin tracking the stressed team member's tasks in a separate backlog for additional analysis and reporting. Pause the video now if you want time to think about the answer.
The correct answer is C. Meet personally with the stressed team member to brainstorm ways to better manage their time. A team member who is stressed by a heavy workload needs support, and a servant leader responds by meeting with that person directly. A personal conversation shows care for the member's well-being, gives the leader a clear understanding of what is driving the stress, and lets the two of them brainstorm practical ways to manage the work, such as reprioritizing tasks, asking teammates for help, or limiting work in progress. This approach protects sustainable pace and psychological safety without exposing the member's difficulties in front of the whole team. Now, why are the other options incorrect? Option A is incorrect. Requesting more resources from management is unnecessary when the team already has slack and the cause of the stress has not been explored. Option B is incorrect. Raising one member's stress at the daily stand-up turns a personal well-being concern into a public status item before the leader understands it. Option D is incorrect. Tracking one person's tasks in a separate backlog adds overhead, reduces transparency, and singles the member out. Therefore, C, Meet personally with the stressed team member to brainstorm ways to better manage their time, is the correct answer.
Show full transcriptShow less
Play from 06:50 Question 4. During a sprint demo, a business representative identifies missing requirements. The agile practitioner realizes that all key stakeholders were not included during requirements detailing. What should the agile practitioner have done to avoid the situation? Here are the options. Option A. Included the stakeholders in the project planning meeting. Option B. Organized an earlier demo to solicit business feedback. Option C. Ensured all business leaders signed off on requirements. Option D. Engaged key stakeholders periodically to collect requirements. Pause the video now if you want time to think about the answer.
The correct answer is D. Engaged key stakeholders periodically to collect requirements. Missing requirements surfaced because some key stakeholders were left out while requirements were being detailed. Agile requirements are elaborated progressively, just in time, so stakeholder engagement must be continuous rather than a single event. Identifying all key stakeholders and engaging them periodically, for example in backlog refinement, story workshops and sprint reviews, ensures their needs are captured as stories are detailed and gives frequent chances to catch gaps early. This steady collaboration is what prevents late surprises when the increment is shown. Now, why are the other options incorrect? Option A is incorrect. Including stakeholders in one planning meeting is a one-time touchpoint and does not cover the ongoing detailing of requirements. Option B is incorrect. An earlier demo would detect the gap sooner but would not prevent it, since the stakeholders would still be absent from requirements work. Option C is incorrect. Formal sign-off freezes requirements on paper and does not ensure the right stakeholders contributed or that needs stay current. Therefore, D, Engaged key stakeholders periodically to collect requirements, is the correct answer.
Play from 09:14 Question 5. During a team meeting, members who are subject matter experts (SMEs) mention that they are continuously working on repetitive tasks, which has lowered motivation. What should the agile practitioner do? Here are the options. Option A. Organize a team-building activity to improve team morale. Option B. Have team members work in pairs to learn from each other and develop new skills. Option C. Ask team members to perform a value stream analysis of their activities. Option D. Add more resources to the team to help with tasks. Pause the video now if you want time to think about the answer.
The correct answer is B. Have team members work in pairs to learn from each other and develop new skills. Subject matter experts who perform the same repetitive tasks lose motivation because their work offers little variety, learning, or mastery. Having team members work in pairs lets the experts share their knowledge and pick up new skills from colleagues, which adds variety to their work and spreads expertise across the team. This builds cross-functional, T-shaped skills, reduces dependence on single specialists, and lets the repetitive work be shared, all of which address the motivation problem directly while improving the team's resilience. Now, why are the other options incorrect? Option A is incorrect. A team-building activity may lift spirits briefly but leaves the repetitive work that causes low motivation unchanged. Option C is incorrect. Value stream analysis targets waste and delays in the process, not the lack of variety and growth that is lowering motivation. Option D is incorrect. Adding resources does not change the nature of the work and makes the repetitive tasks no more engaging. Therefore, B, Have team members work in pairs to learn from each other and develop new skills, is the correct answer.
Play from 11:28 Question 6. An agile practitioner notices that team members are disengaged. As a result, the team's velocity has decreased. What should the agile practitioner do to get the team back on track? Here are the options. Option A. Escalate the issue to the project sponsor. Option B. Remove stories to increase velocity. Option C. Hold a standup to address the issue. Option D. Facilitate a team retrospective. Pause the video now if you want time to think about the answer.
The correct answer is D. Facilitate a team retrospective. Disengagement and falling velocity are signs that something in the way the team works needs attention. A retrospective gives the team a safe, facilitated space to discuss what is affecting motivation, find root causes and agree on improvements it owns. Retrospectives do not have to wait for the end of an iteration; a team can hold one whenever it appears stuck. Facilitating this conversation reflects servant leadership because the practitioner helps the team solve its own problem instead of imposing a fix. Now, why are the other options incorrect? Option A is incorrect. Escalating to the sponsor bypasses the team and signals a lack of trust in its ability to self-organize. Option B is incorrect. Removing stories distorts the velocity figure without addressing why the team is disengaged. Option C is incorrect. A daily standup is a short planning event for the day and is not designed for exploring morale and root causes. Therefore, D, Facilitate a team retrospective, is the correct answer.
Play from 13:28 Question 7. At the retrospective, the burndown chart shows that the project is slightly behind schedule. The project team identifies an inexperienced software engineer as the source of reduced velocity. How should the project team address this issue? Here are the options. Option A. Suggest pair programming during the retrospective. Option B. Ask the product owner to re-prioritize the user stories at the next retrospective. Option C. Re-estimate the story points with team members at the next iteration planning meeting. Option D. Assign less complex user stories to the inexperienced software engineer at the next iteration planning meeting. Pause the video now if you want time to think about the answer.
The correct answer is A. Suggest pair programming during the retrospective. The retrospective is the right place for the team to inspect its way of working and agree on improvements. Pair programming, an XP practice, pairs the inexperienced engineer with a more experienced colleague, so knowledge transfers quickly, defects are caught as code is written and the whole team becomes more capable. It addresses the root cause, a skill gap, rather than the symptom, and it reflects collective ownership because the team solves the problem together instead of isolating one person. Over the following iterations velocity should recover as the engineer gains experience. Now, why are the other options incorrect? Option B is incorrect. Reprioritizing user stories does nothing about the skill gap, and backlog order belongs to the product owner rather than the retrospective. Option C is incorrect. Re-estimating story points changes the numbers on the plan but does not improve the engineer's capability. Option D is incorrect. Steering easy work to one person limits learning, weakens collective ownership and leaves the gap in place. Therefore, A, Suggest pair programming during the retrospective, is the correct answer.
Play from 15:44 Question 8. During a current sprint, a team member asks permission from the scrum master to investigate an alternative design approach. What should the scrum master do? Here are the options. Option A. Discourage the team member from deviating from the plan and document the request during the retrospective. Option B. Encourage the team member to research the issue and present the findings during the retrospective. Option C. Discourage the team member from using experimentation/spikes unless it is fully developed and accounts for a variety of use cases. Option D. Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important. Pause the video now if you want time to think about the answer.
The correct answer is D. Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important. Agile teams improve by experimenting and learning quickly. When a team member wants to explore an alternative design, the scrum master should encourage a timeboxed spike or experiment and help the whole team understand how such investigations reduce uncertainty and support continuous improvement. Developers decide how to do their work, so permission is not really the scrum master's to grant; the scrum master's role is to coach and to foster a culture in which trying new approaches is welcomed and the results are shared. Now, why are the other options incorrect? Option A is incorrect. Discouraging the investigation stifles learning and contradicts the agile emphasis on adapting the approach. Option B is incorrect. Design findings feed the work in progress, and the retrospective is focused on process improvement rather than design results. Option C is incorrect. Demanding a fully developed experiment defeats the purpose of a spike, which is a small, quick investigation. Therefore, D, Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important, is the correct answer.
Play from 18:14 Question 9. An Agile team is under pressure to deliver an application. The product owner anticipates many change requests from customers once the product is released. What should the agile team do? Here are the options. Option A. Demand frequent product reviews by the product owner. Option B. Continuously work with the product owner to do backlog refinement and product reviews. Option C. Have the product owner provide detailed requirement specifications to ensure the proper features are delivered. Option D. During the planning session, ensure the team is committed to deliver within the specifications. Pause the video now if you want time to think about the answer.
The correct answer is B. Continuously work with the product owner to do backlog refinement and product reviews. Agile teams welcome changing requirements, even late, and handle them by working closely with the product owner throughout delivery. Continuous backlog refinement lets incoming change requests be clarified, sized, and ordered by value, while frequent product reviews show customers working increments and gather feedback early. Many changes are absorbed before release instead of piling up afterward, and the team keeps delivering the most valuable items under pressure. Collaboration and short feedback loops are the agile answer to expected change, not tighter upfront control. Now, why are the other options incorrect? Option A is incorrect. Demanding reviews from the product owner is adversarial and ignores ongoing collaboration and refinement of the backlog. Option C is incorrect. Detailed upfront specifications assume requirements are fixed, which conflicts with the expected flow of change. Option D is incorrect. Committing to fixed specifications locks in scope that the product owner already expects customers to change. Therefore, B, Continuously work with the product owner to do backlog refinement and product reviews, is the correct answer.
Play from 20:35 Question 10. The customer needs assistance in determining the efficiency of a set of process activities within the solution. What should the agile team do? Here are the options. Option A. Discuss the efficiency at the next iteration retrospective. Option B. Review the process value stream to determine potential improvements. Option C. Review the value the customer receives from the user story to determine backlog priority. Option D. Discuss the performance of the solution at the next sprint review. Pause the video now if you want time to think about the answer.
The correct answer is B. Review the process value stream to determine potential improvements. Determining the efficiency of a set of process activities is the purpose of value stream analysis, a Lean technique. Mapping the value stream shows each step, the time spent adding value and the time spent waiting, so the team can calculate process efficiency, spot delays, handoffs and other waste, and recommend improvements. Reviewing the process value stream therefore gives the customer a direct, evidence-based answer instead of a general discussion, and it can be done now rather than waiting for a scheduled event. Now, why are the other options incorrect? Option A is incorrect. The iteration retrospective is for the team to improve its own way of working, not to analyze the efficiency of the customer's process activities. Option C is incorrect. Assessing story value helps order the backlog but does not measure how efficiently a process performs. Option D is incorrect. The sprint review inspects the increment and gathers feedback on the product, not a detailed analysis of process efficiency. Therefore, B, Review the process value stream to determine potential improvements, is the correct answer.
Play from 22:44 Question 11. During a review session, an agile team presented done requirements to a group of stakeholders. Stakeholder feedback indicated that the done requirements failed to meet most pressing needs and provide value. What should the team have done to prevent this? Here are the options. Option A. Reprioritized requirements prior to committing to iteration work. Option B. Ensured that requirements remained stable during the iteration cycle. Option C. Had stakeholders focus on items created after the product backlog was initially built. Option D. Worked on features rather than a set of components. Pause the video now if you want time to think about the answer.
The correct answer is A. Reprioritized requirements prior to committing to iteration work. The stakeholders found that completed work did not address their most pressing needs, which means the team built lower-value items first. Before committing to iteration work, the product backlog should be refined and reordered with the product owner and stakeholders so that the highest-value, most urgent requirements are at the top. The team then plans the iteration from those items. Regular reprioritization keeps delivery aligned with current business needs, which change over time. Now, why are the other options incorrect? Option B is incorrect. Keeping requirements stable during the iteration does not ensure that the right requirements were chosen. Option C is incorrect. When an item was created has no bearing on its value, so focusing on newer items does not solve the problem. Option D is incorrect. Delivering features instead of components does not prevent the problem, because features can still be the wrong ones if they are not prioritized by value. Therefore, A, Reprioritized requirements prior to committing to iteration work, is the correct answer.
Play from 24:58 Question 12. An agile team and a traditional development team are working together on a project. Each team exceeds expectations regarding deliverables; however, issues arise when the deliverables are integrated. What should the agile practitioner do? Here are the options. Option A. Foster stronger communication by hosting cross-organizational meetings between the two teams. Option B. Suggest merging the teams to avoid misunderstandings. Option C. Create stories from full technical specifications to avoid ambiguity. Option D. Co-locate the teams to encourage osmotic communication. Pause the video now if you want time to think about the answer.
The correct answer is D. Co-locate the teams to encourage osmotic communication. Both teams perform well on their own, so the integration problems point to a communication gap between them. Co-locating the teams lets members overhear conversations, ask questions as they arise and notice interface mismatches immediately, which is the osmotic communication agile teams rely on. Continuous, informal face-to-face contact surfaces integration concerns as the work is done rather than at hand-off, which is far more effective than occasional formal meetings and fits the agile principle that face-to-face conversation is the most efficient way to convey information. Now, why are the other options incorrect? Option A is incorrect. Periodic cross-organizational meetings add some coordination but leave the gap open between meetings, so issues still surface late. Option B is incorrect. Merging the teams is a disruptive structural change that the situation does not require, since each team already performs well. Option C is incorrect. Writing stories from full technical specifications is a document-heavy approach that does not create the ongoing collaboration the teams lack. Therefore, D, Co-locate the teams to encourage osmotic communication, is the correct answer.
Play from 27:16 Question 13. A scrum master would like to provide information to key stakeholders on the daily resource and project activities. Which tool should the Scrum master use to provide these updates? Here are the options. Option A. Shared vision statement and sprint goal. Option B. Release burnup chart. Option C. Velocity metrics. Option D. Iteration burndown chart. Pause the video now if you want time to think about the answer.
The correct answer is D. Iteration burndown chart. An iteration burndown chart plots the work remaining in the current iteration against the days of the iteration and is updated daily. It is an information radiator that shows stakeholders, at a glance, whether the team is on track to finish the iteration's work and how effort is being consumed day by day. That daily granularity matches the need to report on daily resource and project activities. Other tools describe direction, long-term release progress or historical trends rather than what is happening within the current iteration each day. Now, why are the other options incorrect? Option A is incorrect. A shared vision and sprint goal describe intent and direction, not daily progress or activity. Option B is incorrect. A release burnup chart tracks completed scope across many iterations rather than daily activity within one. Option C is incorrect. Velocity metrics summarize completed work per iteration and are used for forecasting, not daily status. Therefore, D, Iteration burndown chart, is the correct answer.
Play from 29:09 Question 14. A new stakeholder has recently joined a project. During a meeting with the scrum master, the new stakeholder tries to understand the status of the project and the remaining tasks for completion. How should the scrum master inform the new stakeholder? Here are the options. Option A. Show the stakeholder the latest release breakdown for the project. Option B. Invite the stakeholder to attend the next sprint review meeting. Option C. Show the stakeholder the progress radiators for the project. Option D. Invite the stakeholder to attend the next sprint planning meeting. Pause the video now if you want time to think about the answer.
The correct answer is B. Invite the stakeholder to attend the next sprint review meeting. The sprint review is the Scrum event designed for stakeholders. The Scrum Team presents the results of its work to key stakeholders, the increment is inspected, and progress toward the product goal is discussed, with the product backlog adjusted as needed. Inviting the new stakeholder gives them a direct view of what has been done, what remains and how plans are adapting, along with the chance to ask questions and give feedback to the people doing the work. It also starts the regular stakeholder engagement that agile delivery depends on. Now, why are the other options incorrect? Option A is incorrect. A release breakdown shows how scope is planned across releases, not the actual progress inspected against a working increment. Option C is incorrect. Progress radiators show charts without the conversation and inspection of working product a new stakeholder needs to understand status. Option D is incorrect. Sprint planning is where the Scrum Team plans the coming sprint and is not the place to brief a stakeholder on overall status. Therefore, B, Invite the stakeholder to attend the next sprint review meeting, is the correct answer.
Play from 31:21 Question 15. More details for a story are required before the upcoming sprint planning meeting. What should the scrum master do? Here are the options. Option A. Email the product owner requesting detailed story specifications and wait for a response. Option B. Gather the details from the team members before sprint planning. Option C. Schedule a story grooming session with the product owner before sprint planning. Option D. Conduct a planning poker session with the team. Pause the video now if you want time to think about the answer.
The correct answer is C. Schedule a story grooming session with the product owner before sprint planning. Backlog refinement, often called story grooming, is the ongoing activity in which the product owner and the developers add detail, acceptance criteria and estimates to upcoming product backlog items so they are ready for sprint planning. When a story needs more detail before planning, the scrum master should schedule a grooming session with the product owner and the team. The conversation clarifies the story, answers questions and ensures the team can plan the work with confidence. Now, why are the other options incorrect? Option A is incorrect. Emailing and waiting replaces collaboration with a slow handoff and may leave the story unclear. Option B is incorrect. The product owner, not the team alone, is accountable for clarifying what the story requires. Option D is incorrect. Planning poker estimates a story but does not supply the missing details about it. Therefore, C, Schedule a story grooming session with the product owner before sprint planning, is the correct answer.
Play from 33:21 Question 16. A team member does not understand what the project risks are or the impact that they could have. How should an agile leader communicate risks in a way that the team will understand? Here are the options. Option A. Create a RACI chart (responsible, accountable, consulted, informed) that identifies who is accountable for each risk. Option B. Create a Gantt chart that includes slack to accommodate for unknowns. Option C. Create a communications management plan that details who is responsible for communicating risks. Option D. Create a risk burndown chart showing the reduction of risks over time. Pause the video now if you want time to think about the answer.
The correct answer is D. Create a risk burndown chart showing the reduction of risks over time. A risk burndown chart is an information radiator that plots the total risk exposure (typically probability multiplied by impact for each risk) over time. It makes the project risks and their potential impact visible in a simple, graphical form that every team member can read at a glance, and it shows how the team's risk response work is reducing exposure sprint by sprint. That visibility helps the team member understand both what the risks are and how much they matter, which is exactly the communication need described. Now, why are the other options incorrect? Option A is incorrect. A RACI chart maps roles and accountability but does not explain the risks or their impact. Option B is incorrect. A Gantt chart with slack is a schedule tool and does not communicate specific risks or their impact. Option C is incorrect. A communications management plan defines who communicates what, not an understandable view of the risks themselves. Therefore, D, Create a risk burndown chart showing the reduction of risks over time, is the correct answer.
Play from 35:35 Question 17. The amount of information captured in the project's defects is varying within the development team. Team members are becoming frustrated with the defect quality inconsistencies and the frequent clarification required. What should be done to address the issue? Here are the options. Option A. Stop the current iteration to discuss defect quality issues and explore solutions. Option B. Discuss and explore solutions in the next planning meeting and take corrective actions as required. Option C. Generate insights at the next retrospective and adjust processes as decided by the team. Option D. Assign corrective actions to the backlog for the team to identify the mandatory defect information. Pause the video now if you want time to think about the answer.
The correct answer is C. Generate insights at the next retrospective and adjust processes as decided by the team. Inconsistent defect information is a process problem within the team's own way of working, and the retrospective is the event designed for inspecting and adapting the process. At the next retrospective the team can generate insights into why defect reports vary, agree on what information a defect must contain, and own the resulting change. Because the team decides the improvement itself, it is more likely to be adopted and sustained than a rule imposed from outside. Now, why are the other options incorrect? Option A is incorrect. Stopping the iteration is a drastic disruption to delivery for a process issue that can wait for the retrospective. Option B is incorrect. Planning focuses on what work to take on next, while process improvement belongs in the retrospective. Option D is incorrect. Placing corrective actions in the backlog for the team to execute presumes the solution instead of letting the team inspect and agree on it. Therefore, C, Generate insights at the next retrospective and adjust processes as decided by the team, is the correct answer.
Play from 37:59 Question 18. An agile project manager notices that the product manager manages team members' day-to-day tasks in a way that distracts them from their core responsibilities. In addition, the team believes that their questions on product backlog prioritization are not being answered on time. What should the agile practitioner do? Here are the options. Option A. Discuss and address this in the iteration retrospective. Option B. Let the product owner know it is the project manager's responsibility to drive a team's tasks. Option C. Discuss the roles and responsibilities of the project team with the product owner. Option D. Ask the product owner to work extra hours to answer the team's questions. Pause the video now if you want time to think about the answer.
The correct answer is A. Discuss and address this in the iteration retrospective. The problems concern how the team and the product owner work together: task direction that distracts team members and slow answers on backlog prioritization. The iteration retrospective is the event designed for inspecting people, relationships, processes, and tools, and the product owner takes part as a member of the team. Raising both issues there lets everyone discuss the impact openly, clarify expectations about who manages tasks and how quickly prioritization questions are answered, and agree on concrete improvements together. Solutions the whole team agrees on are more likely to stick than a fix imposed by one person. Now, why are the other options incorrect? Option B is incorrect. Agile teams manage their own tasks, so directing tasks is not the project manager's job either. Option C is incorrect. A private discussion with the product owner leaves the team out of agreeing how it wants to work with the product owner. Option D is incorrect. Extra hours are not sustainable and do not correct the product owner's misplaced focus. Therefore, A, Discuss and address this in the iteration retrospective, is the correct answer.
Play from 40:13 Question 19. An organization is undergoing an agile transformation to improve its market position. Management wants minimal overhead in connection with the agile initiative and wants the agile teams to control the work in process (WIP) and ensure that iterations do not result in waste. Which approach should be used in this scenario? Here are the options. Option A. Feature-driven development (FDD). Option B. Extreme Programming (XP). Option C. Scrum. Option D. Kanban. Pause the video now if you want time to think about the answer.
The correct answer is D. Kanban. Kanban is a lightweight method that can be applied to existing processes with minimal overhead, since it prescribes no new roles or mandatory ceremonies. Its core practices are visualizing work and limiting work in process (WIP), which give teams direct control over how much work is underway and expose queues and bottlenecks. Managing flow this way reduces waste such as partially done work and waiting, matching management's goals for the transformation. Now, why are the other options incorrect? Option A is incorrect. Feature-driven development centers on feature design and ownership roles, not WIP control. Option B is incorrect. Extreme Programming emphasizes engineering practices such as pairing and test-driven development rather than WIP limits. Option C is incorrect. Scrum adds defined roles, events and artifacts, which is more overhead than management wants, and does not use explicit WIP limits. Therefore, D, Kanban, is the correct answer.
Play from 42:10 Question 20. An agile team is having a meeting with a customer to formulate the product requirements for the next iteration. The outcome of the meeting is a set of clear and detailed requirements. What should the team do next? Here are the options. Option A. Run automated tests on the legacy functionality. Option B. Ask the customer to write tests that will be used to know when a story has been correctly developed. Option C. Start coding on the selected user stories to meet the requirements. Option D. Write tests that will be used to know when a story has been correctly developed. Pause the video now if you want time to think about the answer.
The correct answer is D. Write tests that will be used to know when a story has been correctly developed. With clear, detailed requirements agreed, the next step in a test-first approach such as acceptance test-driven development or behavior-driven development is to write the tests that define when each story is correctly built. These acceptance tests turn the requirements into concrete, verifiable examples, confirm shared understanding with the customer, guide the coding and support the definition of done. Writing them before development begins reduces defects and rework because everyone knows exactly what done looks like for each story. Now, why are the other options incorrect? Option A is incorrect. Running regression tests on legacy functionality does not prepare the team to build the new stories. Option B is incorrect. The customer helps define acceptance tests, but asking the customer to write them alone hands off work the team should lead collaboratively before coding. Option C is incorrect. Coding before the tests exist removes the clear target that test-first development provides. Therefore, D, Write tests that will be used to know when a story has been correctly developed, is the correct answer.
Play from 44:23 Question 21. A mature agile team welcomes a new member. Due to poor experiences with a previous team, the new member is reluctant to communicate. What should the agile project leader do? Here are the options. Option A. Bring up the new member's impediments at the next meeting to demonstrate team support of input. Option B. Assure the new member that inputs on impediments are valued, and demonstrate this at the next meeting. Option C. Have a senior leader work with the new member to avoid a negative impact on team productivity. Option D. Privately work with the new member to address any impediments. Pause the video now if you want time to think about the answer.
The correct answer is D. Privately work with the new member to address any impediments. The new member is reluctant to communicate because of poor experiences on a previous team, so trust must be rebuilt before the member will speak freely in a group. A servant leader meets privately with the member, listens, and works with them to address any impediments they face. A one-on-one setting removes the pressure of an audience, shows that the leader genuinely cares about the member's concerns, and demonstrates through action that raising impediments leads to help. That foundation of trust allows the member to integrate into the mature team over time. Now, why are the other options incorrect? Option A is incorrect. Raising the member's impediments publicly before trust exists puts them on the spot and deepens the reluctance. Option B is incorrect. Promising that input is valued and then staging a demonstration in a group meeting still exposes a reluctant member before trust has been built. Option C is incorrect. Handing the member to a senior leader adds hierarchy and focuses on productivity rather than on the member's trust and impediments. Therefore, D, Privately work with the new member to address any impediments, is the correct answer.
Play from 46:39 Question 22. Part way through a project, several team members are in conflict over whether or not a deliverable has been properly completed. How should the agile leader reduce this conflict? Here are the options. Option A. Facilitate team agreement on the definition of done (DoD) during the chartering process. Option B. Motivate the team during Tuckman's "storming" phase. Option C. Ensure the product owner is grooming the backlog so user stories are clearly written. Option D. Ensure epics are broken down into smaller user stories for clarity. Pause the video now if you want time to think about the answer.
The correct answer is A. Facilitate team agreement on the definition of done (DoD) during the chartering process. The conflict is about whether a deliverable is complete, which is exactly what the definition of done (DoD) settles. The agile leader should facilitate team agreement on a shared DoD as part of team chartering, the working agreements the team establishes and can revisit at any point. A clear, agreed DoD removes ambiguity about completion, resolves the present dispute on objective grounds and prevents the same argument from recurring on later deliverables. Now, why are the other options incorrect? Option B is incorrect. Motivating the team during storming does not resolve the underlying disagreement about what done means. Option C is incorrect. Clearer user stories help understanding of scope but do not establish the shared quality standard for completion. Option D is incorrect. Splitting epics improves story size and clarity but does not define when a deliverable is done. Therefore, A, Facilitate team agreement on the definition of done (DoD) during the chartering process, is the correct answer.
Play from 48:49 Question 23. A product's scope and acceptance criteria have been detailed, and the product is planned for release at the end of the next quarter. What should the project team do next? Here are the options. Option A. Estimate the project team's capacity. Option B. Determine how much work can be delivered. Option C. Calculate how much work will fit into the next iteration. Option D. Estimate items in the product backlog. Pause the video now if you want time to think about the answer.
The correct answer is D. Estimate items in the product backlog. With scope and acceptance criteria defined and a release target at the end of the next quarter, the team is doing release planning. The first planning step is to estimate the product backlog items, usually in story points, so the total size of the release is known. Only then can the team apply its velocity to judge how much work fits in the release and in each iteration. Without sized backlog items, capacity figures have nothing to be compared against and any forecast of the release date would be a guess. Now, why are the other options incorrect? Option A is incorrect. Team capacity is useful only once the size of the backlog work is known, so it follows estimation. Option B is incorrect. Determining how much work can be delivered requires sized backlog items and a velocity, so it comes later. Option C is incorrect. Fitting work into the next iteration is an iteration planning activity that depends on estimated backlog items. Therefore, D, Estimate items in the product backlog, is the correct answer.
Play from 50:43 Question 24. When considering impact on a project, to whom should an agile project manager give top priority on the stakeholder list? Here are the options. Option A. The stakeholder who can prevent the project from delivering within budget. Option B. The stakeholder who can prevent the project from achieving its goals. Option C. The stakeholder who can delay the project. Option D. The stakeholder who can work as a friend and help prepare the stakeholder list. Pause the video now if you want time to think about the answer.
The correct answer is B. The stakeholder who can prevent the project from achieving its goals. Stakeholders are prioritized by their power to influence the project and the size of the impact they can have. The stakeholder who can prevent the project from achieving its goals can have the greatest impact of all, because the goals are the reason the project exists and the source of its value. Budget overruns and delays are serious, but they are narrower than outright failure to reach the objectives. This stakeholder needs the closest engagement: understanding their concerns early, keeping them informed and involving them in key decisions. Now, why are the other options incorrect? Option A is incorrect. Budget influence matters, but it is a narrower impact than blocking the project's goals. Option C is incorrect. A stakeholder who can cause delays affects the timeline but not, by themselves, whether the goals are achieved. Option D is incorrect. A friendly stakeholder who helps with the list has little influence over the project's outcome. Therefore, B, The stakeholder who can prevent the project from achieving its goals, is the correct answer.
Play from 52:45 Question 25. Prior to a retrospective, discussions among team members indicate conflict. An agile practitioner wants to ensure an open and safe environment during the retrospective. What should the agile practitioner do? Here are the options. Option A. Review established ground rules with the team. Option B. Ask team members specific questions to identify the cause. Option C. Encourage the team to continue working to maintain the iteration's schedule. Option D. Meet with the product owner and stakeholders to discuss the issue. Pause the video now if you want time to think about the answer.
The correct answer is A. Review established ground rules with the team. Psychological safety is essential for an effective retrospective, and signs of conflict make it more important to set the stage carefully. Reviewing the team's established ground rules at the start reminds everyone of the behaviors they agreed to, such as listening without interrupting, focusing on issues rather than people and assuming good intent. This frames the discussion, creates an open and safe environment and allows the conflict to be addressed constructively during the retrospective. Now, why are the other options incorrect? Option B is incorrect. Questioning individuals about the cause beforehand can feel like an interrogation and raise tension. Option C is incorrect. Pressing on with work ignores the conflict and does nothing to create a safe environment. Option D is incorrect. Taking a team matter to the product owner and stakeholders bypasses the team and reduces trust. Therefore, A, Review established ground rules with the team, is the correct answer.
Play from 54:47 Question 26. A newly formed team is struggling to work together and agree on how to complete tasks in the upcoming sprint. What should the scrum master do to support the team? Here are the options. Option A. Resolve the disagreement for the team as a servant leader. Option B. Encourage the team to continue trying to resolve their disagreements. Option C. Advise the team on the correct course of action to avoid disagreements. Option D. Remove the team members that are in disagreement to ensure unity in the team. Pause the video now if you want time to think about the answer.
The correct answer is B. Encourage the team to continue trying to resolve their disagreements. A newly formed team is expected to go through a storming stage as members learn to work together. The scrum master supports self-organization by encouraging the team to keep working through its disagreements, coaching and facilitating where helpful but not taking over. Resolving their own differences builds trust, shared working agreements, and ownership of how they plan the sprint, helping the team progress toward norming and performing. Now, why are the other options incorrect? Option A is incorrect. Resolving the disagreement for the team is directive and undermines self-organization; servant leaders facilitate rather than decide. Option C is incorrect. Telling the team the correct course of action removes their ownership of how they work. Option D is incorrect. Removing members is a drastic, punitive step that ignores normal team development. Therefore, B, Encourage the team to continue trying to resolve their disagreements, is the correct answer.
Play from 56:48 Question 27. Several team members are new to agile and there is a lot of confusion. It seems everyone is coming in with different experiences and following their own agendas. The scrum master decided to hold a presentation on core agile principles and values. What should the scrum master emphasize to the team during the presentation? Here are the options. Option A. The value of agile ceremonies and methods. Option B. Performance and chain of command. Option C. Product deliverables, procedures and features. Option D. Collaboration, value delivery and shared mindset. Pause the video now if you want time to think about the answer.
The correct answer is D. Collaboration, value delivery and shared mindset. A team whose members follow their own agendas needs a common foundation, and the core of agile is a mindset rather than a set of rituals. Emphasizing collaboration, the delivery of customer value and a shared mindset aligns everyone with the Agile Manifesto values and principles, such as individuals and interactions and customer collaboration. Once the team shares these values, the specific practices make sense and members can work toward a common goal instead of their individual habits. Now, why are the other options incorrect? Option A is incorrect. Focusing on ceremonies and methods teaches the mechanics of agile without the underlying values that resolve differing agendas. Option B is incorrect. Performance and chain of command reflect a hierarchical, command-and-control approach that conflicts with agile self-organization. Option C is incorrect. Deliverables, procedures and features are product and process details rather than the core principles and values of agile. Therefore, D, Collaboration, value delivery and shared mindset, is the correct answer.
Play from 58:59 Question 28. During the iteration planning of a newly onboarded agile team, the product owner adds a set of high priority user stories into the iteration backlog. What should the team do first to define the tasks needed to implement the user stories? Here are the options. Option A. Self-organize. Option B. Assign tasks to each team member. Option C. Meet with the customer. Option D. Identify the scrum master. Pause the video now if you want time to think about the answer.
The correct answer is A. Self-organize. Once the product owner has placed the priority stories into the iteration backlog, the developers self-organize to work out how the stories will be delivered. They break each story into tasks together, discuss approach and dependencies, and let members pull work according to skills and capacity. Self-organization is the agile expectation for a team at any stage, including a newly formed one, and it builds shared ownership of the iteration plan. No outside party assigns tasks, and the planning meeting already has the people it needs. Now, why are the other options incorrect? Option B is incorrect. Assigning tasks to each person is command and control and replaces the team pulling work collectively. Option C is incorrect. Clarifying needs comes through the product owner in refinement and planning, and it is not the first step in defining tasks. Option D is incorrect. The scrum master role is established before planning, and identifying it does nothing to define the tasks. Therefore, A, Self-organize, is the correct answer.
Play from 1:00:57 Question 29. There is a database feature requiring three members of a seven person team. A meeting is scheduled at the beginning of the sprint to go over technical needs to complete the story. Who should the Scrum Master invite to the meeting? Here are the options. Option A. The core team and the customer. Option B. The product owner and key stakeholders. Option C. The customer and the sponsor. Option D. The core team and the product owner. Pause the video now if you want time to think about the answer.
The correct answer is D. The core team and the product owner. A meeting at the start of the sprint to work through what a story needs should include the people doing the work and the person who can clarify it. The core team members contribute the technical knowledge and plan how to build the database feature, while the product owner explains the intent, value and acceptance criteria and answers questions about scope. Bringing the team and product owner together creates a shared understanding of the requirement without involving people who add little to the technical discussion. Now, why are the other options incorrect? Option A is incorrect. The customer is represented by the product owner and is not needed to work through technical implementation needs. Option B is incorrect. Key stakeholders do not do the work, and leaving out the core team removes the people who must plan the technical solution. Option C is incorrect. The customer and sponsor cannot plan the technical work, and this pairing omits both the team and the product owner. Therefore, D, The core team and the product owner, is the correct answer.
Play from 1:02:48 Question 30. An experienced product owner presents the epics and corresponding stories during a release planning session with the established team. The executive sponsor asks the team when the features will be delivered. What should the agile team do? Here are the options. Option A. Evaluate how much can be delivered based on the Scrum Master's estimation. Option B. Identify a set of user stories based on the team's velocity. Option C. Initiate an estimation session. Option D. Consult historical data for project completion. Pause the video now if you want time to think about the answer.
The correct answer is C. Initiate an estimation session. The product owner has just presented new epics and stories, so the work has not yet been sized. To answer the sponsor's question about delivery, the developers should first hold an estimation session (for example, relative sizing with planning poker) to estimate the stories. Once the stories carry estimates, the established team can apply its known velocity to forecast how many iterations the features will take and give the sponsor a realistic, evidence-based range. Estimates come from the people doing the work, which keeps the forecast credible and builds commitment to the release plan. Now, why are the other options incorrect? Option A is incorrect. Estimates belong to the developers who will do the work, not to the scrum master, so this undermines team ownership and accuracy. Option B is incorrect. Velocity cannot be applied to stories that have not yet been sized, so selecting stories by velocity skips a necessary step. Option D is incorrect. Historical project completion data does not describe the size of these new epics, so it cannot answer when these specific features will be delivered. Therefore, C, Initiate an estimation session, is the correct answer.
Play from 1:05:04 Question 31. A project team meets to estimate user stories for a sprint. While an important non-functional requirement must be delivered in the sprint, the estimate exceeds sprint capacity. What should the team do? Here are the options. Option A. Estimate only functional requirements that will impact product quality. Option B. Add team resources. Option C. Refer the issue to the product owner. Option D. Break non-functional requirements into those that can be delivered in the given sprint. Pause the video now if you want time to think about the answer.
The correct answer is D. Break non-functional requirements into those that can be delivered in the given sprint. When an important piece of work is too large for the sprint, the agile response is to split it rather than force it in or drop it. The team can break the non-functional requirement into smaller, independently verifiable parts, for example by component, threshold or scenario, and deliver the parts that fit within the sprint capacity while ordering the remainder for following sprints with the product owner. This keeps commitments realistic, lets the team make real progress on the requirement now and preserves a sustainable pace. Now, why are the other options incorrect? Option A is incorrect. Estimating only functional requirements ignores the non-functional requirement that must be delivered. Option B is incorrect. Adding people does not change capacity quickly and new members usually slow the team at first. Option C is incorrect. Referring the issue onward leaves the work too large; the team should first split it into deliverable parts. Therefore, D, Break non-functional requirements into those that can be delivered in the given sprint, is the correct answer.
Play from 1:07:08 Question 32. A graphic designer on an agile team does not attend most meetings. When asked the reason for not attending, the designer told the agile practitioner that the scrum master could represent them in meetings if needed. The team is frustrated and does not agree with this approach. Which conflict resolution method would work best in this scenario? Here are the options. Option A. Avoidance. Option B. Forcing. Option C. Accommodation. Option D. Collaborating. Pause the video now if you want time to think about the answer.
The correct answer is D. Collaborating. The designer skips most meetings and the team is frustrated, so the conflict concerns both the designer's needs and the team's need for engagement. Collaborating, also called problem solving, brings everyone together to discuss the underlying concerns openly, such as which meetings the designer finds valuable and what the team needs from them. It aims for a solution all parties commit to, preserves relationships, and reinforces shared ownership, which makes it the most effective and lasting method here. Now, why are the other options incorrect? Option A is incorrect. Avoidance leaves the frustration unresolved and lets the disengagement continue. Option B is incorrect. Forcing imposes a win-lose outcome that may gain attendance but harms trust and commitment. Option C is incorrect. Accommodation gives in to the designer's preference and ignores the team's legitimate concern. Therefore, D, Collaborating, is the correct answer.
Play from 1:09:02 Question 33. What should a product owner do when a new stakeholder is complaining that they are not receiving the relevant financial data regarding the project. Here are the options. Option A. Work with the scrum master to give the stakeholder access to the related information radiator. Option B. Invite the stakeholder to the next sprint planning session so they can ask questions of the team. Option C. Ask the team to prepare the requested data in the next iteration. Option D. Direct the stakeholder to the project team so they can provide more data. Pause the video now if you want time to think about the answer.
The correct answer is A. Work with the scrum master to give the stakeholder access to the related information radiator. Agile teams provide stakeholders with transparent, self-service access to project information through information radiators such as dashboards and burn charts. When a new stakeholder lacks the financial data they need, the product owner can work with the scrum master to give them access to the relevant radiator, which already displays the information. This answers the need quickly, keeps the data consistent for everyone, and avoids pulling developers away from their work to produce custom reports. Now, why are the other options incorrect? Option B is incorrect. Sprint planning is for the scrum team to plan the sprint, not a forum for stakeholder questions about finances. Option C is incorrect. Asking the team to compile data in the next iteration delays the stakeholder and diverts developers from product work. Option D is incorrect. Redirecting the stakeholder to the team interrupts developers and does not create lasting access to the information. Therefore, A, Work with the scrum master to give the stakeholder access to the related information radiator, is the correct answer.
Play from 1:11:13 Question 34. An organization wants to increase value delivery in its agile projects. What should the agile teams do? Here are the options. Option A. Perform analysis and development work, but no testing because that should be managed by another specialized team. Option B. Master available technology and tools to provide informative dashboards to the stakeholders. Option C. Work with product owners and turn product backlog items into potentially shippable product increments. Option D. Complete projects by their deadlines and share the budgets upfront with project sponsors. Pause the video now if you want time to think about the answer.
The correct answer is C. Work with product owners and turn product backlog items into potentially shippable product increments. Agile teams deliver value by frequently producing working, usable increments. Working closely with the product owner, who orders the product backlog by value, the team turns the highest-value backlog items into potentially shippable increments that meet the definition of done. Each increment can be reviewed, released and used, which provides early value, generates feedback and lets the product evolve toward what customers actually need. That is the most direct way for the teams to increase value delivery. Now, why are the other options incorrect? Option A is incorrect. Handing testing to a separate team breaks cross-functionality and produces work that is not done or shippable. Option B is incorrect. Dashboards improve visibility but do not themselves deliver product value to customers. Option D is incorrect. Meeting deadlines and sharing budgets is a plan-driven focus on constraints, not on delivering value incrementally. Therefore, C, Work with product owners and turn product backlog items into potentially shippable product increments, is the correct answer.
Play from 1:13:25 Question 35. What information should a project team include in an extended stakeholder report to ensure that all current and future stakeholders are aware of the frequent updates? Here are the options. Option A. Team capacity and competence profiles. Option B. A list of tools used for implementation. Option C. A list of open technical issues. Option D. Up-to-date project radiators. Pause the video now if you want time to think about the answer.
The correct answer is D. Up-to-date project radiators. Information radiators, such as burnup and burndown charts, task boards and release progress displays, show the project's current status in a form that is easy to take in at a glance. Including up-to-date radiators in an extended stakeholder report gives every current and future stakeholder the same transparent, frequently refreshed view of progress, so they can follow the frequent updates without needing extra explanation. This supports the transparency and stakeholder engagement that agile depends on. Now, why are the other options incorrect? Option A is incorrect. Capacity and competence profiles are internal team information and do not keep stakeholders up to date on progress. Option B is incorrect. A list of tools is static detail that tells stakeholders nothing about frequent progress updates. Option C is incorrect. A list of open technical issues is a narrow team-level view, not a full picture of project status. Therefore, D, Up-to-date project radiators, is the correct answer.
Play from 1:15:19 Question 36. A customer has difficulty explaining how the highest priority feature will work. What should the agile project manager do? Here are the options. Option A. Create a time-boxed spike story to reduce the technical risk of the feature. Option B. Commence an iteration 0 for the customer and the team to investigate the feature. Option C. Facilitate the decomposition of the feature epic into more manageable user stories. Option D. Facilitate a just-in-time exploration of the functionality by the customer and the team. Pause the video now if you want time to think about the answer.
The correct answer is D. Facilitate a just-in-time exploration of the functionality by the customer and the team. When a customer cannot fully describe how a feature should work, agile teams do not demand a complete specification up front. Instead, the agile project manager facilitates a just-in-time exploration in which the customer and the team examine the functionality together close to when it will be built, using conversations, examples, sketches or quick prototypes. Requirements emerge through this collaboration, and the details are discovered at the last responsible moment, when the most information is available and the cost of change is lowest. Now, why are the other options incorrect? Option A is incorrect. A spike targets technical uncertainty, while the problem here is unclear functional behavior that the customer cannot yet explain. Option B is incorrect. An iteration 0 is setup work at the start of a project and is a heavier response than needed for clarifying one feature. Option C is incorrect. Decomposing the feature into stories requires an understanding of the functionality that the customer has not yet been able to provide. Therefore, D, Facilitate a just-in-time exploration of the functionality by the customer and the team, is the correct answer.
Play from 1:17:40 Question 37. A product owner asks a newly formed scrum team how many story points will be completed in a sprint. What should the scrum master do? Here are the options. Option A. Engage the team to determine the sprint velocity based on previous agile projects. Option B. Average the sprint velocity based on input from team members. Option C. Share the sprint velocity obtained from the sponsor with the team. Option D. Run multiple sprints before determining the sprint velocity with the team. Pause the video now if you want time to think about the answer.
The correct answer is D. Run multiple sprints before determining the sprint velocity with the team. Velocity is an empirical measure of what a specific team actually completes in a sprint, so a newly formed team has no velocity yet. The scrum master should explain this to the product owner and help the team run several sprints, after which an average of the completed points gives a reliable velocity for forecasting. Until then, the team can forecast each sprint from its capacity, but any number given now would be a guess, and setting expectations on it would risk disappointment and loss of trust. Now, why are the other options incorrect? Option A is incorrect. Velocity from previous projects reflects different teams, work and contexts, so it does not represent this new team's capability. Option B is incorrect. Averaging individual opinions produces a guess rather than a measure, since velocity comes from what the team actually completes. Option C is incorrect. A sponsor cannot supply a team's velocity, and imposing a figure from outside undermines the team's ownership of its estimates. Therefore, D, Run multiple sprints before determining the sprint velocity with the team, is the correct answer.
Play from 1:19:59 Question 38. A company is considering developing a new, complex application that will require a large initial investment. However, if successful, the profit potential is high. When preparing an analysis, what should be used to encourage stakeholders who are concerned about project failure to authorize the initial investment? Here are the options. Option A. Calculated planned percent complete (PPC). Option B. Many small minimally marketable features (MMFs). Option C. Story points rather than cost estimates. Option D. Calculated earned value (EV). Pause the video now if you want time to think about the answer.
The correct answer is B. Many small minimally marketable features (MMFs). Stakeholders worried about failure on a large investment are reassured when value and learning arrive early. Planning the product as many small minimally marketable features, each the smallest set of functionality that delivers recognizable value to customers, allows incremental release and earlier returns. Each delivery validates assumptions and gives the stakeholders a decision point to continue, change direction or stop, so the investment is exposed in smaller steps and the risk of total failure is reduced. Now, why are the other options incorrect? Option A is incorrect. Planned percent complete reports schedule progress but does not reduce investment risk. Option C is incorrect. Story points are a relative sizing unit and do not reassure stakeholders about failure. Option D is incorrect. Earned value measures performance against plan after work starts and does not reduce the risk of the investment. Therefore, B, Many small minimally marketable features (MMFs), is the correct answer.
Play from 1:22:14 Question 39. A team member has made a mistake on a project. How should the scrum master address the mistake? Here are the options. Option A. Encourage all team members to follow existing processes. Option B. Require team members to complete a peer review of work and deliverables. Option C. Facilitate a retrospective to identify areas of improvement. Option D. Reward those who have the lowest occurrences of mistakes. Pause the video now if you want time to think about the answer.
The correct answer is C. Facilitate a retrospective to identify areas of improvement. The scrum master should treat the mistake as a learning opportunity rather than a matter of blame. Facilitating a retrospective lets the team examine what happened, find root causes in the process or environment and agree on improvement actions. This supports psychological safety, so people feel able to surface problems, and turns the mistake into continuous improvement for the whole team. Now, why are the other options incorrect? Option A is incorrect. Reinforcing existing processes assumes they are sound and skips understanding why the mistake happened. Option B is incorrect. Mandating peer reviews imposes a fix without diagnosis and bypasses the team's own improvement decisions. Option D is incorrect. Rewarding low error counts encourages hiding mistakes and undermines psychological safety. Therefore, C, Facilitate a retrospective to identify areas of improvement, is the correct answer.
Play from 1:24:04 Question 40. An agile team is planning the next iteration for a product release that has accumulated technical debt. What should the team do? Here are the options. Option A. Add code cleanup activities to the product backlog and request prioritization by the product owner. Option B. Add code cleanup activities to the next iteration and request clarification from the product owner. Option C. Add code cleanup activities to the next iteration and ask the product owner to end the current iteration. Option D. Add code cleanup activities to the next release backlog and request documentation from the product owner. Pause the video now if you want time to think about the answer.
The correct answer is A. Add code cleanup activities to the product backlog and request prioritization by the product owner. Technical debt is real work that competes for the same capacity as new features, so it should be made visible in the product backlog. The team adds the code cleanup items to the product backlog, explains their impact on quality, risk, and future velocity, and asks the product owner to prioritize them. This respects the product owner's accountability for ordering the backlog while giving the developers a transparent way to advocate for paying down debt. The prioritized cleanup work can then be pulled into upcoming iterations during planning. Now, why are the other options incorrect? Option B is incorrect. Placing cleanup work directly into the iteration bypasses backlog ordering, and the product owner is not the person to clarify technical cleanup tasks. Option C is incorrect. Nothing justifies cancelling the current iteration, which is a drastic step reserved for when its goal becomes obsolete. Option D is incorrect. A separate release backlog fragments the work, and the product owner is not responsible for producing technical documentation about the debt. Therefore, A, Add code cleanup activities to the product backlog and request prioritization by the product owner, is the correct answer.
Play from 1:26:33 Question 41. A product owner has various items in a product backlog and does not know how to prioritize them. How should the agile practitioner coach the product owner? Here are the options. Option A. Sort the stories in the backlog by descending story points and release the stories at the top of the list equal to the team's velocity. Option B. Prioritize the most valuable product features in the backlog first. Option C. Determine the features with the highest risk and release those first. Option D. Determine which features comprise the smallest feature set that could be successful in the market and establish viability of the product. Pause the video now if you want time to think about the answer.
The correct answer is B. Prioritize the most valuable product features in the backlog first. Value-driven delivery is the main principle for ordering a product backlog: the features that deliver the most value to customers and the business come first. The agile practitioner should coach the product owner to rank items by business value, weighing risk, dependencies and cost against that value with techniques such as MoSCoW or relative value scoring. Putting the highest-value work first maximizes return early, gives stakeholders useful increments sooner, and means that if the project ends early, the most important work has already been done. Now, why are the other options incorrect? Option A is incorrect. Sorting by story points orders the backlog by size, which has no connection to value. Option C is incorrect. Risk is one factor to weigh, but releasing whatever is riskiest first ignores the value it delivers. Option D is incorrect. Defining a minimum viable product applies to a launch decision and does not give a method for ordering an existing backlog. Therefore, B, Prioritize the most valuable product features in the backlog first, is the correct answer.
Play from 1:28:50 Question 42. What should a team do when they complete all sprint goals earlier than expected? Here are the options. Option A. Begin working on an item in the backlog. Option B. Ask the scrum master to select an item from the backlog on which to work. Option C. Ask the product owner to select an item from the backlog on which to work. Option D. Jointly decide with the scrum master on an item from the backlog on which to work. Pause the video now if you want time to think about the answer.
The correct answer is C. Ask the product owner to select an item from the backlog on which to work. The product owner is accountable for the product backlog and its ordering, so when the team finishes the sprint goal early, it should go to the product owner to identify the next item to work on. The developers and the product owner then agree on what can realistically be added to the sprint. This keeps the most valuable work flowing and respects the roles: the product owner decides what is most valuable next, while the developers decide how much they can take on. Now, why are the other options incorrect? Option A is incorrect. Starting a backlog item without consulting the product owner risks working on something that is not the highest priority. Option B is incorrect. The scrum master does not order the backlog or choose work for the team. Option D is incorrect. Deciding jointly with the scrum master still leaves out the product owner, who owns the backlog order. Therefore, C, Ask the product owner to select an item from the backlog on which to work, is the correct answer.
Play from 1:30:46 Question 43. The agile team disagrees with the business stakeholders on completing some epics. What could help eliminate misunderstandings? Here are the options. Option A. Agree on requirements with all stakeholders. Option B. Begin planning every four iterations. Option C. Consider previous sprint demo feedback when planning the next sprint. Option D. Include the reasons for the project in the contract. Pause the video now if you want time to think about the answer.
The correct answer is C. Consider previous sprint demo feedback when planning the next sprint. Misunderstandings between the team and business stakeholders are best removed through frequent inspection of working product. At each sprint review the team demonstrates the increment and stakeholders give feedback, and using that feedback when planning the next sprint shows stakeholders that their input shapes the work. Over successive sprints this feedback loop converges the team's and the stakeholders' understanding of what completing each epic requires, replacing assumptions with evidence from the actual product. Now, why are the other options incorrect? Option A is incorrect. Seeking one-time agreement on all requirements with every stakeholder is a big-upfront approach and does not keep understanding aligned as work proceeds. Option B is incorrect. Planning only every four iterations reduces the frequency of alignment and lets misunderstandings grow between planning points. Option D is incorrect. Stating the reasons for the project in a contract does not create the ongoing collaboration needed to resolve disagreements about the epics. Therefore, C, Consider previous sprint demo feedback when planning the next sprint, is the correct answer.
Play from 1:32:50 Question 44. An agile leader notices that a team member is becoming very quiet and disengaged in meetings. What should the agile leader do to identify team members' personalities and motivators? Here are the options. Option A. Use the DISC framework with each team member. Option B. Use MoSCoW ratings to keep people engaged. Option C. Hire a SAFe coach to provide encouragement. Option D. Employ BDUF to help with providing structure to meetings. Pause the video now if you want time to think about the answer.
The correct answer is A. Use the DISC framework with each team member. DISC is a behavioral assessment model describing four styles: dominance, influence, steadiness and conscientiousness. Using it with each team member helps the agile leader understand individual personalities, communication preferences and motivators, which can explain why someone has become quiet and disengaged. The leader can then adapt how they engage that person and help the team understand one another, supporting collaboration and psychological safety. Now, why are the other options incorrect? Option B is incorrect. MoSCoW is a requirements prioritization technique and reveals nothing about personalities or motivators. Option C is incorrect. A SAFe coach supports scaling agile across teams and is not a means of identifying individual personalities. Option D is incorrect. Big design up front is a design approach and has nothing to do with understanding team members. Therefore, A, Use the DISC framework with each team member, is the correct answer.
Play from 1:34:50 Question 45. An agile coach advised a project manager to continuously improve their ability to support their team and remove any obstacles in the project's way. What role is the agile coach advising to the project manager to take on? Here are the options. Option A. Scrum master. Option B. People manager. Option C. Servant leader. Option D. Squad leader. Pause the video now if you want time to think about the answer.
The correct answer is C. Servant leader. Servant leadership is the practice of leading by serving the team: understanding its needs, supporting its growth, and removing obstacles so it can deliver. The coach's advice to continuously improve support for the team and clear impediments describes exactly this leadership style. In agile environments, project managers are encouraged to adopt servant leadership rather than command-and-control behavior, focusing on enabling self-organizing teams to do their best work. Now, why are the other options incorrect? Option A is incorrect. Scrum master is a specific Scrum accountability, while the advice describes a leadership approach applicable to any project manager. Option B is incorrect. A people manager handles line responsibilities such as staffing and appraisals, not the team-serving stance described. Option D is incorrect. Squad leader is not a standard agile role and does not capture leading through service. Therefore, C, Servant leader, is the correct answer.
Play from 1:36:40 Question 46. When prioritizing features to be delivered in an iteration, on what should an agile team defer work? Here are the options. Option A. High-risk and high-value. Option B. High-risk and low-value. Option C. Low-risk and low-value. Option D. Low-risk and high value. Pause the video now if you want time to think about the answer.
The correct answer is C. Low-risk and low-value. In the value and risk prioritization model, high-value and high-risk features are done first, so the team delivers important functionality while retiring risk early. High-value and low-risk features come next. Low-value and low-risk features are done last, so these are the items the team defers to later iterations, and some may never be needed. Low-value and high-risk features fall into a separate category: they are avoided, because they bring risk without enough benefit to justify it. Now, why are the other options incorrect? Option A is incorrect. High-risk and high-value features are tackled first to deliver value and reduce uncertainty early, not deferred. Option B is incorrect. High-risk and low-value features are avoided altogether rather than simply scheduled for a later iteration. Option D is incorrect. Low-risk and high-value features deliver significant value with little uncertainty, so they are scheduled early. Therefore, C, Low-risk and low-value, is the correct answer.
Play from 1:38:31 Question 47. During a review session, a customer representative is concerned that a story fails to satisfy the scope of work. However, the product owner declares that the scope of work is complete. What should be done with this story? Here are the options. Option A. Mark it as incomplete and prioritize it for the next sprint. Option B. Mark it as complete, since the product owner has the final say. Option C. Discard it and create a new story for the remaining scope of work. Option D. Mark it as complete, since the team completed the scope of work. Pause the video now if you want time to think about the answer.
The correct answer is A. Mark it as incomplete and prioritize it for the next sprint. A story is done only when it meets its acceptance criteria and delivers what the customer needs. When the customer representative shows during the review that the story does not satisfy the scope of work, declaring it complete would misreport progress and ignore valid customer feedback. The honest and transparent response is to treat the story as incomplete, return it to the product backlog and have the product owner prioritize the remaining work, typically for the next sprint. This keeps velocity and progress reporting accurate and keeps the customer engaged in defining value. Now, why are the other options incorrect? Option B is incorrect. The product owner represents the customer and cannot override clear evidence that the agreed scope has not been met. Option C is incorrect. Discarding the story hides unfinished work and loses the history and effort already invested in it. Option D is incorrect. The team finishing its tasks does not make the story complete when the customer shows the scope is not satisfied. Therefore, A, Mark it as incomplete and prioritize it for the next sprint, is the correct answer.
Play from 1:40:44 Question 48. A software team is developing a product in an environment with increased uncertainty. Although there is a clear vision of the goals to be achieved, the product owner is not fully certain about how some of the product features should work. How should the product owner address this situation? Here are the options. Option A. Improve the product testing and quality assurance skills among the team. Option B. Facilitate more product planning sessions with the software team. Option C. Consider moving to a more predictive product development approach. Option D. Develop a prototype of the product to obtain feedback from users. Pause the video now if you want time to think about the answer.
The correct answer is D. Develop a prototype of the product to obtain feedback from users. When the goals are clear but how certain features should work is uncertain, the best way to reduce uncertainty is to learn from users quickly. A prototype lets users see and try the proposed behavior so the product owner can gather feedback, validate assumptions and refine the product backlog before the team invests heavily in full development. This applies validated learning and short feedback loops, which suit high-uncertainty environments far better than more planning or analysis. Now, why are the other options incorrect? Option A is incorrect. Better testing skills improve quality but do not clarify how the features should work. Option B is incorrect. More planning sessions rely on speculation instead of real user feedback. Option C is incorrect. Predictive approaches suit stable, well-understood requirements, not high uncertainty. Therefore, D, Develop a prototype of the product to obtain feedback from users, is the correct answer.
Play from 1:42:52 Question 49. On what should an agile team work to achieve predictable flow? Here are the options. Option A. Small user stories. Option B. Simple acceptance criteria. Option C. Lean features. Option D. Lean backlogs. Pause the video now if you want time to think about the answer.
The correct answer is A. Small user stories. Small user stories are the main lever for predictable flow. They are easier to understand and estimate, move through the workflow quickly and carry less hidden risk, so cycle times become shorter and less variable. Finishing small items often creates a steady stream of completed work, faster feedback and more reliable forecasts. Large items, by contrast, block work in progress, cause uneven throughput and make forecasts unreliable. Now, why are the other options incorrect? Option B is incorrect. Simple acceptance criteria may hide necessary conditions and do not by themselves smooth the flow of work. Option C is incorrect. Lean features is not an established agile practice for creating flow, and features are usually too large to flow smoothly. Option D is incorrect. Keeping the backlog lean reduces waste in refinement but does not make the flow of work through the team predictable. Therefore, A, Small user stories, is the correct answer.
Play from 1:44:36 Question 50. For what is the MoSCoW method used? Here are the options. Option A. Estimating story size. Option B. Prioritizing stories. Option C. Validating a product. Option D. Tracking progress. Pause the video now if you want time to think about the answer.
The correct answer is B. Prioritizing stories. MoSCoW is a prioritization technique that sorts requirements or user stories into must have, should have, could have and will not have this time. Teams and product owners use it to agree which items are essential for a release or time box and which can be deferred, making value-based trade-offs explicit when time or capacity is limited. It says nothing about the size of an item or the progress made on it. Now, why are the other options incorrect? Option A is incorrect. Story size is estimated with techniques such as story points, planning poker or affinity estimating. Option C is incorrect. Product validation relies on customer feedback, demonstrations and acceptance testing. Option D is incorrect. Progress is tracked with burndown or burnup charts, task boards and other information radiators. Therefore, B, Prioritizing stories, is the correct answer.
Play from 1:46:13 Question 51. An agile team notices that the same problems continue to occur during multiple iterations. Several team members have suggestions to fix the problem. What is the proper agile approach to handle this? Here are the options. Option A. Hold frequent retrospectives and share the responsibility for making changes. Option B. Understand that this is the nature of innovative business and strive to work harder. Option C. Collect team member feedback and discuss them privately with the product owner. Option D. Conduct a team-building exercise to increase trust among the team members. Pause the video now if you want time to think about the answer.
The correct answer is A. Hold frequent retrospectives and share the responsibility for making changes. Recurring problems across iterations call for inspection and adaptation, which is exactly what retrospectives provide. Holding retrospectives frequently gives the team a regular, safe forum to examine why the same issues keep appearing, evaluate the suggestions team members already have, and agree on concrete improvement actions. Sharing responsibility for making the changes builds collective ownership, so improvements are actually carried out and followed up rather than left to one person. This reflects the agile principle that at regular intervals the team reflects on how to become more effective and adjusts its behavior accordingly. Now, why are the other options incorrect? Option B is incorrect. Accepting recurring problems as inevitable and simply working harder ignores continuous improvement and risks an unsustainable pace. Option C is incorrect. Discussing feedback privately with the product owner removes transparency and takes the improvement decision away from the self-organizing team. Option D is incorrect. Nothing indicates a trust problem, and a team-building exercise does not address the specific process issues the team keeps encountering. Therefore, A, Hold frequent retrospectives and share the responsibility for making changes, is the correct answer.
Play from 1:48:43 Question 52. An agile team is working on the first sprint, and have already planned the second and third sprints. However, market conditions now require a change to the features. What should the product owner do? Here are the options. Option A. Communicate the importance of the business need to the team and refine the product backlog. Option B. Ask the team to discuss the changes to the features with the customer. Option C. Meet with the agile team lead to prioritize the requirements. Option D. Discuss and prioritize the requirements with the team. Pause the video now if you want time to think about the answer.
The correct answer is A. Communicate the importance of the business need to the team and refine the product backlog. Agile welcomes changing requirements, even late, to deliver customer advantage. The product owner is accountable for maximizing value and owns the product backlog, so when market conditions change they should explain the business need to the team, so everyone understands why the change matters, and refine the product backlog to reflect the new features and their order. Plans for later sprints are adapted through the backlog, which keeps the team aligned with the product goal and the market. Now, why are the other options incorrect? Option B is incorrect. Delegating the change discussion to the team abdicates the product owner's responsibility for the product backlog. Option C is incorrect. Prioritization belongs to the product owner, not to a meeting with a team lead. Option D is incorrect. The product owner seeks input from the team but remains accountable for backlog order, so prioritizing with the team is not the product owner's own action. Therefore, A, Communicate the importance of the business need to the team and refine the product backlog, is the correct answer.
Play from 1:50:56 Question 53. An agile coach is facing a dilemma: On one hand, there is a requirement that is vital and will consume all capacity of the team. On the other hand, there are some chore-related tasks that will improve the team's ability to produce results. The team insists on implementing these tasks since they will increase efficiency. What should the agile coach do? Here are the options. Option A. Characterize chores as low priority since they do not add obvious value to the product. Option B. Delegate chore-related tasks to another team. Option C. Escalate the issue to the shareholders/steering committee. Option D. Get the product owner and team to meet to prioritize the work. Pause the video now if you want time to think about the answer.
The correct answer is D. Get the product owner and team to meet to prioritize the work. The conflict is a prioritization question between a vital requirement and improvement chores that would raise the team's productivity. The product owner is accountable for ordering the backlog, and the developers understand the cost and benefit of the chores, so the agile coach should facilitate a conversation in which both sides share their information and reach a transparent decision. This respects each role, lets the team explain how the chores increase future capacity, and lets the product owner weigh that long-term gain against the immediate business value of the requirement. Now, why are the other options incorrect? Option A is incorrect. Labeling the chores low priority overrides the team's input and ignores the efficiency gains, and the coach does not own backlog order. Option B is incorrect. Handing the chores to another team removes them from the people who understand and benefit from them and does not resolve the prioritization question. Option C is incorrect. Escalating to a steering committee is unnecessary when the product owner and team can resolve the trade-off themselves through collaboration. Therefore, D, Get the product owner and team to meet to prioritize the work, is the correct answer.
Play from 1:53:24 Question 54. The risk profile of a project has increased beyond the upper threshold of tolerance. The product owner and project leader meet to discuss an approach for dealing with this. What should the team do next? Here are the options. Option A. Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints. Option B. Add risk mitigation time to each requirement. Option C. Apply the 80/20 rule, reserving 20 percent of each sprint's capacity for risk mitigation. Option D. Hold all risks until they become issues, then add issue resolution tasks to the product backlog. Pause the video now if you want time to think about the answer.
The correct answer is A. Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints. When the risk profile exceeds the tolerance threshold, the team must reduce exposure proactively. In agile, risk responses are handled as work: mitigation tasks are added to the backlog, forming a risk-adjusted backlog, and the product owner orders them alongside features based on value and risk reduction. Prioritizing them into the current and upcoming sprints makes the response visible and ensures it is actually delivered, and progress can be tracked with tools such as a risk burndown chart. Now, why are the other options incorrect? Option B is incorrect. Padding every requirement with time is not a targeted response, and it hides the mitigation work instead of making it visible and prioritized. Option C is incorrect. A fixed capacity reserve is arbitrary and does not identify or order the specific actions needed to bring the risks back within tolerance. Option D is incorrect. Waiting for risks to become issues abandons proactive risk management when exposure is already beyond tolerance. Therefore, A, Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints, is the correct answer.
Play from 1:55:46 Question 55. A project manager is working on an agile team. A team member mentions that risks threatening the release date of the current sprint are not being addressed. What should the project manager do to make sure team members are following up on risks? Here are the options. Option A. Hold one daily coordination meeting to determine the reason team members are not following up on risks. Option B. Ask the team to review the executed tasks and follow up on the upcoming threats. Option C. Display the major risks, assumptions, issues, and dependencies (RAID) log visually to highlight the risk status. Option D. Create one sprint to update and follow up on major release risks. Pause the video now if you want time to think about the answer.
The correct answer is C. Display the major risks, assumptions, issues, and dependencies (RAID) log visually to highlight the risk status. Making risks visible is the agile way to ensure they are followed up. Displaying the risks, assumptions, issues and dependencies (RAID) log as an information radiator shows the status of the major risks to everyone at all times, so the team sees which threats to the release date are unaddressed and who owns them. This transparency prompts the team to act on risks during its normal work and events, such as the daily standup, without the project manager having to chase individuals. Now, why are the other options incorrect? Option A is incorrect. A meeting to find out why risks are not followed up investigates blame rather than making risk status visible. Option B is incorrect. Reviewing executed tasks looks backward and does not keep risk status continuously visible. Option D is incorrect. Dedicating a whole sprint to risk follow-up delays value delivery and treats risk management as a separate phase. Therefore, C, Display the major risks, assumptions, issues, and dependencies (RAID) log visually to highlight the risk status, is the correct answer.
Play from 1:58:10 Question 56. During the implementation of a story, a scrum team notifies the scrum master of a technical challenge that is causing a delay. What should the scrum master advise the team to do? Here are the options. Option A. Implement the story since the team is running behind schedule. Option B. Create a spike to finalize the story's technical approach. Option C. Transfer the story to a scrum team experienced in solving similar problems. Option D. Ask the product owner to reduce the story's priority and wait until more technical details are available. Pause the video now if you want time to think about the answer.
The correct answer is B. Create a spike to finalize the story's technical approach. A spike is a short, time-boxed piece of research or prototyping used to reduce technical uncertainty before committing to an approach. When a technical challenge is delaying a story, the scrum master should coach the team to run a spike so it can explore options, learn quickly and settle the technical approach. The outcome of the spike lets the team implement the story with confidence and produce better estimates, which reduces the risk of rework and wasted effort from pushing ahead on an unproven design. Now, why are the other options incorrect? Option A is incorrect. Pushing ahead with implementation while the technical approach is unresolved invites rework and quality problems. Option C is incorrect. Handing the story to another team creates a dependency and prevents this team from building its own capability. Option D is incorrect. Deprioritizing the story and waiting does nothing to resolve the uncertainty, which only the team's investigation will reduce. Therefore, B, Create a spike to finalize the story's technical approach, is the correct answer.
Play from 2:00:26 Question 57. During a daily stand up meeting, a developer expresses concerns that the selected technology limits the number of concurrent users. What should the agile team do? Here are the options. Option A. Ask the team to conduct research to find a viable solution. Option B. Select a better technology for team implementation. Option C. Obtain customer input on their technology requirements. Option D. Consult the product owner about their non-functional requirements. Pause the video now if you want time to think about the answer.
The correct answer is A. Ask the team to conduct research to find a viable solution. A limit on concurrent users is a technical constraint, and the developers are the people best placed to investigate it. In keeping with self-organization, the team should take the concern raised at the daily stand-up and conduct focused research, often as a time-boxed spike, to understand the limitation and find a viable solution. This produces facts rather than guesses, lets the team bring concrete options and their trade-offs to the product owner, and resolves the risk early before more work is built on the technology. Now, why are the other options incorrect? Option B is incorrect. Replacing the technology is a large, premature decision made before the team has investigated the limitation or its options. Option C is incorrect. Customers are not the right people to resolve a technical constraint, and going to them directly bypasses the product owner. Option D is incorrect. Discussing requirements with the product owner does not tell the team whether the technology can be made to work, so the constraint stays unresolved. Therefore, A, Ask the team to conduct research to find a viable solution, is the correct answer.
Play from 2:02:40 Question 58. The team underestimated the complexity of a story, resulting in new decomposition of the work to be delivered in the current sprint and items to be returned to the backlog. What should the Scrum Master do next? Here are the options. Option A. Ask the project manager to work with the product owner to help generate clearer stories in the future. Option B. Develop guidelines to prevent future occurrences. Option C. During the retrospective, discuss the issue and create an action plan to avoid it in the future. Option D. Allow the team to devise a corrective action without external intervention. Pause the video now if you want time to think about the answer.
The correct answer is C. During the retrospective, discuss the issue and create an action plan to avoid it in the future. The underestimated story has already been handled within the sprint by decomposing the work and returning items to the backlog. The next step for the scrum master is to help the team learn from it: in the sprint retrospective, the scrum master facilitates a discussion of why the complexity was missed, such as unclear stories or insufficient refinement, and the team creates its own action plan to avoid a repeat. This keeps improvement in the team's hands and turns the event into lasting learning. Now, why are the other options incorrect? Option A is incorrect. Routing the issue through a project manager bypasses the scrum team, which owns its own improvement. Option B is incorrect. Guidelines written by the scrum master are imposed on the team rather than created and owned by it. Option D is incorrect. Stepping back entirely abandons the scrum master's role of facilitating the team's inspection and adaptation. Therefore, C, During the retrospective, discuss the issue and create an action plan to avoid it in the future, is the correct answer.
Play from 2:04:57 Question 59. A seven-member agile team's composition varies considerably in age, gender, culture, personality type, and professional background. When planning a team-building event, what type of interpersonal skills should the project leader use? Here are the options. Option A. Networking. Option B. Social awareness. Option C. Communication. Option D. Leadership. Pause the video now if you want time to think about the answer.
The correct answer is B. Social awareness. Social awareness, a component of emotional intelligence, is the ability to perceive and understand the feelings, needs and perspectives of others, including people of different ages, cultures, genders, personalities and backgrounds. When planning a team-building event for a diverse team, the leader needs this skill to choose activities that are inclusive and comfortable for everyone and that build trust rather than alienating some members. Sensitivity to these differences is what makes the event effective at bringing the team together. Now, why are the other options incorrect? Option A is incorrect. Networking builds professional contacts outside the team and does not address sensitivity to team diversity. Option C is incorrect. Communication matters in every situation, but it does not specifically address understanding diverse needs and perspectives. Option D is incorrect. Leadership is a broad capability and does not name the specific skill of reading and respecting differences among people. Therefore, B, Social awareness, is the correct answer.
Play from 2:06:53 Question 60. A stakeholder complains about the amount of changes that are being introduced to a project. What should the product owner do? Here are the options. Option A. Escalate the complaint to the scrum master. Option B. Suggest implementing a more rigorous change governance. Option C. Coach the stakeholder on agile principles. Option D. Agree to limit scope changes going forward to control costs. Pause the video now if you want time to think about the answer.
The correct answer is C. Coach the stakeholder on agile principles. Agile approaches welcome changing requirements, even late in development, because they help the customer gain a competitive advantage. A stakeholder who is uncomfortable with frequent change may expect a traditional, fixed-scope approach. The product owner should coach the stakeholder on agile principles, explaining how short iterations, continuous prioritization of the product backlog, and frequent feedback keep the product aligned with the most valuable needs and manage the effect of change. Now, why are the other options incorrect? Option A is incorrect. Escalating to the scrum master is unnecessary when the product owner can address the stakeholder directly. Option B is incorrect. A more rigorous change governance slows responsiveness and runs against agile principles. Option D is incorrect. Limiting scope changes discards the value of adapting to new information. Therefore, C, Coach the stakeholder on agile principles, is the correct answer.
Play from 2:08:42 Question 61. A key resource is switching between projects to obtain more visibility and acclaim. However, project work has grown and become a burden. What should the agile project leader do? Here are the options. Option A. Add more resources to projects to ensure work sharing. Option B. Encourage the resource to undergo time management training. Option C. Ask management to ensure that the resource is available to only one project at a time. Option D. Allow the resource to continue switching between projects to deliver high customer value. Pause the video now if you want time to think about the answer.
The correct answer is C. Ask management to ensure that the resource is available to only one project at a time. Constant switching between projects causes heavy context-switching losses, slows every project the person works on and leads to overload and burnout. Agile favors stable, dedicated team members who focus on one body of work, which keeps flow and velocity predictable. Because resource allocation across projects is an organizational decision, the agile project leader should work with management to make the key resource available to one project at a time. This removes the impediment at its root instead of treating its symptoms. Now, why are the other options incorrect? Option A is incorrect. Adding more people does not stop the key resource from multitasking and creates onboarding overhead of its own. Option B is incorrect. Time management training puts the burden on the individual while the structural multitasking problem remains. Option D is incorrect. Letting the switching continue keeps the overload and context-switching waste that are already hurting the work. Therefore, C, Ask management to ensure that the resource is available to only one project at a time, is the correct answer.
Play from 2:10:53 Question 62. What is the risk of using agile in a distributed team? Here are the options. Option A. Frequent integration of work produced. Option B. Lack of shared knowledge of user stories. Option C. Need for more locations to learn agile. Option D. Unclear team structure. Pause the video now if you want time to think about the answer.
The correct answer is B. Lack of shared knowledge of user stories. Agile relies heavily on conversation to build shared understanding of user stories, with the story card serving as a reminder for a discussion rather than a full specification. When team members are distributed, those informal conversations happen less often, so members may interpret stories differently. This lack of shared knowledge of user stories leads to misaligned work, rework and defects, making it a key risk for distributed agile teams that must be offset with deliberate communication and refinement practices. Now, why are the other options incorrect? Option A is incorrect. Frequent integration is a beneficial agile practice that reduces risk rather than creating it. Option C is incorrect. Teaching agile in several locations is a logistical matter, not a core delivery risk. Option D is incorrect. Agile defines clear team roles, and distribution does not inherently make the team structure unclear. Therefore, B, Lack of shared knowledge of user stories, is the correct answer.
Play from 2:12:45 Question 63. A scrum team has eight developers, but only two are database engineers. During the last few retrospectives, the team identified that most sprint stories are dependent upon database engineers. This has created a bottleneck in completing stories. What should be proposed to the team? Here are the options. Option A. Have other team developers attend training to learn database skills. Option B. Monitor the retrospectives of two additional sprints before taking action. Option C. Plan fewer stories for the sprint to reduce the database engineer's workload. Option D. Ask the scrum master to work with the product owner to remove backlog stories that have database dependency. Pause the video now if you want time to think about the answer.
The correct answer is A. Have other team developers attend training to learn database skills. A recurring bottleneck caused by only two database engineers shows the team is not cross-functional enough for its work. Proposing that other developers train in database skills builds T-shaped team members who can share the load, reduces dependency on specialists and increases the team's flow and resilience. The issue has already surfaced in several retrospectives, so it is time to act on the root cause rather than wait or reduce delivery. Now, why are the other options incorrect? Option B is incorrect. The bottleneck has already been confirmed over several retrospectives, so further waiting only prolongs it. Option C is incorrect. Planning fewer stories treats the symptom and lowers delivery without removing the skill dependency. Option D is incorrect. Removing valuable stories because of a team skill gap sacrifices customer value instead of fixing the team's capability. Therefore, A, Have other team developers attend training to learn database skills, is the correct answer.
Play from 2:14:58 Question 64. A scrum master is part of a project team using technologies overseen by the IT department. The IT director oversees several company initiatives and is unfamiliar with the details of each one. As an active project stakeholder, to which meeting should the IT director be invited? Here are the options. Option A. Planning. Option B. Daily scrum. Option C. Sprint demo. Option D. Retrospective. Pause the video now if you want time to think about the answer.
The correct answer is C. Sprint demo. The sprint demo, or sprint review, is the event designed for stakeholders. The scrum team shows the increment, and stakeholders discuss progress, give feedback and help adapt the product backlog. For an IT director who oversees several initiatives and is not involved in the details, the review offers a concise view of real progress and a direct chance to influence direction without taking part in the team's working sessions. Now, why are the other options incorrect? Option A is incorrect. Planning is a working session for the scrum team to forecast and plan the sprint, not an event aimed at stakeholders. Option B is incorrect. The daily scrum is a short event for the developers to inspect progress and adapt their plan, not a stakeholder forum. Option D is incorrect. The retrospective is for the scrum team to examine its own way of working, and outside attendees can reduce psychological safety. Therefore, C, Sprint demo, is the correct answer.
Play from 2:16:49 Question 65. A large, corporate organization is forced to hire new team members in a geographically remote location from the current team. The manager of the department is concerned about the team not being colocated. What behavior would indicate the team is not working well together? Here are the options. Option A. Team members are sending more emails to the team. Option B. The duration of feedback cycles has increased. Option C. The velocity has increased by having the new team work on items. Option D. New team members requested to move meetings due to time differences. Pause the video now if you want time to think about the answer.
The correct answer is B. The duration of feedback cycles has increased. Agile depends on short, frequent feedback loops between team members and with the customer. When a team is not collaborating well across locations, questions wait for answers, reviews stall and handoffs slow down, so the time needed to get feedback grows. A lengthening feedback cycle is therefore a clear signal that communication and collaboration are breaking down, and it directly reduces the team's ability to inspect and adapt. It is an observable symptom the team can discuss in a retrospective and address with better tools, overlapping hours or working agreements. Now, why are the other options incorrect? Option A is incorrect. More emails can simply reflect adjustment to distributed work and do not by themselves show poor teamwork. Option C is incorrect. Rising velocity after adding the new members suggests the team is delivering more, not that it is struggling. Option D is incorrect. Asking to move meetings for time zones is a normal, healthy adjustment for a distributed team. Therefore, B, The duration of feedback cycles has increased, is the correct answer.
Play from 2:19:08 Question 66. A new CIO advocates an agile framework for new IT projects, but the team has reservations. How should the CIO ensure that the team will be aligned with this? Here are the options. Option A. Obtain executive team buy-in by conducting a meeting to present the advantages of agile principles and processes. Option B. Issue a memo of understanding that agile principles should be implemented for all new projects. Option C. Introduce agile principles and processes, then make the change an experiment to obtain buy-in. Option D. Require all staff and management to attend agile training and adhere to its principles. Pause the video now if you want time to think about the answer.
The correct answer is A. Obtain executive team buy-in by conducting a meeting to present the advantages of agile principles and processes. Agile adoption succeeds only when leadership supports it, because executives set the priorities, funding, governance and reward systems teams work within. Executive sponsorship is a key condition for an agile transformation. By presenting the advantages of agile principles and processes to the executive team and obtaining their buy-in, the CIO secures visible, consistent support from the top. Managers can then remove organizational obstacles, and the team sees that the change is backed and lasting, which eases their reservations and aligns them with the new way of working. Now, why are the other options incorrect? Option B is incorrect. A memo mandating agile imposes the change from the top and tends to deepen resistance. Option C is incorrect. Running agile as an experiment without leadership backing leaves the team unsure the change will last and without support to remove organizational obstacles. Option D is incorrect. Compulsory training with an order to comply relies on mandate rather than building genuine team alignment. Therefore, A, Obtain executive team buy-in by conducting a meeting to present the advantages of agile principles and processes, is the correct answer.
Play from 2:21:37 Question 67. A product owner complains that some of the requirements identified several iterations ago have not been implemented. The product owner wants to know why the status of these requirements was not communicated. What should the Scrum Master do? Here are the options. Option A. Point out that the team chose to work on other requirements to speed up the project. Option B. Ensure that the product owner reviews the contents of the information radiator. Option C. Ensure that the next sprint planning meeting reviews the satisfaction histogram. Option D. Point out that it is the responsibility of the product owner to clarify requirements. Pause the video now if you want time to think about the answer.
The correct answer is B. Ensure that the product owner reviews the contents of the information radiator. The product owner's complaint is about status communication, not prioritization or requirement clarity. Agile teams communicate status through information radiators such as the task board, burndown chart, and product backlog view, which are highly visible and always current. The scrum master should make sure the product owner knows where this information lives and reviews it regularly, so that the status of every requirement is visible without waiting for someone to report it. This reinforces transparency and helps the product owner manage the backlog with accurate information. Now, why are the other options incorrect? Option A is incorrect. Pointing out the team's choice sounds defensive and does not fix the communication gap the product owner raised. Option C is incorrect. A satisfaction histogram measures team or stakeholder satisfaction and says nothing about requirement status. Option D is incorrect. Requirement clarification is not the issue raised, and deflecting responsibility damages collaboration. Therefore, B, Ensure that the product owner reviews the contents of the information radiator, is the correct answer.
Play from 2:23:54 Question 68. Why is stakeholder engagement important for project success? Here are the options. Option A. To participate in establishing a shared vision as a member of the team. Option B. To provide the acceptance criteria for the delivered items. Option C. To propose implementation methods to the development team. Option D. To evaluate the performance of the development team. Pause the video now if you want time to think about the answer.
The correct answer is A. To participate in establishing a shared vision as a member of the team. Stakeholder engagement matters because stakeholders help shape and share the vision of what the project must achieve. When they collaborate with the team in establishing that vision, everyone works toward the same goals, priorities reflect real business needs and feedback throughout the project stays aligned with expected outcomes. This shared vision underpins every later activity, from backlog ordering to acceptance, which is why engagement is central to project success in an agile approach. Now, why are the other options incorrect? Option B is incorrect. Acceptance criteria are one narrow contribution, worked out with the product owner, not the reason engagement drives success. Option C is incorrect. Implementation methods belong to the development team, not to stakeholders. Option D is incorrect. Evaluating the development team's performance is not the purpose of stakeholder engagement. Therefore, A, To participate in establishing a shared vision as a member of the team, is the correct answer.
Play from 2:25:50 Question 69. During an iteration planning meeting, the team suggests changes to add product value that will require extra work and impact the schedule. What should the agile project leader do? Here are the options. Option A. Re-estimate the project. Option B. Finish the product as it was initially planned. Option C. Try to include as many changes as possible. Option D. Ask the product owner for approval to proceed. Pause the video now if you want time to think about the answer.
The correct answer is D. Ask the product owner for approval to proceed. The product owner is accountable for maximizing product value and for the content and order of the product backlog. When the team proposes changes that add value but also add work and affect the schedule, the agile project leader should bring them to the product owner, who weighs the added value against the cost and schedule impact and decides whether and when to include them. This keeps scope decisions with the role that owns them and keeps the team focused on the highest-value work. Now, why are the other options incorrect? Option A is incorrect. Re-estimating the whole project is premature before anyone has decided whether the changes should be made. Option B is incorrect. Rejecting the changes outright ignores potential value and takes the decision away from the product owner. Option C is incorrect. Absorbing as many changes as possible without a prioritization decision invites scope creep and overcommitment. Therefore, D, Ask the product owner for approval to proceed, is the correct answer.
Play from 2:27:47 Question 70. New stakeholders are joining a project team where the agile coach will educate them about their roles and responsibilities. How should the stakeholders ensure their objectives are met by product delivery? Here are the options. Option A. Provide feedback for completed user stories. Option B. Define how the features will be implemented. Option C. Tell the team which features to include in the backlog. Option D. Write acceptance criteria for the user stories. Pause the video now if you want time to think about the answer.
The correct answer is D. Write acceptance criteria for the user stories. Acceptance criteria state the conditions a user story must satisfy to be accepted, so they are the most direct way for stakeholders to make sure their objectives are built into the product. By contributing to or writing acceptance criteria with the product owner, stakeholders express what success looks like before development starts, the team gains a clear target for design and testing, and the story is verified against those conditions when it is completed. This links stakeholder expectations to delivery throughout the iteration, not only at the end. Now, why are the other options incorrect? Option A is incorrect. Feedback on completed stories arrives after the work is done and reacts to results rather than defining the objectives up front. Option B is incorrect. How features are implemented is decided by the developers, not by stakeholders. Option C is incorrect. Stakeholders can propose features, but the product owner decides the content and order of the product backlog. Therefore, D, Write acceptance criteria for the user stories, is the correct answer.
Play from 2:29:50 Question 71. Midway through a two-week sprint, an agile team realizes that the features cannot be delivered within the sprint. The team determines that another week will be required to complete all committed features. What should the team do? Here are the options. Option A. Plan for overtime, and include the effort as part of the estimation. Option B. Increase team velocity to deliver more story points. Option C. Identify the reason for over-commitment to the sprint and create an action plan for the following sprint. Option D. Add resources to assist with sprint execution. Pause the video now if you want time to think about the answer.
The correct answer is C. Identify the reason for over-commitment to the sprint and create an action plan for the following sprint. A sprint is a fixed timebox, so the team does not stretch it by a week or overload itself to rescue the plan. It works with the product owner on what can still be completed, returns unfinished work to the product backlog and treats the shortfall as learning. Identifying why it overcommitted, whether through estimation errors, hidden complexity or ignoring past velocity, and agreeing on improvement actions in the sprint retrospective lets the next sprint be planned realistically and sustains a predictable pace. Now, why are the other options incorrect? Option A is incorrect. Planned overtime breaks sustainable pace and hides the planning problem instead of fixing it. Option B is incorrect. Velocity reflects work actually completed, and raising it on demand is not something a team can simply choose to do. Option D is incorrect. Adding people mid-sprint brings onboarding overhead and rarely speeds up delivery in the short term. Therefore, C, Identify the reason for over-commitment to the sprint and create an action plan for the following sprint, is the correct answer.
Play from 2:32:07 Question 72. An agile team is optimizing the workflow by investing in initiatives to identify and reduce unnecessary handovers and delays. What should the team do in this situation? Here are the options. Option A. Create a value stream map. Option B. Draw a risk burndown chart. Option C. Use a kanban board. Option D. Make a cumulative flow diagram. Pause the video now if you want time to think about the answer.
The correct answer is A. Create a value stream map. A value stream map is a Lean tool that charts every step required to deliver value, from request to delivery, and records both the time spent adding value and the time spent waiting between steps. By making handoffs, queues and delays explicit, it shows where non-value-adding activity occurs and where the process can be simplified. That makes it the right tool for a team specifically seeking to identify and reduce unnecessary handovers and delays across its workflow. Now, why are the other options incorrect? Option B is incorrect. A risk burndown chart tracks risk exposure over time and does not reveal handovers or waiting time. Option C is incorrect. A kanban board visualizes current work states but does not analyze end-to-end handoffs and delays. Option D is incorrect. A cumulative flow diagram shows work quantities by state over time, not the specific handovers between process steps. Therefore, A, Create a value stream map, is the correct answer.
Play from 2:34:05 Question 73. When working with Lean approaches, which process includes the sequence of steps for delivering value and those required to carry them out? Here are the options. Option A. Value stream mapping. Option B. Long-term Lean planning. Option C. Business process modeling. Option D. Planning poker. Pause the video now if you want time to think about the answer.
The correct answer is A. Value stream mapping. Value stream mapping is the Lean technique that captures the full sequence of steps needed to deliver value to the customer, together with the activities, handoffs and waiting time involved in carrying them out. By mapping the current state, the team distinguishes value-adding steps from waste such as delays and rework, and then designs a future state with a smoother, faster flow. It is a primary Lean tool for identifying and eliminating waste across a process. Now, why are the other options incorrect? Option B is incorrect. Long-term Lean planning is not a defined Lean technique for mapping the steps that deliver value. Option C is incorrect. Business process modeling documents workflows generally but does not focus on value and waste in the Lean sense. Option D is incorrect. Planning poker is a relative estimation technique and does not map a delivery process. Therefore, A, Value stream mapping, is the correct answer.
Play from 2:35:52 Question 74. During a planning session, four out of five team members vote to include eight story points in a particular story, while the fifth member votes for five story points. How should this be handled? Here are the options. Option A. The story should be assigned eight story points as per the majority vote. Option B. The story should be added to the backlog and reassessed later. Option C. The story should be assigned points after a discussion with the fifth team member to see if a consensus can be reached. Option D. The decision for the number of story points should be made by the customer. Pause the video now if you want time to think about the answer.
The correct answer is C. The story should be assigned points after a discussion with the fifth team member to see if a consensus can be reached. Relative estimation techniques such as planning poker aim for consensus, and the value of a differing estimate lies in the conversation it starts. The team member who voted five may see a simpler approach, or the others may know about complexity that this person has missed. The team should discuss the reasoning behind the differing estimate and, if needed, vote again until it converges on a value everyone accepts. This shared understanding of the story is often more valuable than the number itself. Now, why are the other options incorrect? Option A is incorrect. Taking the majority vote skips the discussion that could reveal important information about the story. Option B is incorrect. Deferring the story delays planning without resolving the small difference in understanding. Option D is incorrect. Estimates belong to the people doing the work, not to the customer. Therefore, C, The story should be assigned points after a discussion with the fifth team member to see if a consensus can be reached, is the correct answer.
Play from 2:38:04 Question 75. A senior team member feels underutilized. What should the agile practitioner do? Here are the options. Option A. Transfer the senior member to another team that will more fully utilize their skill set. Option B. Conduct a performance evaluation to determine whether or not this member is a team player. Option C. Encourage the project team to involve the senior member in more project activities. Option D. Ask the functional manager to determine the best course of action. Pause the video now if you want time to think about the answer.
The correct answer is C. Encourage the project team to involve the senior member in more project activities. In a self-organizing team, members decide together how to use each other's skills. The agile practitioner should encourage the team to involve the senior member in more activities, such as complex stories, design discussions, pairing and mentoring. This puts the member's experience to work, raises engagement and increases the capability of the whole team. The practitioner acts as a coach who helps the team solve the issue internally rather than moving people or escalating. Now, why are the other options incorrect? Option A is incorrect. Transferring the member removes valuable expertise from the team without trying to engage them first. Option B is incorrect. A performance evaluation treats an engagement concern as a performance problem and damages trust. Option D is incorrect. Handing the issue to the functional manager bypasses the team's ability to self-organize. Therefore, C, Encourage the project team to involve the senior member in more project activities, is the correct answer.
Play from 2:40:06 Question 76. An agile team member from a cross-functional team has been unable to complete assignments due to tasks assigned by the functional manager. What should the scrum master do? Here are the options. Option A. Dismiss the team member. Option B. Discuss the situation with the functional manager. Option C. Report the functional manager to the project sponsor. Option D. Demand that the functional manager respect the project charter. Pause the video now if you want time to think about the answer.
The correct answer is B. Discuss the situation with the functional manager. Competing assignments from a functional manager are an impediment that the team member cannot easily resolve alone. The scrum master removes impediments and works across organizational boundaries, so the right step is a collaborative conversation with the functional manager to understand the competing demands, explain the effect on the team's commitments, and agree on how the team member's availability will be handled. Direct, respectful dialogue usually resolves the conflict and preserves a relationship the team will continue to need. Now, why are the other options incorrect? Option A is incorrect. Dismissing the team member punishes the person for an organizational conflict and does not remove the cause. Option C is incorrect. Reporting to the sponsor escalates before any attempt at direct resolution and damages trust. Option D is incorrect. Making demands is confrontational and less effective than collaborative problem solving. Therefore, B, Discuss the situation with the functional manager, is the correct answer.
Play from 2:42:03
The correct answer is A. Share the information radiator. Agile teams keep progress visible at all times through information radiators such as a task board, burndown chart or Kanban board. These displays show the current state of the iteration in real time, so a customer representative asking midway through the iteration can see exactly where the work stands without waiting for a formal report or a scheduled event. Sharing the information radiator supports transparency, requires no extra reporting effort and gives the most up-to-date view of progress. Now, why are the other options incorrect? Option B is incorrect. A release plan shows intended timing at a high level, not the current progress within the iteration. Option C is incorrect. The retrospective is the team's event for improving its process and is not the place to give a customer a progress update. Option D is incorrect. A project report is a static snapshot that may already be outdated and adds documentation overhead compared with a live radiator. Therefore, A, Share the information radiator, is the correct answer.
Play from 2:44:04 Question 78. Early in a project, stakeholder analysis is performed; however, an organizational restructure redefines key roles. What should the project team do? Here are the options. Option A. Note the changes to the restructure and roles that affect team activities. Option B. Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements. Option C. Email a copy of the project vision to those redefined for key roles and ask if they need to be involved in the project. Option D. Obtain a copy of the redefined key roles to update the stakeholder analysis. Pause the video now if you want time to think about the answer.
The correct answer is B. Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements. Stakeholder analysis is not a one-time activity. When an organizational restructure redefines key roles, the people who hold influence, interest, and requirements may have changed, so the team should engage the affected stakeholders directly and hold two-way conversations to refresh the analysis. Direct engagement uncovers new needs, concerns, and expectations that an organization chart cannot reveal, and it builds the collaborative relationships that agile delivery depends on. Updating the analysis in this way keeps the product backlog and engagement approach aligned with the people who now shape the outcome. Now, why are the other options incorrect? Option A is incorrect. Merely noting the changes records the restructure but does nothing to learn what the new stakeholders need from the project. Option C is incorrect. Emailing the vision is one-way communication that leaves it to recipients to decide their involvement and rarely surfaces real requirements. Option D is incorrect. A list of redefined roles shows the new structure but captures none of the interests, expectations, or requirements of the people in those roles. Therefore, B, Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements, is the correct answer.
Play from 2:46:36 Question 79. A software development team is working in an environment in which increased competition, demanding customer expectations, and new technological developments pose significant challenges. How should the team plan improvements to their product? Here are the options. Option A. Follow the project schedule created at the start of the project. Option B. Hold regular retrospectives and have team members commit to specific actions. Option C. Allow team members to choose improvement items and trust their judgment. Option D. Encourage team members to write code that is tightly coupled together. Pause the video now if you want time to think about the answer.
The correct answer is B. Hold regular retrospectives and have team members commit to specific actions. In a volatile environment shaped by competition, rising customer expectations and new technology, a team must inspect and adapt frequently. Regular retrospectives give the team a structured cadence to reflect on what is working, identify what should change and agree on concrete improvement actions. Having team members commit to specific, owned actions turns those discussions into real change, and reviewing the actions at the next retrospective closes the loop. This steady cycle of reflection and commitment lets the team keep improving how it delivers value as conditions shift. Now, why are the other options incorrect? Option A is incorrect. Following a fixed schedule created at the start ignores the changing conditions and prevents the team from adapting. Option C is incorrect. Trusting individual choices without a shared reflection and commitment process leaves improvements uncoordinated and easy to drop. Option D is incorrect. Tightly coupled code makes the product harder to change, which works against adapting to a fast-moving market. Therefore, B, Hold regular retrospectives and have team members commit to specific actions, is the correct answer.
Play from 2:49:04 Question 80. An agile team provides feedback that user stories include insufficient details to understand the requirements. What should the agile practitioner do? Here are the options. Option A. Coach the product owner to update only the acceptance criteria. Option B. Instruct the agile team to fix the user stories during the next retrospective. Option C. Facilitate a user story workshop with the agile team. Option D. Inform the product owner's manager that the work items provide insufficient details. Pause the video now if you want time to think about the answer.
The correct answer is C. Facilitate a user story workshop with the agile team. A user story is a placeholder for a conversation, and missing detail is resolved by bringing people together to talk. A user story workshop gathers the team, the product owner and relevant stakeholders to discuss the stories, clarify intent, split large items and agree on acceptance criteria. The practitioner facilitates rather than directs, so shared understanding is built collaboratively and the team gains the detail it needs before committing to the work. This also improves how future stories are written. Now, why are the other options incorrect? Option A is incorrect. Limiting changes to acceptance criteria may leave other gaps in the stories and excludes the team from the conversation. Option B is incorrect. Retrospectives improve the process rather than refine backlog items, and instructing the team is not facilitation. Option D is incorrect. Reporting the product owner to a manager escalates prematurely and damages collaboration. Therefore, C, Facilitate a user story workshop with the agile team, is the correct answer.
Play from 2:51:10 Question 81. The team is aware that they will need to integrate a new component to their solution in the next few weeks. The team does not have any experience with this component. What should the team do next? Here are the options. Option A. Ask for a team extension so that an engineer with the needed experience can be added to the team. Option B. Suggest that the product owner perform the initial investigation and present the outcome to the team. Option C. Request that the product owner include a spike in the next iteration's backlog so they can perform an initial investigation. Option D. Propose alternative components with which the team has experience. Pause the video now if you want time to think about the answer.
The correct answer is C. Request that the product owner include a spike in the next iteration's backlog so they can perform an initial investigation. The team faces technical uncertainty about a component it has never used, and integration is coming soon. A spike is a timeboxed investigation that lets the team build knowledge, reduce risk and improve its estimates before committing to the integration work. Because the product owner orders the backlog, the team asks the product owner to include the spike in the next iteration, keeping the work visible and prioritized while the developers perform the investigation themselves. Now, why are the other options incorrect? Option A is incorrect. Adding an engineer is premature before the team has even explored the component and may not be needed. Option B is incorrect. Technical investigation belongs to the developers, not the product owner. Option D is incorrect. Swapping the component to avoid learning ignores the solution's need and the decision already made to integrate it. Therefore, C, Request that the product owner include a spike in the next iteration's backlog so they can perform an initial investigation, is the correct answer.
Play from 2:53:27 Question 82. Why should an agile coach model agile principles and behaviours, become self-aware, and be present? Here are the options. Option A. To better listen, serve and help the team grow their strengths individually and as a team. Option B. To convince people what they need to do. Option C. To help better disguise the command and control approach. Option D. To understand team dynamics and develop a high performing team. Pause the video now if you want time to think about the answer.
The correct answer is A. To better listen, serve and help the team grow their strengths individually and as a team. An agile coach is a servant leader whose purpose is to serve the team and help its members grow. Modeling agile principles and behaviors shows the team what the mindset looks like in practice. Self-awareness helps the coach notice their own reactions and biases, and being present allows them to listen fully. Together these let the coach truly hear the team, respond to its real needs and help people develop their strengths individually and as a team, which leads to empowered, self-organizing teams. Now, why are the other options incorrect? Option B is incorrect. Convincing people what to do is directive persuasion, the opposite of the coaching stance of listening and serving. Option C is incorrect. Disguising command and control is manipulative and contradicts the transparency and servant leadership a coach must model. Option D is incorrect. Understanding team dynamics is a means the coach uses, while the reason for these behaviors is to listen to, serve and grow the people on the team. Therefore, A, To better listen, serve and help the team grow their strengths individually and as a team, is the correct answer.
Play from 2:55:35 Question 83. An agile team is struggling with an issue. A team member mentions that another team had a similar issue that was resolved, but lessons learned documents are unavailable. What should the agile practitioner do? Here are the options. Option A. Suggest that all agile teams share weekly reports on their projects. Option B. Encourage the team to independently find a solution. Option C. Work with the team to create a solution for disseminating team knowledge throughout the company. Option D. Recommend hiring an external expert to advise on the best methods for sharing knowledge among teams. Pause the video now if you want time to think about the answer.
The correct answer is C. Work with the team to create a solution for disseminating team knowledge throughout the company. The team is losing time solving a problem that another team has already solved, which is waste caused by knowledge that never left the team that learned it. The agile practitioner should collaborate with the team to create a way of spreading team knowledge across the company, such as communities of practice, shared wikis, cross-team demos or open retrospective outcomes. Working with the team keeps ownership with the people who will use the solution and turns a one-off gap into lasting organizational learning, supporting continuous improvement beyond a single team. Now, why are the other options incorrect? Option A is incorrect. Weekly status reports add overhead and rarely capture the practical lessons that would solve problems like this one. Option B is incorrect. Sending the team off alone ignores existing knowledge and repeats the waste of solving a solved problem. Option D is incorrect. Hiring an external expert is costly and unnecessary when the team can build a fitting knowledge-sharing approach itself. Therefore, C, Work with the team to create a solution for disseminating team knowledge throughout the company, is the correct answer.
Play from 2:57:51 Question 84. The agile coach of a development team uses a servant leadership approach. The team is starting the third iteration of an upgrade to a software product, and work is going slower than initially planned. What should the coach do to help the team? Here are the options. Option A. Help the team to remove impediments that stall project progress. Option B. Work with the development team to adjust the work plan. Option C. Ask the product owner to assign more resources to the project. Option D. Command and control the team to achieve plan goals. Pause the video now if you want time to think about the answer.
The correct answer is A. Help the team to remove impediments that stall project progress. A servant leader supports the team by clearing obstacles so the team can do its best work. When progress is slower than planned, the coach works with the team to identify what is slowing it down, such as dependencies, waiting time, tooling problems or outside interruptions, and helps remove those impediments. This addresses the cause of the slowdown while leaving the team in charge of how it organizes and plans its own work. Now, why are the other options incorrect? Option B is incorrect. Adjusting the work plan treats the symptom and does not address what is causing the slowdown. Option C is incorrect. Adding resources rarely fixes a slowdown quickly and is not the coach's first response before the cause is understood. Option D is incorrect. Command and control contradicts servant leadership and undermines team self-organization. Therefore, A, Help the team to remove impediments that stall project progress, is the correct answer.
Play from 2:59:52 Question 85. An executive notices a kanban board in a highly visible location and expresses concerns to the project manager that too many people will see it. What should the project manager do? Here are the options. Option A. Cover up the kanban board every time the project team is not actively updating it. Option B. Demonstrate how the kanban board is necessary for assigning proper ownership for the work that has been done. Option C. Explain that the kanban board enables the team to complete the work and increases transparency on work that is not done. Option D. Remove the kanban board immediately and place it in a location where it is not visible. Pause the video now if you want time to think about the answer.
The correct answer is C. Explain that the kanban board enables the team to complete the work and increases transparency on work that is not done. A kanban board is an information radiator placed in a visible location on purpose. The project manager should explain to the executive that the board helps the team manage and complete its work and that its visibility makes progress, bottlenecks and unfinished work transparent to everyone. Transparency allows problems to be seen and addressed early, so hiding the board would remove one of its main benefits for the team and the organization. Now, why are the other options incorrect? Option A is incorrect. Covering the board defeats its purpose as an information radiator and signals secrecy. Option B is incorrect. A kanban board visualizes workflow for the team and is not mainly a tool for assigning ownership of completed work. Option D is incorrect. Hiding the board removes transparency and the shared visibility the team relies on. Therefore, C, Explain that the kanban board enables the team to complete the work and increases transparency on work that is not done, is the correct answer.
Play from 3:02:07 Question 86. During its first sprint, a new scrum team realizes that it has insufficient team members with test automation skills to efficiently complete its stories. What should the team do? Here are the options. Option A. Cross-train some members in the automation framework to broaden their capacity with that skill. Option B. Ask the product owner to add team members to boost this particular skill set. Option C. Send a member to automation framework training when funds are available. Option D. Avoid using test automation by swarming on the testing tasks and using manual testing. Pause the video now if you want time to think about the answer.
The correct answer is A. Cross-train some members in the automation framework to broaden their capacity with that skill. The team has some test automation skills, just not enough of them. A self-organizing, cross-functional team addresses this by cross-training other members in the automation framework, for example by pairing with those who already know it. This broadens capacity in the scarce skill, removes the bottleneck, encourages generalizing specialists and keeps the quality benefits of automated testing, all without waiting for outside help. Now, why are the other options incorrect? Option B is incorrect. The product owner does not staff the team, and adding people is slow and ignores the skills already present. Option C is incorrect. Waiting for funds delays the solution indefinitely and develops only one person. Option D is incorrect. Abandoning automation sacrifices quality and long-term efficiency instead of building the needed skill. Therefore, A, Cross-train some members in the automation framework to broaden their capacity with that skill, is the correct answer.
Play from 3:04:13 Question 87. During sprint planning, team members have differing opinions on a feature that delivers business value but fails to provide a long-term solution for the customer. How should the team resolve this? Here are the options. Option A. Refer to the values of the agile framework and the team. Option B. Review the signed customer contract. Option C. Check the sprint priority list. Option D. Submit the problem to the product owner. Pause the video now if you want time to think about the answer.
The correct answer is A. Refer to the values of the agile framework and the team. The disagreement is about whether to deliver short-term business value through a solution that does not serve the customer in the long term. The team should resolve it by returning to the agile values and principles and to its own team values, such as customer satisfaction through valuable software, continuous attention to technical excellence and sustainable development. These shared values give the team a common basis for weighing the trade-off and reaching a decision together rather than leaving the disagreement unresolved. Now, why are the other options incorrect? Option B is incorrect. A contract sets terms but does not help the team weigh short-term value against the long-term solution. Option C is incorrect. The priority list shows order, not how to balance immediate value against long-term quality. Option D is incorrect. Handing the problem off avoids the team discussion needed to resolve its own disagreement. Therefore, A, Refer to the values of the agile framework and the team, is the correct answer.
Play from 3:06:10 Question 88. A member of a project's development team approaches the team lead and requests database administrator training. The team member believes that their inability to handle this work and to rely on outside specialists is impacting team velocity. What should the agile team lead do? Here are the options. Option A. Send the member to training. Option B. Ask the outside specialists if database administration is required from the team. Option C. Send one member to training only after asking the team if there is an issue with the current work flow. Option D. Wait until all members of the team can attend training. Pause the video now if you want time to think about the answer.
The correct answer is A. Send the member to training. Agile teams aim to be cross-functional so that they can deliver finished work without waiting on external specialists. The team member has identified a concrete dependency that is slowing the team and has proposed a practical remedy. Supporting that request by sending the team member to database administrator training builds the team's capability, develops a generalizing specialist, and removes a source of delay. A servant leader enables the growth that team members ask for when it clearly helps the team deliver value. Now, why are the other options incorrect? Option B is incorrect. Asking the outside specialists does not reduce the dependency that is hurting velocity. Option C is incorrect. Holding the training until the team confirms a problem already identified adds delay and second-guesses the team member's insight. Option D is incorrect. Waiting for the whole team to attend is unnecessary and prolongs the dependency on outside specialists. Therefore, A, Send the member to training, is the correct answer.
Play from 3:08:14 Question 89. An agile team is building a training safety video based on current government regulations. The agile coach knows the regulations are likely to change before the release date. How should the agile coach address this change? Here are the options. Option A. Plan for the second release to include regulatory changes and new features. Option B. Hold off making changes during the current release because the regulatory changes cannot be planned for. Option C. Verify the team is building the product in increments which can be adapted at the last minute if necessary. Option D. Monitor regulatory discussions to get a head start on the upcoming regulatory changes. Pause the video now if you want time to think about the answer.
The correct answer is C. Verify the team is building the product in increments which can be adapted at the last minute if necessary. Agile welcomes changing requirements, even late in development, for the customer's competitive advantage. When regulations are expected to shift before release, the best protection is to build the training video in small, independent increments that can be revised quickly once the new rules are known. Short iterations and frequent feedback keep the cost of change low, so the team can adjust content late without large rework and still release a product that complies with the regulations in force at release. Now, why are the other options incorrect? Option A is incorrect. Deferring the regulatory changes to a second release would ship a safety video that is already noncompliant. Option B is incorrect. Refusing to change during the release contradicts the agile principle of welcoming changing requirements. Option D is incorrect. Monitoring discussions alone does not make the product able to absorb the change when it arrives. Therefore, C, Verify the team is building the product in increments which can be adapted at the last minute if necessary, is the correct answer.
Play from 3:10:35 Question 90. A key stakeholder feels they do not understand the project at a comprehensive level. What should the agile practitioner do? Here are the options. Option A. Send daily status emails to let stakeholders know what progress is being made. Option B. Invite stakeholders to attend daily Scrum meetings to get feedback. Option C. Share information via interactive methods such as a brainstorming session. Option D. Build the feature backlog and then solicit stakeholder feedback. Pause the video now if you want time to think about the answer.
The correct answer is C. Share information via interactive methods such as a brainstorming session. A stakeholder who lacks a comprehensive understanding of the project needs a richer, two-way conversation, not more one-way data. Agile favors face-to-face, interactive communication because it lets people ask questions, surface assumptions and build a shared picture of the vision, goals and scope. Interactive sessions such as brainstorming or collaborative workshops engage the stakeholder directly, reveal what they do not yet understand and give them a voice in shaping the work, which builds both understanding and commitment far more effectively than reports or status meetings. Now, why are the other options incorrect? Option A is incorrect. Daily status emails are one-way push communication and do not build a comprehensive understanding of the project. Option B is incorrect. The daily scrum is a short planning event for the developers and shows day-to-day task progress, not the broad project picture. Option D is incorrect. Building the backlog first and asking for feedback afterward delays engagement and does not address the current lack of understanding. Therefore, C, Share information via interactive methods such as a brainstorming session, is the correct answer.
Play from 3:12:49 Question 91. What should a scrum master do when one team member falls behind in their tasks? Here are the options. Option A. Move the task to another team member who has spare capacity in the sprint. Option B. Ask the team for suggestions. Option C. Privately offer the team member encouragement to meet task commitments. Option D. Notify the product owner. Pause the video now if you want time to think about the answer.
The correct answer is C. Privately offer the team member encouragement to meet task commitments. When one team member falls behind, a servant leader first supports that person rather than exposing or bypassing them. A private conversation offering encouragement protects psychological safety, shows that the scrum master is on the member's side, and gives the member room to mention any obstacle that the scrum master can then help remove. This approach motivates the individual to meet the commitments they made to the team while preserving their dignity and the trust within the team. Public or directive responses risk embarrassing the member and discouraging openness in the future. Now, why are the other options incorrect? Option A is incorrect. Moving the task to someone else is the scrum master assigning work, which undermines both the member and the team's self-organization. Option B is incorrect. Putting one person's delay before the whole team before speaking with them can embarrass the member and damage psychological safety. Option D is incorrect. Notifying the product owner escalates a minor individual matter that the scrum master can support directly. Therefore, C, Privately offer the team member encouragement to meet task commitments, is the correct answer.
Play from 3:14:51 Question 92. The coach on a new agile team notices that one team member is influencing most of the team's decisions. What should the coach do? Here are the options. Option A. Replace the team member with a more collaborative individual. Option B. Permit the team member to continue influencing because agile teams are self-organizing. Option C. Ask probing questions to other team members to encourage dissenting viewpoints. Option D. Intervene if the team's velocity drops. Pause the video now if you want time to think about the answer.
The correct answer is C. Ask probing questions to other team members to encourage dissenting viewpoints. When one person dominates decisions, the team loses the diverse perspectives that make self-organization work, and quieter members may stop contributing. A coach handles this through facilitation, not authority: asking probing, open questions of the other team members invites their views and makes healthy dissent safe. This builds psychological safety and leads to more balanced, better-informed decisions while still leaving the decision-making with the team. The dominant member is not punished; the group simply learns to hear more voices. Now, why are the other options incorrect? Option A is incorrect. Replacing the team member is a heavy, punitive step that skips coaching and harms trust. Option B is incorrect. Self-organization means the whole team decides together, not that one member dominates unchecked. Option D is incorrect. Waiting for velocity to drop is reactive and lets an unhealthy dynamic settle in first. Therefore, C, Ask probing questions to other team members to encourage dissenting viewpoints, is the correct answer.
Play from 3:16:57 Question 93. A new product owner needs to manage the backlog of a high-visibility, fast-moving project that is consuming a considerable amount of time. What should the product owner do? Here are the options. Option A. Schedule regular meetings with the scrum team to write, groom, and size user stories. Option B. Focus on stories based on the highest number of story points to first address those items with the highest value. Option C. Seek regular input from project stakeholders, and reflect this input in the backlog's priorities. Option D. Schedule in-person, monthly meetings with key stakeholders to review the project's progress. Pause the video now if you want time to think about the answer.
The correct answer is C. Seek regular input from project stakeholders, and reflect this input in the backlog's priorities. In a high-visibility, fast-moving project, priorities shift quickly, and the product owner's core accountability is maximizing value through the ordering of the product backlog. Seeking regular input from stakeholders and reflecting that input in backlog priorities keeps the backlog aligned with business needs as they evolve, and it lets the product owner manage a time-consuming backlog by focusing effort on what matters most. Frequent stakeholder collaboration also builds trust and transparency, which is especially important when many people are watching the outcome. Now, why are the other options incorrect? Option A is incorrect. Refinement with the team does not address the need here, because writing and sizing stories does not tell the product owner what stakeholders value most. Option B is incorrect. Story points measure size or effort rather than value, so ordering by the largest estimates does not deliver the most value first. Option D is incorrect. Monthly progress reviews are too infrequent for a fast-moving project and focus on status rather than on shaping backlog priorities. Therefore, C, Seek regular input from project stakeholders, and reflect this input in the backlog's priorities, is the correct answer.
Play from 3:19:26 Question 94. During an iteration review, the agile team asserts that a product is complete because development and review were finished. The product owner disagrees, since the product has not been tested. What should the agile practitioner do? Here are the options. Option A. Work with the agile team and product owner to agree on the definition of done. Option B. Ask the sponsor to determine whether the product is completed. Option C. Plan another review after the product has been tested. Option D. Add testing to the backlog, and have the product owner reprioritize. Pause the video now if you want time to think about the answer.
The correct answer is A. Work with the agile team and product owner to agree on the definition of done. The disagreement shows that the team and the product owner hold different views of what complete means. The definition of done creates a shared understanding of the quality standards an increment must meet, and testing is normally an essential part of it. The agile practitioner should facilitate a conversation in which the team and the product owner agree on an explicit definition of done that includes testing. Work that does not meet it is not done and returns to the product backlog, and future disputes of this kind are prevented. Now, why are the other options incorrect? Option B is incorrect. The sponsor does not decide completion criteria, and escalating avoids the collaboration the situation needs. Option C is incorrect. Scheduling another review treats the symptom and leaves the underlying disagreement about done unresolved. Option D is incorrect. Testing is part of finishing the work, not a separate backlog item for the product owner to prioritize. Therefore, A, Work with the agile team and product owner to agree on the definition of done, is the correct answer.
Play from 3:21:36 Question 95. During an interview for an agile team lead for a global company, a candidate is asked: "How do you ensure your project is aligned with the stakeholders' priorities?" How should the candidate respond? Here are the options. Option A. Engage the change management team to determine prioritization of the backlog. Option B. Allow the stakeholders to decide on the priority and build the backlog. Option C. The entire team should discuss and prioritize the backlog factoring in stakeholder input. Option D. Only the agile team lead and team need to decide how to prioritize the project deliverables. Pause the video now if you want time to think about the answer.
The correct answer is C. The entire team should discuss and prioritize the backlog factoring in stakeholder input. Alignment with stakeholder priorities comes from collaboration: the team discusses and prioritizes the backlog while actively factoring in stakeholder input. This keeps stakeholders engaged and ensures their needs shape the order of work, while the team brings its knowledge of effort, risk and dependencies to the decision. Combining both perspectives, with the product owner guiding value-based ordering, produces a backlog that reflects business value and remains realistic to deliver. Now, why are the other options incorrect? Option A is incorrect. A change management team is not responsible for backlog prioritization and would add an unnecessary layer between stakeholders and the team. Option B is incorrect. Letting stakeholders build and order the backlog alone excludes the team's input on effort, risk and dependencies. Option D is incorrect. Excluding stakeholders from prioritization is the opposite of ensuring alignment with their priorities. Therefore, C, The entire team should discuss and prioritize the backlog factoring in stakeholder input, is the correct answer.
Play from 3:23:52 Question 96. A project has several features that will deliver immediate customer value. The product owner needs to determine which features to include in the upcoming iteration. What should the product owner have the customer review and approve? Here are the options. Option A. Work breakdown structure (WBS). Option B. Description of all features' functions and an estimate of their cost. Option C. Priority list of desired features and functions. Option D. Comprehensive schedule of immediate deliverables. Pause the video now if you want time to think about the answer.
The correct answer is C. Priority list of desired features and functions. In agile planning the product owner works with the customer on a prioritized list of desired features and functions, which is effectively the ordered product backlog. Having the customer review and approve that priority order ensures that the upcoming iteration delivers the highest-value items first. It keeps the customer collaborating on value decisions while leaving the developers to plan how much they can take on and how to build it. Now, why are the other options incorrect? Option A is incorrect. A work breakdown structure is a predictive planning tool and does not express customer value priorities for an iteration. Option B is incorrect. Full descriptions and cost estimates for every feature are excessive up-front detail and do not show what matters most. Option D is incorrect. A comprehensive schedule is predictive planning, and the iteration content is set by value priority, not a fixed schedule. Therefore, C, Priority list of desired features and functions, is the correct answer.
Play from 3:25:51 Question 97. The product owner wants to build security firewalls into the product. How can the team members support this? Here are the options. Option A. Add new security features to the backlog and prioritize. Option B. Execute a spike to research security features for the project. Option C. Ask questions to determine where and how the product owner wants to use the product. Option D. Ask questions to determine if the product owner can define the desired level of security. Pause the video now if you want time to think about the answer.
The correct answer is A. Add new security features to the backlog and prioritize. Security firewalls are new work, and in agile all work the product needs is made transparent in the product backlog. Team members support the product owner by capturing the new security features as backlog items so they can be refined, estimated and prioritized against the rest of the work. Once the items are visible in the backlog, the product owner can order them by value and risk, and the team can plan them into upcoming iterations instead of leaving the request as an informal wish that might be forgotten. Now, why are the other options incorrect? Option B is incorrect. A spike researches how to build something, but the immediate need is to capture the requested work so it can be prioritized. Option C is incorrect. Asking where the product will be used does not turn the security request into work the team can plan and deliver. Option D is incorrect. Questioning whether the product owner can define the security level does not move the request into the backlog where it can be refined and prioritized. Therefore, A, Add new security features to the backlog and prioritize, is the correct answer.
Play from 3:28:01 Question 98. During planning for the next iteration, an agile team identifies most of the story points that are expected to be delivered. How should an agile practitioner work with the team to help identify the iteration's remaining scope? Here are the options. Option A. Convince the team to stop planning and keep the size small. Option B. Identify the technically minimal and achievable tasks. Option C. Refer to the remaining prioritized backlog items. Option D. Select some of the smallest items from the backlog. Pause the video now if you want time to think about the answer.
The correct answer is C. Refer to the remaining prioritized backlog items. Once most of the expected story points are identified, the remaining capacity should be filled with the next items in priority order. The agile practitioner helps the team refer to the remaining prioritized backlog items and select those that fit the available capacity, so the iteration continues to deliver the highest value work. The ordered product backlog, maintained by the product owner, is the authoritative guide to what comes next. Now, why are the other options incorrect? Option A is incorrect. Stopping planning early leaves capacity unused and is not the practitioner's decision to force on the team. Option B is incorrect. Picking technically minimal tasks ignores business priority and may deliver little value. Option D is incorrect. Choosing the smallest items simply because they fit ignores the priority order and can displace more valuable work. Therefore, C, Refer to the remaining prioritized backlog items, is the correct answer.
Play from 3:30:00 Question 99. A development team for a small company experiences long delays between product completion and release for validation and testing. The company is concerned that this will impact its ability to compete in the marketplace. What analysis should the team use to understand the issues? Here are the options. Option A. Risk management. Option B. Variance and trend. Option C. Kano model. Option D. Fishbone diagram. Pause the video now if you want time to think about the answer.
The correct answer is D. Fishbone diagram. The team already knows the symptom: long delays between product completion and release for validation and testing. To understand the issues behind it, the team needs root cause analysis, and a fishbone (Ishikawa) diagram is built for this. It organizes possible causes into categories such as people, process, tools and environment, helping the team move beyond the symptom to the underlying factors that create the delay. Once the causes are understood, the team can target improvements that shorten the time to market. Now, why are the other options incorrect? Option A is incorrect. Risk management deals with uncertain future events, while the delays are a current problem that needs causal analysis. Option B is incorrect. Variance and trend analysis shows how far performance deviates from plan and how it changes over time, but it does not explain why the delays occur. Option C is incorrect. The Kano model classifies features by their effect on customer satisfaction and does not analyze process delays. Therefore, D, Fishbone diagram, is the correct answer.
Play from 3:32:02 Question 100. During a project's last few sprints, an agile practitioner notices an increase in defects. A root cause analysis indicates that a poor understanding of the requirements was caused by the inability of the product owner to communicate clearly. What should the agile practitioner do? Here are the options. Option A. Inform the product owner's manager so that corrective action may be taken. Option B. Communicate this to the product owner, and offer to help facilitate discussion with the team. Option C. Encourage a team member to raise this during the retrospective to ensure that the product owner is aware. Option D. Escalate this issue to the sponsor so that corrective action may be taken. Pause the video now if you want time to think about the answer.
The correct answer is B. Communicate this to the product owner, and offer to help facilitate discussion with the team. A servant leader addresses problems directly, respectfully and early. The agile practitioner should share the root-cause findings with the product owner and offer to facilitate conversations with the team, for example through backlog refinement sessions, story workshops or agreed acceptance criteria. This respects the product owner's role, coaches toward better communication and restores shared understanding of requirements quickly, which matters because defects are already rising late in the project. Collaboration and facilitation come before escalation, and they keep trust intact within the team. Now, why are the other options incorrect? Option A is incorrect. Going to the product owner's manager skips direct conversation and turns a coaching need into an escalation. Option C is incorrect. Delegating the message to a team member delays action and avoids the practitioner's own responsibility to coach. Option D is incorrect. Escalating to the sponsor is premature when direct facilitation with the product owner has not been tried. Therefore, B, Communicate this to the product owner, and offer to help facilitate discussion with the team, is the correct answer.





