Agile Teams

Some Example Role Definitions For Agile Teams
BUSINESS TEAM
Product Owner

Responsible for setting the vision, roadmap, release plan, and the features/stories for the technical team to execute. They are the sole decision maker with regard to the product. They are the interface to any stakeholders for the product/program. The Product Owner may not also play the role of Scrum Master (as these roles have conflicting goals).

Business Analyst

A Business Analyst is an extension of the Product Owner. He assists the Product Owner in crafting stories, maintaining the backlog, and managing dependencies/priorities. Even though the Business Analyst may write stories for the Product Owner, the Product Owner still is accountable for them as though he wrote them himself.

Technical Analyst

A Technical Analyst is an extension of the Product Owner. For stories of a very technical nature, it may be necessary to have a Technical Analyst to help craft Acceptance Criteria and other artifacts to ensure a story is sufficiently detailed for execution. Some scenarios may include identifying system interface needs (to/from external systems), identifying data definitions, or data mappings to/from systems of record. Even though the Technical Analyst may assist the Product Owner (or Business Analyst) in story writing, the Product Owner still is accountable for them as though he wrote them himself.

TECHNCIAL TEAM
Tech Lead

Expert in one or more technologies within the development domain. Assists in guiding the design as stories are implemented. Mentors developers in technical areas and assists in on-boarding new team members. Develops stories but at a reduced capacity from other developers. May flex into other roles (such as QA) as necessary to ensure successful sprint completion with the exception of Scrum Master (as these roles have conflicting goals).

Developer

Responsible for development of stories. People in this role may need to have different, but complementary, technical expertise to ensure the team as a whole has all the experience necessary to successfully execute stories. May flex into other roles (such as QA) as necessary to ensure successful sprint completion.

Quality Analyst/Test Engineer

Responsible for creation of test plans/cases, validation of acceptance criteria, and test automation. May flex into other roles on the Technical Team (such as Developer) as necessary to ensure successful sprint completion.

SUPPORTING ROLES
Scrum Master

The team process facilitator. The Scrum Master is responsible for ensure the team has the resources they need to be successful (team advocate) and is following the required/agreed to processes. Facilitates the scrum events/activities (but is not responsible for running them). Monitors team health metrics, identifies structural impediments, and assists in clearing any impediments (either self-identified or identified by the team). Tracks retrospective outcomes and assists the team with inspection & adaption. The Scrum Master also serves as the team “psychologist” to assist personalities to meld successfully and navigate the stages of team development (form, storm, norm, perform). The Scrum Master may not play the role of Product Owner or Technical Team member (as these roles have conflicting goals).

Project Manager

The Project Manager is responsible for creating documentation and reporting metrics that take the agile/scrum activities and translates them, as necessary, to ensure governance requirements are met.

Development Manager

The Development Manager is a Servant leader that protects the team from outside influences, assists the Scrum Master with institutional roadblocks (those that are outside the team; may also be outside the scope of the teams particular initiative).