Long time ago I wrote a post proposing the use of Evernote as a virtual story board. In practice, I’ve been using this method myself on some projects, and I liked it for several reasons, mainly because of the great acceptance of Evernote and also because of the higher quality of the documentation I could see at project closing, since the tool makes it easy and quick for everyone to write about user stories, personas, retrospectives, impediments, and so on. However, this method had important issues. To name a few: the Product Owner had to share her user account, reprioritizing was tough, the technical team preferred other tools to manage tasks, etc.
Now I have to say I've changed my mind: Asana is my best option. I use Asana for getting things done, interacting with students and project teams, and even for tracking my children’s homework ;-) and also for agile projects, of course. In agile projects, Asana has always been my first option for sprint backlog virtual boards, but I insisted with Evernote for the other uses. When I used Asana not for agile, I liked Asana for documentation as well. I insisted with Evernote because I could work offline, but this is not a real issue nowadays, isn't it? If I don’t have access to a network wire, then I usually have access to a Wi-Fi network; if not I can always use my mobile Wi-Fi hotspot… In conclusion: I keep a tool for everything related to task management, and this tool is Asana, I don’t need any other one.
In this post I will try to explain how to use Asana on projects under Scrum methodology. If you want to see the example I’ve prepared (as if you were the Scrum Master) then you can go to:
- user: email@example.com
- password: pmpeople