4 ms·

We use Trello at work. We use it as a ticketing system/issue tracker, to-do list, and workflow system. I think it is great as far as it goes. It's got a great v

We use Trello at work. We use it as a ticketing system/issue tracker, to-do list, and workflow system. I think it is great as far as it goes. It's got a great visual design, it's very simple and free-form. Frankly however it forces too many decisions on me. I don't want to have to think about all the things that you're required to think about. It's a bit too free-form. Tickets and issues and all that isn't something I want to dedicate a bunch of time to; I just want something on rails that has already made smart default decisions about workflow out of the box, then allow me to tweak it from there. Again, maybe it's a function of how we use Trello. But even the fact that it's basically unstructured is a negative to me. Give me something with smart defaults out of the box so that there is a workflow clearly delineated, and we don't have to invent our own on the fly.

alexboots 14y ago
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 14y ago
  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.
goblin89 14y ago
Trello and Asana both are pretty generic and seem to refrain from enforcing any particular use case through UI. I also found this genericness hard at first, especially having used FogBugz and other “traditional” PM / ticket tracking tools that do all the decisions for you. However, I seem to be stopping caring too much about creating “proper” cards (we use Trello as well), adopting the “create a card with whatever is on your mind if you feel there's a need for it”-like approach. I like it, and it's fast, maybe it'll will work for you, too? Of course, some things still have to be considered before creating the card—e.g., task atomicity—but that's the case with any tool. It depends on your workplace and workflow, though. If there's a certain degree of formality there, I think it's much better to have this enforced by UI, because then decision making is likely to become a real problem.

alexboots 14y ago

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 14y ago
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.

goblin89 14y ago

Trello and Asana both are pretty generic and seem to refrain from enforcing any particular use case through UI. I also found this genericness hard at first, especially having used FogBugz and other “traditional” PM / ticket tracking tools that do all the decisions for you. However, I seem to be stopping caring too much about creating “proper” cards (we use Trello as well), adopting the “create a card with whatever is on your mind if you feel there's a need for it”-like approach. I like it, and it's fast, maybe it'll will work for you, too? Of course, some things still have to be considered before creating the card—e.g., task atomicity—but that's the case with any tool. It depends on your workplace and workflow, though. If there's a certain degree of formality there, I think it's much better to have this enforced by UI, because then decision making is likely to become a real problem.