With my team I use two products: Pivotal Tracker and Trello. Pivotal is great for development projects. It talks to Github and Campfire, allows us to visually

With my team I use two products: Pivotal Tracker and Trello. Pivotal is great for development projects. It talks to Github and Campfire, allows us to visually plan things, and has a great worfklow built in for moving stories through the development process. That said, it's not really well suited for either a) non-development projects such as system upgrades, server builds, research projects, etc or b) a steady stream of one-off fixes and tasks that don't tie back to a larger development effort. Small enhancements, bug fixes, infrastructure work, and the like. I originally tried to squeeze all this into Pivotal but it's sort of a square peg/round hole scenario. Trello, on the other hand, is great for all the other "stuff" my team has to do. I can have one board that shows me at a glance what everyone is working on (we put placeholder cards in Trello for projects that are being managed in Pivota - there's usually only one or two at any given time). It's very flexible and adapts well for various types of work. In a pinch, I could replace Pivotal with Trello, but I would lose out on all of the integrations with Github and Campfire, as well as the more structured story card format and the agile workflow. Combining the two gives us the best of both worlds.