The backlog project should be a list of all feature development for the website, this can range from small tasks (a few hours work) to large projects (called EPICs).
The project should have the following sections:
- Done: Tasks that are complete and live on the website
- In Review: Tasks that are on staging / uat for testing
- In Progress: Tasks that are currently being worked on
- Backlog: Tasks that have not been started yet
Task naming convention
[Estimate] <client initials> // <area / sub project> // <task description>
- Estimate: every task should be estimated by the team who will work on the task, all tasks should be estimated in hour used the fibonacci sequence: 1,2,3,5,8,13,21,34,55,89,144
- Client Initials: this is required so we can identify the client in the company weekly sprint board eg SFC (its always in CAPS) for Shoes For Crews
- Area / Sub Project: the grouping for the task eg. CHECKOUT (usually in CAPS)
- Task Description: A short description of the task eg. "Implement Address Lookup"
Scoping small / medium / large tasks
All the tasks should also be documented in the Help Center for the client so we can refer back to it, the hep center documentation should be started when the project is signed off and updated throughout the project
- Outlined in a single task
- There should be enough detail to allow any developer (or anyone) to see the task and understand the issue we are trying to solve, the suggested approach and detail of how the task should be completed.
- A single task should not have an estimate of over 21, if over this is needs to be split into multiple tasks.
- Outlined in a few tasks in the backlog,and grouped together using the Area / Sub Project
- Any more than 5 tasks should be moved to an EPIC or Large task with it's own project
Epic's and Large tasks
- Outlined in a separate project in asana
- One task in the Backlog should link to the project
- The project for the Epic should have the sections:
- In Review
- In Progress
- To Do
Example in the backlog:
And the project: