Exam PMP topic 1 question 793 discussion

In Agile practice guide page 51 it mentioned that: the team does not need iterations in order to retrospect. Team members may decide to retrospect at these key times: - When the team completes a release or ships something. It does not have to be a monumental increment. It can be any release, no matter how small. - When more than a few weeks have passed since the previous retrospective. - When the team appears to be stuck and completed work is not flowing through the team. - When the team reaches any other milestone.

waiting for a milestone is too late

According the pratice guide: "When the team reaches any other milestone."

The project manager should organize the first team retrospective when the team reaches a major milestone (option B). In agile methodologies, particularly Scrum, retrospectives are typically held at the end of each sprint or iteration. A major milestone could be considered a significant point in the project's progress, making it an opportune time for the team to reflect on their work, processes, and collaboration. This helps identify areas for improvement, celebrate successes, and ensures continuous adaptation and learning throughout the project.

This timing coincides with a natural pausing point in the project, allowing the team to reflect on their progress, learnings, and areas for improvement before moving on to the next phase. Major milestones could be finishing an initial prototype, completing a key user story, or reaching a specific development or delivery target. This approach gives the team enough time to accumulate experiences and gather meaningful data for introspection and discussion.

B is the answer. "When the team reaches a major milestone.

The correct answer is B. "When the team reaches a major milestone." In agile methodologies, retrospectives are typically held at the end of each iteration or sprint, which can be considered as reaching a major milestone. The retrospective is a chance for the team to look back on the sprint, discuss what went well and what could be improved, and plan for the next sprint. Holding a retrospective at the end of a major milestone ensures that the team is consistently evaluating and improving its processes throughout the project.

B. When the team reaches a major milestone

Pretty clearly B.

A. When more than a few weeks have passed.

The best choice from the given options would be: B. When the team reaches a major milestone. In Agile methodologies, retrospectives are typically held at the end of each sprint or iteration, which can be considered a "major milestone". This allows the team to reflect on what went well, what didn't, and how they can improve for the next sprint. Regularly scheduled retrospectives are a core part of the inspect-and-adapt philosophy of Agile. Option A, waiting for more than a few weeks, might not be effective in an Agile environment where iterations are often shorter than a few weeks. Option C, waiting until the team completes a release of a monumental increment, may be too late for effective inspection and adaptation. Option D, organizing a retrospective when the work is progressing well, doesn't follow the regular cadence recommended in Agile methodologies. Moreover, retrospectives are not just for when things are going well; they are also an opportunity to address and learn from challenges and failures.