What is one potential root cause of Team Sync anti-patterns?

The correct answer is B. Lack of collective ownership. Lack of collective ownership is the root cause because when team members feel responsible only for their individual tasks rather than the team's shared outcome, syncs devolve into siloed status reports instead of genuine coordination. Without shared accountability, there's no mot

Coaching and Facilitation

Question

Options

AOvercommunication between team members
BLack of collective ownership
COccasional conflict within the team
DFrequent verification and integration during the Iteration

How the community answered

(43 responses)

A
12% (5)
B
79% (34)
C
7% (3)
D
2% (1)

Explanation

Lack of collective ownership is the root cause because when team members feel responsible only for their individual tasks rather than the team's shared outcome, syncs devolve into siloed status reports instead of genuine coordination. Without shared accountability, there's no motivation to surface blockers, help others, or align on the bigger picture - the hallmarks of Team Sync anti-patterns.

Why the distractors are wrong:

A (Overcommunication): Anti-patterns stem from poor communication quality, not too much of it - more collaboration generally helps teams.
C (Occasional conflict): Healthy disagreement is normal and even productive; it's chronic, unresolved conflict that causes problems, not occasional friction.
D (Frequent verification and integration): This describes continuous integration, an Agile best practice that actively prevents anti-patterns by catching issues early.

Memory tip: Think "No owner = no coordination." When everyone owns only their slice, nobody owns the sync - so it breaks down. Collective ownership is the glue that makes team ceremonies work.

Topics

#Team Sync#anti-patterns#collective ownership#team dysfunction

Community Discussion

No community discussion yet for this question.

Full SAFE-SSM Practice