Product Backlog - list of all product features, product owner responsible for prioritizing

Sprint Backlog - the to do list for the sprint

Burndown Chart - chart that shows how much work remains in a sprint
Release Backlog - same as the product backlog, may involve one or more sprints

Estimating:
User Story - high level definition of what the customer wants to do 'As a (user), I want (function) so that (desired result)
Story Points - simple way to estimate a level of effort (relative scoring used - from 1 - 10, with 1 being easy and 10 being most
Business Value - each user story has in the Product Backlog has a business value assigned - typically H, M, L
 that (desired result)
ng easy and 10 being most difficult.
Product Backlog
Complete the Product Backlog with data for each of the stories (components) of the project. Fields with calculated data are shaded in grey. For definitions of
each data component, hover over the title.

Overall Project Estimates

The data is calculated from the Work Estimate for
details below Sprint 1 93
Work Estimate for
Sprint 2 31
Work Estimate for
Sprint 3 0
Work Estimate for
Sprint 4 0
Work Estimate for
Sprint 5 0
Work Estimate for
Sprint 6 0

Work Estimate for

Sprints 7 and beyond 0
Total Sprint Information
This data should be completed
at the beginning of the current Current Sprint: 1
Sprint Total User Story Hours 93
Total available hrs for
the sprint: 120
Focus Factor 78%
Number of Resources in
Sprint 3
This data should be updated Current Sprint In-Progress Details
daily to determine resource User Stories Hours
requirements to finish the Remaining 25
current Sprint
Work Hours Remaining 24 Assume 8 hours per day
Difference: -1
Work Days Remaining
Number
in Sprint of Days in 1
Sprint 5
Sprint
Details Team Sprint 1 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Later
Analyst / Prep Development Total User Time
Epic Sprint User Story Role User Story Name Story Details Acceptance Test Criteria Tasks work Estimate QA Story Remaining
New Art Gallery Website 1 Gallery Owner Create web page for each There are 20 artists currently 1. 20 web pages must be on the website 1. Develop a template for each artist to 5 60 10 75 0
artist exhibiting at the gallery. 2. Each artist must be listed on the page with their fill out for each piece of art that is to be
Each artist should be bio displayed on the website.
provided 1 page to showcase 3. At least one piece of art should be described and 2. Request bio and picture from each
their art a picture included on each page artist
3. Request artist to fill out template of
each art piece to be presented on
webpage along with at least 1 picture of
art piece
3. Update each artists web page with
Name, Bio & art pieces requested with
pictures.

75 0 0 0 0 0 0
New Art Gallery Website 1 Gallery Owner Create main Gallery New gallery wants to build a 1. The main page of the website should describe 1. Define the look and feel of the 10 8 18 0
Webpage community between the the gallery and its mission. webpage for the gallery
artists, the gallery & the 2. The main page of the website should have a link 2. Obtain the content that describes the
customers. to each of the artist pages that are currently gallery's mission
exhibiting at the gallery 3. Determine and implement a way to
link to all the artists from the main page
simply

18 0 0 0 0 0 0
New Art Gallery Website 2 Gallery Owner Artist & Customer Customers should be able to 1. Customers should be able to send a message to 5 24 2 31 0
communication chat directly with artists to the artist. There is no requirement that the artist
learn more about any art respond immediately.
pieces they may be 2. Artists must have a way to respond to the
interested in. customer
3. The interaction between artist and customer can
be public or private.
0 31 0 0 0 0 0
Sprint Progress Tracking - An Example
This Tab enables the Scrum Master to track the progress of the Sprint relative to the Plan. Each day, enter the number of h
remaining in the Sprint. The graph compares the planned Sprint completion with the actual progress. The Ideal Line shows
that would be expected if the Sprint proceeds as planned. The Time Remaining line shows the actual progress for the Sprin
day, if the Time Remaining is above the Ideal Line, the project is running late. If this is a consistent and significant trend for
two days, defer some stories to a later Sprint and record this change in the Project Information. Use the Blockers table to re
Sprint activities that affected the Sprint. These should be used to improve estimates for later Sprints.

Enter Sprint 2 This example uses different data than that in the Product Backlog
Number Example

Day of the Sprint - Enter Total

assumes 10 day Hours
sprints Remaining Ideal Line

0 126 126
1 115
2 115
3 115
4 98
5 93
6 91
7 14
8 14
9 0
10 0 0

Blockers Hours Spent

Data Base 8
Prod Issue
Meetings 12
Sick
Slush 3
Bug
TOTAL 23
day, enter the number of hours
ess. The Ideal Line shows the progress
tual progress for the Sprint. On any
nt and significant trend for more than
se the Blockers table to record non-
nts.

in the Product Backlog

 Time remaining
Days Remaining 140
In this example, the Sprint is
running behind schedule at
120 this point

100

80
Enter Total Hours
Remaining
60 Ideal Line

40 The Sprint is back on

track because the team
found a more efficient
way to develop part of
20 the work.

0 11; 0
0 2 4 6 8 10 12
Day of the Sprint
 Enter Total Hours
Remaining
Ideal Line

e Sprint is back on
ack because the team
ound a more efficient
ay to develop part of
e work.