# XXX - Priorities

# Priority

# Critical

# High

# Medium

# Low

# Status

Status helps us see what the Team is working on and what is Blocking the Team from doing their work well. If a status is blank, then is hasn't started yet.

# A - In Progress

As soon as you pick up the task, you should immediately mark it "In Progress". In Progress simply means the task has started, whether you finish it in a hour or 4 days later.

# B - Testing / Review

Once, ANY task has been accomplished, it should move to Testing / Review and reassigned. This allows for checks and balances to assure that someone else is seeing your work. When you mark the task into Testing / Review, please add a comment for the new assignee about what to Review.

# C Out for Approval

This typically means that we are waiting on the Client to Review and Approve this task. Either the Client, if active in Asana, or the AM / PM will mark the task complete once it's approved.

# D - Complete

This means that someone other than the original assignee has reviewed the task, and the client has approved the task is done accordingly.

# Correction Required

If the PM / AM or the client, anywhere in the process decides that the task was not accomplished correctly. Comments should be to instruct the assignee of what changes should be made. The task should be reassigned to the original Assignee. Once the original assignee, receives the task and understands the request, the process should start back over at "In Progress".

# Blocked / On Hold

1. Client told us to hold off
2. we need to regroup for a change in direction (design or otherwise)
3. The task was started but blocked by someone else, ie the PM needs to test or something

• Situation 1. AM or PM hears from client, and decide to pause the direction of the task or project
• Situation 2. Assignee changes the status to "Blocked / On Hold" because it's dependent on some other task, in which case the Task should be marked dependent on the appropriate task.

If a task is marked "Blocked / On Hold", the task should be de-assigned from whomever and the appropriate Bezar Responsible task created. For example: Follow up with X, Get Approval for X, Meet with X to discuss

# Need More Information

If a PM or Assignee doesn't fully understand the task, or it's too general of a request, mark the task as "Need More Information" with a comment of what you don't understand about it. Bring this up in the next Daily Stand up or Sprint Planning Meeting.

# Size

# 1 - Simple Task

You have absolutely no questions about the task. Understand what is to be expected. Shouldn't take more than 2-3 hrs.

# 3 - Medium Task

You know what to do, maybe have a question or two, but waiting for the answer doesn't stop you from doing what you think is right. Shouldn't take you more than 5 - 8 hrs.

# 5 - Large Task

Same as "3", but may be nice to break it down to simpler tasks, though not needed. Shouldn't take more than 5 days (est. < 25hrs.)

# 8 - Huge Task

Anything that can't be done in a week or is too general of a task, should be marked 8. These tasks need to be broken down into more manageable tasks. Tasks that are Sized as 8 should be reassigned to PM with a comment of why you feel it's an 8. 8s will also me moved to Timeline by the PM and broken down.

# Sprint

• Current
• Up Next - Ready to Schedule
• To Finalize - Not fully fleshed out
• Later - Ideas, Icebox, Someday