GitHub Boards (Kanban) [DELETE]

Columns

The following columns are used to define each stage of our delivery process. You need to be familiar with these when using the board as you will be expected to move around your own tasks and update them for others:

Notes

A place for guidance and general notes. Important notes here include the estimated Sprint hours and a guide to how to use the board.

New Items

Anything new lives here. This should be a short-lived column with items quickly being moved to other columns in the Daily Standup or during a project kick-off meeting.

Backlog

A place for all tasks to exist before being picked up. The Backlog is reviewed at the end of each Sprint (week).

Sprint Backlog

The planned work for this Sprint. All tasks should be fully fleshed out, estimated and have the correct labels by the time they reach this column.

When an item is in Sprint Backlog and is not already assigned it becomes ‘fair game’ and can be picked up by any of the team Engineers to progress.

In Progress

Work that is currently in progress lives here. When an item is in this column it must be assigned, estimated and be actually ‘active’ otherwise it should move back to the Sprint Backlog or worst case the Backlog.

Code Review

At this point, the related pull request should replace the issue on the board (issue should be closed) and be moved into this column when code has been committed to the Development Environment (with test data), and testing instructions have been written.

QA

For pull requests that are in undergoing INTERNAL testing. If QA fails then pull requests will naturally be moved back to In Progress for further work to be assigned and carried out.

Good To Go

Pull requests move here when Code is on Staging Environment (with test data), and testing instructions have been updated for review by non-technical. Successful pull requests should, merged, deployed and then moved to ‘Done’.

Done (Date/Quarter)

All completed work and closed issues/pull requests are eventually moved to a Done list. We name ‘Done’ lists based on the current yearly quarter (Q1, Q2, etc) to better keep track on what work has been achieved over a quarterly period.

Use of Labels

Labels are a very important part of the board and should be used on all active tickets, both non-technical and technical cards should use labels (see code / admin).

See here for a list of the labels and their uses.

Automation

Board currently has the most basic level of automation rules, see below:

 

1. When an pull request is closed it is moved to ‘Done’

2. When a new issue is created in any linked repo it is moved to ‘New Items’

3. When a pull request is marked as needing a code review it is moved to ‘Code Review’.

4. When a pull request passes code review it is moved to ‘QA’.

5. When issues or pull requests are re-opened, they are moved to ‘Backlog’