| We also use Asana and Kanban. However we have a simplified use in Asana. I've found that you have too many projects and places where to look. We have one project called Kanban board, with all the features for web, iPhone and Android app (8 people use it). This board has several headers: * To Production
-> All tasks that are ready to be deployed * To Test - Second test (5)
-> All tasks that have to be tested a second time * To Test - First test (15)
-> All tasks that need to be tested * Development - Finished (10)
-> All tasks that have been comitted, but haven't been deployed to the alpha sever/app. * Development - Working (7)
-> All tasks that developers/designers are working on. * Pending - Bugs
-> All tasks that need to be fixed. * Pending - Analysis
-> All tasks that need to be analyzed (improve description, break them into subtasks) * Pending - New (20)
-> All tasks that need to be done * Backlog
-> All future tasks / features / suggestions We use projects to indicate if the task is for web, iPhone or Android; and tags if it's urgent. There can not be more tasks that the number between parenthesis. If there are 12 in Finished for example, we know we have to deploy to the alpha server/app. |
My feeling is that it's maybe more important which states and principles one has and that everyone understands them than whether they reside in one or four projects. Personally, I think it's a bit easier to focus if I only have to look at the stuff that is relevant at the moment, but I see where you're coming from.
How did you chose the number of slots: 5, 15, 10, 7 and 20?