Product Backlog
For this project we are maintaining the Product Backlog via Github Issues and Projects Kanban. The two are linked so that changes in one should be reflected in the other.
The Story Score and Risk Level are primarily viewable as Tags attached to an issue. Note that the Max Story Score is 8, anything higher should be broken down into smaller components.
Issues are added as we are made aware of them, or as requirements are discovered.
In the Projects Kanban, issues are organized in the To-Do section such that the top 5-10 issues are the next immediate priority. Do note that re-prioritization will likely need to occur every 5-10 issues that are taken up and moved into a later step. This is in large part because we cannot know how smoothly each part will progress and must be re-evaluating progress and priorities.
The issues listed in the In-Progress column are not ordered. If an issue is blocked by another issue it should be labelled as 'blocked' with a comment describing the blockage.
The waiting review column can be ordered. Reviewers should start with the top most issue. If something is a priority it can be moved to the top and should be reviewed next.
As of the project 3 submission deadline, 9 product backlog items were still in "to-do", 4 were "in-progress", and 28 were "complete".
Most pressing at the top and least pressing at the bottom.
