Process

We rage to build the machine!

Then Sage to dial it in...

Modes

• Rage
• Sage

Workflow

Our initial approach is oriented around the Invisible Suburbs GitHub Project 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 pain points 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.

• Backlog
• Design
• Ready
• Development
• Review
• Testing
• Done

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

• Design has their own processes and workflows, so this is mainly indicators about how to sync up on hand off to Development
• 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

Ready

• Purpose:
• Progression:
  • When work is picked up and started, this moves to Development
  • Cards wills only ever be self-assigned -- if you're interested in working on a card from Ready, self-assign and then move to Development once you begin working on it

Development

• What do we need to include as documentation?

Review

• Code Review
• Design Approval

Testing

• Automated
• Manual
• User

Done

ToDo

• Create descriptions for each column
• Create definition of done for each column

Issues

When is a draft converted to issue?

• Titles
• User Stories
• Links to specs
• Links to assets
• BDD Scenarios (Amos)
• Milestones
  • summoner-alpha
• Tags

Resources

• Kanban
• v3 Project Statuses - WIP for addressing each of the items in the TODO section