Title: Agile Team Members – Roles and Responsibilities - Aaron Sanders, This Agile Guy
Headings: Agile Team Members – Roles and Responsibilities
Agile Team Members – Roles and Responsibilities
Agile Team Members – Roles & Responsibilities
Program/Release/Project TEAMS
Program/Release/Project CORE Team consists of:
Representing multiple TEAMS as a Core Team member
Scrum Of Scrums
Representing multiple ROLES in a Core Team
Scrum Team consists of:
DESCRIPTION of Roles & Responsibilities
Product Manager aka Product Owner
Role definition
Responsibilities
Challenges
Program Manager
Role definition
Responsibilities
Program Management responsibilities
Scrum Master responsibilities
Architect
Role definition
Responsibilities
Engineering Manager
Role definition
Responsibilities
Product Developer
Role definition
Responsibilities
QA
Role definition
Responsibilities
UED
Role definition
Responsibilities
Operations
Role definition
Responsibilities
Role comparisons
Program Manager vs. Product Manager Comparison
Advantages to PMs and EMs having a Program Mgr on a project

Content: Agile Team Members – Roles & Responsibilities
The key to successful team building is creating unity while celebrating the individuality of each team member => Common purpose supported by unique contributions
Team is held responsible for a release, individuals are held accountable to their commitments
Each team member has one or more roles on a project
When a team member has more than one role on a project, potential conflicts may occur. Always think checks & balances before signing up for multiple roles
Team Members – Roles & Responsibilities
Program/Release/Project TEAMS
Program/Release/Project CORE Team consists of: Representing multiple TEAMS as a Core Team member
Scrum Of Scrums
Representing multiple ROLES in a Core Team
Scrum Team consists of: DESCRIPTION of Roles & Responsibilities
Product Manager aka Product Owner
Program Manager
Architect
Engineering Manager
Product Developer
QA
UED
Operations
Role comparisons
Program Manager vs. Product Manager Comparison
Advantages to PMs and EMs having a Program Mgr on a project
Program/Release/Project TEAMS
Program/Release/Project CORE Team consists of: Product Owner (aka Product Manager)
Engineering Manager
Architect
QA Manager
Program Manager (aka Project Manager, Scrum Master)
Representing multiple TEAMS as a Core Team member
Cannot attend multiple stand ups
Scrum team too large and being split
New teams being formed
One core team member on multiple Scrum teams
Stagger daily stand ups
Attend one stand up and send a proxy to the other
Scrum Of Scrums
Starts ON TIME
Attendees
Core team members
VP of the group
All other VP direct reports
Scrum Master is the Director of Program Management
Product Owner is the Director of Product Management
Program or Project Manager (Scrum Master) for the project answers the following
What was accomplished on the project yesterday? What is happening today on the project? What is blocking the project from progressing to deployment? What are other projects with which this one is being integrated? A proxy of another core team member who attended the daily stand up can answer if needed
Product Owner provides business and domain answers for clarification of project direction
Side conversations are parked and follow-up meetings arranged
Scrum Master records all blockers and follow-up arrangements
Scrum Master lists out existing blockers and follow-ups made
VP prioritizes blockers
NOTE: Every attempt is made to resolve all blockers in the day they are raised.