ScrumWorks (there is a free and pro version)
VersionOne (paid only)
Jira (paid only, needs plugins)
Banana Scrum is free and looks good. It was talked about on HackerNews awhile back.
After experimenting with lots of this software, my team has reverted to the whiteboard for Iteration Goals, and sticky notes for the iteration's tasks. We've found that you can't beat the tactile qualities of post-it notes.
Items in a software package can be easy to ignore if you don't manage it closely. But if you look at the whiteboard and see more sticky notes in the "pending" column than there should be, you instantly know something is wrong and can dive in.
In short, don't use a tool if you can get everybody in a co-located space -- use the walls. Hard to ignore big flashing lights that say the build is broken or large burn-down charts that show the iteration is off the rails.
But if you can't get all co-located, or if you're forced to have a team that's too large, or if your Product Owner is actually a committee of seven, etc -- there are good reasons for using some kind of tool on occasion.
Comments
I have had some success with:
ScrumWorks (there is a free and pro version) VersionOne (paid only) Jira (paid only, needs plugins)
Banana Scrum is free and looks good. It was talked about on HackerNews awhile back.
After experimenting with lots of this software, my team has reverted to the whiteboard for Iteration Goals, and sticky notes for the iteration's tasks. We've found that you can't beat the tactile qualities of post-it notes.
Items in a software package can be easy to ignore if you don't manage it closely. But if you look at the whiteboard and see more sticky notes in the "pending" column than there should be, you instantly know something is wrong and can dive in.
I'd like to second these thoughts.
In short, don't use a tool if you can get everybody in a co-located space -- use the walls. Hard to ignore big flashing lights that say the build is broken or large burn-down charts that show the iteration is off the rails.
But if you can't get all co-located, or if you're forced to have a team that's too large, or if your Product Owner is actually a committee of seven, etc -- there are good reasons for using some kind of tool on occasion.