Our Development Workflow on Trello
Every product has a board
This might sound like an obvious one, but when you have as many products on the go as we do, its important to make sure you can quickly get an overview of the state of a project at a glance. So by having each of our products in separate boards, we can easily see not only where each project is at, but also what has been happening to it recently.
Bugs, Features and Resources
Every board we have has at least three global lists: Bugs, Features and Resources. We don’t use an external bug tracker so any bug that get reported to us go on the “Bugs” list. Similarly the “Features” board is where we keep track of any features that we want to add to a project. “Resources” is more of a generic list of stuff that may contain things like setup guides, deployment guides, marketing plans etc. Basically any (small) internal documentation goes in here.
We use Trello’s labels to signify the status of a card. We generally just use green, yellow and orange (orange = in progress, yellow = testing, green = complete). This gives us an easy way to see the exact status of each card in our lists. This is maybe a different approach to others as most people I’ve seen use lists to separate card statuses. But this works for us.
Assignment and Archiving
We operate a simple system where, if you have started working on a card, you assign yourself to that card. Once you have finished working on that card you can un-assign yourself from the card. If you are passing the card on, to someone else to test for example, you can assign them to the card and update the label as required. Once a card is completed and has been deployed, the project leader can archive the card. This keeps the board clean and organised.