Retrospectives CT-AT Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A team has been holding retrospectives every sprint, but the same issues keep appearing. The team feels that the retrospectives are not leading to real improvement. What is the most likely reason for this?

   • AAction items from previous retrospectives were not tracked or implemented.
   • BThe team is not using the right retrospective technique.
   • CThe retrospective is held too frequently.
   • DThe team does not have a dedicated facilitator.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   During a retrospective, the team is discussing a sprint where a critical bug was introduced. The discussion becomes heated, with team members blaming each other. The facilitator wants to steer the conversation toward constructive improvement. What should the facilitator do?

   • AAsk the team to vote on who is responsible for the bug.
   • BRemind the team of the retrospective's purpose and refocus the discussion on processes and solutions rather than individuals.
   • CEnd the retrospective early and schedule a separate meeting to address the conflict.
   • DAllow the discussion to continue so that all feelings are expressed and the team can move on.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What is the primary purpose of a retrospective in agile software development?

   • ATo plan the work for the next iteration in detail
   • BTo assign blame for issues that occurred during the iteration
   • CTo review and improve the team's process and collaboration
   • DTo demonstrate working software to stakeholders
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   In a retrospective, the product owner is present and tends to dominate the discussion, steering it toward product backlog items rather than team process. The facilitator wants to keep the retrospective focused on the team's collaboration and improvement. What should the facilitator do?

   • AAllow the product owner to lead the discussion since they are a key stakeholder.
   • BAsk the product owner to leave the retrospective to avoid any influence.
   • CChange the retrospective technique to one that limits each person's speaking time.
   • DPolitely remind the product owner that the retrospective is for the team to discuss their process, and suggest that product-related discussions be taken to a separate meeting.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A team's retrospective is consistently running over the allotted time, and action items are not being defined because the discussion takes up all the time. The facilitator wants to ensure the retrospective ends on time and produces actionable outcomes. Which approach should the facilitator take?

   • AAsk the team to define action items before the retrospective and bring them to the meeting.
   • BShorten the retrospective to 30 minutes to force the team to be more concise.
   • CStrictly time-box each phase of the retrospective and reserve the last 10 minutes specifically for defining action items.
   • DLet the discussion continue until the team feels they have covered everything, then define action items in a follow-up meeting.
   Reveal Solution Discussion Select an answer first