Your distributed agile team spans three time zones with six developers in India, four in Poland, and three in the United States. After six sprints, retrospective data shows that defect rates have increased by 40% and the team reports frustration with asynchronous communication. Most collaboration happens through written messages, and the daily standup rotates times weekly to accommodate all zones, resulting in inconvenient hours for different team members each week. Despite using collaborative tools, integration issues are discovered late. Team morale is declining. What structural change would most effectively address these delivery and collaboration challenges?

Question

Accepted Answer

The correct answer is A. Option A is correct because it addresses the root cause—insufficient synchronous collaboration time—through team structure rather than forcing collaboration across incompatible time zones. ECO Process Task 4.3 (support performance by addressing team structure) and Process Task 2.2 (communication management) support organizing teams for sustainable flow. Sub-teams with full-stack capabilities can maintain agile practices within their time zones while coordinating asynchronously at integration points, which is more sustainable than forcing global synchronous collaboration. Option D is the main distractor and seems reasonable for increasing collaboration, but forcing a four-hour overlap across three widely separated time zones likely means very early or late hours for some members, which is unsustainable and will further damage morale. It treats symptoms rather than reorganizing for success. Option B adds process overhead without addressing communication issues. Option C assumes tools are the problem when the issue is structural—better tools cannot overcome the fundamental challenge of asynchronous work requiring synchronous collaboration.

More Process Questions