Scrum backlog excel templates [closed]

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 9 years ago.

Improve this question

I开发者_如何学编程'd like to try scrum with my team. Studied a lot of posts about scrum tools here, but i think it's all superfluous and excel file is ok for product and sprint backlog. But it's problem to fing a good template. Maybe somebody could share excel template he is using for scrum backlog? Thanks.

---

Excel is really an extremely powerful tool and is very appropriate for the product backlog (and it has my preference if suitable: just share the product backlog on a network drive and there you go). I have used the following templates successfully in the past:

• Henrik Kniberg's Index Card Generator and a wall for the sprint backlog
• Petri Heiramo's advanced product and sprint backlog template (video tutorial here)

You can browse my personal collection for more of them but I recommend the two above.

---

Don't have any templates, but what tool you use for scrum is indeed whatever works for you, so excel could be just as good as any other. Just so long as it's quick and easy for all to use.

I was taught scrum techniques using physical props. Sticky notes and meeting drawing boards. The idea is you use that for a while, and then see if you can fit it into technology after if it doesn't hinder the scrum process.

I'd just try and knock up an excel template that fits for you, starting from a blank worksheet and just build up whatever seems to work.

Though for backlogs it may be better to have a tool that manages it if you are going to have a lot of items, and especially if you will have many stakeholders inputting into it. Maybe a bug tracking kind of tool. Plenty of good open sources ones about. Don't know how they fit into scrum, but always thought the likes of bugzilla could work but haven't tried it.

---

I'll say it is a good idea to start for a couple of sprints on paper.

It will let you understand the process before having to fight against the difficulties in using the software tool.

On the other hand, scrum can be used for projects of different nature, and not in all cases will have computers available.