Project Management

This project uses ZenHub to enhance GitHub's built-in issue tracker for project management. It can be used either from the ZenHub site or through a browser extension. To use it, you'll need to approve linking your ZenHub and GitHub accounts when you log in.

The primary views we use are our Kanban board and release reports.

Issue Flow

1. New issues (bugs, feature requests, etc…) get added to bottom of the New Issues column.
2. When the team has had an opportunity to evaluate it, relevant tags will be added, an size will optionally be added based on the perceived difficulty and risk of completing, and will be placed in either tie Icebox column for ideas that we want to work on but are out of scope for the time being, or the Backlog column for work the team is ready to take on. The Backlog column is ordered with the highest priority items at the top. | Size | T-Shirt Size | Meaning | |:----:|:------------:|:--------| | 1 | XXS | Almost no difficulty or risk | | 2 | XS | A very small amount of difficulty or risk | | 3 | S | A little difficulty or risk | | 5 | M | Some difficulty or some risk | | 8 | L | Some difficulty and some risk | | 13 | XL | Difficulty or risky | | 21 | XXL | Very difficult or risky |
3. When the team has chosen an issue to start work on, it gets moved to the Todo column
4. When an issue is in progress, it gets moved to the In Progress column
5. When an issue has some work done for it and feedback is requested but it's not ready for final review, it gets moved to the Draft column
6. When an issue is ready for, and in, final review, it gets moved to the In Review column. Issues that will be resolved with code into the codebase should use ZenHub to connect their Pull Request to the issue, and not move the issue by hand
7. When an issue is resolved, either through a Pull Request or by other means, it will be moved to the Closed column