Scribd
Upload
47 views

Scrum - Dev Process Refresher

This document provides an overview of Scrum processes and roles for a development team. It outlines expectations for transparency, team structure with product teams, Scrum masters, and a sprint schedule. Key aspects of the Scrum process like sprint planning, daily standups, burn down charts, demos and retrospectives are defined. Engineering roles and responsibilities are discussed as well as stages for testing, managing the engineering backlog and integrating with a mainline branch.

Uploaded by

sithjunk
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
47 views

Scrum - Dev Process Refresher

This document provides an overview of Scrum processes and roles for a development team. It outlines expectations for transparency, team structure with product teams, Scrum masters, and a sprint schedule. Key aspects of the Scrum process like sprint planning, daily standups, burn down charts, demos and retrospectives are defined. Engineering roles and responsibilities are discussed as well as stages for testing, managing the engineering backlog and integrating with a mainline branch.

Uploaded by

sithjunk
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Scrum and process refresher

Transparency
Everyone acts better when understands rules
Goals Development methodology Development process

Teams distribution
Product teams Team Lead and Scrum Master in each team Teams structure to be agreed every sprint basing on Product Backlog

Scrum iteration

Roles Product Owner


Scope Priorities Sprint acceptance

Roles Scrum Master


Enables close cooperation across all roles and functions Removes barriers Ensures that process is followed Highlights potential issues

Roles Team
Commits to the Sprint Works as a team to reach Sprint goal Demos the result

What about engineering roles?


Team Leads, Test Leads:
Ensure that practices are not skipped Help to optimize process

Architects
Attends Sprint Planning Assists in Design decisions Assists in research activities Code review

Sprint Schedule
Day 1: Sprint Planning Day 2-10: Daily Scrum meeting Day 2-Day 8: Implementation Day 9: No Development
Integration Smoke test Remaining bugfix after integration

Day 10: Demo -> Delivery to Mainline team

Sprint Planning
Tool (ScrumWorks now) Sprint capacity (8* people* 5 Ideal hours) Decomposition of tasks Architectural review Definition of Done All team members are involved in estimation Sprint backlog from Product backlog

Daily Scrum
Stable time Keep short Whiteboard or ScrumWorks Remind about rules Scrum of Scrums for each Product team

Burn Down
Instrument for progress tracking Daily review Decisions on next actions (notifications/scope change)

Demo
Who should be invited?
PO PM + Robert Calder (optional) Team Android SPb (optional)

Who is chairing? Meeting invitation beforehand (SM) Agenda + List of open issues Adobe Connect as demonstration tool Meeting minutes for formal acceptance (SM)

Retrospective review
What went well? What should be changed? Review sprint results in ScrumWorks Detect planning or process mistakes Agree on changes

User Story development process

Testing stages

Engineering backlog
Refactoring activities OEM Patch review Process improvements Smoke and Regression tests

Work with default branch on ML


When do we sync with Mainline code? as often as possible

You might also like