Most teams that are building internet updatable software are leveraging cloud-based tooling for Project Management and Code Source Control. The maturation in the space has facilitated increased collaboration over the last few years with remote teams.

We don’t want this to turn into a blog spam top 20 project management tools in 2020, as there are a few google search page results worth of those. More broadly, we’ll touch on some vital considerations of project management tools and call out the most popular members of this general cohort.


  • An easy mistake to make in project management tooling is to throw 20 required fields at them with opaque flows. The more complex a project management tool is, the less involvement you’ll see from team members. We encourage teams to keep status and configuration as easy as possible.

Project/Team Access

  • How do your teams organize?
  • Is restriction of access between projects mandatory?

Role Based Access Control

  • Similar to the team separation, do you need different role levels?
  • Do you need guest access for clients to read specific issues or leave comments?


  • With Code Repositories / Version Control System
  • Chatop Integrations (Slack, MSFT Teams, Mattermost, Zulip Chat)
  • With other project management tools (think cross organizational syncing or Design => Dev)
  • Roadmapping or Requirements as a Service tooling


  • Depends fully on your culture. At a high level, you’ll want to see your team’s current progress & what’s been completed.

Single Sign On

  • Do you need to integrate with G-suite, Office365, Okta, Auth0 or another identity provider?
  • Further configuration with standards such as SCIM can help onboard & offboard employees.

Data Migration

  • Many tools (established or neveau) will provide migration support via their client success teams.

Data Location and Retention

  • Does your organization have requirements for the location of data? Certain regions? On Premise in your organization’s data center?


In our discussions with software development teams, the following tools have come up most in conversations (in alphabetic order).

In the traditional project management bucket: Asana, Basecamp, Github, Gitlab, Jira,, Pivotal Tracker, Rally Dev, Service Now & Trello.

A little more roadmap focused: Aha!, ProductBoard, ProductPlan.

At the end of the day, you’ll probably want to test out each of these tools with some team members in order to get feedback from them. Keep your culture in mind, a tool will not fix that.