Business Analysis Templates & Aides


Recent Templates | Categories | Search | Subscribe (RSS)

Product Backlog Template

Product Backlog Template
Statistics: 12062 Views // 8 Comments // Article Rating
Posted by: sumit.soni on Monday, April 18, 2016

I have created Product Backlog Template, which is attached here.  As, i am new to Agile, i want you guyz to go through it and let me know what additions/changes i should do in it.

Features include: Product Backlog, Sprints Backlog, Product Burndown Chart, User Stories

 

DOWNLOAD: You must be logged-on in order to download templates.

COMMENTS

Sbarnes posted on Thursday, November 10, 2016 9:09 AM
Can someone please provide a summary of how this template works.

Thank You
Joan01 posted on Tuesday, March 7, 2017 7:37 AM
Hi,
Can not open the PDF

Thanks
cedric01 posted on Tuesday, February 6, 2018 11:00 AM
Hi, Thanks for the template ; would some one tell me how do you estimate the Story Point ?
b700@hotmail.co.uk posted on Friday, February 9, 2018 6:36 PM
Get the team into an estimation session, go though each story and ask each member to give a score based on complexity from 1 to 13 (1,2,3,5,8,13). Facilitate discussions between the highest and the lowest score holders to deduce their rationales and redo the activity and see the difference. Check it out on YouTube too, I haven't checked but I'm sure you'll find something.
cedric01 posted on Monday, February 12, 2018 3:46 AM
Thanks for your advises, It will help !
sumit.soni posted on Thursday, April 26, 2018 1:24 AM
Thanks Everyone who liked and contributing more ideas to the template that i developed. :)

For any further questions, you can reach me on sumit2111988@gmail.com
viniciustreichl posted on Friday, August 16, 2019 10:15 AM
Perfect Template, thanks very much for share.
hrawal posted on Monday, September 30, 2019 5:54 PM
Would be really effective is there was some VBA that could take the Sprints, Stories and Estimates and populate the sprint sheets as they are assigned/estimated to see how the sprints are taking shape and if they are over/under subscribed (dependent upon the development team size).

Stories may be part of a Epic (and Epic part of a Theme) so this should be included. Also needs prioritisation for the stories - MoSCoW or another prioritisation process. This will assist with Sprint planning as you can see which stories must be included so as to add value to the Sprint.

You could possibly also add the BDD elements (Acceptance criteria) i.e. Given, When, Then ...

Regards the estimation question there are a number of techniques including Fibonacci (as above), T- Shirt sizing (S, M, L, XL), Planning Poker (https://en.wikipedia.org/wiki/Planning_poker), etc. Estimation requires the involvement of the Development Team who should be experienced in developing the application and who can therefore provide estimates with some degree of confidence.

There is always JIRA of course ....

Only registered users may post comments.




Copyright 2006-2019 by Modern Analyst Media LLC