Roles

1) What are the Roles and what they are accountable for

#Product Owner

The System Level Product Manager/Owners will perform the same roles and responsibilities of a product level Scrum Master but across an integrated Scrum Team. Her are the responsibilities: Clearly expressing Product Backlog items (Stories & Tasks) by working closely on a regular cadence with Product Manager to clearly articulate the product requirements for the team; Ordering the items in the Product Backlog to best achieve goals and missions; Optimizing the value of the work the Development Team performs; Defines Acceptance criteria Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Approves Scope Ensuring the Development Team understands items in the Product Backlog to the level needed Notify PO’s on other teams where there are dependencies to achieve a goal; track these dependencies in conjunction with the other PO’s Create stories that sync with Roadmap in Backlog Ensures the stories are linked to the appropriate Functional epics in Backlog Potentially create engineering epics for large-scale engineering work (in exceptional circumstances only and with clear collaboration with Product Manager as Epics are tracked at Functional level to ensure completeness of release increment) Ensures these engineering epics are linked to the appropriate Functional initiatives in Backlog

Architects

Engineering Manager/Leads:

Accountable for: Measuring Dev delivery progress Assigning resources & team structure

Scrum Master:

Scrum Master Service to the Product Owner The Scrum Master works with the Product Owner in several ways, including: • Finding techniques for effective Product Backlog management; • Helping the Scrum Team understand the need for clear and concise Product Backlog items; • Understanding product planning in an empirical environment; • Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; • Ensures all Stories are mapped to Epics in JIRA • Understanding and practicing Scrum; and, • Facilitating Scrum events as requested or needed. Scrum Master Service to the Development Team The Scrum Master works with the Development Team in several ways, including: Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value products; Removing impediments to the Development Team’s progress; Facilitating Scrum events as requested or needed; and, Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood. Scrum Master Service to the Organization The Scrum Master works with the organization in several ways, including: Leading and coaching the organization in its Scrum adoption; Planning Scrum implementations within the organization; Helping employees and stakeholders understand and enact Scrum and empirical product development; Causing change that increases the productivity of the Scrum Team; and, Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization. Tracking dependencies across the teams Tracking overall resource allocation and capacity forecasting Identifying/ tracking/resolving risks

Role	Accountable for Defining Work Items	Contributes in Work Items by:
Product Owner	Themes Epics Features Define Feature Roadmap	Prioritized entire backlog including bugs/feature requests Helping to create/groom work items Accepts work and moves PBI Story state from Verifiable to Done once items are complete
Architects	Non-Functional Features Defining the implementation design by helping create PBI/stories. Estimation of High level Features at a sprint effort level with feedback from engineering	Defining Feature Roadmap Themes Definition Epics Definition Features PBI/Stories
Engineering Manager/Leaders	Accountable for Defining the: Defining the composition and properties of all Backlog item types & process	todo
Tech Lead	todo	todo
Scrum Masters	Manage Team capacity measurement Ensure acceptance criteria is complete and work item hygiene is good
Developers/Testers		Grooming Features & PBIs/Stories Breaking down stories into tasks
SRE/Devops