[pmontra]

The functionality is there. You can label cards with people and set a due date. There are free plugins that allow to set a time estimate on the cards and compute the total for a column.

Still, I don't think I want to use Trello on my projects (I use it in some projects for customers). I can't articulate well the reasons but the general feeling is that if the project is not trivial you start having too many cards and the columns get too long and you start losing stuff. It's not for long living projects, where you need to store information that let you tell who decided what and why two years ago. It's better suited for short bursts of activity and to dispatch tasks to executors. Probably one project manager to assign tasks and developers to report on their accomplishment. It could be a good tool for that.

As an example of what it shouldn't be used for: bug tracking. We are creating cards for bugs on a project but Trello cards are not well suited for that, neither to input bug reports nor for managing them. To be fair, I bet that Trello didn't design for this use case. That someone is using it for this maybe means that it's appreciated beyond its limits.