3 Easy Ways to Add Agile Methodology to Your GitHub Projects While Keeping Developers Happy

If you’re a founder, product manager, scrum manager, or technical lead working with a team of developers, you know it’s not always easy to add Agile methodology to their workflow. This is especially true if you try to get developers to use software they don’t understand, think they need, or want to use.

We’ll let you in on a little secret: developers hate being forced into a project management approach. In a perfect, pristine world, developers could focus just on writing code and nothing else. They get that there are other people involved; designers who create digital assets for us, writers who spin words that capture the work we’ve done. Even marketers, we suppose, need to be kept in the Agile loop.

But we hate having to use an entirely different system on top of coding, git commits, and pull requests.

If the developers on your team feel the same way, don’t try to herd cats; instead let them use one of the tools they know and love: GitHub.

So how can you add Agile methodology to your source control tool and keep your developers happy? 

Use GitHub’s Agile Projects

Since October 2016, GitHub has offered a way to track GitHub Issues, Pull Requests, and Notes, with Projects. GitHub Projects let you have kanban-style boards for managing work, and cut across separate code repositories. This lets you round up, say, all the tasks for your next sprint and list them in one place.

A GitHub Projects' kanban-style board
A GitHub Projects’ kanban-style board

GitHub Projects are great for developers because they are an extension of what developers are already used to: GitHub Issues and Pull Requests. When developers finish writing code to fix a bug reported via an Issue, the message they wrote to summarize what they did can automatically close an Issue once it’s live. This means you don’t have to poke your developers to keep the project management app up-to-date; it’s already done.

What’s more, GitHub Projects let you group Issues and Pull Requests (which are code waiting to go live) by Milestone. Let’s say you have a first-quarter release that’s important to sales and marketing. Developers will be able to report the status of their work in detail through Issues. This allows everyone else on the team, or other teams, to see their progress by viewing Milestones.

GitHub Milestones
GitHub Milestones

If you’ve ever used Trello, working with GitHub Issues (like Cards) and Projects (like Boards) will be very familiar to you. Let’s take a closer look at how Github Projects work.

Creating GitHub Projects is easy:

1. Log into your company’s GitHub account.

2. Go to the “Projects” tab.

GitHub Projects tab

3. Give your new project a name, a description (optional), and start with the “Kanban (Basic)” template.

GitHub Projects templates

4. Click “Create Project.”

5. Your new Project will open, with a handy set of instructions on the left, and Issue cards, which you can drag into their proper places, on the right.
GitHub project instructions


6. Continue to add issues that you want to track (such as the resized logo you need for the next release) into the Project. You can search for existing (open or closed) Issues, or add notes. GitHub Notes are hard to find in the documentation, but easy to create once you know the trick: click the + next to the ellipses to the right of a Project columns’ name.
GitHub Notes

Make GitHub Projects more Agile with ZenHub

As nice as GitHub Projects are, they’re missing one really important Agile methodology ingredient: Epics.

In Agile methodology, Epics are bigger than single user stories, sometimes bigger than any one sprint or iteration. For product managers, founders, and executives, they’re the things that matter most.

Unfortunately, GitHub doesn’t have Epics (neither does Trello, out of the box). But there’s a neat service for GitHub called ZenHub, that adds Epics, enhances Projects, and adds a number of very useful reports to GitHub.

ZenHub
ZenHub

With ZenHub Epics, you can organize a bunch of User Stories in the form of Issues into a single coherent whole; scheduling it, tracking it, and measuring its progress.

A ZenHub Epic
A ZenHub Epic

Not having Epics as part of your Agile toolbox can hurt your team. If you use Trello, but not Epics, each sprint will fill up with small issues and improvements. Meanwhile, the big things, the things that matter most and that would normally have been captured as Epics, will not be addressed fast enough.

ZenHub does more than Epics for its approximate $5/month per seat price tag. It can actually predict delivery dates so you don’t have to do the math, and delivers management-ready release reports.

ZenHub release reports
ZenHub release reports

And for your developers, ZenHub offers burndown charts to show progress made towards completing a Milestone.

ZenHub burndown charts
ZenHub burndown charts

Use Trello instead

GitHub and ZenHub are great solutions when your Agile team is mostly developers. But what if they’re not? What if most of your cross-functional team are people who don’t think like developers? Or you don’t want to complicate the software development process with issues from other teams, that have nothing to do with software development?

Trello makes for an excellent Agile management tool for teams more interested in results and process than management reports. With it, and a consensus around how your team will use this tool, you can orchestrate both simple and robust Agile projects.

Trello straps rockets to a kanban board: you can have as many boards, lists and cards as you need. You can add information, links, and integrations to cards, and move cards from list to list and board to board as needed. Here’s a great Agile starter board you can use as a template.

An Agile start board for Trello
An Agile start board for Trello

Most Agile project management tools have a product backlog list for defined tasks, a sprint backlog for the tasks enumerated for this sprint, and a current sprint for tasks in progress. But if this structure doesn’t work for your style of Agile management, Trello lets you set up your own lists as you see fit.

Your team members are free to create and edit cards, adding comments, checklists, due dates, tags, and notes — essentially having all the conversation that’s needed about a specific task. Trello will make sure everyone is up to date, log comments, and alert team members when they are mentioned in any card. Three things make Trello particularly well-suited for Agile management:

  • Chrome browser extensions: Such extensions can add specific features to Trello. For example, they can create functionality for creating task points, tracking time spent on tasks, generating Gantt charts, and exporting cards.
  • Power-Ups: There’s a wide variety of powerful integrations available for Trello, including integrations with GitHub. Everything from adding calendar views, to including custom fields that connect to Google Drive documents. The Power-Ups are great for your developers, who may be feeling a bit left out.

But what if you want both?

Trello is a great Kanban tool, but what if you really don’t want to give up GitHub’s robust version control features? Well, it turns out there’s a way you can get the best of both world. Developers who want to stay in GitHub can do so, and leaders who want to use Trello to track a project’s progress can do it. How?

By using Unito. Unito is a workflow management platform that gives you the ability to use the tools you need while streamlining your workflow. All it takes is a few clicks:

A screenshot of adding a block of work with Unito

Add a block of work for Trello and GitHub

A screenshot of a flow built between Trello and GitHub in Unito

Use flows to connect your blocks.

A screenshot of the flow customization process in Unito

Customize your flow.

And you’re done! Now pull requests, issues, and comments can be pulled from GitHub and added to your Trello board automatically. Additionally, any comments or updates made in Trello will be carried over to GitHub. With just a couple minutes, you’ve made it possible for everyone to use the tool they need. Want to know more about what Unito can do for your workflow? Check it out here.

Bring agility back to GitHub

Whether you go with GitHub, ZenHub, or Unito, bringing agility back to your projects doesn’t have to be difficult. You don’t have to sacrifice your workflow just because your teams can’t agree on what tools they should be using. Make your workflows better by giving everyone the power to use the tool they need.

What next?

1. If you enjoyed this article, there’s a good chance your friends and colleagues will too. Why not share it on Twitter, Facebook, or LinkedIn?

2. Watch this video explaining the power of Unito

3. Learn how Unito’s simple, no-code interface can help you sync tools in seconds

4. Check out Unito’s pricing plans to see which might be the best for you (there’s also a two-week free trial!)

Start your free trial