[alexboots]

I work on projects on a pretty small scale (5 website, 1 or 2 of them need changes at a time -- some of them have 30 tickets, some have 3 or 4) and trello is perfect for me. If I fullscreen it I can get a good 'at a glance' look at everything i'm working on, and I have a colour code I use on labels to set the importance on projects.

I feel like trello has a certain tipping point for tickets :: at a certain point, its causes inefficiency. That being said, I felt pivotal tracker to be a bit lumbersome for my needs. I had to think too much / navigate the ticketing system.

I'd like to ask people who have used pivotal what thought think of it?

I haven't used Asana, but will check it out.

[davewasthere]

Been using Pivotal for a few years and really love it. For Agile/Scrum software development it's close to perfect. But I'm not sure how it'd play with other scenarios.

My major plus points for it is how it automagically calculates velocity and adjusts the following user story schedule accordingly. I'm not a big fan of the right-to-left panel layout, but it's not a deal breaker. It makes my life easier, which is what I want in a software package.

I love the design of Trello and could possibly move to that, but I'd miss the scheduling/velocity/estimating features. Also, some projects have a ton of stories and feel that Trello would be unwieldy. I have used Trello for personal to-do list type stuff though.