[namityadav]

Maybe this is a good place to ask this question: We are considering using Trello for our startup. But we are concerned that when we have a lot of items in a board or list, then the card representation of tasks will make it harder to scan them (compared to the lists that Asana uses). Also, traversing through a lot of tasks in a list is easy in Asana: You just keep pressing the down arrow in the list, and the right side will keep showing you more details about each task. How do we do the same thing in Trello?

[mhp]

I'm assuming you are thinking of using Trello as a bug tracking app? We purposefully did not design Trello to be used that way, even though a lot of people do, so it might fall down when you go that route. It is not a replacement for a bug tracking application. There are plenty of those out there (FogBugz, Jira, Pivotal) and there are even kanban type programs like Trello for software development (AgileZen, LeanKit, Sprintly).

Trello is designed for a high level overview of a project. So if you start to get too many items on your board, either it's not the right tool for what you are trying to do, or you need to think more about what you are adding to Trello. For example, you could use Excel to take notes, or make a todo list, but it's not the right tool for that. Trello really shines when you are using it for group collaboration and either focusing on a high level (and leaving the details to something else) or only focusing on the very top level important details.

I know a lot of companies that use Trello in tandem with tracking apps. There's even a nice bookmarklet that integrates with a bunch of them (FogBugz, Jira, Github, Saleforce) so you can hit one button and turn your case into a card in Trello. See https://github.com/danlec/Trello-Bookmarklet But don't make the mistake of trying to duplicate what those programs do in Trello.

[Nagyman]

I work at a medium sized business and we're having little trouble adopting Trello. It's been about 8 months since we started, and other departments have also adopted it for their own projects. Once introduced, they love it. It's a great way for everybody within the company to have visibility of what others are doing.

We meet regularly with other departments to triage their request queue (list) and move it forward. It's great for them to see the software process and see their request in context with the (many) other requests.

We often break out separate project boards and link to it from a master (planning) board. That really helps break down the larger tasks.

mhp noted that it's not designed for bugs, but we have no problem using it for that, in conjunction with some GitHub issue tracking.

I'm certain a startup would have no issues adopting it into a great workflow.

[mneumegen]

If you have that many tasks you probably want to use something like Fogbugz. What I like about Trello is it forces you to keep you task lists relatively short (The way I think it should be).

[ohwp]

Maybe you could take a look at YouTrack: http://www.jetbrains.com/youtrack/ (compare the Agile board)

I think Trello looks nice(r), but it's easy to create a mess with it.