Scrum

Project Management Methodology

Workflow

1. Product Owner adds ideas to Product Backlog
2. Sprint Planning produces the…
3. Sprint Backlog
4. Sprint happens over 1-3 weeks with Daily Scrums
5. Outcome is a potentially shippable product
6. Sprint Review is a retrospective

Roles

1. Product Owner
2. Scrum Master
3. Team Members (implementers)

Sprint

A sprint is the Traditional Waterfall methodology – Planning, Building, Testing, Release – but over 1–2 weeks.

Each sprint works on a micro-release.

Ceremonies / Meetings

1. Sprint Planning
2. Daily Scrum
3. Sprint Review

Sprint Planning

The most important user stories from the Product Backlog are added to the Sprint backlog.

This happens at the frequency of sprints.

The product owner and team estimate the relative sizes of user stories (Story Points). These are estimated as a ranked list.

Daily Scrum

A daily check in with the team and scrum master to investigate progress.

Sprint Review

At the end of the Sprint.

• What went well?
• What went wrong?
• How can I improve in the future?

Artifacts / Documents

1. Product Backlog
2. Sprint Backlog
3. Burndown Chart

Product Backlog

All the product features are written as user stories:

As a ___,
I need to ___,
so that ___.

A product feature may contain multiple user stories.

A user story can be broken down into multiple subtasks.

The product backlog defines what is needed to accomplish a Product Goal. a Product Goal must be accomplished (or abandoned) before taking on the next.

Sprint Backlog

The sprint backlog are the items required to fulfill the Sprint Goal.

Contains the most important user stories. Rule of thumb: Take on 85-115% of what you think you can do.