Courseiva

CCNA Agile Frameworks and Methodologies Questions

75 of 93 questions · Page 1/2 · Agile Frameworks and Methodologies · Answers revealed

1
MCQeasy

A company transitioning from a waterfall to a Scrum framework wants to ensure continuous improvement. Which Scrum event is specifically designed for inspecting and adapting the process?

A.Daily Scrum
B.Sprint Review
C.Sprint Retrospective
D.Sprint Planning
AnswerC

The Sprint Retrospective is the dedicated event for the Scrum Team to inspect its own process and create a plan for improvements to be enacted during the next Sprint.

Why this answer

Sprint Retrospective. The Sprint Retrospective is the Scrum event specifically designed for inspecting and adapting the team's process to enable continuous improvement. Option A (Daily Scrum) is for daily coordination, option B (Sprint Review) inspects the product increment and adapts the Product Backlog, and option D (Sprint Planning) plans the work for the upcoming sprint.

2
MCQmedium

During Sprint Planning, the Product Owner proposes a user story that is too large to fit in one Sprint. What should the team do?

A.Collaboratively break down the story into smaller, sprint-sized stories.
B.Reject the story and ask for a smaller one.
C.Accept the story and work overtime to complete it.
D.Accept the story and commit to completing it in the Sprint.
AnswerA

Decomposition is a standard Agile practice.

Why this answer

In Scrum, user stories that are too large (often called 'epics') must be decomposed into smaller, sprint-sized stories during Sprint Planning. The Product Owner and Development Team collaboratively break down the story to ensure each piece can be completed within a single Sprint, maintaining the Sprint Goal and timebox. This aligns with the Agile principle of sustainable pace and the Scrum Guide's emphasis on the Development Team's self-organization to determine how to deliver the Product Backlog items.

Exam trap

PMI often tests the misconception that the Product Owner alone decides story size or that the team should simply reject or accept oversized stories, but the correct Scrum practice is collaborative decomposition during Sprint Planning.

How to eliminate wrong answers

Option B is wrong because rejecting the story outright violates the collaborative nature of Sprint Planning; the team should work with the Product Owner to refine the backlog, not simply refuse work. Option C is wrong because accepting a story that is too large and working overtime contradicts the Agile principle of sustainable pace and the Scrum rule that the Sprint timebox is fixed; overtime is not a standard practice for handling oversized stories. Option D is wrong because committing to complete a story that is too large for one Sprint is unrealistic and undermines the Sprint Goal, leading to likely failure and loss of trust in the team's commitments.

3
Multi-Selecthard

Which THREE are principles of the Agile Manifesto? (Choose three.)

Select 3 answers
A.Deliver working software frequently, with a preference to the shorter timescale.
B.Business people and developers must work together daily throughout the project.
C.Welcome changing requirements, even late in development.
D.Use pair programming for all production code.
E.Individuals and interactions over processes and tools.
AnswersA, B, C

This is principle #3.

Why this answer

The Agile Manifesto explicitly states 'Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.' This principle emphasizes iterative delivery and rapid feedback cycles, which are core to Agile frameworks like Scrum and XP.

Exam trap

PMI often tests the distinction between the four Agile values and the twelve Agile principles, so candidates must memorize which statements belong to each category to avoid selecting a value when the question asks for a principle.

4
MCQhard

You are the project manager for a cross-functional team developing a mobile banking application using Scrum. The team consists of 7 members: 3 developers, 2 testers, 1 UX designer, and 1 product owner. The product owner is highly available and prioritizes the backlog weekly. The team has been working for 3 months and consistently delivers each sprint. However, after the last sprint review, stakeholders complained that the product does not meet their expectations—specifically, the user interface is not intuitive, and a critical security feature is missing. The product owner insists that the backlog items were clearly defined and prioritized. The development team argues that they followed the acceptance criteria exactly. Retrospectives have been unproductive, with team members blaming each other. The Scrum Master is frustrated. Based on the Scrum Guide, what is the MOST likely root cause of these issues?

A.The team did not conduct a proper sprint review to gather stakeholder feedback early.
B.The development team did not collaborate enough with the Product Owner during the sprint.
C.The Scrum Master failed to facilitate effective retrospectives and team collaboration.
D.The Product Owner did not sufficiently refine the Product Backlog and ensure acceptance criteria were clear and complete.
AnswerD

The Product Owner is accountable for the backlog's clarity and value; missing features indicate inadequate refinement.

Why this answer

The root cause is that the Product Owner failed to sufficiently refine the Product Backlog and ensure acceptance criteria were clear and complete. The stakeholders' complaints about an unintuitive UI and missing critical security feature indicate that the Product Owner did not validate the backlog items against stakeholder expectations or include non-functional requirements (like security) in the acceptance criteria. According to the Scrum Guide, the Product Owner is responsible for ensuring that the Product Backlog is transparent, visible, and understood, which includes refining items to a level of detail that enables the team to deliver value.

Exam trap

The trap here is that candidates often blame the development team for not collaborating or the Scrum Master for poor facilitation, but the CAPM exam emphasizes the Product Owner's accountability for backlog clarity and stakeholder alignment, especially when missing critical features like security or usability.

How to eliminate wrong answers

Option A is wrong because the sprint review is an opportunity to inspect the increment and adapt the Product Backlog, but the team has been conducting sprint reviews and stakeholders only complained after the last one; the issue is not about the timing of feedback but about the backlog items themselves lacking critical requirements. Option B is wrong because the development team collaborated with the Product Owner as evidenced by following the acceptance criteria exactly; the problem is that the acceptance criteria were incomplete, not that collaboration was lacking. Option C is wrong because while the Scrum Master facilitates retrospectives, the unproductive retrospectives are a symptom of deeper issues (unclear backlog and blame culture), not the root cause; the Scrum Master's frustration is a result of the team's inability to identify the real problem.

5
MCQeasy

A Scrum team has a Product Backlog Item (PBI) that is too large to be completed in one sprint. What is the best action for the team to take?

A.Ask the Product Owner to break the PBI into smaller PBIs.
B.Add the PBI to the sprint backlog and try to complete it.
C.Move the PBI to the next sprint to allow more time.
D.Remove the PBI from the product backlog entirely.
AnswerA

Decomposition is a standard practice to ensure PBIs fit within a sprint.

Why this answer

The best action is to ask the Product Owner to break the PBI into smaller PBIs. Large PBIs are difficult to estimate and complete within a sprint, so decomposition is key. Option B is incorrect because adding it to the sprint backlog would risk incomplete work.

Option C is incorrect because merely deferring does not solve the issue of size. Option D is too drastic and may lose valuable scope.

6
Multi-Selecteasy

Which THREE are events in the Scrum framework? (Choose three)

Select 3 answers
A.Grooming
B.Sprint Retrospective
C.Daily Stand-up
D.Sprint Planning
E.Release Planning
AnswersB, C, D

Sprint Retrospective is a Scrum event.

Why this answer

The correct Scrum events are Sprint Planning, Daily Stand-up (Daily Scrum), and Sprint Retrospective, which correspond to options B, C, and D. Option A (Grooming) is not a Scrum event; backlog refinement is an ongoing activity. Option E (Release Planning) is not part of the Scrum framework; it may be used in other methodologies.

7
MCQmedium

Refer to the exhibit. What is the most likely explanation for the data?

A.The sprint duration is too short.
B.The team is highly productive.
C.The story points are overestimated.
D.The team has not begun the sprint work.
AnswerD

Zero completion across all days strongly suggests work has not started.

Why this answer

The exhibit shows a sprint burndown chart where the remaining work line remains flat at the initial value across all 10 days, indicating that no work has been completed. This is the most likely explanation because if the team had begun any work, the burndown line would show a downward trend. Option A is incorrect because a too-short sprint would still show some completion of tasks.

Option B is incorrect because high productivity would result in a steeper downward slope. Option C is incorrect because overestimated story points might cause a slower start but would not prevent all progress.

8
Multi-Selecthard

Which THREE of the following are core values of the Agile Manifesto?

Select 3 answers
A.Individuals and interactions over processes and tools.
B.Responding to change over following a plan.
C.Following a plan over responding to change.
D.Working software over comprehensive documentation.
E.Contract negotiation over customer collaboration.
AnswersA, B, D

This is one of the four values.

Why this answer

The Agile Manifesto explicitly values 'Individuals and interactions over processes and tools.' This means that while processes and tools are important, the people doing the work and how they communicate take precedence. The Manifesto emphasizes that collaboration and human factors drive project success more than rigid adherence to prescribed procedures.

Exam trap

The trap here is that PMI often tests candidates by presenting the exact opposite of a Manifesto value (e.g., 'Following a plan over responding to change') as a plausible option, exploiting the common misconception that Agile means 'no planning' rather than 'adaptive planning.'

9
MCQhard

A distributed Scrum team is having difficulty with communication across time zones. The Daily Scrum is scheduled at 9 AM in the US, which is midnight in India. What is the best approach to resolve this?

