When I start a Scrum Project, the first thing I do is to create a new workspace in Asana named after the project. Then I invite team members to join (usually no more than 9) and some business representatives (no more than 4). In order to reach more stakeholders and keep communication fluent among the team and between team and business people, I create a private channel in Slack.
In Asana I start creating these 6 public projects:
- PROJECT MANAGEMENT: For tasks regarding up front planning, reference notes, documentation links, etc.
- BACKLOG: For the tasks representing product backlog items (user stories and epics).
- REL1: First Release Backlog items (user stories and epics).
- SPR1.1: First Sprint Backlog for the first release (technical tasks).
- SPR1.2: Second Sprint Backlog for the first release.
- REL2: Second Release Backlog list is convenient when moving stories from release #1.
Product Owner is supposed to manage the backlog and the releases lists. Team members are supposed to manage sprint lists.
Now let's see step by step how to use Asana on some key points during the agile project lifecycle.




