PMP · Question #713
Five agile teams working together on a product recently performed release planning. Midway through the project, each team showed that their progress was on track. When all of the teams integrated at t
The correct answer is D. Ensured frequent and continuous integration of work to obtain early feedback and continuous. To avoid late-stage integration issues in a multi-team agile project, the project manager should have ensured frequent and continuous integration of work across all teams. This practice enables early detection of integration problems and provides immediate feedback, allowing for
Question
Options
- APerformed a Scrum of Scrums on a regular basis to help the teams remove impediments
- BFormed a separate quality assurance team to test all items coming from each team at the end of
- CArranged an online session on the integration concept and suggested tools to the teams
- DEnsured frequent and continuous integration of work to obtain early feedback and continuous
How the community answered
(36 responses)- A14% (5)
- B6% (2)
- C3% (1)
- D78% (28)
Why each option
To avoid late-stage integration issues in a multi-team agile project, the project manager should have ensured frequent and continuous integration of work across all teams. This practice enables early detection of integration problems and provides immediate feedback, allowing for timely resolution.
While Scrum of Scrums helps with impediment removal and coordination between teams, it focuses on communication and identifying cross-team dependencies, not directly on the technical integration of code or features.
Forming a separate QA team at the end for testing reinforces a "big bang" integration approach, which is precisely what caused the issues. Agile promotes quality throughout the development lifecycle, not just at the end.
Arranging an online session on integration concepts and tools is a good educational step, but it doesn't ensure the actual implementation of continuous integration practices, which is the critical missing piece.
The core principle missed here is continuous integration. In multi-team agile environments, teams must integrate their work frequently (daily or multiple times a day) rather than waiting until the end. This ensures that integration issues are detected and resolved early, preventing a cascade of problems and keeping the overall product release on track by providing continuous feedback.
Concept tested: Agile Continuous Integration
Source: https://www.atlassian.com/continuous-delivery/continuous-integration
Topics
Community Discussion
4
Dervla O.Mar 20, 2026D is correct here. The stem tells you each team was fine individually but integration failed, which is the classic symptom of siloed work that waits too long before coming together. Frequent and continuous integration surfaces those issues early when they are cheap to fix, instead of at release planning when you discover the committed content is at risk. A sounds tempting because Scrum of Scrums helps with coordination, but coordination alone does not catch technical integration defects the way actually integrating the work does. Read the stem twice and lock onto the word integrated as your signal.
Fatima Z.Mar 17, 2026D is correct, and the giveaway is the phrase continuous integration. CI means teams integrate early and often, not just at release time. Think of the acronym EARLY: Evaluate And Release Little Yields frequently. Scrum of Scrums (A) helps with impediments but does not force the code to actually merge. A separate QA team (B) is anti-agile and just delays feedback. Training (C) is nice but does not cause the behavior change needed.
Mateus R.Mar 16, 2026D is the right call here. A is tempting because Scrum of Scrums sounds like the agile answer to everything, but the real disease here is waiting to integrate, and only continuous integration fixes that.
Dervla O.Mar 16, 2026Agree on D but flag the word "continuous" in the stem because if it says "regular" or "periodic" integration, the exam is pointing you toward C and you need to read it twice before locking in.