Project Name

CATEGORY
Product Backlog

Acceptance Tests

Backlog - Who is user?

Backlog - Type of user

Weak or Missing
-2 Not broken down into
individual backlog
entires OR not
prioritized
-2 Many low priority
backlog entries have
detailed acceptance
criteria (LOW PRIORITY
ITEMS SHOULD NOT BE
DETAILED)
-2 User is indicated in
few stories
-2 Stories exist for only
one type of user

Low

Medium

Strong

Min

Max

NA

NA

2 All backlog entries

clearly prioritized

-2

NA

NA

2 All high priority

backlog entries have
detailed acceptance
criterian

-1

-2

-2

-2

-2

1 Most stories indicate 2 All stories indicate at

at least one normal flow least one normal flow
story test
story test.

-1

NA

NA

-1

NA

NA

-2

NA

NA

-2

-1 User is indicated in
some stories

1 User is indicated in
most stories

NA
-1 Most stories indicate
what the software does
but not what the user
wants to achieve

NA

Backlog - What does user want to do? (for high

priority stories)

-2 Most stories do not

indicate what the user
wants to do

Backlog - Why do they want to do it? (for high

priority stories)

-2 Few stories indicate

-1 Some stories indicate 1 Most stories indicate
the benefit to the user of the benefit to the user of the benefit of the user
implementing the story implementing the story implementing the story

Backlog - Story Tests Normal Flow (for high

priority stories)

-1 Some stories do not

indicate a normal flow
story test

Backlog - Story Tests Alternate Flow (for high

priority stories)

-1 Some (At least one)

alternate flows are
focused on navigation or NA
design or
implementation details

Backlog - Story Tests Error Flow (for high priority

stories)

-2 Missing many error

flow story tests

Backlog - Clear story descriptions (for high priority -2 Many of stories are
stories)
unclear.

NA

-1 Error flows relate to

implementation errors
not errors under user
control
-1 Some of the stories
are unclear

2 User is indicated in all

stories
NA

1 Most stories indicates 2 All stories indicates

what the user wants to what the user wants to
do with the system
do with the system

2 All stories indicate the

benefit of the user
implementing the story

Backlog - Concise story descriptions

-2 Many of stories are

overly elaborate or
-1 Some stories are
include design elements overly elaborated
or gui navigation details

NA

NA

-2

Backlog - Redundant stories

-1 Some of the stories

are redundant.

NA

NA

-1

-1

-1

-1

-1

-1

NA

1 identify and descibe

tools and process
1 identify and descibe
tools and process
1 identify and descibe
tools and process
1 identify and descibe
tools and process
1 identify and descibe
tools and process

Work Oganization Source Control

-1 not described

0 partial

NA

Work Oganization Builds

-1 not described

0 partial

NA

Coordination method and team meetings

-1 not described

0 partial

NA

Coordination method technical knowledge sharing -1 not described

0 partial

NA

Coordination method project tracking

-1 not described

0 partial

NA

Identify scrum master for each sprint in advance

-1 missing

NA

NA

1 scrum master
identified for all sprints

-2

Done checklist

-1 missing or
inconsistent

NA

1 partial

2 clear, includes
elements related to
development and testing
of a backlog entry

-2

Formating

-4 Format is awkward
and hard to follow

-2 Format is sometimes
awkward and hard to
follow

-1 Format is occasionally
NA
awkward and hard to
follow

-4

Student ID

-2 Student ID or Name or
NA
both are missing.

NA

-2

Max
Ceiling

NA

You

0
20
20

Total
0