How do teams structure their GitHub Project boards (To Do, In Progress, Review, Done) in large repos?

[Suhebdevtechnosys]

Select Topic Area

Question

Feature Area

Issues

Body

How do big development teams organize and manage their work using GitHub boards — what columns do they use, how do they track progress, and how do they keep things clear and manageable in large projects?

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[karantaragi07]

Large teams use GitHub Boards like a lightweight Kanban tool. Typical columns are To Do → In Progress → In Review → Done, sometimes with extra columns like Blocked or QA. Progress is tracked via linked issues/PRs, milestones, and automation rules e.g., moving cards when a PR is merged. To keep things manageable, teams filter by assignee, milestone, or repo, archive old items, and use meta boards for cross-repo tracking.

[CSWaleed]

🧩 1. Board Setup: Columns That Work at Scale

Most large teams use a Kanban-style board with columns like:

📌 Common Column Structure
Column Purpose
Backlog All upcoming ideas, feature requests, or tasks not yet prioritized.
To Do / Sprint Backlog Approved tasks that are ready to be worked on in the current sprint or cycle.
In Progress Work that is currently being developed.
In Review / Code Review Pull Requests waiting for peer review.
Testing / QA Items undergoing manual/automated testing.
Blocked (optional) Tasks that can't move forward due to dependencies or issues.
Done Completed and deployed tasks.

Large teams sometimes add:

"Needs Spec" for items that need more requirements.

"Ready for Release" for code that's done but not yet deployed.

🏗️ 2. Organizing by Milestones, Labels, and Assignees

To manage complexity, teams combine boards with these GitHub features:

🏁 Milestones

Used to group issues/PRs for a specific release, sprint, or epic.

Useful for tracking progress toward big goals.

🏷️ Labels

Used to categorize tasks across multiple dimensions:

Type: bug, feature, chore, refactor

Priority: P0, P1, low-priority

Area: frontend, backend, API, docs

Status: needs review, awaiting feedback, etc.

👥 Assignees

Each issue or PR is assigned to the current owner or responsible developer.

Prevents confusion over who’s doing what.

📊 3. Tracking Progress
📌 GitHub Projects (Beta) / Projects v2

The newer GitHub Projects system (Projects v2) is more flexible and powerful:

Custom fields: Priority, Story points, Status, etc.

Filters and Views: Tailored views for teams (e.g. QA sees only Testing tasks).

Charts: Burndown, throughput, and progress visuals.

Large orgs often:

Create separate boards per team or per area (e.g., "Frontend", "DevOps").

Use automation rules to move cards between columns when PRs are opened, merged, or issues closed.

Integrate with third-party tools like Jira, ZenHub, or Linear if more complexity is needed.

🔁 4. Workflows and Best Practices for Clarity
✅ Best Practices

Daily triage: Review incoming issues and prioritize.

Weekly grooming: Refine backlog, break down large tasks.

Sprint planning: Move items from backlog to “To Do” with owners and estimates.

Retrospectives: Look back at what was completed or blocked.

👀 Clarity and Visibility

Pin key boards in the org/repo.

Use clear, standardized issue templates.

Keep issues up to date — close stale ones and clarify vague tasks.

Avoid overcrowding: archive or split boards when too full.

🛠️ Bonus: Automations That Scale

Automatically move cards when:

PR is opened → “In Review”

PR is merged → “Done”

Slack or Teams integrations for board updates.

GitHub Actions to update statuses or post comments based on CI/CD results.

📌 Summary
Practice Why It Helps
Use standard columns like Backlog → Done Visualize workflow clearly
Tag and assign everything Ownership and filtering
Use milestones and labels Grouping and prioritizing work
Automate where possible Save time and avoid manual errors
Keep it lean and clean Prevent overwhelm and confusion

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