Unfortunately it’s not a scalable template. To create a 20 day sprint backlog template you’d need to update all of the burndowns etc. I’ll see if I can find some time over the next couple of weeks to make a 20 day sprint template for you!

Subscribe to my RSS feed if you haven’t already so that you will be notified once it’s up.

Thanks,

Tara

I am using scalc in open office what am I missing ?….

thanks
Mark

In this instance, the ten categories drive the ten category-level burndown charts – hence why they’re limited to ten (although we rarely use more than 4 in a particular sprint).

I actually use the ‘category’ field to differentiate between products and/or product owners. I could also imagine using them to track progress against objectives.

Feel free to insert additional columns if you would like to add another level(s) of hierarchy e.g epic, project, theme etc… – we do.

Thanks,

Tara

What confuses me is the ‘CATEGORY’ item I find on the product backlog template.

It seems to be a way to group related user stories. But how are they grouped: should that be by Epic, and is there a reason to allow just 10 Epics.

Should I group by Theme, but then, how do I releate Themes to Epics?

Or are Categories more like different products, or eventualy sub-products?

Thanks for all eventual comments.

Ed

During the sprint meeting, the user stories with the highest priorities are divided into tasks, and the are put in the sprint backlog. Is the ‘CATEGORY’ in the The c e
But I thought that at after the sprint meeting, all that should remain are user stories. Are the categories remainingninhe mpi ThemsIwould like tu use a good idean idea about spri am confused about the notion ‘category’ on your