Project Support Links
GitHub Projects
Overview
The course uses GitHub Projects to manage the collaborative group project. GitHub Projects offers a combination of familiarity, integration with GitHub repositories, transparency, and flexibility that makes it an ideal choice for managing collaborative coding projects within an educational context. In this course, you will learn how to effectively use GitHub Projects to manage your group's development workflow using a Kanban board.
Instructions
The following steps will guide you through creating a new GitHub Project for your group:
- Open the group's project repository in GitHub.
- Click Projects from the repository navigation menu and then New project. A dialog will open to create a new project.
- Under Start from scratch, click Board to create a kanban-style project board.
- Give the project an appropriate name.
- Keep the ☑️ Import items from repository option checked.
- Click Create project and the project board will be created.
GitHub Projects is used because it supports coordination without adding another tool outside your repository workflow. Since the board is connected to your GitHub issues and repository, it helps your team plan work, reduce confusion, and maintain visibility into progress. Together, these features create a simple system for accountability and help the team focus on completing the most important tasks first.
Using the Board
After the project board has been created, your team should use it as the central place to track work throughout the block. The Kanban board gives everyone a shared view of what needs to be done, what is actively being worked on, and what has already been completed.
The recommended workflow for using the board is:
- Add work items to the board as issues or tasks that describe a specific piece of work.
- Keep new or to do work in the To Do column.
- Move a task to In Progress when a team member begins working on it.
- Assign tasks to specific team members so ownership is clear.
- Optionally, customize the columns to reflect weekly sprints or other milestones.
- Move tasks to Done only when the work has been completed and reviewed according to your team process.
- Review the board during team check-ins so everyone can see blockers, priorities, and next steps.