Which practice coordinates dependencies weekly?

Which practice coordinates dependencies weekly?

• A. PI Planning
• B. System Demo
• C. Release Planning
• D. Scrum of Scrums

Answer: (D)

Coordinating dependencies across multiple teams on a regular cadence is handled by the Scrum of Scrums. In this practice, a representative from each Agile Team (often the Scrum Master) meets to surface cross‑team dependencies, blockers, and integration risks. The weekly rhythm keeps teams aligned, helps resolve issues before they derail multiple teams, and supports the ART’s ongoing synchronization as work is delivered across teams. This differs from PI Planning, which is a large, endpoints-in-time planning event for the next Program Increment; System Demo, which showcases integrated progress at intervals; and Release Planning, which focuses on coordinating a set of features for a broader release horizon rather than ongoing cross‑team dependency coordination.

Coordinating dependencies across multiple teams on a regular cadence is handled by the Scrum of Scrums. In this practice, a representative from each Agile Team (often the Scrum Master) meets to surface cross‑team dependencies, blockers, and integration risks. The weekly rhythm keeps teams aligned, helps resolve issues before they derail multiple teams, and supports the ART’s ongoing synchronization as work is delivered across teams. This differs from PI Planning, which is a large, endpoints-in-time planning event for the next Program Increment; System Demo, which showcases integrated progress at intervals; and Release Planning, which focuses on coordinating a set of features for a broader release horizon rather than ongoing cross‑team dependency coordination.