PMPRocket
PMP Practice QuestionsAgile Ceremonies
Process Domain

Agile Ceremonies PMP Practice Questions

Test yourself with 7 free, scenario-based PMP practice questions on agile ceremonies, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Question 1 of 7

A Scrum team's daily standup has been taking 45 minutes instead of the 15-minute timebox. Team members are solving complex problems and discussing code during the standup. What should the Scrum Master do?

  1. A.Refocus the standup on its three core questions and 'park' detailed discussions to an after-standup session with interested parties.
  2. B.Extend the standup timebox to 30 minutes — allowing more discussion time gives the team space to resolve blockers collaboratively rather than deferring them to separate follow-up meetings.
  3. C.Cancel the daily standup and replace it with a weekly status meeting — the team's evolved communication habits suggest a less frequent synchronous format is more appropriate for their coordination needs.
  4. D.Require team members to submit written daily updates instead of attending — asynchronous updates capture the same information more efficiently and eliminate the overhead of a live standup meeting.
Show answer and explanation

Correct answer: A

The daily standup is a 15-minute synchronization meeting focused on: what did I do yesterday, what will I do today, and are there any impediments? Detailed problem-solving and design discussions should be 'parked' and addressed in a separate meeting with only relevant participants. Extending the timebox undermines the discipline of the event. Canceling it eliminates a core Scrum ceremony. Written updates eliminate the face-to-face synchronization benefit.

Question 2 of 7

During a sprint review, a stakeholder who was not involved during the sprint suggests major changes to the product based on the demo. What is the MOST appropriate response?

  1. A.Reject the changes outright — the sprint review is a demonstration event, not a change control forum, and accepting scope requests during reviews undermines sprint planning boundaries.
  2. B.Thank the stakeholder for the feedback, document the suggestions as potential backlog items, and allow the product owner to prioritize them.
  3. C.Commit to implementing the requested changes in the next sprint — rapid responsiveness to stakeholder feedback is a core agile value, and committing quickly signals strong team-stakeholder alignment.
  4. D.Extend the current sprint to incorporate the requested changes — extending preserves the team's current context and makes implementation more efficient than waiting for the next planning cycle.
Show answer and explanation

Correct answer: B

The sprint review is a feedback loop designed to inspect the increment and adapt the backlog. Stakeholder feedback — even late feedback — is valuable in agile. The product owner captures it as potential backlog items and prioritizes them against existing work in the next refinement session. Rejecting feedback outright conflicts with the agile principle of welcoming changing requirements. Committing immediately bypasses the product owner's prioritization role. Extending the sprint breaks the sprint timebox.

Question 3 of 7

What is the PRIMARY purpose of the Sprint Retrospective in Scrum?

  1. A.To present the product increment to stakeholders and obtain their feedback and formal acceptance of the work completed during the sprint.
  2. B.To select sprint backlog items and establish the sprint goal by breaking down prioritized stories into a concrete delivery commitment for the upcoming iteration.
  3. C.To inspect how the team worked during the sprint and identify process improvements for the next sprint
  4. D.To update the risk register with new risks and lessons identified during the sprint, ensuring impediments and ownership are captured before the next sprint begins.
Show answer and explanation

Correct answer: C

The Sprint Retrospective is a timeboxed meeting where the Scrum team inspects itself — its processes, interactions, and tools — and creates a plan for improving how it works. It answers: What went well? What didn't go well? What improvements can we commit to? The sprint review handles stakeholder feedback on the product. Sprint planning selects backlog items. While retrospectives generate learning, updating a formal risk register is a predictive artifact not central to the retrospective's purpose.

Question 4 of 7

During sprint planning, the team disagrees about which user stories to commit to. The product owner wants 12 stories completed but the team estimates capacity for only 8. What should happen?

  1. A.The product owner has final authority over sprint scope — if they have selected 12 stories based on business priority, the team must commit to delivering all 12 regardless of their capacity assessment.
  2. B.Split the difference by committing to 10 stories and planning extended working hours to absorb the remaining two — a midpoint commitment balances the product owner's value goals with the team's stated capacity.
  3. C.Defer sprint planning until full agreement is reached — proceeding with unresolved commitment disputes undermines team ownership and creates a sprint that the team cannot fully commit to delivering.
  4. D.The team and product owner negotiate to select the 8 highest-priority stories the team can realistically complete, with the team's capacity determining the commitment.
