Retrospectives CT-AT Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A team is under pressure to deliver a release and some members suggest skipping the retrospective to save time. The Scrum Master wants to emphasize the value of the retrospective. Which statement best explains why the retrospective should still be held?

   • AThe retrospective allows the team to review the product backlog and plan the next sprint.
   • BThe retrospective is a mandatory agile ceremony that cannot be skipped under any circumstances.
   • CThe retrospective provides a regular opportunity for the team to reflect on their process and identify improvements, which is essential for long-term productivity and quality.
   • DThe retrospective is a good opportunity for the team to socialize and build rapport.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A team has been using the same retrospective format for several sprints, and participation has declined. The team is distributed across time zones, and the retrospective is held at a time that is inconvenient for some members. The Scrum Master wants to improve engagement and ensure that all team members can contribute. Which approach would be most effective?

   • ARotate the retrospective time to accommodate different time zones and use an asynchronous tool for collecting input before the meeting.
   • BUse a new retrospective technique, such as 'Sailboat', to make the meeting more engaging.
   • CRecord the retrospective and ask absent members to watch it later.
   • DKeep the same time but shorten the retrospective to 30 minutes to reduce the burden.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which step in the retrospective process involves the team sharing what they observed during the iteration?

   • ADeciding what to do
   • BSetting the stage
   • CGathering data
   • DClosing the retrospective
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A team has been holding retrospectives for several months, but the team's velocity has not improved, and the same problems keep occurring. The Scrum Master wants to understand why the retrospectives are not leading to improvement. What is the most likely reason?

   • AThe team does not have a dedicated facilitator.
   • BThe action items from the retrospectives are not being implemented or tracked.
   • CThe team is not using the right retrospective technique.
   • DThe retrospective is held too frequently, causing the team to become complacent.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   After a retrospective, the team agreed on an action item to improve their automated testing. The action item was added to the sprint backlog, but during the sprint, it was not addressed. What should the team do to improve follow-through on action items?

   • AMove the action item to the product backlog and let the product owner prioritize it.
   • BWait until the next retrospective to discuss why it was not completed.
   • CReview the action item at the next daily stand-up and assign a specific team member to report progress.
   • DRemove the action item since the team did not address it.
   Reveal Solution Discussion Select an answer first