---
# System prepended metadata

title: Asana Etiquettes

---

# Asana Etiquettes 

Keeping the project updated in Asana(PM Tool) is very critical for planning and proper communication. This can lead to a very smooth development flow. Not following these guidelines can lead to **CHAOS**.

## Development Pipeline Stages

### Backlog (PM Moves)
Backlog holds all the future feature which we will develop but in future. These features aren't scheduled for development as of yet. 

### Upcoming Sprint (PM Moves)
Upcoming sprint has all the tickets which are coming up for development in the next weekly cycle. 

### Current Sprint (PM Moves)
Current Sprint has all the tickets which are planned and assigned to the developers for development with clear due dates. This usually happens after a sprint call. 

### In Progress (Developer Moves) 
Any ticket which is under active development goes in this stage. One ticket per developer should be present in this stage.

### PR Raised (Developer Moves) 
Once a developer has finished development on a feature and raises a PR(Pull Request) the ticket should be moved to this stage. 

### Deployed(Developer Moves) 
When a feature is fully tested after deployment by the developer they move the task to this stage.

### Accepted(PM Moves)
PM reviews the feature in `Deployed` stage and moves it to `acceepted` stage and accepts it. 
If the feature is not satisfactory PM leaves a note and moves ticket to `In Progress` stage.



## Basic asana etiquettes 

1. Configure Asana in slack. This helps get notifications right in slack when you are mentioned, assigned etc. 
2. Install Asana mobile app. app links ->[:iphone:](https://apps.apple.com/us/app/asana-mobile/id489969512) [:telephone_receiver:](https://play.google.com/store/apps/details?id=com.asana.app&hl=en_IN) 
3. We make user stories in a particular format refer this [great article](https://simpleprogrammer.com/writing-world-class-software-tickets/) on how to do it.
4. Ensure a task is properly defined and has all the scopes of the  task before you start work on it. If not then **DO ASK MANY QUESTIONS**.
5. **Always** reply to comment if you are mentioned in it. 
6. To acknowledge a comment(instruction) in asana you like a comment. 
7. Create subtasks with clear due dates. 
8. Only complete a task(main) when you move the task to `Deployed` stage.
9. Sub tasks can be completed while the feature is `in progress`. This helps the team get an idea about the progress you are making in a ticket ticket. 
10. Create UI related tasks for UI developer at the very beginning of the task planning. This helps plan the work and in the process you even dive deep in the feature. 
11. Update the status of tasks as per the task stages. Move your tickes across `in progress`, `PR Raised`, `Deployed`.

## User Story Template 

