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: The person responsible for protecting the team from interrupts with outside work now has great influence to interrupt someone working. Please use due diligence in volunteering for, or assigning people, multiple roles. Scrum Team consists of: Scrum Master role – usually Project or Program Manager but can be anyone on the team
Product Owner role – usually Product Manager but can be anyone on the team
The Team of 7 people, +/- 2, Responsible for Task Completion :: Development, QA, Architect, OPS, UED Engineers, etc
Core Team
DESCRIPTION of Roles & Responsibilities
Product Manager aka Product Owner
Role definition
“CEO” of the product
Vertical – focus on long and short term product vision of a product line
Represents customer’s interest
Represents the product to the outside world (Customer)
Responsibilities
Responsible for market, business case, and competitive analysis
Responsible for long and short term product vision
Responsible for ROI and Net Profit
Prioritizes features for releases based upon expected ROI
Writes Acceptance Criteria
Writes user stories
Makes tradeoff decisions between scope (value in Expected ROI) and schedule (higher operating expense in longer release cycles)
Challenges
Resisting the temptation to “manage” the team. The team may not self-organize in the way you would expect it to. This is especially challenging if some team members request your intervention with issues the team should sort out for itself. Resisting the temptation to add more work
Being willing to make hard choices during a planning meeting. Balancing the interests of competing stakeholders. Program Manager
Program Managers can perform both Project & Program Manager roles.