Scrum with Asana
This post is actually an update of this other I published back in August 2016. Almost a year and a half after, I continue using and recommending Asana to manage tasks in Scrum projects, but I’ve got some new habits I’d like to share today:
- Now I prefer to use Organizations, better than Workspaces. In an organization, members are invited with their corporate email address –not Gmail, for instance–. Inside an organization you have teams (you don’t say workspaces). I prefer organizations for these reasons: 1) I think I give a more professional image in front of customers and third parties; 2) I can move projects from one team to another; 3) I manage in one place all my tasks and notifications coming from all teams I belong to; and 4) I can invite an unlimited number of guests –limited access members– not having the corporate email domain –Asana is not allowing unlimited guests in workspaces anymore: each guest now counts towards the limit of 15–.
- I’ve upgraded to premium plan some teams, so that I can have unlimited dashboards, I can add custom fields –to set user story sizes, pending hours for tasks, issue states, etc.–, I can also limit some guests’ access so that they are only able to make comments, I can have project templates, etc.
- I’ve validated a way of organizing Scrum projects. Basically it consists on using 5 projects –related tasks–. Task management tasks use the term project as a synonym for “related tasks list”, this is not the concept of “project” we use in professional project management.
For each of my projects, I use these 5 lists of tasks:
- One list for sharing notes on project management.
- One list for the product backlog.
- One list for each release backlog.
- One list for each sprint.
- One list for defect tracking.
In order to show all this in a practical way, I’ve prepared this video following again the Havannah case study. I hope it can be useful –in Spanish, 33 minutes–
Click here to see the presentation with my summary of the Havannah project.
Click here to download the Excel file for the release plan.
Click here to download the Excel file to draw burndown charts.