Task tracking tool evaluations

From Deep Blue Robotics Wiki
Revision as of 02:34, 9 October 2016 by DBrettle (Talk | contribs)

Jump to: navigation, search
Tool Task board Mobile support Cost Task dependencies Task groups Slack integration Open source
Kyber.me No Yes Free No Yes. Via slack channels. Yes No
Taiga.io Free for public projects
Drupal's PM plugin
PHProjekt
BugGenie
Asana No. Per user pricing. Declined to allow us to use the Asana for Students program.
Teamweek Would need to investigate non-profit discount
PivotalTracker Free for public projects

Task board

The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a kanban board) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".

Mobile Support

It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).

Cost

Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.

Task Dependencies

Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.

Task Groups

The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.

The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.

Slack Integration

The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.

Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.

Open source

The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.