State of Vermont Enterprise Project Management Office

Vermont Enterprise Project Management Office

Scrum Terminology Link to Glossary of Scrum Terms from srumalliance.org
Roles Description

Ensures the Scrum process is followed, coaches on Scrum roles and facilitates the removal of impediments for the team. The person assigned to this role has Scrum
Scrum Master experience and/or training.

Responsible for the overall vision of the project product. Works with stakeholders to identify, document and prioritize user stories (requirements), defines user story
Product Owner acceptance criteria, and determines if that criteria has been met.
Scrum Team Makes and meets scrum commitments (i.e., does the work).

Not a Scrum team role, but these are interested parties who are in some way impacted by the project. The Product Owner works with them on defining and prioritizing
user stories. They may participate in Product Backlog Grooming Meetings and Sprint Review meetings (see descriptions of these meetings below). The Scrum Master
Stakeholders may work with them to resolve impediments (i.e., issues and roadblocks).
Created & Updated Worksheet
Scrum Deliverables Description By Tab
A list of the Scrum Team members and Stakeholders.
Scrum Team Info &
Stakeholder Register Scrum Master 2
Prioritized List of user stories (requirements). This is a living document that is maintained by the Product Owner throughout the
Product Backlog project as user stories are added, refined, modified, deleted, reprioritized, etc. Product Owner 3

Sprint Backlog A list of the Product Backlog items that the team committed to do in the sprint. Shows tasks, assignments and status of work. Scrum Master 4
A graphical representation of the work commitments (represented as story points) completed (burnup) and the work left to do
Burnup/Burndown Charts (burndown). Scrum Master 4

Sprint Retrospective Log Use this log to track lessons learned at the end of each sprint and the improvements the team agrees to try for the next sprint. Scrum Master 9

A chart and graphical representation that shows story points committed and completed by each sprint. The trend is used for
Sprint Velocity Chart release planning. Scrum Master 5

An evolving schedule/plan of the number of releases, the high level functionality to be included in each release, and the timing of
Release Plan each release. Product Owner 6

Impediment List (optional) Track impediments that need resolution. Impediments are issues and roadblocks. Scrum Master 8

Parking Lot (optional) Track items that need to be revisited at another time. Scrum Master 7
 State of Vermont Enterprise Project Management Office

Deliverable
Produced or Worksheet
Scrum Events Description Scheduled By Attendees Meeting Length* Updated** Tab
Gather user stories from Stakeholders via a
requirements gathering exercise/session. This
meeting is optional because this is just one method Required: Product Owner and
TBD - Depends on
to use to gather requirements. See Requirements Stakeholders. Scrum scope and
Gathering on the EPMO website for more info on this The Product Owner may engage a BA
Product Owner whether user stories Product Backlog 3
topic. or PM to facilitate the session and/or are gathered in one
to help with documenting user
or multiple sessions.
stories.
Storytime Session(s)
(Optional)

Discuss and make updates to the Product Backlog in Required: Product Owner, Scrum
preparation for sprint planning. Product Owner 30 minutes to 2
Scrum Master Master & Scrum Team Product Backlog 3
answers questions about the user stories, user hours
Optional: Stakeholders
stories are updated for clarification, large user
stories (epics) are broken down into smaller ones,
dependencies between user stories are identified,
Product Backlog Grooming and acceptance criteria is added and clarified.

The Scrum team focuses on the user stories that are 1 to 2 hours for
listed as the highest priority on the Product Backlog. Scrum Master Sprint Backlog 4
every week of sprint
They estimate these user stories, breaks them down Required: Product owner, Scrum
into tasks, and commit to which ones to complete in Master & Scrum Team
Sprint Planning the next sprint.

Required: Scrum Master & Scrum Sprint Backlog &

A 15 minute stand-up meeting. Team members take Scrum Master Team 15 minutes Burnup/Burndown 4
turns providing the following: what they completed Optional: Product Owner Charts
yesterday, what they plan to complete today, and
stating any impediments they have to completing
their work. The Sprint Backlog is updated with the
Daily Scrum status of work and any new tasks or assignments.
 State of Vermont Enterprise Project Management Office

