Welcome to AgileShout

Question

1

Does anyone specifically use a tool for agile processes? Currently we use a software package called Axosoft. It gets us some nice features like burndowns, velocity, and sprint planning. However we find it more of a burden to use than a simple taskboard made of cork and tacks. It's just too big and complex for our needs.

Does anyone else use a tool like this? If so, what is it and what have been your experiences?

flag	asked Nov 3 at 21:47 John Merriwether 285●7

Jimmy Bosse · Accepted Answer · 2009-12-17 12:54:42Z UTC

You need to adapt to both your team and your business owner. We have tried several different system. I like Target Process, especially the new Kanban board, but for my current business owner, the physical task board works best and we have greatly increased our productivity since switching to it. the key is to sit down every iteration, sprint, or other predefined amount of time and discuss making small changes to enhance your process. Don't make too many at once, and make sure you go back to review if it is working. This is how we found out that the physical board works best with our environment. Adapting to your environment is the essence of Agile.

Ilja Preuß · Answer 2 · 2009-11-11 12:38:12Z UTC

1

I have condensed my current thinking on Agile Planning tools in a recent blog post

Conclusion: no current software can beat index cards for collocated teams.

answered Nov 11 at 12:38

Ilja Preuß
106●1

Brenden McGlinchey · Answer 3 · 2009-11-20 16:03:54Z UTC

Tools can be extremely helpful for teams that have individuals in geographically disparate locations and for larger enterprises with large volumes of requirements. They can also help to quickly build the metrics and graphs necessary to give feedback to the team and management about flow, progress, and impediments. Simplicity is key.

We find that starting teams with physical cards backed up with a simple spreadsheet is the best way to keep organizations focused on their thinking and on improving their process - rather than implementing rules around a tool. After a few iterations the teams can investigate and choose a tool that meets their needs and adds value.

Improperly used, tools can blind an organization to unhealthy behaviors. Electronic format has a tendency to encourage a large amount of requirements to build in a backlog. The physical feedback of cards in limited space has the effect of encouraging lower work-in-progress... even for business and stakeholders. Teams should not have to alter their thinking to accommodate a tool's functionality. Find a tool that is flexible enough to meet your needs and capable enough to produce output that justifies the time spent using the tool. We are partners with VersionOne and find their tool helpful for most teams.

thoughtadrian · Answer 4 · 2009-11-21 12:19:03Z UTC

Agree with Brenden - it's important to define your approach before choosing a tool that steers you in its codified direction.

Also like the criteria Ilja has layed out in his blog post.

One tool that hasn't been mentioned in this dialog is Mingle - ThoughtWorks' entrant in the agile project management space. Though I haven't used Version One, I find Mingle's flexibility to be superior to some of the other products in this space. (Full disclosure: I work for ThoughtWorks).

I do like having a physical card wall in addition to a tool. There's a visceral feel to moving a physical card that can't be duplicated in software. Also - if you have a physical card wall in a common area, it's in the team's "face" - rather than being a hideable, closeable window on the desktop.

Jonathan Cogley · Answer 5 · 2009-11-04 13:30:39Z UTC

We have used TargetProcess with some success. On one of our teams, they have abandoned software in favor of a physical taskboard. On another team, we have changed over to do backlog management on a physical board and the developer team uses the software for daily tasks while working on stories.

The priorities seem to be:

Product Owner

Big visible charts (physical) are easier than looking at software
Backlog management needs to be fast and easy

Developers

Easy integration of tasks with source code control
Almost some resistance to physical since they have to get up from their chair to move items along, check story numbers, etc. Prefer to stay electronic.

We have also looked at RallyDev in the past. Their local seminars are awesome - some very smart people - go to one if you can.

We also looked at VersionOne a few years back but didn't pursue it at the time.

Agile Process Tools

5 Answers