A.Record the Daily Scrum for the India team to watch later.
B.Replace the Daily Scrum with asynchronous updates.
C.Rotate the time of the Daily Scrum so that no one is always inconvenienced.
D.Hold two separate Daily Scrums for each location.
AnswerC

Fair rotation supports team collaboration.

Why this answer

Rotating the Daily Scrum time shares the inconvenience of time zone differences equitably across the distributed team, preserving the event's purpose of daily synchronization and inspection. The Scrum Guide requires the Daily Scrum to be held at the same time and place each day, but for distributed teams, rotating the time is an acceptable adaptation that maintains the event's time-boxed, collaborative nature without breaking the inspect-and-adapt cycle.

Exam trap

The trap here is that candidates often choose Option B (asynchronous updates) because it seems efficient, but the CAPM exam tests that the Daily Scrum must remain a synchronous, collaborative event for the Development Team, not a reporting mechanism.

How to eliminate wrong answers

Option A is wrong because recording the Daily Scrum for later viewing eliminates real-time collaboration, inspection, and adaptation, violating the Scrum principle that all team members should synchronize their work daily. Option B is wrong because replacing the Daily Scrum with asynchronous updates removes the essential face-to-face (or real-time) communication and commitment that the event is designed to foster, turning it into a status report rather than a planning session. Option D is wrong because holding two separate Daily Scrums fragments the team, preventing cross-location synchronization and undermining the single-team accountability that Scrum requires.

10
MCQmedium

In a hybrid agile project, the team uses Scrum for development but the organization requires a detailed upfront plan. How can the team comply while staying agile?

A.Ignore the organizational requirement and continue with pure Scrum.
B.Create a high-level plan early and elaborate as work progresses.
C.Use predictive planning for the entire project.
D.Create a detailed plan and revise it only at the end.
AnswerB

This satisfies the need for an initial plan while allowing flexibility.

Why this answer

In a hybrid agile project, creating a high-level plan early and elaborating as work progresses allows the team to satisfy the organization's need for upfront planning while maintaining an agile approach by embracing change and iterative refinement. Option A is incorrect because ignoring organizational requirements could lead to lack of support or compliance issues. Option C is incorrect because using fully predictive planning contradicts agile principles.

Option D is incorrect because it requires a detailed plan upfront, which is not adaptive, and only revising at the end is too inflexible.

11
Multi-Selecthard

Which THREE principles are common to multiple agile methodologies?

Select 3 answers
A.Comprehensive documentation over working software.
B.Individuals and interactions over processes and tools.
C.Customer collaboration over contract negotiation.
D.Responding to change over following a plan.
E.Following a plan over responding to change.
AnswersB, C, D

This is a core value of the Agile Manifesto.

Why this answer

Options B, C, and D are correct. These are three of the four values from the Agile Manifesto: Individuals and interactions over processes and tools (B), Customer collaboration over contract negotiation (C), and Responding to change over following a plan (D). Option A is the opposite of the Manifesto's value 'working software over comprehensive documentation'.

Option E is the opposite of 'responding to change over following a plan'.

12
MCQmedium

A team is working on a project with high uncertainty. Which agile framework is most suitable?

A.Waterfall
B.V-Model
C.Kanban
D.Scrum
AnswerD

Scrum provides defined roles, time-boxed iterations, and regular inspection/adaptation.

Why this answer

Scrum is the most suitable agile framework for projects with high uncertainty because it uses iterative sprints with frequent feedback loops, allowing the team to adapt to changing requirements. In contrast, Waterfall (option A) is a plan-driven, sequential model that does not accommodate uncertainty well. V-Model (option B) is also plan-driven and focuses on verification and validation, not agile.

Kanban (option C) is agile but is more flow-based and less prescribed; while it can handle uncertainty, Scrum's structured iterations are generally recommended for high uncertainty. Therefore, option D (Scrum) is correct.

13
MCQhard

A Kanban team notices that cycle time is increasing despite stable demand. Which action is most likely to reduce cycle time?

A.Add more developers to the team.
B.Use pair programming for all development tasks.
C.Increase WIP limits to allow more work in progress.
D.Implement continuous integration to reduce integration delays.
AnswerD

Implementing continuous integration reduces integration delays and defects, directly lowering cycle time.

Why this answer

Implementing continuous integration reduces integration delays and defects, which directly lowers cycle time. Increasing WIP limits (C) would likely increase cycle time. Pair programming (B) may improve quality but not primarily cycle time.

Adding more team members (A) can increase handoffs and slow flow.

14
MCQeasy

In Kanban, what is the primary purpose of limiting Work in Progress (WIP)?

A.To reduce multitasking and improve focus.
B.To ensure each task is done correctly the first time.
C.To increase throughput.
D.To make the team work faster.
AnswerA

Limiting WIP prevents team members from juggling too many tasks at once.

Why this answer

Limiting Work in Progress (WIP) in Kanban is primarily intended to reduce multitasking and improve focus. By restricting the number of tasks in progress, team members concentrate on completing current work before starting new items, which minimizes context switching and enhances flow. Although increased throughput can be a benefit, the core purpose is to improve focus and flow.

Option A correctly identifies this primary purpose. Option B relates to quality, which is a secondary effect. Option C, increased throughput, is a result but not the primary purpose.

Option D is incorrect because limiting WIP does not aim to make the team work faster; it aims to improve efficiency and flow.

15
MCQeasy

Which of the following is a key benefit of using a Kanban board?

A.Fixed time iterations.
B.Visualizing the workflow.
C.Sprint planning ceremonies.
D.Defined roles such as Product Owner.
AnswerB

Visual boards are central to Kanban to show work progress.

Why this answer

Kanban boards make the workflow visible, showing the status of each work item. Options A, C, and D are characteristics of Scrum, not Kanban.

16
MCQhard

An organization is scaling Scrum across multiple teams. They have dependencies between teams that cause delays. What is the most appropriate framework to address this?

A.Use the Scaled Agile Framework (SAFe) with program increment planning.
B.Keep teams independent by decoupling all dependencies.
C.Have all teams work in the same Sprint but with no synchronization.
D.Use a separate integration team to handle dependencies.
AnswerA

SAFe's PI planning aligns teams around shared goals and explicitly manages dependencies.

Why this answer

SAFe provides program increment planning to synchronize teams and manage dependencies. Option B is ideal but often impractical. Option C creates a bottleneck.

Option D ignores the need for coordination.

17
MCQmedium

A team using Scrum consistently fails to complete all planned work in a sprint. What should the Scrum Master do first?

A.Add more team members.
B.Help the team break down user stories into smaller pieces.
C.Remove the Product Owner from daily stand-ups.
D.Increase the sprint length.
AnswerB

Smaller stories enable better estimation and completion within the sprint.

Why this answer

Breaking user stories into smaller pieces enables the team to estimate more accurately and complete work within the sprint. Option A is wrong because simply adding more team members does not address the root cause of incomplete work and can introduce communication overhead. Option C is wrong because the Product Owner is a vital participant in daily stand-ups to provide clarification and prioritize work; removing them hinders collaboration.

Option D is wrong because increasing sprint length reduces feedback frequency and does not solve the underlying issue of work sizing or estimation.

18
MCQeasy

Refer to the exhibit. What issue does the Kanban board reveal?

A.Not enough items are done.
B.The backlog is too large.
C.The WIP limit is exceeded.
D.The team is overworked.
AnswerC

The In Progress column has 4 items, exceeding the limit of 3.

Why this answer

The Kanban board shows 4 items in the 'In Progress' column, but the Work-In-Progress (WIP) limit is set to 3. This indicates that the WIP limit is exceeded, violating Kanban principles and causing potential bottlenecks. Option A is incorrect because the issue is not about the number of done items but the limit in progress.

Option B is incorrect as the backlog size is not the direct issue shown. Option D is a possible consequence but not the primary issue revealed by the board.

19
Multi-Selecthard

According to the Scrum Guide, which THREE of the following are Scrum events?

Select 3 answers
A.Product Backlog Refinement
B.Daily Scrum
C.Sprint Planning
D.Release Planning
E.Sprint Retrospective
AnswersB, C, E

The Daily Scrum is a 15-minute event for the development team.

Why this answer

Scrum defines five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Product Backlog refinement is an ongoing activity, not an event. Release planning is not part of Scrum.

The other three are official events.

20
Drag & Dropmedium

Drag and drop the steps in the correct order as they typically occur during the early phases of a project according to PMI's project management framework.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

According to PMBOK, initiating processes include developing the project charter and identifying stakeholders. The project manager should be assigned as early as possible, typically before or during charter development. While the kick-off meeting is part of planning, it often follows initiating.

Therefore, the correct sequence is: first assign the project manager, then develop and approve the project charter, then identify stakeholders, and finally conduct the kick-off meeting.

21
MCQmedium

