Your distributed agile team spans three time zones with only a two-hour daily overlap. Sprint planning consistently runs over time, with the India-based developers joining at 6 AM their time and the US-based product owner available only until 11 AM EST. Retrospectives reveal that 40% of stories require significant rework because developers interpreted requirements differently than intended. The team has tried detailed acceptance criteria, but misunderstandings persist. Team velocity is 30% below similar co-located teams. What structural change would most effectively address this challenge?

Question

Accepted Answer

The correct answer is B. This tests understanding of how agile practices must adapt to distributed team realities while maintaining collaboration principles (ECO Process Task 4.2 on collaboration tools and techniques). Option B addresses the root cause—shared understanding gaps—by creating concrete, testable examples that reduce ambiguity across cultural and linguistic differences. Example mapping synchronously during the limited overlap creates high-value collaboration time investment that prevents much larger rework costs. Option A is the attractive wrong answer because it seems efficient, but asynchronous planning increases interpretation gaps that are causing the 40% rework. Option C adds process overhead without improving shared understanding—documents don't resolve ambiguity as effectively as examples. Option D fragments the team and creates integration risks, contradicting agile's emphasis on whole-team collaboration. The difficulty is recognizing that more detailed documentation (common traditional approach) won't solve this problem as effectively as better collaboration techniques.

More Process Questions