Project Management Part I - bluecolab/BlueColab_MobileDataViz GitHub Wiki
We use GitHub Projects to help manage the development of the app.
View the Project here: https://github.com/orgs/bluecolab/projects/15
If the above doesn't work, you need to be added to the GitHub org. Please reach out to an intern or Leanne for help.
See here for help.
We use the key AWM
.
Views allow us to view specific aspects of the project.
Purpose: The backlog contains a list of all the stories (tasks) we need to do related to the app.
Columns:
- Title: The name of the story.
- Assignees: Whose working on the story.
- Status: Status of story:
Todo
,In progress
, orPR
,Done
,Blocked
. - Points: The difficulty of task from 1-5.
- Priority: Priority of story:
Low
,Medium
,High
,Very High
. - Label: Multiple options, serves as a quick view of what the story is about. You can choose more then one.
- Type: Type of story:
Bug
(fixing a issue),Feature
(adding an enhancement), orTask
(if other two are not applicable). - Milestone: The semester the work is done in.
- Sprint: The 2-week-ish time period work is done in. Blue CoLab uses sprints - sprints end when the 'Summary' assignments are due or when midterm/final take place.
Each of the above can be added via the linked view by clicking on the small down arrow or editing it cell directly.

Link | What is it? | Kanban
Purpose: List the tasks that are being worked on for the current sprint. As you progress through the story you can move them around to change their status.
Notes: If you see that this board is blank, it seems a new sprint was started. Update the previous' sprint stories so they are under the current one. This can be done via the Backlog view.

Purpose: List the tasks that are being worked on for the current semester. This board should auto update as you progress through sprints.

Purpose: Lists all stories that are finished.

Purpose: Lists all stories in order. Scroll all the way down to find the number for the next story.