A software development team has been using a feature branch workflow with long-lived branches. They frequently experience merge conflicts and integration delays. The team wants to adopt a more agile approach to reduce these issues. Which practice should the team adopt?

A.Adopt continuous integration, integrating code at least daily
B.Implement timeboxed iterations for each feature
C.Implement feature flags to hide incomplete work
D.Use pair programming to improve code quality
AnswerA

Continuous integration ensures frequent merging, reducing merge conflicts and integration delays.

Why this answer

Continuous integration (CI), which requires developers to merge their changes into the main branch frequently (at least daily) to detect conflicts early. Feature flags allow incomplete work to be hidden while merged, but the core practice to avoid merge conflicts is CI. Pair programming helps code quality but not integration delays.

Timeboxing is a sprint planning technique, not directly related to integration.

22
Multi-Selectmedium

Which TWO practices are characteristic of Extreme Programming (XP)? (Choose two)

Select 2 answers
A.Test-driven development
B.Daily stand-ups
C.Pair programming
D.Sprint retrospectives
E.Product owner
AnswersA, C

Test-driven development is a core XP practice.

Why this answer

Options A and C are correct. Pair programming and test-driven development are core XP practices. Option B (daily stand-ups) is from Scrum.

Option D (sprint retrospectives) is from Scrum. Option E (product owner) is a Scrum role.

23
Multi-Selecthard

Which THREE roles are defined in the Scrum Guide? (Select THREE)

Select 3 answers
A.Customer
B.Scrum Master
C.Product Owner
D.Development Team
E.Project Manager
AnswersB, C, D

The Scrum Master is a defined role responsible for facilitating Scrum and removing impediments.

Why this answer

Options B, C, and D are correct. The Scrum Guide defines three roles on a Scrum Team: the Scrum Master (B), the Product Owner (C), and the Development Team (D). Option A (Customer) is not a defined Scrum role; customers are stakeholders external to the team.

Option E (Project Manager) is also not a Scrum role, as traditional project management responsibilities are distributed among the Scrum roles.

24
MCQmedium

A startup is using Scrum to develop a mobile app. The product owner has a clear vision and has written detailed user stories for the first release. During sprint planning, the development team estimates that they can complete 40 story points per sprint. However, after two sprints, the team has only completed 30 points per sprint. The product owner is concerned and wants to hold the team accountable. The team says that the estimates were optimistic and that they are still learning the technology. The Scrum Master notices that the team is not using pair programming or test-driven development (TDD) as originally planned. The product owner suggests reducing scope for the next sprint to match the team’s actual velocity. The Scrum Master must decide the best way to proceed. What should the Scrum Master do?

A.Replace the team lead to send a message about accountability
B.Encourage the product owner to use the actual velocity of 30 as the basis for future sprint planning
C.Set a goal of 40 story points and ask the team to be more productive
D.Insist that the team adopt pair programming and TDD immediately to improve productivity
AnswerB

Using empirical data (actual velocity) leads to more realistic planning and reduces pressure on the team.

Why this answer

The Scrum Master should use empirical data (actual velocity of 30 story points) to guide future sprint planning, not the initial optimistic estimate. This aligns with the Agile principle of transparency and adapting based on real team performance, especially when the team is still learning the technology. The product owner can then adjust scope realistically, avoiding overcommitment and fostering trust.

Exam trap

The trap here is confusing a target velocity with actual velocity, leading candidates to choose options that enforce accountability or impose practices, rather than using empirical data to adjust planning.

How to eliminate wrong answers

Option A is wrong because replacing the team lead does not address the root cause—unrealistic estimates and lack of engineering practices—and undermines team accountability without solving the velocity gap. Option C is wrong because setting a goal of 40 story points without adjusting for actual velocity ignores empirical data and pressures the team, likely leading to further underdelivery and burnout. Option D is wrong because insisting on pair programming and TDD immediately may not be feasible if the team lacks experience with these practices; forcing adoption without training or gradual integration can reduce productivity further.

25
MCQmedium

An XP team is practicing pair programming. A new developer feels uncomfortable because the partner frequently corrects their code. What is the best way to foster a positive pairing experience?

A.Ask the senior developer to only observe and not comment.
B.Have the new developer work alone until they gain more confidence.
C.Discontinue pair programming for that pair.
D.Encourage the pair to set expectations and rotate roles (driver/navigator) regularly.
AnswerD

Clear roles and rotation promote balanced participation and learning.

Why this answer

Setting expectations and rotating roles (driver/navigator) is a core XP practice that fosters collaboration, psychological safety, and skill transfer. In pair programming, the driver writes code while the navigator reviews and suggests improvements; rotating roles ensures both developers contribute equally and learn from each other, reducing the new developer's discomfort by making corrections a shared, constructive process rather than a one-sided critique.

Exam trap

The trap here is that candidates often assume the problem is the senior developer's behavior or the new developer's lack of confidence, leading them to choose isolation (Option B) or avoidance (Option A or C), rather than recognizing that the XP framework provides a structured role-rotation mechanism to resolve such interpersonal friction.

How to eliminate wrong answers

Option A is wrong because asking the senior developer to only observe and not comment defeats the purpose of pair programming, which relies on real-time feedback and knowledge sharing; silent observation prevents the new developer from learning from the senior's expertise. Option B is wrong because having the new developer work alone until they gain more confidence contradicts the XP principle of collective code ownership and continuous collaboration, and it delays the learning that pair programming provides. Option C is wrong because discontinuing pair programming for that pair avoids addressing the root issue of mismatched expectations; it fails to leverage the proven benefits of pair programming and may reinforce the new developer's anxiety rather than building their skills.

26
MCQeasy

A product owner is writing user stories for a new feature. Which of the following is a best practice for ensuring the stories are well-formed?

A.Store all stories in a single document for traceability
B.Assign each story to a specific developer for ownership
C.Write stories after the sprint starts to ensure accuracy
D.Ensure each story is small enough to complete in one sprint
AnswerD

Stories should be sized so they can be completed within a single iteration (INVEST: Small).

Why this answer

The INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) are the standard for well-formed user stories. Storing stories in a single document makes them hard to prioritize and track. Assigning stories before the sprint limits flexibility.

Writing stories after the sprint is too late.

27
MCQhard

Refer to the exhibit. The team has a capacity of 5 story points for the sprint. Which items should they commit to?

A.Item 1 only
B.Items 2 and 3
C.Items 1 and 2
D.Item 3 only
AnswerA

Item 1 is the highest priority and fits within the 5-point capacity.

Why this answer

The team should take the highest-priority item that fits within capacity. Item 1 (High priority, 5 points) fits exactly. Option B is wrong because item 2 (Low) and item 3 (8) exceed capacity.

Option C is wrong because item 1 (5) and item 2 (1) total 6, exceeding capacity. Option D is wrong because item 3 alone exceeds capacity.

28
Drag & Dropmedium

Drag and drop the steps for managing project quality in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Quality management starts with planning, then assurance, control, metrics definition, and corrective actions.

29
Multi-Selecteasy

Which TWO are Scrum artifacts? (Choose two.)

Select 2 answers
A.Kanban Board
B.User Story
C.Product Backlog
D.Sprint Backlog
E.Gantt Chart
AnswersC, D

The Product Backlog is an ordered list of work for the product.

Why this answer

The Product Backlog is a Scrum artifact because it is an ordered list of everything that is known to be needed in the product, serving as the single source of requirements for any changes to be made. The Sprint Backlog is also a Scrum artifact, as it comprises the Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. Both are explicitly defined in the Scrum Guide as the three artifacts (along with the Increment).

Exam trap

The trap here is that candidates confuse common Agile tools (like Kanban Boards or User Stories) with the specific Scrum artifacts defined in the Scrum Guide, leading them to select options that are widely used in practice but not formally recognized as artifacts.

30
MCQmedium

During a sprint review, the team demonstrates a new feature to stakeholders. One stakeholder says, 'This isn't what we wanted. We need a completely different approach.' The product owner is upset because the feature took two weeks to build. The team is frustrated because they followed the product owner's specifications exactly. The Scrum Master observes that the product owner did not involve stakeholders during the sprint and based the user stories on assumptions. The product owner wants to add the rework to the next sprint. However, the team's capacity is already full. The Scrum Master needs to help the team and product owner recover. What should the Scrum Master do first?

A.Remove the product owner from the project to prevent future miscommunication
B.Blame the team for not clarifying requirements during the sprint
C.Coach the product owner to collaborate with stakeholders during the sprint to validate assumptions early
D.Add the rework to the next sprint and ask the team to work overtime
AnswerC

Early and frequent feedback prevents such surprises; the product owner should show progress more often.

Why this answer

The root cause is lack of stakeholder involvement during the sprint. The Scrum Master should encourage the product owner to engage stakeholders regularly, perhaps by showing early increments or holding more frequent demos. Adding rework without adjusting scope will cause the team to fail the next sprint.

