Scrum-y Tools

As a QA Professional, I’m always looking to be in the know about tools and techniques companies use to deliver software.  I’ve worked in companies that have used Waterfall, Agile, and a mix and match of everything in between. With that, I’ve been exposed to a variety of tools to track testing and Scrum project progress.

It’s almost a given that everyone has a grip on the tools they’re using.  However, no matter what company and tool, sometimes the tools just don’t quite fit what we are looking for.  Below are three tools that I’ve worked with and a quick highlight of the pros and cons of each.

 

 

 

JIRA:

http://www.atlassian.com/software/jira/overview

So far, the tool I’ve used the most is JIRA.  JIRA tracks bugs, tasks, and other issues and comes with a set of reports for upper management.  JIRA is especially useful for tracking medium to complex projects, but may be overkill for organizations that handle smaller projects.  The Greenhopper add-on is especially useful for Agile Project Management.

Pros: The drag and drop functionality for tickets is handy, easy to pull stats from for reporting, very visual interface.

Cons: It can be quite costly to use JIRA depending on the number of users. All web-based; therefore, access to information is dependent on the internet (or internal connectivity).

on-time Scrum-y ToolsOnTime:

http://www.axosoft.com/

Axosoft’s OnTime is great for organizations where client feedback drives the product backlog.  Because OnTime is so customizable, it’s best for the organization to have their internal SDLC process in place before trying to implement this tool; otherwise, it can get hairy trying to put the pieces together while configuring OnTime.

Pros: Client issues can easily be ported into defect tickets, can define work flows to move tickets from different departments, intuitive to use.

Cons: Unable to add inline attachments to tickets, web interface has less functionality than the downloadable client.

Redmine Scrum-y ToolsRedmine:

http://www.redmine.org/

Organizations that have plenty of different projects on the go can use Redmine to track issues, tickets, and time spent on each task.  Redmine can also act as your company’s central repository for documents and other project artifacts.

Pros: being able to move tickets from project to project, facilitates team collaboration and easily searchable.

Cons: UI is not as intuitive as other tools, needs more built in reports and dashboards.

What tools have you used to track projects and what do you like/not like about it?