HKSM
Scrum Masters /Scrum Teams Collaboration Plan
A plan that describes how multiple Scrum Masters and Scrum Teams coordinate and synchronize their work so they can deliver the highest possible value in the least amount of time.
Key Points
- Defines cross-team events and cadence (e.g., Scrum of Scrums, joint Sprint Reviews, integrated Retrospectives).
- Establishes how dependencies are managed and how impediments are escalated and resolved across teams.
- Aligns shared standards and practices such as Definition of Done, tooling, integration, and communication channels.
- Sets flow policies and metrics (e.g., WIP limits, cycle time, value delivery) to optimize speed and outcomes.
Example
In a program with seven Scrum Teams building a cloud platform, the plan sets a daily Scrum of Scrums for dependency checks, a weekly integrated build and demo, shared backlog refinement every two weeks, a unified Definition of Done for integration, and a clear path for escalating cross-team blockers to a Scrum Master sync meeting.
PMP Example Question
In a scaled Scrum environment, which artifact outlines how multiple Scrum Masters and Scrum Teams will coordinate to manage dependencies, remove cross-team impediments, and accelerate value delivery?
- Product Roadmap
- Scrum Masters /Scrum Teams Collaboration Plan
- Communication Management Plan
- Team Working Agreement
Correct Answer: B — Plan for cross-team collaboration among Scrum Masters and Scrum Teams
Explanation: This plan specifically defines coordination mechanisms across Scrum teams to maximize value delivery, which is broader and more targeted than general communication or a single team's working agreement.
