0% found this document useful (0 votes)
48 views18 pages

Release Projections: Project Burndown

The document includes a project burndown chart showing the projected velocity and remaining work for 3 releases over 10 sprints of a product. It also includes a product backlog listing user stories for features like user registration, login, fund transfer, and bill payment. Each story includes acceptance criteria with estimates of the story size.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
48 views18 pages

Release Projections: Project Burndown

The document includes a project burndown chart showing the projected velocity and remaining work for 3 releases over 10 sprints of a product. It also includes a product backlog listing user stories for features like user registration, login, fund transfer, and bill payment. Each story includes acceptance criteria with estimates of the story size.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 18

<Product Name> Release Projections

Project Burndown
### Project start
80
7 Sprint length (days)
3 Release 1 sprints (#) 70
7 Release 1 release sprint length (days) 60

Remaining Points
### Release 1 date
50
2 Release 2 sprints (#)
0 Release 2 release sprint length (days) 40
### Release 2 date 30
3 Release 3 sprints (#) 20
0 Release 3 release sprint length (days)
10
### Release 3 date
0
Plan Start 1 2 3 4 5 6 7
Actual

<Product Name> Product Backlog


ID Title Description
EP1.1 User Register The homepage shall have the register
option on the right side of the screen

EP1.2 User Register The user shall be provided data input boxes
for
account and personal information in the
registration page

EP1.3 User Register The log in ID shall be data input box

EP1.4 User Register Below the login ID shall be the


password data input box

EP1.5 User Register The user shall have the option to


confirm the details beside password box
EP1.6 User Register The user shall be provided with a
register button below the pw box

EP1.7 User Register The user shall be displayed an error is data


incorrect and shall be given an
option to retype/re-enter details

EP2.1 User LogIn User navigate to the Login Page

EP2.2 User LogIn User enter valid UserID and Password

EP2.3 User LogIn User account home page is displayed


EP2.4 User LogIn User enter invalid UserID or invalid
Password
Error Message Is Displayed

EP2.5 User LogIn User get UserID by Entering


SSN,Provide_x000D_
Date Of Birth and Last Name
EP2.6 User LogIn User get Password by Entering SSN,Provide
Date Of Birth and Last Name

EP2.7 User LogIn User can use the option to get the UserID by
providing email or Mobile Number

EP2.8 User LogIn User can use the option to get the _x000D_
Password by providing email or Mobile
Number

EP3.1 User Fund Transfer User register new person for fund transfer
while registering new person  
User has to provide his account details

EP3.2 User Fund Transfer User select the new person as nominee ,
register and provide the amount to transfer

EP3.3 User Fund Transfer If nominee register fails, error


message will be displayed
EP3.4 User Fund Transfer User get the confirmation code through
the option 1.email 2.text message

EP3.5 User Fund Transfer User enter the code to transfer


the amount in the fund transfer page

EP3.6 User Fund Transfer If it is a valid code and sufficient amount


User
will get navigate to confirmation details
page
and payment confirmation is displayed
EP3.7 User Fund Transfer If User enter a invalid code fails
error message will be displayed

EP3.8 User Fund Transfer User if have no sufficient fund in account


_x000D_
error message will be displayed

EP4.1 User Pay Bill User shall have the option to register payee.
While registering the payee, User need to
provided
payee account details like details, address,
email and Phone

EP4.2 User Pay Bill User shall have the option to get the
confirmation email/ text for the status of
payee

EP4.3 User Pay Bill While paying the bill ,User has the option  
to select the Payee from the list of
registered Payee

EP4.4 User Pay Bill User shall the option to search the Payee
from the list of registered Payee

EP4.5 User Pay Bill User have the option to select the payee
and _x000D_
enter the amount for the Bill Payment

EP4.6 User Pay Bill User should have sufficient fund in their
account
otherwise error message will be
displayed for the insufficient fund
EP4.7 User get the confirmation email/text
message after the successful Bill Payment
Requirement Empirical PERT Calculations
Improvement Actual Sprints Target
roject Burndown
Maintenance Sprint Velocity Remain Burn
Overhead Start 6 10 73
1 8 9 73
2 9 8 64
3 3 7 61
4 7 6 54
5 9 5 45
6 12 4 33
7 8 3 25
8 7 2 18
9 8 1 10
10 10 0 0
3 4 5 6 7 8 9 10

Running Sprint Release


Acceptance Criteria Type Size Total CompletedDates
The register option shall be a rectangular Requirement 3 3
box on the right
of the screen and shall take to the
registration page when selected

The Account number data input box shall be Requirement 2 5


a numeric data input box
with max length of 12 and personal details
shall be
data input box for name, address and phone
number

The data input box shall accept Requirement 5 10


alphanumeric characters with a max length
of 15

The paswword data input box shall accept Requirement 2 12


alphanemric and special characters
with a max length of 10

The confirm details option shall notify Requirement 3 15


the user if details not filled
The register option shall be a rectangular Requirement 3 18
selct box which shall
check whether the User ID and PW entered
are valid
and shall if valid shall send a confirmation
text/email to user

If there is an error in the data entered by Requirement 4 22


user for ID/PW or
personal details, that particular data input
box shall be
cleared of data and show a red color
border to help the user retype the info

In the Login Page UserID input box , Requirement 2 24


password input box
and submit button should be displayed

In the LogIn page User can enter UserID in Requirement 3 27


the input box which
accept alphanumeric and max length of 10
and can enter password
in the input box which accept
aplhanumeric and max length of 8

User Account summary should be displayed Requirement 2 29


In the LogIn page User can enter Requirement 1 30 ###
invalidUserID in the input box which accept
alphanumeric and max length of 10 and can
enter invalid password in
the input box which accept aplhanumeric
and max length of 8
then Error Message will be displayed

User get UserID by entering SSN in input Requirement 3 33


box that accept numeric max length is 9
and then provide Date Of Birth in input box
that accept numeric max length 8 and
then provide last name that is alphabet max
length 20
User get Password by entering SSN in input Requirement 2 35
box that accept numeric max length is 9
and then provide Date Of Birth in input box
that accept numeric max length 8
and then provide last name that is alphabet
max length 20

User can get the UserID by entering email in Requirement 3 38


the input box
that accept alphanumeric max length 15
and or mobile number numeric max length
10

User can get the Password by entering email Requirement 2 40


in the _x000D_
input box that accept alphanumeric max
length 15
andor mobile number numeric max length
10

User provide nomineeaccount details in the Requirement 3 43


input box
which accept numeric max length 20

User provide the amount in the input box Requirement 3 46


which accept numeric max length  25

User Nominee register fails Error Requirement 2 48


message will be displayed
User can get confirmation code by entering Requirement 3 51
email in the input box
which accept alpha numeric and max length
is 25
and mobile number in the input box
numeric max length 10

User enter the code in the fund transfer Requirement 1 52


page
in the input box max length 4

User will get navigate to the payment Requirement 1 53


confirmation page
and can see the confirmation details
User enter invalid code in the input box Requirement 1 54
which
accept numeric max length 4
error message will be displayed

User have insufficient fund_x000D_ Requirement 2 56


the Error message will be displayed.

In the Bill Payment page User have add Requirement 3 59


Payee button
which will navigate to the Payee
registeration page

In the Pay Bill Page User have the option to Requirement 2 61


enter email in
the input box and it accept alphanumeric
and special characters
and mobile number in the input box that
accepts
only numbers max 10 to get the Payee
registeration.

In The Pay Bill Page User can search Payee Requirement 3 64


by typing the
Payee in the input box alphanumeric max
length is 15
and select from the list of registered Payee

In Pay Bill page User can selects the Payee Requirement 3 67


and
enter the amount in the input box max
length 10 only numbers

In Pay Bill page User can selects the Payee Requirement 2 69


and
enter the amount in the input box
max length 10 only numbers

In the Pay Bill page if User has not sufficient Requirement 1 70


amount in
their account and try to pay then the Error
message will be displayed
User will navigate from Pay Bill page to Requirement 3 73
Confirmation
Pay page and successfully sent message
will be displayed
P Scope ML Scope O Scope
Plan Remain Remain Remain
Burn 12 8 3
73 120 80 30
66 108 72 27
58 96 64 24
51 84 56 21
44 72 48 18
37 60 40 15
29 48 32 12
22 36 24 9
15 24 16 6
7 12 8 3
0 0 0 0

Release
Goals
Release 1: <goal>
478202495.xlsx

<Product name> - Sprint <#>


Sprint Dates: <Month> <DD> - <Month> <DD>, <YYYY>
Available working hours in the sprint Days in sprint: 4.5
Sprint Goal M Tu W Th F
<DD> <DD> <DD> <DD> <DD>
Sprint Planning Sprint Planning Sprint Planning Sprint Planning Sprint Review +
Demonstrate the ability to <sprint goal>. (NOTE: Define a sprint goal in terms of working customer functionality Retrospective
you will be able to demonstrate to internal stakeholders and possibly release to the marketplace.) Developers
<Developer name> 4 6 6 6 4
<Developer name> 4 6 6 6 4
Burndown: Hours & Points Remaining <Developer name> 4 6 6 6 4
<Developer name> 4 6 6 6 4
140 20 <Developer name> 4 6 6 6 4
18 Total sprint hours:
120
Estimated Hrs Remaining

Total per day:

Story Points Remaining


16
100 14

80 12
10
60 8
40 6
4
20
2
0 0
1 2 3 4 5
Actual
Day of Sprint Plan
Story Points

Feature Burndown - Based on estimated hours remaining


M Tu W Th F
Task Description Acceptance Criteria Type Story Responsible <DD> <DD> <DD> <DD> <DD>
Sprint Planning Sprint Planning Sprint Planning Sprint Planning Sprint Review +
Points Retrospective

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 8 Developer name 8 8 8 8 8
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 5 Developer name 5 5 5 5 5
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

Page 13 of 18
478202495.xlsx

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 3 Developer name 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 2 Developer name 2 2 2 2 2
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 1 Developer name 1 1 1 1 1
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

Actual Hrs Remaining 120 120 120 120 120


Schedule Hrs Remaining 130 98 65 33 0
Story Points Remaining 19 19 19 19 19
Day: 1 2 3 4 5
Issues
Team Member
<issue>

Team Member
<issue>
<issue>

Page 14 of 18
478202495.xlsx

<Product name> - Sprint <#>


Sprint Dates: <Month> <DD> - <Month> <DD>, <YYYY>
Available working hours in the sprint Days in sprint: 9
Sprint Goal M Tu W Th F M T W Th F Total
<DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD>
Demonstrate the ability to <sprint goal>. (NOTE: Define a sprint goal in terms of working customer functionality Sprint Planning Sprint Review +
Retrospective
you will be able to demonstrate to internal stakeholders and possibly release to the marketplace.) Developers
<Developer name> 2 6 6 6 6 6 6 6 6 2 52
<Developer name> 2 6 6 6 6 6 6 6 6 2 52
<Developer name> 2 6 6 6 6 6 6 6 6 2 52
Burndown: Hours & Points Remaining <Developer name> 2 6 6 6 6 6 6 6 6 2 52
300 20 <Developer name> 2 6 6 6 6 6 6 6 6 2 52
Total sprint hours: 260
18
Total per day: 29
Estimated Hrs Remaining

250

Story Points Remaining


16
14
200
12
150 10
8
100
6
4
50
2
0 0
1 2 3 4 5 6 7 8 9 10 Actual
Plan
Day of Sprint Story
Points

Feature Burndown - Based on estimated hours remaining


M Tu W Th F M T W Th F
Task Type Story Responsible <DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD> <DD> Done Accepted
Sprint Planning Sprint Review +
Points Retrospective (Y) (Y/N)
<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 8 Developer name 8 8 8 8 8 8 8 8 8 8
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 5 Developer name 5 5 5 5 5 5 5 5 5 5
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 3 Developer name 3 3 3 3 3 3 3 3 3 3
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 2 Developer name 2 2 2 2 2 2 2 2 2 2
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 1 Developer name 1 1 1 1 1 1 1 1 1 1
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
Page 15 of 18
478202495.xlsx
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

Actual Hrs Remaining 240 240 240 240 240 240 240 240 240 240
Schedule Hrs Remaining 260 231 202 173 144 116 87 58 29 0
Story Points Remaining 19 19 19 19 19 19 19 19 19 19
Day: 1 2 3 4 5 6 7 8 9 10
Issues
Team Member
<issue>

Team Member
<issue>
<issue>

Page 16 of 18

You might also like