Skip to content
PMPHard

PMP Practice: Survey all necessary parties to reach consensus

Question 2 of 2 in Build Shared Understanding

Pick an answer below — you'll get the explanation instantly, no signup.

Cedar Tanaka is leading a hybrid project at Bright Pulse Labs to develop a customer-facing mobile app with both predictive infrastructure components and agile feature development. Three months into the project, the infrastructure team (working in two-month phases) delivered their first component to the agile feature teams (working in two-week sprints). The feature teams immediately escalated that the infrastructure API uses REST endpoints when they had built their entire sprint backlog assuming GraphQL. Both teams insist they communicated their technical approach in their respective planning sessions, which were held separately. The rework will delay the next three sprints and require infrastructure re-architecting. The project sponsor is demanding to know why this wasn't caught earlier. What should Cedar have done to prevent this misunderstanding?
Show answer & explanation

Correct answer: Established cross-team integration workshops at iteration boundaries where both teams could review and validate interface designs and technical assumptions together

Explanation

In hybrid environments where different teams operate on different cadences, building shared understanding requires structured integration points where teams can collaboratively validate assumptions and dependencies. Cross-team integration workshops create a forum for teams to surface and resolve technical misalignment before implementation begins. The key failure here was that both teams planned in isolation — each communicated within their own context but never verified their mutual understanding of critical interfaces. Regular collaborative touchpoints would have revealed the GraphQL versus REST assumption conflict during planning, not after delivery. This approach respects each team's operating rhythm while creating intentional moments for shared understanding across the hybrid structure.

**Why not B:** This introduces bureaucracy and delays without solving the core problem. Documentation review by a PMO doesn't create shared understanding between teams — it just adds a gatekeeper. The teams still wouldn't be talking to each other, and a PMO reviewer might not catch subtle technical misalignments. This is a predictive control mechanism applied to a situation requiring collaborative sense-making.

**Why not C:** While having an architect involved seems reasonable, making one person responsible for ensuring consistency treats shared understanding as a deliverable rather than a collaborative activity. This creates a single point of failure and removes ownership from the teams themselves. The architect can't be in all planning sessions simultaneously if teams work on different cadences, and teams won't develop the habit of validating assumptions together. This also doesn't scale well and reduces team autonomy.

**Why not D:** Daily status reports are a reactive monitoring mechanism that won't prevent planning-level misunderstandings. By the time implementation details appear in status reports, teams have already committed to their approaches and begun building. This also creates reporting overhead without fostering direct team-to-team dialogue. The problem occurred at the planning and assumption level, not during execution monitoring. Status reports are artifacts, not conversations.

Key Concept

This question covers Survey all necessary parties to reach consensus under Build Shared Understanding (People).

Share:

This is 1 of 100 free PMP questions

Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.

Unlock All Questions