---
# System prepended metadata

title: v3 Project Statuses/Kanban Stages
tags: [' project management', v3]

---

---
tags: v3, project management
---

# v3 Project Statuses/Kanban Stages

**Purpose:** Started writing this in the [Linear Process Overview](/fVljK-opQymCqqSrFDHbSw) and wanted to bring into a more generalized document since this applies to both Linear and GitHub Projects

Our initial approach is oriented around the [Invisible Suburbs GitHub Project](https://github.com/orgs/HausDAO/projects/3/views/1) Kanban view and the associated issues that can be created/connected to repos in our DAOhaus GitHub organization.

We intend to start with this approach and refine and iterate and see if we experience any painpoints that a more involved tool such as Linear can solve. We want to meet folks where they're used to working and limit the amount of friction as we're setting up new processes.

## Project Statuses

- Issues flow through different status stages
    - **Backlog -> Design -> Ready -> Development -> Review -> Testing -> Done/Cancelled**
- **Backlog**
   - Purpose:
        - Issues start here and detail is gradually added as it's available
        - These can be bugs, feature requests, general ideas, etc.
    - Progression:
        - Moves when it's decided that the team should work on these
        - If design is already available (or it doesn't need design) -> **Spec**
        - If it needs design and there aren't already design files -> **Design**
            - Not all issues may require design, so some may move into **Spec** right away
- **Design**
    - Purpose:
        - Issues here require design work such as Figma wireframes
        - Examples: UX/UI designs for specific features, UI mockups for specific components
        - Design team will largely work within these issues and own the processes around managing this work and handoff
        - Design team may have an internal process for estimating and scoping, and would add these estimates to the effort level/issue details
    - Progression:
        - Once there is a Figma design associated with the issue, this moves into **Spec**
        - Design team can decide if they want their work to also move to **In Progress**
- **Spec** (we don't currently have this status, so this happens before **Ready**
    - Purpose:
        - Issues here are ready to be specced/scoped for development work
        - Suggested to follow a specific template for this -- ensuring that there are clear details and a rough estimate of the work 
        - Add clear deliverables and break out any sub-tasks if this is a larger issue
    - Progression:
        - Once all the details are added, this moves to **Ready**
- **Ready**
    - Purpose:
    - Progression:
        - When work is picked up and started, this moves to **In Progress**
    - 