Scrum Team Representatives
A team-selected delegate who attends Scrum of Scrums (SoS) meetings on the team's behalf. The person chosen can change, based on who is best positioned to address the current topics, dependencies, and issues.
Key Points
- Chosen by the team and may rotate depending on current needs and expertise.
- Represents the team in SoS to discuss progress, dependencies, risks, and impediments.
- Must be empowered to speak for the team and bring back agreements and actions.
- Can be any role (e.g., developer, tester, Scrum Master, Product Owner) best suited for the topics.
Example
Several Scrum teams are integrating services for a release. This week, Team A nominates their backend developer to attend the SoS because the main issue is an API contract with Team B. Next sprint, when deployment risks are the focus, the DevOps engineer represents the team instead.
PMP Example Question
In a multi-team Agile program, which practice best reflects how a Scrum Team Representative should be chosen for the Scrum of Scrums?
- Always send the Scrum Master to maintain consistency across sprints.
- Rotate only among senior engineers, regardless of the topic being discussed.
- Select the team member most knowledgeable about current cross-team issues and dependencies.
- Have the program manager represent all teams to streamline communication.
Correct Answer: C — Select the person best suited to the current issues.
Explanation: The representative is chosen by the team based on who can best address the current SoS topics, and the person may change over time.
