For example, you might see something like “Menu System” or “Homepage” on this board and can quickly see that “Menu System” is currently in “Development”, while the “Homepage” is currently in “Discovery”. This gives team members a birds-eye view of high-level features or bodies of work. The purpose of this Project board is to track the Epics, which can be seen as the "parent" issues of a set of related issues. Boards have columns which represent the state of a given issue, such as “To Do”, “Doing”, “Done”, etc.įor our purposes, we’ve created two main project boards: This time period is typically what is being worked on currently, or coming up in the future. Each of these will be explained in more detail below.Ī project board is a collection of issues being worked on during a given time. This article will go over one of the ways we’ve been using GitHub Projects for our clients, and set forth some more guidelines that might be useful for your next project.įirst, let’s go over a few key components that we’re using for our project organization. One of our favorite additions has been the Projects tab, which gives any repository the ability to organize issues onto boards with columns and provides some basic workflow transitions for tickets. Many of those guidelines we set forth still apply, but GitHub itself has changed quite a bit since then. We first wrote about managing projects with GitHub back in 2012 when it was still a bit fresh.
At Lullabot, we’ve been using GitHub, as well as other project management systems for many years now.
0 kommentar(er)