Blaming the team is inappropriate. Instead, the product owner should renegotiate the sprint goal with the team.

31
MCQeasy

In Scrum, what is the purpose of the Sprint Retrospective?

A.To inspect and adapt the team's process.
B.To review the product increment with stakeholders.
C.To plan the work for the next sprint.
D.To update the product backlog.
AnswerA

The retrospective focuses on process improvement.

Why this answer

The Sprint Retrospective is an opportunity for the team to inspect its own process and create a plan for improvements. Option A correctly identifies this purpose. Option B describes the Sprint Review, which focuses on the product increment.

Option C describes Sprint Planning, which plans the work for the upcoming sprint. Option D describes Product Backlog refinement, which is an ongoing activity to update and prioritize the backlog.

32
MCQmedium

An organization is transitioning from a traditional project management approach to Scrum. The project manager has been reassigned as a Scrum Master but continues to assign tasks to team members and track individual progress. The team is becoming demotivated. What should the Scrum Master do differently?

A.Coach the team to self-organize and take ownership of their work
B.Continue assigning tasks but explain that it is necessary for accountability
C.Switch to Kanban to reduce process overhead
D.Ask the team to write daily status reports to increase visibility
AnswerA

The Scrum Master should foster self-organization and empower the team to decide how to complete their work.

Why this answer

In Scrum, the team is self-organizing and decides how to do the work. The Scrum Master should facilitate the team's ownership of tasks, not assign them. Asking the team to write daily status reports adds bureaucracy.

Changing to Kanban may not be necessary; the issue is the Scrum Master's behavior. Firing team members is not a solution.

33
MCQhard

In the Scaled Agile Framework (SAFe), what is the primary responsibility of the Solution Train Engineer (STE)?

A.Designing the technical architecture for the solution.
B.Acting as a servant leader to coordinate and improve the solution train's delivery.
C.Facilitating the Agile Release Train (ART) ceremonies.
D.Defining the solution vision and roadmap.
AnswerB

The Solution Train Engineer is a servant leader who facilitates the solution train's events, resolves impediments, and drives continuous improvement.

Why this answer

The Solution Train Engineer (STE) is a servant leader who facilitates and coordinates the solution train's events and processes, ensuring alignment and continuous improvement, similar to the Release Train Engineer at the program level. Option A is incorrect because designing the technical architecture is the responsibility of the System Architect. Option C is incorrect because facilitating ART ceremonies is the role of the Release Train Engineer (RTE).

Option D is incorrect because defining the solution vision and roadmap is typically the role of the Solution Manager or Product Manager.

34
MCQhard

A geographically distributed agile team using Scrum is experiencing frequent integration issues and delays caused by incompatible code changes. Which Extreme Programming (XP) practice would best address this problem?

A.Pair programming
B.Continuous integration
C.Test-driven development (TDD)
D.Refactoring
AnswerB

Continuous integration demands frequent merging and automated builds, catching integration conflicts early—critical for distributed teams.

Why this answer

Continuous Integration (CI) involves merging all developer working copies to a shared mainline several times a day, ensuring early detection of integration issues. Option A is wrong as pair programming focuses on code quality but not specifically integration. Option C is wrong since test-driven development improves unit tests but not integration.

Option D is wrong as refactoring improves design but not integration frequency.

35
Multi-Selecteasy

Which TWO are benefits of using an iterative approach in agile projects?

Select 2 answers
A.Ability to adapt to changing requirements
B.Less documentation is needed
C.Faster feedback from stakeholders
D.Reduced overall project cost
E.Postponed testing until the end of the project
AnswersA, C

Iterations allow the team to reprioritize based on feedback and new information.

Why this answer

Iterative development allows early and frequent delivery of working product increments, enabling faster feedback. With shorter cycles, the team can adapt to changing requirements. Iterations do not necessarily reduce total project cost (often they increase predictability but not cost), and they do not postpone testing—testing occurs each iteration.

Final documentation is not reduced; documentation is typically just-in-time.

36
MCQeasy

At the daily stand-up meeting, a team member consistently arrives 10 minutes late, causing the meeting to start late. What is the best agile practice to address this?

A.Impose a fine for lateness to discourage the behavior.
B.Have the team discuss the issue and agree on a new start time, with a commitment to start promptly.
C.Escalate the issue to management to enforce punctuality.
D.Cancel the daily stand-up until the team member arrives on time.
AnswerB

Agile teams are self-organizing and should address impediments as a team. The Scrum Master can facilitate this conversation.

Why this answer

Agile teams are self-organizing and should collaboratively address issues like tardiness. The team can agree on a new start time and hold each other accountable, with the Scrum Master facilitating if needed. Option A is wrong because imposing a fine is punitive and conflicts with agile principles of respect and collaboration.

Option C is wrong because escalating to management bypasses the team's self-organization and can damage trust. Option D is wrong because canceling the stand-up removes a key inspect-and-adapt opportunity and does not solve the underlying issue.

37
MCQmedium

A Scrum Master notices the daily stand-up meetings are consistently running over the 15-minute timebox and becoming unproductive. What should the Scrum Master do?

A.Make daily stand-ups optional for team members.
B.Ask team members to submit written status reports instead.
C.Cancel the daily stand-up and replace with email updates.
D.Enforce the 15-minute timebox strictly.
AnswerD

Timeboxing ensures the meeting stays focused and efficient.

Why this answer

The Scrum Master is responsible for facilitating Scrum events and ensuring they stay within their timeboxes. Enforcing the 15-minute timebox (D) is the most direct and appropriate action to keep the stand-up focused and productive. Option A (making stand-ups optional) would reduce participation and collaboration, not address the timebox issue.

Option B (written status reports) removes the interactive, collaborative nature of the stand-up. Option C (canceling stand-ups and replacing with email) eliminates the event entirely, losing its value. Therefore, D is correct.

38
MCQhard

A distributed agile team has members in three different time zones. They use Scrum with two-week sprints. The daily Scrum is held at 9:00 AM Eastern Time, which is inconvenient for the team members in India (7:30 PM) and Australia (11:00 PM). The team is struggling with communication and frequently misses the daily Scrum. The product owner is not attending anyway, but the development team members from remote locations feel left out. The Scrum Master wants to improve the situation. The team has decided to try alternating the time of the daily Scrum. However, the product owner insists that the team should all be available at a fixed time. The remote developers are becoming disengaged. What should the Scrum Master do?

A.Replace the daily Scrum with a daily email status update
B.Hold two separate daily Scrums: one for each time zone region
C.Enforce the fixed time rigidly and ask remote members to adjust their schedules
D.Rotate the daily Scrum time each sprint to share the inconvenience fairly
AnswerD

Rotating times ensures that all team members can occasionally attend during their normal working hours, fostering inclusion.

Why this answer

The core of the problem is the meeting time. The Scrum Master should advocate for the team and suggest rotating the time to accommodate everyone, ensuring that the whole team can attend. Having two separate daily Scrums would break the team cohesion.

Recording the meeting doesn't allow for live interaction. Moving to email updates eliminates the event's purpose.

39
MCQeasy

An agile team is using a burndown chart for the first time. After six days of a two-week sprint, the burndown chart shows that the remaining work has increased compared to the previous day. The team is confused. They had completed several tasks, but new tasks were added to the sprint backlog after the sprint started. The product owner says the additions were urgent and necessary. The development team is frustrated because they feel the sprint goal is at risk. The Scrum Master must address this situation. What should the Scrum Master do?

A.Instruct the team to ignore the burndown chart and focus on delivering the original sprint goal
B.Explain to the product owner that the sprint backlog is frozen once the sprint starts and cannot be changed
C.Ask the product owner and team to renegotiate the sprint scope, either removing some planned work or deferring the new work to the next sprint
D.Manually adjust the burndown chart to show the completed tasks and hide the additional work
AnswerC

Scrum allows the product owner to change the sprint backlog only if the team agrees and adjusts scope accordingly.

Why this answer

The Scrum Master should facilitate a negotiation between the product owner and the development team to re-evaluate the sprint backlog. In Scrum, the sprint backlog can be clarified or renegotiated with the product owner, but the sprint goal must remain achievable. By asking the team and product owner to either remove planned work or defer the new tasks, the Scrum Master protects the sprint goal and maintains team focus, which is the core responsibility of the Scrum Master in an agile framework.

Exam trap

The trap here is that candidates often assume the sprint backlog is completely frozen once the sprint starts, but Scrum allows changes as long as the team and product owner agree and the sprint goal remains viable.

How to eliminate wrong answers

Option A is wrong because instructing the team to ignore the burndown chart disregards a key agile metric for tracking progress and transparency; the burndown chart is a tool for visibility, not a distraction. Option B is wrong because the sprint backlog is not frozen; the product owner can influence the backlog, but the team must agree to any changes that affect the sprint goal—this option incorrectly states an absolute rule that contradicts Scrum's flexibility. Option D is wrong because manually adjusting the burndown chart to hide additional work violates the principle of transparency in Scrum and would mislead the team and stakeholders about the true state of the sprint.