Show answer and explanation

Correct answer: D

In Scrum, the development team owns the commitment. The team selects the stories they believe they can complete based on their capacity and velocity. The product owner maximizes value by ensuring the highest-priority items are selected first. Forcing the team to commit to more than they can accomplish leads to failed sprints and erodes trust. Committing to unachievable scope creates unsustainable pressure. Deferring indefinitely is not productive — the ceremony has a timebox.

Question 5 of 7

A newly formed Scrum team struggles with their first sprint review because stakeholders give conflicting and vague feedback. What practice would BEST improve future sprint reviews?

  1. A.Prepare a clear agenda with specific questions for stakeholders and share it before the review to focus feedback.
  2. B.Limit sprint review attendance to the product owner and Scrum Master — a smaller audience eliminates unfocused feedback and keeps the review efficient and action-oriented.
  3. C.Replace sprint reviews with a written acceptance process — documented sign-off is more rigorous and defensible than verbal feedback sessions and reduces recurring meeting overhead.
  4. D.Ask stakeholders to submit written feedback forms instead of attending — written input gives stakeholders more time to reflect and typically produces more structured, actionable feedback.
Show answer and explanation

Correct answer: A

Providing a structured agenda and targeted questions before the sprint review helps stakeholders come prepared with focused feedback. Questions like 'Does this meet your acceptance criteria?' or 'What would make this more useful?' direct conversations toward actionable outcomes. Limiting attendance reduces the feedback pool — diverse stakeholder perspectives are valuable. Replacing with a written process eliminates the collaborative inspection that is central to agile. Written forms lose the dynamic discussion benefits.

Question 6 of 7

A Scrum team member says the daily standup is 'useless bureaucracy' since the team already communicates via chat. What is the BEST response?

  1. A.Agree and cancel the standup since the team is already coordinating effectively through informal chat — when asynchronous communication works well, a daily ceremony adds unnecessary overhead.
  2. B.Explain that the standup provides synchronous commitment and shared awareness that asynchronous chat cannot fully replicate.
  3. C.Make attendance optional to accommodate the team member's preference — flexibility in ceremony participation reflects the agile principle of valuing individuals over rigid processes.
  4. D.Report the team member to HR for failing to follow the agreed Scrum process — consistent non-compliance with team ceremonies is a conduct issue that requires formal documentation.
Show answer and explanation

Correct answer: B

The daily standup creates a daily commitment cadence and shared situational awareness that supports team coordination. While chat is valuable for async communication, the standup surfaces blockers, fosters team accountability, and builds rapport in real time. If standups feel bureaucratic, the Scrum Master should coach the team to make them more purposeful and inspect whether the three questions are being addressed effectively. Canceling or making it optional eliminates the synchronization event. HR escalation is extreme and counterproductive.

Question 7 of 7

A Scrum team has been running for 6 months but has never implemented any improvements from their retrospectives. What is the MOST likely root cause?

  1. A.The team may be identifying improvements but not assigning ownership, timelines, or tracking progress — making commitments without accountability.
  2. B.The team does not believe retrospectives are valuable — low buy-in for the ceremony results in superficial discussions that fail to generate actions the team is motivated to actually implement.
  3. C.The Scrum Master is not facilitating the retrospective effectively — weak facilitation allows teams to discuss issues without structuring the conversation toward specific, actionable commitments.
  4. D.The team's velocity is too high to absorb process improvements — teams operating at maximum throughput have insufficient capacity to implement changes without disrupting their delivery commitments.
Show answer and explanation

Correct answer: A

The most common reason retrospective improvements go unimplemented is lack of accountability: improvements are identified but not assigned an owner, given a due date, or tracked in the next retrospective. The Scrum Master should ensure each improvement action has: a clear owner, a completion target (often the next sprint), and a review in the following retrospective. Without this structure, retrospectives become complaint sessions without change. This is a facilitation and team discipline issue.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

Start Interactive PracticeTry the PMP Mock Exam

More Process practice questions

Risk Management (21)Quality Management (18)Integration Management (16)Resource Management (16)Earned Value Management (12)Schedule Management (11)