Why use Excel to track Scrum and why this template?
There are smaller teams that rely on part-time developers who don’t want overhead
Small teams may discuss on “stuff” and move on with work, and don’t particularly care about documenting everything
Simple projects may not have the budget to organise things
And yes, I know that these are excuses for not creating a “usable” tool. But organisations continue to live in a bubble.

So, here we are.

Using this template you can

• track projects and sprints
• track backlog, impediments and retrospective remarks
• record effort against tasks (which can relate back to backlog)
• summarise effort and show beautiful charts

There are no fancy formulae, macros, and automation to take the dog on a walk when you work.

All that said, I think no one should use Excel templates for use cases like this. But I really can’t quite preach something else when I have been an ardent fan of their simplicity.