40
MCQhard

During a Scrum sprint, the development team discovers that a critical dependency on another team's API cannot be resolved until the next sprint. The product owner insists on delivering the current sprint goal without adjusting scope. The team is struggling to meet the definition of done. What should the Scrum Master do first?

A.Order the team to work overtime to complete the remaining work
B.Ignore the dependency and ask the team to do their best
C.Escalate the issue to the program manager for resolution
D.Facilitate a discussion between the product owner and team to renegotiate the sprint goal
AnswerD

The Scrum Master coaches the team and product owner to collaborate on scope adjustments when dependencies block work.

Why this answer

The Scrum Master should facilitate a discussion with the product owner and team to explore options, such as removing the blocked work or adjusting the sprint goal. The Scrum Master is a servant leader who helps the team and product owner negotiate scope. Ordering the team to work overtime violates Scrum principles.

Escalating to management bypasses the Scrum framework. Ignoring the impediment would lead to failure.

41
MCQmedium

Refer to the exhibit. The team wants to pull a new item into In Progress. What should they do first?

A.Ignore the WIP limit and pull the item.
B.Move an item from In Progress to Done.
C.Increase the WIP limit for In Progress.
D.Add the item to To Do.
AnswerB

Completing an item frees WIP capacity to pull a new item.

Why this answer

The In Progress column is at its WIP limit of 3 items. To pull a new item into In Progress, the team must first complete one of the current items by moving it to Done, freeing up a slot. This respects the WIP limit and ensures flow efficiency.

Option B is correct: move an item from In Progress to Done. Option A is wrong because ignoring WIP limits violates Kanban principles. Option C is wrong because the team should first complete work before adding more.

Option D is wrong because adding to To Do does not address the WIP limit issue.

42
MCQhard

During a sprint, the team identifies a critical defect that requires immediate attention. What should the Scrum Master do?

A.Report to management.
B.Add the defect to the product backlog.
C.Allow the team to fix the defect within the sprint if possible.
D.Stop the sprint and restart.
AnswerC

The team can adjust work within the sprint as long as the sprint goal is achievable.

Why this answer

The Scrum Master should facilitate the team to self-organize and address the critical defect within the current sprint if it does not compromise the sprint goal. Option A is wrong because reporting to management is not the Scrum Master's immediate action; the team handles the work. Option B is wrong because adding the defect to the product backlog would delay the fix, and urgent defects are best handled within the sprint.

Option D is wrong because stopping the sprint is a drastic measure that should be reserved for extreme situations, not a typical response to a defect.

43
MCQeasy

A startup is adopting Scrum for the first time. During the Sprint Review, stakeholders request many changes to the product increment. What is the best way for the Scrum Master to handle this?

A.Let the Development Team decide which changes to implement immediately.
B.Add the changes to the current Sprint Backlog immediately.
C.Ask the Product Owner to add the changes to the Product Backlog for prioritization in future Sprints.
D.Ignore the feedback since the Sprint is complete.
AnswerC

The Product Owner manages the Product Backlog; feedback is captured and prioritized for future Sprints.

Why this answer

In Scrum, the Sprint Review is a time for stakeholders to inspect the increment and provide feedback, but changes cannot be made to the current Sprint as the Sprint Goal and scope are fixed. The Product Owner is responsible for managing the Product Backlog, so the best action is to capture these change requests and have the Product Owner add them to the Product Backlog for future prioritization. This ensures the Development Team remains focused on the current Sprint Goal and that changes are evaluated against business value and priority in upcoming Sprints.

Exam trap

The trap here is that candidates confuse the Sprint Review with a mid-Sprint change opportunity, thinking stakeholder feedback must be acted on immediately, rather than understanding that the Product Backlog is the proper channel for all new requirements.

How to eliminate wrong answers

Option A is wrong because the Development Team should not decide on implementing changes immediately; they are focused on delivering the current Sprint Goal, and unplanned changes disrupt the Sprint Backlog and violate the Sprint's timebox. Option B is wrong because adding changes to the current Sprint Backlog mid-Sprint violates the Scrum principle of a fixed Sprint Backlog and can destabilize the Sprint Goal; changes should only be introduced if the Sprint Goal is not threatened, and even then, only the Product Owner can cancel the Sprint. Option D is wrong because ignoring stakeholder feedback contradicts the inspect-and-adapt principle of Scrum; feedback is valuable for future Sprints and should be captured, not discarded.

44
Multi-Selecteasy

Which TWO are benefits of self-organizing teams?

Select 2 answers
A.Faster decision making.
B.Higher creativity.
C.More consistent processes.
D.Better adherence to a fixed plan.
E.Reduced overhead of management.
AnswersA, E

Team members can decide quickly without waiting for management approval.

Why this answer

Self-organizing teams make faster decisions (A) because they are empowered to act without waiting for management approval. They also reduce overhead of management (E) because less direct supervision is needed. Option B (higher creativity) may occur but is not a primary benefit; C (consistent processes) is not a benefit as self-organization may lead to variability; D (better adherence to fixed plan) contradicts the adaptive nature of self-organization.

Therefore, the correct answers are A and E.

45
MCQmedium

Refer to the exhibit. A team uses this CI pipeline. What action should the team take to resolve the pipeline failure?

A.Skip the Test stage and proceed to Deploy.
B.Review the Build stage for errors.
C.Fix the failing unit test in test_calculator.py and re-run the pipeline.
D.Deploy the code manually because the Build succeeded.
AnswerC

The pipeline indicates a unit test failure; fixing the test and re-running is the appropriate corrective action.

Why this answer

The Test stage failed due to a unit test error; the team must fix the failing test and re-run the pipeline. Option A is wrong as skipping tests would compromise quality. Option B is wrong because the Build stage succeeded.

Option D is wrong because the pipeline is not yet ready for deployment.

46
MCQeasy

What is the primary role of the Product Owner in Scrum?

A.Manage the team
B.Remove impediments
C.Maximize the value of the product
D.Write code
AnswerC

The Product Owner maximizes value by managing the backlog.

Why this answer

The Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. Option A is wrong because the Scrum Master manages the Scrum process, not the Product Owner. Option B is wrong because removing impediments is the Scrum Master's role, not the Product Owner's.

Option D is wrong because writing code is the Development Team's responsibility.

47
MCQhard

Refer to the exhibit. An Agile team used this project policy to control access to user stories in their project management tool. A developer reports that they cannot access a user story in the 'confidential' folder. Their request includes the tag 'confidential'. What is the most likely cause?

A.The policy is malformed.
B.The developer is not authorized to read any user stories.
C.The developer's request matches the condition in the Deny statement.
D.The user story is located in a different project.
AnswerC

The Deny statement explicitly blocks access when the tag condition is met.

Why this answer

The developer's request matches the condition in the Deny statement. The project policy includes a Deny statement that applies when the request tag 'confidential' is present. Since the developer's request includes that tag, the Deny overrides the Allow, blocking access.

Option B is incorrect because the developer is authorized by the Allow statement, but the Deny explicitly revokes that authorization for this specific condition.

48
MCQeasy

During a sprint retrospective, the team identifies that they often spend too much time in daily stand-up meetings. What is the recommended timebox for the daily Scrum in Scrum?

A.As long as needed to resolve all blockers
B.30 minutes, to allow for detailed discussion
C.15 minutes, focused on progress toward the sprint goal
D.10 minutes, with a strict agenda
AnswerC

Scrum guide states the daily Scrum is 15 minutes.

Why this answer

The daily Scrum is timeboxed to 15 minutes regardless of team size. Extending the time would reduce productivity. Adding an agenda or switching to email are not prescribed and would change the event's purpose.

49
MCQmedium

A Scrum Master notices that the development team is not self-organizing and often waits for instructions. What is the best coaching approach?

A.Escalate to the Product Owner to provide more detailed specifications.
B.Encourage the team to make decisions collaboratively and support them when they face obstacles.
C.Assign a technical lead to direct the team.
D.Hold daily status meetings to assign tasks.
AnswerB

This empowers the team to self-organize with the SM as a facilitator.

Why this answer

The Scrum Master should coach the team to make decisions collaboratively, fostering self-organization. Option A shifts responsibility to the Product Owner, which does not address the team's lack of self-organization. Option C undermines self-organization by assigning a technical lead to direct the team.

Option D is command-and-control, not agile, and would further inhibit self-organization.

50
MCQhard

A company uses Scrum with two-week sprints. The team's velocity is 30 story points per sprint, and they have a well-refined product backlog. However, stakeholders frequently introduce urgent, high-priority requests mid-sprint, which the Product Owner accepts because of stakeholder pressure. As a result, the team is overcommitted each sprint, often leaving 40% of planned work incomplete. The Product Owner is frustrated because promised features are delayed, and the team feels demotivated due to constant interruptions. The Scrum Master has been asked to intervene. What is the best course of action for the Scrum Master?

