Projects

Breaking the pipeline down into concrete manageable projects helps keep us on task and aids prioritisation of development of specific pipeline components above others. Projects are managed via the repo's project boards. Project boards can't be assigned to specific milestones (only issues can), so we can simple prefix the project names with the name of the milestones we wish to assign them to, e.g. 02. DESIGN: FITS Keywords. We can change the prefix as projects progress from design to implementation etc.

Individual issues/tasks can be assigned to projects and by default will start in the ≣ queued column. During our scheduled reviews we can move tasks into the ⥅ up next and ► in progress columns. Once tasks are closed they automatically move to the ↺ review column. We check these tasks during the scheduled review, determine if any associated followup tasks need scheduled or documentation needs written/updated. Finally tasks are moved into the ☑︎done column.