I'm trying to use Trello to keep tasks and bugs for my current startup, but it didn't scale so well - its nice for few lists and cards but not many (I might just be using it wrong, I've nevr done Scrum/Kanban etc)
If we were modeling it in Trello, our columns would be:
* backlog
* on deck
* working
* on hold
* to review
* done this week
* done previously
We also have a separate backlog for technical stuff.
As you can see by the number of cards, our 50-square-foot wall rack displays a lot more than fits on a single screen. So the medium may just not match the use; my personal Trello boards are definitely smaller.
That said, you should also consider whether you need to track less stuff. It is only worth creating a card if there's some reasonable chance that you'll actually do something with the card. It's much easier to learn to just let go of things than it is to have a 1000-item backlog slowing you down every time you try to work with it.
I also encourage people to put more time into bug reduction and less into bug management. Even though we're a startup, we are very happy we've built an extensive unit testing suite, and a more modest suite of end-to-end tests. Having tried it both ways, it's my considered opinion that if I need a database to keep track of all the mistakes I'm making, I should make fewer mistakes.
I'd even argue that trello allows for too much things to be visible on one board if you are using it to visualize your software development process.
Try to remove everything from your process board that is not relevant for the 'now' and move everything that is more vague to somewhere else (another board, spreadsheet, txt file).
I am a huge fan of getting rid of backlogs. I feel they do more harm than good, especially if the backlog manages the same entities that will later end up in your process. Usually you don't know whether it makes sense to work on something until briefly before you start doing it. So planning too far ahead is just waste (of time, nerves, decisions, …).
I also think wpietri is spot on with the recommendation to spend time on bug reduction & scope reduction to improve focus. Ideally you don't want to work on too many things at the same time which is easier said than done.
What we do is that we try to define the reason why we put something on the board. That way it is easier to re-prioritize and easier to spot low hanging fruit and things that we could drop in the meantime.
Dint scale so well ? There can be so many other reasons for that and yes you maybe right in thinking so.
And besides Trello can be put to use for so many other things as well like managing your monthly expenses , a school using it for announcements and parents receiving notifications on their device, etc.