Required: Product Owner, Scrum

The team demonstrates/presents the completed Sprint Backlog &
Scrum Master Master & Scrum Team 1 to 2 hours 4
user stories to the Product Owner. Based on the Sprint Velocity Chart
Optional: Stakeholders
acceptance criteria, the Product Owner accepts or
Sprint Review rejects the work as being complete.

This is a lessons learned exercise focused on what Required: Product Owner, Scrum
Sprint Retrospective
worked well and what can be improved on for the Scrum Master Master & Scrum Team 1 to 1.5 hours 9
Log (optional)
Sprint Retrospective next sprint.

*All activities in Scrum are time-boxed (i.e. have time limits). The Scrum Master establishes the time limit and the meetings end as scheduled.
**Parking Lot & Impediments List may be updated at any of these meetings. Use is optional.
 State of Vermont Enterprise Project Management Office

Scrum Team Info & Stakeholder Register

Project Name: Scrum Team Goal:

Roles Name State Entity Contact Info

Scrum Master

Product Owner

Scrum Team Members:

Stakeholders:
 State of Vermont Enterprise Project Management Office

Product Backlog
Priority User Stories Story
ID # As a_______ I Want to_______ So I Can _________ Acceptance Criteria Points Sprint # Status

1 Not Committed

2 Not Committed

3 Not Committed

4 Not Committed

5 Not Committed

6 Not Committed
7 Not Committed

8 Not Committed

9 Not Committed
10 Not Committed
Not Committed
Not Committed
Not Committed
Not Committed
Not Committed
Not Committed

Not Committed
Not Committed
Not Committed
State of Vermont Enterprise Project Management Office

Not Committed
Not Committed
 State of Vermont Enterprise Project Management Office

Sprint Backlog
Task Points Story Points Progress
Sprint Start Date: Sprint End Date: Sprint #:
Backlog Completed Remaining
ID Tasks Status Assigned to Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Points Points

1 EXAMPLE Done Bob 34 1 5 2 10 0 0 10 3 1 2

Not Assigned
Not Assigned
Not Assigned

Total 1 5 2 10 0 0 10 3 1 2 0 0
Burndown 34 33 28 26 16 16 16 6 3 2 0
Burn-up 0 1 6 8 18 18 18 28 31 32 34

Sprint Burn Charts

Sprint Burnup Chart
Sprint Burndown Chart
40 40
3534 35 34
33 32
30 30 31
28 28
25 26 25
20 20
18 18 18
15 16 16 16 15
10 10
8
5 6 5 6
3 2
0 0 0 0 1
Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10

Story Points Story Points

 2
0 0 0 0 1
Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
State of Vermont Enterprise Project Management Office

Story Points Story Points

 State of Vermont Enterprise Project Management Office

Sprint Velocity Chart

Sprint # Sprint Start Date Sprint End Date Comments
Story Points Story Points
Committed Completed Variance
1 13 8 5 Example
2 21 19 2 Example
3
4
5
6
7
8
9
10
AVG: 17.0 13.5 3.5

Sprint Velocity
25

20

15

10

0
1 2 3 4 5 6 7 8 9 10

Story Points Committed Story Points Completed

 State of Vermont Enterprise Project Management Office

Parking Lot
# Item Date Parked Timing to Address Owner
Sprint Submitted
# By
1
2
3
4
5
6
7
8
9
10
 State of Vermont Enterprise Project Management Office

Impediments List
# Description Reported By Date Assigned To Backlog Resolution Date Sprint
Reported ID(s) Resolved #
Impacted
 State of Vermont Enterprise Project Management Office

Sprint Retrospective Log

Sprint # Item # Continue Doing

Sprint # Item # Stop Doing

Sprint # Item # Start Doing

Done
Assigned
Not Assigned

Not Committed
Committed
Closed
Done