Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

How we track work

Christa Hartsock edited this page Dec 4, 2021 · 4 revisions

We have chosen to track work across two Github Projects:

  1. Pangolin Discovery
  2. Pangolin Delivery

Discovery

Discovery is where ideas are first added and research and design work happens. Work flows through the following columns in a kanban style:

To do

New ideas are added to this column by default. The column is prioritized with the next stories to be researched and/or designed are placed at the top.

In progress

  • Tasks unrelated to user stories are being worked on.
  • User research or design work is happening on user stories that need it.

Review required

Work is complete on the task, but a peer review step is required before we can consider the task to be complete.

Done / Ready for Delivery

  • Tasks unrelated to user stories have been completed, to be archived at the next demo.
  • Tasks with upcoming development work are ready to be moved to the Delivery board

Icebox

Any ideas that are good, but that we are not ready to take on can be parked in the Icebox

Delivery

The Delivery project board is where the Near team will track stories through the development, review, and deployment process.

Icebox

This is where stories first appear on the delivery board (both conceptually and automagically, thanks to our configured automation). They could be stories at any stage: engineering-proposed tasks, bugs, drafts of user stories, stories that have been written after being on the Done / Ready for Delivery column in the Discovery board, etc.

The Product Manager is responsible for reviewing these stories and deciding which are in scope for the current phase of work based on the product vision, and collaborating with the engineers to decide which user stories, chores, and bugs from the Icebox to pull into and prioritize in the Backlog.

Backlog

This is a prioritized list of stories that are ready for development and we are committing to doing in near-term land in this column. Most important ones should be at the top.

Ideally the delivery team will review these stories in prioritized order in planning at beginning of the iteration, so that everyone has a shared understanding of the work to be done.

In progress

Development work is actively happening on this story.

Review in progress

A Pull Request has been opened for this story and another engineer has been requested to review it. Stories should not stay in this column for very long.

Reviewer approved

Another engineer has approved this Pull Request, but it has not yet been merged. Stories should not stay in this column for very long.

On staging

The PR has been merged, and the changes have been deployed to the staging environment and ready for demo.