PMP · Question #97
A solution designer in an agile team often passes the design information to team members without any documentation. This has resulted in misunderstandings within the team. What should the agile leader
The correct answer is B. Review the process that resulted in this situation. When an agile solution designer's lack of documentation leads to team misunderstandings, the agile leader should review the process to understand the root cause of the situation.
Question
A solution designer in an agile team often passes the design information to team members without any documentation. This has resulted in misunderstandings within the team. What should the agile leader do?
Options
- AMove the solution designer to another team
- BReview the process that resulted in this situation
- CAsk the team to document the design
- DStop work until the design document is completed
How the community answered
(63 responses)- A3% (2)
- B81% (51)
- C11% (7)
- D5% (3)
Why each option
When an agile solution designer's lack of documentation leads to team misunderstandings, the agile leader should review the process to understand the root cause of the situation.
Moving the solution designer to another team is a punitive and premature action that fails to address the systemic process issues within the current team.
In an agile environment, addressing issues requires a focus on continuous improvement. Reviewing the process allows the team to identify the underlying reasons for the lack of documentation and subsequent misunderstandings, enabling collaborative solutions that improve communication and knowledge sharing, rather than just addressing symptoms.
Simply asking the team to document the design without investigating why it's not happening currently is a superficial solution that is unlikely to be sustainable or resolve the root cause.
Stopping work until the design document is completed contradicts agile principles of continuous flow and iterative delivery, causing unnecessary delays and hindering agility.
Concept tested: Agile continuous improvement, process analysis
Source: https://www.pmi.org/disciplined-agile/agile-glossary/retrospective
Topics
Community Discussion
6
Wesley A.Jun 24, 2026B is correct. I picked C on my first attempt and it cost me - the trap is jumping straight to a fix instead of examining why the situation happened in the first place. The agile leader reviews the process first, then collaborates with the team on improvements rather than mandating documentation top-down.
Carlos M.Jul 5, 2026Going with B. C is tempting because documentation fixes the immediate pain, but agile leadership is about inspecting and adapting the process, not jumping straight to a mandate.
Orla P.Jul 6, 2026B is the safer pick but keep in mind the exam expects you to balance inspect and adapt with immediate team enablement, so if the stem emphasizes a recurring blocker rather than a one-off, C gets back into play.
Zlatan X.Jul 5, 2026Confirmed B. At the program level you always examine the process and team interdependencies driving the breakdown before touching personnel or mandating artifacts, because the root cause of the communication gap is what needs governance attention.
Wesley A.Jul 7, 2026Agreed on B, and the trap on my first attempt was D because it sounds like you are addressing the gap directly, but mandating artifacts without understanding the interdependencies just papers over the root cause and adds bureaucracy.
Orla P.Jul 5, 2026I first leaned toward C since the lack of documentation is the obvious pain point and asking the team to fix it sounds practical. But the agile leader should not jump straight to prescribing a fix for the symptom. B is correct because you need to review the process that got the team here in the first place, which is a core servant-leader move. Once the root cause is clear, the team can decide together whether documentation, a shared whiteboard, or something else is the right way forward.