Simplified Sprint and Backlog Management in GitHub - Need Guidance

[dineshsonachalam]

Select Topic Area

Question

Feature Area

Projects

Body

I'm currently managing a small team of 5 developers. We previously used Azure DevOps for sprint and backlog management, which was straightforward and worked well for us. However, we've recently transitioned to using GitHub, and I'm finding the project management tools there a bit confusing.

Here's what I need:

• A simple way to manage sprints and backlogs.
• The ability to create features with a list of tasks and subtasks.
• A clear way to track these on a sprint board.

I'm struggling with understanding how GitHub issues, pull requests, milestones, and project boards fit together. I don't need anything complex—just two boards (one for the sprint and one for the backlog) that are simple and not too messy.

Is there a way to achieve this simplicity within GitHub's tools? Any tips, best practices, or recommendations would be greatly appreciated!

Guidelines

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

[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! 💬

[TikoyX]

Hi Dinesh. I unfortunately can't help you but i'm also searching for something to do this.
I'm surprised how few features GitHub have to do something like this, specially when you consider how big they are.

However, it sounds like you second point is related to issues and sub-issues?