A.Instruct the Product Owner to defer all mid-sprint changes to the next sprint.
B.Add a capacity buffer to each sprint to accommodate unexpected requests.
C.Implement a change control board to approve all mid-sprint changes.
D.Facilitate stakeholder negotiation to limit mid-sprint changes and reinforce the importance of the sprint goal.
AnswerD

This balances protecting the sprint while allowing flexibility for critical changes, and it aligns with the Scrum Master's role as a facilitator.

Why this answer

The Scrum Master's primary role is to protect the Scrum framework and facilitate collaboration. By negotiating with stakeholders and reinforcing the sprint goal's importance, the Scrum Master addresses the root cause—uncontrolled scope changes—without violating Scrum principles. This approach preserves the team's focus and velocity, preventing overcommitment and demotivation.

Exam trap

The PMI-CAPM exam often tests the misconception that the Scrum Master should enforce rigid rules (like deferring all changes) or add buffers, rather than facilitating collaboration and coaching the Product Owner on stakeholder management.

How to eliminate wrong answers

Option A is wrong because instructing the Product Owner to defer all mid-sprint changes is authoritarian and ignores the Product Owner's authority to manage the backlog; Scrum allows changes before the sprint is over if they don't disrupt the sprint goal. Option B is wrong because adding a capacity buffer violates the empirical nature of Scrum—it artificially inflates estimates and hides the real issue of scope creep, leading to inaccurate velocity tracking. Option C is wrong because implementing a change control board introduces a waterfall-like governance process that contradicts Scrum's principle of self-managing teams and the Product Owner's sole responsibility for backlog prioritization.

51
MCQmedium

A Scrum team has a stable velocity of 30 story points per sprint. The Product Owner requests that the team deliver 50 story points in the next sprint to meet a market deadline. What is the best course of action for the Scrum Master?

A.Coach the Product Owner on the team's capacity and discuss options such as scope reduction or deadline extension.
B.Instruct the Development Team to work overtime to meet the request.
C.Remove the Sprint Retrospective to free up time for development.
D.Add two extra days to the Sprint to allow more work.
AnswerA

The Scrum Master helps the Product Owner understand that velocity is an observed measure and that overcommitting is counterproductive.

Why this answer

The Scrum Master should coach the Product Owner on the importance of sustainable pace and realistic planning, and facilitate a conversation about trade-offs. Option B is wrong as pushing the team can lead to burnout and quality issues. Option C is wrong as skipping events undermines the framework.

Option D is wrong as the Scrum Master should not make unilateral changes.

52
MCQhard

Refer to the exhibit. What does the increase in remaining work from Day 3 to Day 4 indicate?

A.The team had a holiday on Day 4.
B.The team removed some work from the Sprint Backlog.
C.The team finished work faster than expected.
D.The team added new work to the Sprint Backlog.
AnswerD

An upward trend indicates that the remaining effort increased, which happens when new tasks are identified or scope is added.

Why this answer

An increase in remaining work on a burndown chart from Day 3 to Day 4 indicates that the team added new work to the Sprint Backlog (or re-estimated existing work upward). Option A is incorrect because a holiday would result in no work being done, so the remaining work line would stay flat, not increase. Option B would cause a decrease in remaining work as scope is removed.

Option C would show a steeper decline, not an increase.

53
MCQhard

A Scrum Master observes that the Development Team consistently overcommits during Sprint Planning and often fails to deliver all committed items by the Sprint Review. What should the Scrum Master do?

A.Take over the Sprint Planning and assign work based on the Product Owner's priorities.
B.Change the Sprint Goal to be less ambitious each Sprint to ensure delivery.
C.Mandate that the team can only commit to a maximum of 80% of their velocity.
D.Coach the team on using historical velocity data and encourage them to commit to a realistic amount of work.
AnswerD

Coaching the team to make data-driven decisions empowers them to improve their planning and commitment accuracy.

Why this answer

The Scrum Master should coach the team on using historical velocity data to make realistic commitments, fostering self-management and continuous improvement. Option A is wrong because the Scrum Master should not take over Sprint Planning; that undermines the team's autonomy. Option B is wrong because lowering the Sprint Goal artificially does not address the root cause of overcommitment.

Option C is wrong because mandating a fixed percentage of velocity violates self-organization and does not teach the team to estimate effectively.

54
MCQmedium

Given the exhibit, which action should the Scrum Master take?

A.Ask the team to start work on User Story B in parallel.
B.Add another user story to the Sprint Backlog to keep the team busy.
C.Cancel the Sprint and start a new one.
D.Encourage the team to focus on completing User Story A, and defer B and D to the next Sprint.
AnswerD

Completing A aligns with velocity; uncommitted items can wait.

Why this answer

The Scrum Master should protect the Sprint Goal and ensure the team focuses on completing committed work. In this scenario, User Story A is the highest priority and likely critical for the Sprint Goal; deferring B and D to the next Sprint maintains focus, avoids overloading the team, and preserves the integrity of the current Sprint. This aligns with the Scrum principle of delivering a potentially releasable increment at the end of each Sprint.

Exam trap

The trap here is that candidates may think adding more work (Option B) or parallelizing (Option A) shows efficiency, but Scrum values focus and completion over multitasking, and canceling a Sprint (Option C) is only for when the Sprint Goal is invalid, not for workload management.

How to eliminate wrong answers

Option A is wrong because starting User Story B in parallel would split the team's focus, increase work-in-progress (WIP), and risk incomplete stories at Sprint end, violating the Scrum principle of finishing committed work before adding new tasks. Option B is wrong because adding another user story to the Sprint Backlog when the team is already busy would increase scope without capacity, likely causing unfinished work and undermining the Sprint Goal. Option C is wrong because canceling the Sprint is a drastic measure reserved for when the Sprint Goal becomes obsolete (e.g., market shift or technology failure), not for normal prioritization adjustments; the team can still deliver value by completing User Story A.

55
Multi-Selecteasy

Which TWO of the following are core roles in the Scrum framework?

Select 2 answers
A.Product Owner
B.Business Analyst
C.Project Manager
D.Tester
E.Scrum Master
AnswersA, E

Product Owner is a core Scrum role responsible for maximizing product value.

Why this answer

The Product Owner is a core Scrum role responsible for maximizing the value of the product and managing the Product Backlog. This role is explicitly defined in the Scrum Guide as one of the three accountabilities (alongside the Scrum Master and Developers) and is essential for the framework's operation.

Exam trap

PMI often tests the misconception that traditional project roles like Business Analyst or Tester are part of Scrum, when in fact Scrum deliberately minimizes role definitions to three core accountabilities.

56
MCQhard

A Product Owner is struggling to prioritize a backlog that includes both technical debt and new features. According to agile principles, which approach is most appropriate?

A.Alternate between technical debt and features each sprint.
B.Always prioritize technical debt because it improves velocity.
C.Prioritize based on business value, considering the cost of delay for each item.
D.Always prioritize new features over technical debt because they deliver immediate value.
AnswerC

Cost of delay helps evaluate the relative value of features and debt.

Why this answer

Agile prioritization focuses on business value and cost of delay, considering both new features and technical debt. Option A is wrong because ignoring technical debt can harm future value delivery. Option B is wrong because value should be the primary driver.

Option D is wrong because arbitrary alternation is not value-driven.

57
Matchingmedium

Match each conflict resolution technique to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Seek a win-win solution

Each party gives up something

One party imposes a solution

Emphasize areas of agreement

Retreat from the conflict

Why these pairings

The correct matches are: Withdraw/Avoid (retreating), Smooth/Accommodate (emphasizing agreement), and Collaborate/Problem Solve (integrating perspectives). Common confusions include misattributing definitions to Force or Compromise.

58
Multi-Selectmedium

Which TWO activities are considered part of Product Backlog refinement? (Select TWO)

Select 2 answers
A.Running the Daily Scrum
B.Conducting the Sprint Retrospective
C.Prioritizing items in the Product Backlog
D.Demonstrating the increment at the Sprint Review
E.Adding detailed acceptance criteria to user stories
AnswersC, E

The Product Owner continuously prioritizes backlog items to maximize value; this is part of ongoing refinement.

Why this answer

Options C and E are correct because prioritizing items in the Product Backlog and adding detailed acceptance criteria to user stories are key activities in Product Backlog refinement. Refinement involves breaking down items, adding details, and ordering them to make them ready for upcoming Sprints. Options A, B, and D are not part of refinement: the Daily Scrum, Sprint Retrospective, and Sprint Review are separate Scrum events.

59
Multi-Selecteasy

Which TWO practices are part of the Scrum framework?

Select 2 answers
A.Pair Programming
B.Sprint Review
C.Continuous Deployment
D.Sprint Retrospective
E.Backlog Refinement
AnswersB, D

The Sprint Review is a Scrum event to inspect the increment and adapt the Product Backlog.

