About

Accounts

You are at the newest post.Click here
to check if anything new just came in.

17:46

Pivotal Tracker. It lasts for a long time, until the product outgrows it. As long as the team is small and lean, you won't have any issues, though.

What I definitely NOT recommend:* Trac: Does the job, but the UX is terrible. Over-configuration quite likely, especially for small teams.* Redmine: Same as Trac, but in Ruby instead of Python.* JIRA: Once you join the dark side, there's no going back.* Virtually every TODO SaaS: It doesn't work out. Things go stale. You'd have to do a pretty awesome job at onboarding the team to get it working. It's just too vague. Some I've tried and failed with are Wunderlist, Trello and Basecamp.

Generally:* If your team is fully distributed, most of the tools I don't recommend might work, because they could be set up as the primary channel of communication. Once it has become the main way to communicate, it will work out, because all information is in one place, and the overhead of the tool can't be navigated around by means of personal communication.* If the whole team is on site, just use damn post-it notes. It doesn't get any leaner. If you need a tool in addition to post-it notes, make sure to keep both in sync, or at least define the single source of truth.* It's tempting for an engineer to create a really intricate workflow that covers all the bases. This will only tie you down in bureaucracy in reality. Spent as little time as possible on workflows, and let people improvise for edge cases. I presume you work with intelligent humans - they'll to the responsible thing.* Define a single source of truth. The issue tracker should have precedence over coffee maker conversations, and coffee maker conversations that are actually relevant should be recorded in the issue tracker. If you look back at an issue in a year, you won't remember every decision you made in a conversation. Document the shit out of stuff.