PRODUCTION

GITHUB PROJECT BOARD

Github Projects

We use Github Projects as our primary project board to keep development on track. Paired with Github repos for our code base, Projects helps us manage tasks using a Scrum/Agile approach. We create epic tickets and break them into sub-tickets/tasks to keep things organized. Developers and PMs, your job is to keep tickets updated to reflect the actual state of work—clients are counting on us!

Lane Names and Descriptions

We keep lane names consistent across projects for clarity. Here’s what each lane means:

Epics

Holds epic tickets, which stay here until all sub-tasks are done.
PMs close epic tickets once all sub-tasks are completed and closed.

Parking Lot

Tickets not planned for the next three or more sprints live here.

Backlog

Tickets are ordered by priority and completeness (all requirements added?).
During Sprint Planning, developers pull tickets from here to the Sprint Backlog to define the sprint’s deliverable (increment).

Sprint Backlog

Actionable tickets with all requirements, assigned to a developer for the current sprint.
Ordered by priority, with top-priority tickets at the top.

In Progress

Tickets actively being worked on, assigned to the developer handling them.

Ready for QA

Developers move tickets here after deploying to the dev environment and verifying functionality.
Add a comment summarizing what’s done and assign the PM (or designated QA person) for testing.

Done

Tickets that pass QA land here.
Closed after functionality is deployed to production and QA’d.

Moving Tickets Between Lanes

Keep the board tidy by moving tickets promptly:

Developers: When starting to work on a ticket, pull that ticket from the Sprint Backlog lane into the In progress lane.
When done, deploy your work to the dev environment, move the ticket to the Ready for QA lane, add a comment describing the work you've completed, and assign the PM to let them know that ticket is ready for QA.
PMs: If a ticket has issues during QA, add a comment describing the issue, reassign the developer, and move it back to In Progress.

Adding Good Comments

Clear, concise comments keep everyone in the loop:

Summarize what’s completed, what’s in progress, or any deviations from the ticket’s acceptance criteria.
Use slash commands for code snippets or accordions to hide non-essential details.
Add screenshots to clarify issues, but tuck them in an accordion to reduce visual clutter.

Other Helpful Tips

Use the search bar to filter by sprint tag for quick navigation.
Stick to our consistent ticket naming format—it makes filtering a breeze.
- Suggested format: [EPIC-ABBREVIATION] / [Subtask description]

Turn bullet points into sub-tickets with one click (hover over the item, click the three-dot button).

Tickets only appear on the project board if (manually) assigned to the Project—Project assignment is in the ticket view, two items below Assignees in the right sidebar.

Once assigned to the Project, Lane status (among other Project options) are available to set.

Page updated

Report abuse