How we use project boards

Description of our project boards

We would like to try out Github projects in this project due to integration with Github Issues that we would use anyway, and to reduce the amount of different systems to manage in the process. Project Boards gives the same functions as Trello while being in the same system.

---

We will have certain tasks that aren't related to any user stories, and these would be labeled with either "tech", "wiki", "backend", "frontend" or "report" label. This will keep track of the tasks/issues regarding them. All tasks should be labeled with either the user story they belong to, or the best descriptive label there is.

---

Our Sprint Project Boards has seven columns to manage how far in the production process our tasks are.

1. User Stories: This column is where we keep the sprint goal, and the user stories for the sprint.
   • This column is not to be edited during sprints.
2. Todo Tasks: This is where we keep the tasks that the user stories have been split into, in addition to other tasks that come up during the sprint.
   • When starting at a task, convert it to an issue and assign yourself to it.
   • Move it to "In progress"
3. In progress: This is where we move the tasks that a team member is actively working on.
   • Tasks that are actively worked on should be in this column.
   • If there is next to nothing done with it and you will not continue, move back to "Todo tasks" column and remove yourself as assigned.
4. Quality Assurance: The tasks in this column are either ready for quality assurance, or actively being looked upon for QA.
   • QA Should not be done by the same member that did the task itself.
   • QA should not take more than a few minutes, as it only requires a different team member to poke at the task in question.
   • The team member doing QA should move task to "Done" and close the issue afterwards.
5. Blocked: Tasks that for whatever reason cannot be actively worked on. Could be due to dependencies on other tasks.
6. Done: Tasks that are complete and ready for production. They've been through QA and are for all intents and purposes complete.