Why this answer

The correct answers are B (Sprint Review) and D (Sprint Retrospective). These are two of the five formal events defined in the Scrum Guide. Sprint Review occurs at the end of each Sprint to inspect the Increment and adapt the Product Backlog.

Sprint Retrospective is held after Sprint Review to inspect the team's processes and plan improvements. Option A (Pair Programming) is an Extreme Programming (XP) practice, not a formal Scrum event. Option C (Continuous Deployment) is a DevOps practice, not defined in Scrum.

Option E (Backlog Refinement) is a common practice in Scrum but is not a time-boxed event in the Scrum Guide; it is considered an ongoing activity.

60
MCQhard

You are the Scrum Master for a distributed team of 8 developers working on a mobile app. The team uses two-week Sprints and has a stable velocity of 20 story points. In the current Sprint, the team committed to 22 points. By Day 5 of the Sprint (out of 10), the team has completed only 6 points. During the Daily Scrum, several members mention they are blocked by missing API documentation from a third-party vendor. The Product Owner says the vendor promised the documentation by Day 3, but it has not arrived. The developers have started working on other tasks, but they are not well-defined and are causing confusion. What should the Scrum Master do?

A.Tell the team to continue working on other tasks and hope the documentation arrives soon.
B.Facilitate a meeting with the vendor to escalate the issue, and work with the team to re-prioritize the Sprint Backlog, possibly removing low-priority items to achieve a realistic Sprint Goal.
C.Ask the Product Owner to remove the blocked stories from the Sprint Backlog without consulting the team.
D.Extend the Sprint by 3 days to allow the vendor to deliver the documentation and the team to complete the work.
AnswerB

The Scrum Master removes impediments and helps the team self-organize to adjust the Sprint Backlog.

Why this answer

The Scrum Master's primary responsibility is to remove impediments and facilitate the team's progress. By escalating the missing API documentation to the vendor and facilitating a re-prioritization of the Sprint Backlog, the Scrum Master directly addresses the blocker and ensures the team can focus on well-defined, achievable work. This aligns with the Scrum Guide's principle of transparency and adaptation within the Sprint, especially given the team's stable velocity of 20 points and the current 6-point completion rate.

Exam trap

The trap here is that candidates may think extending the Sprint (Option D) is a valid solution, but Scrum strictly enforces time-boxed Sprints, and altering the duration would break the empirical inspection and adaptation cycle.

How to eliminate wrong answers

Option A is wrong because it ignores the Scrum Master's role as an impediment remover; hoping for the documentation to arrive without proactive escalation leaves the team blocked and risks Sprint failure. Option C is wrong because the Product Owner cannot unilaterally remove stories from the Sprint Backlog without consulting the team, as this violates the collaborative commitment made during Sprint Planning and undermines team ownership. Option D is wrong because extending the Sprint violates the time-boxed nature of Sprints in Scrum, which are fixed at two weeks; changing the Sprint duration would set a bad precedent and does not address the root cause of the missing documentation.

61
MCQmedium

A project team is adopting Kanban. They currently have a cycle time of 10 days and a throughput of 5 items per week. The team wants to improve predictability. Which action would most directly help?

A.Add more team members.
B.Decrease the WIP limits.
C.Make the work items smaller.
D.Increase the WIP limits.
AnswerC

Smaller items reduce variance in size and complexity, leading to more predictable cycle times.

Why this answer

Making work items smaller directly reduces variability in cycle time and throughput, which improves predictability in Kanban. Smaller items are easier to estimate, flow more consistently through the system, and reduce the risk of large items blocking the workflow, leading to more reliable delivery forecasts.

Exam trap

The trap here is that candidates confuse improving flow (by adjusting WIP limits) with improving predictability (which requires reducing variability in item size), leading them to choose Option B instead of C.

How to eliminate wrong answers

Option A is wrong because adding more team members does not directly improve predictability; it may increase throughput but can introduce coordination overhead and variability, making cycle times less predictable. Option B is wrong because decreasing WIP limits can reduce multitasking and improve flow, but it does not directly address the size or variability of work items, which is the root cause of unpredictability. Option D is wrong because increasing WIP limits would increase work in progress, leading to longer cycle times, more context switching, and higher variability, which worsens predictability.

62
MCQhard

A team is struggling with frequent requirement changes during a Sprint. The Product Owner keeps adding new items. What should the Scrum Master do?

A.Accept the changes as the Product Owner is the voice of the customer.
B.Ask the team to work overtime to include the new items.
C.Increase the Sprint length to accommodate changes.
D.Remind the Product Owner that once a Sprint is planned, no changes are allowed that endanger the Sprint Goal, and help them hold off until the next Sprint.
AnswerD

This protects the Sprint's focus and teaches the PO to respect the timebox.

Why this answer

Once a Sprint is planned, the Product Owner should not add items that would endanger the Sprint Goal. The Scrum Master's role is to protect the Sprint and guide the Product Owner to defer changes to future Sprints. Option A is incorrect because blindly accepting changes disrupts the Sprint.

Option B is incorrect because asking the team to work overtime is unsustainable and violates the principle of sustainable pace. Option C is incorrect because increasing the Sprint length breaks the timebox and does not address the root cause.

63
Multi-Selectmedium

Which TWO statements about the Sprint Backlog are true? (Select TWO)

Select 2 answers
A.It is a subset of the Product Backlog.
B.It is created during Sprint Planning.
C.It includes tasks decomposed from user stories.
D.It is owned by the Product Owner.
E.It cannot be changed during the Sprint.
AnswersB, C

During Sprint Planning, the team selects items and creates a plan, which becomes the Sprint Backlog.

Why this answer

Options B and C are correct. The Sprint Backlog is created during Sprint Planning (B) and includes tasks decomposed from user stories (C). Option A is false because the Sprint Backlog is not just a subset; it includes the plan for delivery.

Option D is false because the Sprint Backlog is owned by the Development Team, not the Product Owner. Option E is false because the Sprint Backlog can be changed during the Sprint by the Development Team as needed.

64
Multi-Selectmedium

Which THREE are formal Scrum ceremonies (events) as defined in the Scrum Guide?

Select 3 answers
A.Sprint Planning.
B.Backlog refinement.
C.Daily Scrum.
D.Sprint Review.
E.Release planning.
AnswersA, C, D

Sprint Planning is a Scrum ceremony to plan the work for the sprint.

Why this answer

The Scrum Guide defines five formal events: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself. Backlog refinement is not a formal ceremony; it is an ongoing activity. Release planning is not part of Scrum.

Therefore, the three correct ceremonies among the options are Sprint Planning (A), Daily Scrum (C), and Sprint Review (D).

65
MCQeasy

Refer to the exhibit. The team's velocity is 30 points per sprint, and they have already committed to stories totaling 22 points. What is the team's remaining capacity for this sprint?

A.22 points
B.30 points
C.8 points
D.52 points
AnswerC

30 - 22 = 8 points remaining capacity.

Why this answer

The team's remaining capacity is the difference between their velocity (30 points) and the work already committed (22 points), so 30 - 22 = 8 points. Option C is correct. Option A (22 points) is the committed work, not remaining capacity.

Option B (30 points) is the full velocity. Option D (52 points) adds them instead of subtracting.

66
MCQeasy

A team is new to Agile and wants to implement a framework that emphasizes iterative development, time-boxed iterations, and a prioritized backlog. Which framework should they adopt?

A.Kanban
B.Scrum
C.Lean
D.Extreme Programming (XP)
AnswerB

Scrum fits the description perfectly.

Why this answer

Scrum is the correct framework because it explicitly prescribes time-boxed iterations (sprints), a prioritized backlog (Product Backlog), and iterative development through defined events like Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. This aligns directly with the team's requirements for a structured Agile framework that enforces these core practices.

Exam trap

PMI often tests the distinction between frameworks that emphasize flow (Kanban) versus those that emphasize time-boxed iterations (Scrum), leading candidates to mistakenly choose Kanban because they associate it with Agile without recognizing its lack of fixed iterations and prioritized backlog.

How to eliminate wrong answers

Option A (Kanban) is wrong because Kanban focuses on continuous flow and visualizing work in progress (WIP) without requiring time-boxed iterations or a formally prioritized backlog; it uses a pull system rather than fixed-length sprints. Option C (Lean) is wrong because Lean is a set of principles (e.g., eliminate waste, amplify learning) derived from Toyota Production System, not a specific framework with time-boxed iterations and a backlog; it lacks prescribed ceremonies. Option D (Extreme Programming (XP)) is wrong because while XP emphasizes iterative development and customer involvement, its primary focus is on engineering practices (e.g., pair programming, test-driven development, continuous integration) and does not mandate a prioritized backlog or time-boxed iterations as its central mechanism.

67
Multi-Selectmedium

Which THREE activities are part of the Sprint Planning meeting in Scrum?

