GPMD run their workflow in weekly iterations (Monday to Friday) and the workflow consists of the following activities:
- PLANNING THE WORK
- DOING THE WORK
- REVIEWING THE WORK
- RELEASING THE WORK
- REVIEWING THE PRIORITIES
PLANNING THE WORK
1. Select a task(s) that require action
The PMs and Product Owners select task(s) that require action in the coming week(s) from the client's Asana backlog, project or support queue.
2. Add task(s) to the weekly Sprint Board
Tasks and support tickets which have been prioritised for the week ahead will be added to the weekly Sprint Board found under the GPMD Internal Workspace in Asana.
Tasks are added to the weekly Sprint Board by clicking on the 'Add this task to another project' option and then selecting the relevant Sprint Board i.e Sprint Board 26-30 Nov.
Ensure the task is added to the 'To Do' section.
3. Tag task(s) against relevant resource group
Each task needs to be tagged against one of the following resource groups:
- Frontend (Developer)
- Backend (Developer)
- Solutions Expert
To add a tag, click on the menu icon (...) and select the option 'Tags'.
Then, start typing the name of the tag you wish to enter and select the relevant option from the dropdown.
4. Prioritise the tasks!
It's the responsibility of the GPMD PMs and Product Owners to prioritise the tasks in the weekly Sprint Board.
Top to bottom prioritisation. The task at the top being the first priority.
DOING THE WORK
1. Select a task & estimate it
If you are actively working on a project, chances are tasks have already been assigned to you and estimated as part of the planning session for that particular project, but if you are not working a project, or don't have any tasks assigned to you, then you must:
- Select the first task you're capable to doing from in order of priority
- Start tracking your time
- If you are able to estimate the task, estimate it, otherwise add [?] in the estimate field
2. Task(s) 'In Progress'
When you start work on a task, move it into the 'In Progress' section of the Asana board
3. Task(s) 'In Review'
When you are done working on a task, move it into the 'In Review' section of the Asana board and reassign it to the Product Owner or PM. If you're unsure whom the PM or Product Owner is, reassign the task to the person who created the task. Then, stop tracking your time.
REVIEWING THE WORK
1. QA the work
The PM or Product Owner QA's the work.
Task passes testing
If the task passes testing, mark it as complete in Asana and move to step 2.
Task doesn't pass testing
If the work doesn't past testing, it is reassigned to the developer who originally did the work and moved back into the 'In Progress' section of the Sprint Board.
2. Create a Release task
Once a task is ready for release, the PM or Product Owner does the following:
- Creates a release task in the weekly Sprint Board
- Adds it to the 'To Do' section
- Pastes the link of the task that pasted testing into the description field of the release task
- Assigns the release task to the Support Manager
RELEASING THE WORK
The Support Manager or a developer releases the work. Please note the release may not always happen in the same week. If that's the case, the release task will be move to the following week's Sprint Board.
REVIEWING THE PRIORITIES
At the end of each week, the PM's, Product Owner's and Support Manager review the outstanding tasks which didn't get completed during that given week and do the following:
Release tasks - get moved to the following week's sprint board
Tasks in 'To Do' - Decide whether to move it back to the client's 'backlog', 'projects' or 'support queue' projects or to next week's sprint board
Tasks 'In Progress' - Should be moved to the following week's sprint board into the 'In Progress' section
Tasks 'in Review' - Should be moved to the following week's sprint board into the 'To Do' section and a tag 'QA' should be added against them