Select 3 answers
A.Selecting which Product Backlog items will be done in the Sprint.
B.Defining the Sprint Goal.
C.Creating a detailed release plan.
D.Estimating the effort of all items in the Product Backlog.
E.Decomposing selected items into tasks.
AnswersA, B, E

The team selects items from the Product Backlog to forecast for the Sprint.

Why this answer

Options A, B, and E are correct. Sprint Planning involves selecting Product Backlog items that will be done in the Sprint (A), defining a Sprint Goal (B), and decomposing selected items into tasks (E). Option C (creating a detailed release plan) is not part of Sprint Planning; release planning is typically a higher-level activity.

Option D (estimating the effort of all items in the Product Backlog) is done during Product Backlog refinement, not Sprint Planning.

68
MCQeasy

A newly formed agile team is about to start their first sprint. The product owner has a well-groomed backlog and the team has done relative sizing using planning poker. The team is excited but unsure about the process. They ask the Scrum Master what the primary goal of the first iteration should be. The Scrum Master should explain that the most important goal of the first sprint is to deliver a potentially releasable increment of the product. However, some team members are worried they may not be able to deliver enough due to team formation and learning the codebase. The product owner wants to see a visible outcome. What should the Scrum Master recommend as the primary focus for the first sprint?

A.Create a detailed design document for the entire release
B.Focus exclusively on setting up the development environment and CI/CD pipeline
C.Deliver a small but complete user story that adds value to the product
D.Skip the sprint goal to allow the team to learn without pressure
AnswerC

Delivering a working increment demonstrates the Scrum cycle and provides immediate value.

Why this answer

In Scrum, the primary goal of every sprint, including the first, is to deliver a potentially releasable increment of the product. Option C is correct because delivering a small but complete user story that adds value ensures the team practices the full Scrum cycle—from backlog refinement to definition of done—while producing a tangible outcome that satisfies the product owner's need for visible progress. This approach balances team learning with value delivery, which is the core purpose of an agile iteration.

Exam trap

The trap here is that candidates confuse 'learning the codebase' with 'no deliverable,' and choose Option B or D, but Scrum mandates a potentially releasable increment every sprint, even the first, to enforce inspect-and-adapt cycles.

How to eliminate wrong answers

Option A is wrong because creating a detailed design document for the entire release violates agile principles of just-in-time planning and iterative development; it delays value delivery and assumes requirements are stable, which contradicts the empirical process control of Scrum. Option B is wrong because focusing exclusively on setting up the development environment and CI/CD pipeline, while important, does not constitute a potentially releasable increment; the sprint goal must include a deliverable that provides business value, not just technical infrastructure. Option D is wrong because skipping the sprint goal removes the time-boxed commitment and focus that drives agile teams; learning occurs naturally during the sprint, but without a goal, the team cannot inspect and adapt based on a working increment.

69
Multi-Selecthard

Which TWO are core practices of Extreme Programming (XP)?

Select 2 answers
A.Sprint review.
B.Test-driven development (TDD).
C.Pair programming.
D.Product backlog grooming.
E.Retrospectives.
AnswersB, C

TDD is a core XP practice where tests are written before code.

Why this answer

Test-driven development (TDD) (option B) and pair programming (option C) are core practices of Extreme Programming (XP). TDD involves writing automated tests before writing the code, and pair programming involves two programmers working together at one workstation. The other options are not XP core practices: Sprint review (A) is a Scrum ceremony, product backlog grooming (D) is a Scrum activity, and retrospectives (E) are also a Scrum event.

70
MCQmedium

The team notices that work is piling up in the Testing column. The WIP limit for Testing is 3, but currently there are 5 items. What should the team do first?

A.Move items from Backlog to To Do to increase throughput.
B.Ignore the WIP limit and continue as is.
C.Move some testing items back to In Progress.
D.Focus the team on completing testing items until the WIP limit is met.
AnswerD

Swarming helps reduce the bottleneck.

Why this answer

When a WIP limit is exceeded, the team should swarm on the bottleneck to complete the items in that column, thereby reducing work-in-progress and restoring flow. In Kanban, exceeding a WIP limit signals a constraint that must be resolved by finishing existing work, not by adding more. This aligns with the core principle of limiting WIP to improve throughput and cycle time.

Exam trap

The trap here is that candidates often think moving items backward (Option C) or forward (Option A) will help, but Kanban strictly enforces finishing work in the current column before pulling new work from upstream.

How to eliminate wrong answers

Option A is wrong because moving items from Backlog to To Do would increase the inflow of work, making the bottleneck worse and violating the WIP limit even further. Option B is wrong because ignoring the WIP limit defeats the purpose of Kanban, which uses explicit limits to expose bottlenecks and drive continuous improvement. Option C is wrong because moving testing items back to In Progress would increase WIP in the upstream column, violating its own limit and hiding the real issue—it does not resolve the testing bottleneck.

71
Matchingmedium

Match each project management process group to its primary purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Define a new project or phase

Establish scope and plan actions

Complete work defined in plan

Track progress and manage changes

Finalize activities and close project

Why these pairings

The five process groups are Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Each has a distinct purpose: Initiating authorizes, Planning defines scope and plan, Executes performs work, M&C tracks and adjusts, Closing formalizes completion.

72
MCQhard

A Scrum team has five members. During a Sprint, two members are pulled to work on a critical production issue. The remaining three are unable to complete all committed stories. What should the Scrum Master do?

A.Extend the Sprint by one week to complete the remaining work.
B.Ask the Product Owner to remove work from the Sprint Backlog.
C.Let the Development Team decide how to adjust the Sprint Backlog.
D.Remove the least valuable stories from the Sprint Backlog.
AnswerC

The Development Team self-organizes to handle changes and can renegotiate scope.

Why this answer

In Scrum, the Development Team is self-organizing and responsible for managing its own work within the Sprint. When two members are pulled to a critical production issue, the remaining three team members have the authority to decide how to adjust the Sprint Backlog to reflect their reduced capacity. The Scrum Master should facilitate this self-management rather than imposing a solution, as option C respects the team's autonomy and the Scrum principle of self-organization.

Exam trap

PMI often tests the misconception that the Scrum Master or Product Owner should directly manage the Sprint Backlog, when in fact the Development Team has exclusive authority over it during the Sprint.

How to eliminate wrong answers

Option A is wrong because extending the Sprint violates the time-boxed nature of Sprints in Scrum, which are fixed-duration events (typically 2-4 weeks) and should not be extended for scope changes. Option B is wrong because asking the Product Owner to remove work from the Sprint Backlog bypasses the Development Team's authority to manage the Sprint Backlog; the Product Owner can only reorder the Product Backlog, not directly modify the Sprint Backlog during the Sprint. Option D is wrong because removing the least valuable stories is a decision that should be made by the Development Team, not unilaterally by the Scrum Master, and it assumes a value judgment that may not align with the team's priorities.

73
MCQmedium

Refer to the exhibit. An Agile team uses Git for source control. Based on the git log, which integration strategy is the team using to incorporate changes from feature branches?

A.Merge
B.Cherry-pick
C.Rebase
D.Squash
AnswerA

The merge commit shows that changes from feature-x were merged into main.

Why this answer

The presence of a merge commit (a1b2c3d) with two parents indicates a merge strategy. Rebase would show a linear history, squash would show a single commit, and cherry-pick would not show a merge commit.

74
MCQhard

Refer to the exhibit. What problem does this Kanban board reveal?

A.The WIP limit for In Progress is exceeded.
B.The To Do column is nearly empty.
C.Too many items are in the Done column.
D.There are blocked items that need attention.
AnswerA

The WIP limit is 3, but there are 5 items in progress, causing overloading and potential bottlenecks.

Why this answer

The In Progress column shows 5 items while its WIP limit is set to 3, meaning the WIP limit is exceeded. This is the problem revealed by the Kanban board. Option B is incorrect: a nearly empty To Do column is not necessarily a problem; it may indicate that work is being pulled efficiently.

Option C is incorrect: having many items in Done is a positive sign of completed work, not a problem. Option D is incorrect: there is no indication of blocked items in the exhibit.

75
MCQhard

Refer to the exhibit. The team has a policy of not committing code that fails tests. What does this indicate about their process?

A.They practice test-driven development.
B.They are violating continuous integration principles.
C.They use continuous integration correctly.
D.They need more pair programming.
AnswerB

A failed build in CI should be addressed immediately; the presence of failures indicates a breakdown in the CI process.

Why this answer

The team's policy of not committing code that fails tests indicates that they may delay integration until tests pass, which can lead to large, infrequent integrations. This violates continuous integration (CI) principles, which require frequent merging of code changes, even if tests fail temporarily, to quickly detect and fix issues. Option A is not necessarily true; TDD involves writing tests before code, but the policy alone doesn't confirm TDD.

Option C is incorrect because the policy actually undermines proper CI. Option D is tangential and not indicated by the policy.

Page 1 of 2 · 93 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Agile Frameworks and Methodologies questions.