What users are saying about

Backlog vs Git

Backlog
9 Ratings
Git
75 Ratings

Backlog

9 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 9.3 out of 100

Based on 9 reviews and ratings

Git

75 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 9.3 out of 100

Based on 75 reviews and ratings

Feature Set Ratings

    Project Management

    9.4

    Backlog

    94%

    Git

    Feature Set Not Supported
    N/A
    Backlog ranks higher in 8/8 features
    Backlog ranks higher in 8/8 features

    Task Management

    10.0
    100%
    2 Ratings
    N/A
    0 Ratings

    Gantt Charts

    9.0
    90%
    2 Ratings
    N/A
    0 Ratings

    Scheduling

    9.9
    99%
    2 Ratings
    N/A
    0 Ratings

    Team Collaboration

    9.9
    99%
    2 Ratings
    N/A
    0 Ratings

    Support for Waterfall Methodology

    7.9
    79%
    2 Ratings
    N/A
    0 Ratings

    Document Management

    9.0
    90%
    2 Ratings
    N/A
    0 Ratings

    Email integration

    9.9
    99%
    2 Ratings
    N/A
    0 Ratings

    Mobile Access

    9.9
    99%
    2 Ratings
    N/A
    0 Ratings

    Attribute Ratings

    • Backlog is rated higher in 1 area: Likelihood to Recommend
    • Git is rated higher in 1 area: Support Rating

    Likelihood to Recommend

    9.9

    Backlog

    99%
    2 Ratings
    9.1

    Git

    91%
    35 Ratings

    Likelihood to Renew

    Backlog

    N/A
    0 Ratings
    10.0

    Git

    100%
    1 Rating

    Usability

    Backlog

    N/A
    0 Ratings
    9.0

    Git

    90%
    1 Rating

    Support Rating

    8.0

    Backlog

    80%
    2 Ratings
    8.5

    Git

    85%
    22 Ratings

    Implementation Rating

    Backlog

    N/A
    0 Ratings
    9.0

    Git

    90%
    2 Ratings

    Likelihood to Recommend

    Backlog

    The user interface is very good. It is more intuitive in nature. It is easy to use and robust in operation. The dashboard is designed on modernized UI and the interface is also intuitive. I can easily navigate things on my own.

    Read full review

    Carol Aleman | TrustRadius Reviewer
    Carol Aleman
    View all 2 answers on this topic

    Git

    GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository.The limitations with GIT are seen when checking in large files.

    Read full review

    Anonymous | TrustRadius Reviewer
    Verified User
    View all 35 answers on this topic

    Pros

    Backlog

    • Gantt chart
    • Github support

    Read full review

    Sanyam Jain | TrustRadius Reviewer
    Sanyam Jain
    View all 2 answers on this topic

    Git

    • Ability to create branches off current releases to modify code that can be tested in a separate environment.
    • Each developer had their own local copy of branches so it minimizes mistakes being made.
    • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
    • Conflicts are displayed nicely so that developers can resolve with ease.

    Read full review

    Anonymous | TrustRadius Reviewer
    Verified User
    View all 35 answers on this topic

    Cons

    Backlog

    • The biggest drawback that I want Backlog to fix as soon as possible is that is does not provide any place to explain the problem or bug virtually.
    • There is a need for a tab or space to attach screenshot or video to easily explain the bug or problem in the project.

    Read full review

    Carol Aleman | TrustRadius Reviewer
    Carol Aleman
    View all 2 answers on this topic

    Git

    • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
    • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
    • Many different GUIs, many people (including myself) opt to just use the command-line.

    Read full review

    Gabriel Samaroo | TrustRadius Reviewer
    Gabriel Samaroo
    View all 35 answers on this topic

    Pricing Details

    Backlog

    General

    Free Trial
    Yes
    Free/Freemium Version
    Yes
    Premium Consulting/Integration Services
    —
    Entry-level set up fee?
    No

    Starting Price

    —

    Git

    General

    Free Trial
    —
    Free/Freemium Version
    —
    Premium Consulting/Integration Services
    —
    Entry-level set up fee?
    No

    Starting Price

    —

    Likelihood to Renew

    Backlog

    No score
    No answers yet
    No answers on this topic

    Git

    Git 10.0
    Based on 1 answer
    Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.

    Read full review

    Anonymous | TrustRadius Reviewer
    Verified User
    View all 1 answers on this topic

    Usability

    Backlog

    No score
    No answers yet
    No answers on this topic

    Git

    Git 9.0
    Based on 1 answer
    Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.

    Read full review

    Anonymous | TrustRadius Reviewer
    Verified User
    View all 1 answers on this topic

    Support Rating

    Backlog

    Backlog 8.0
    Based on 2 answers
    I would give 9 but one less because of the high price.

    Read full review

    Sanyam Jain | TrustRadius Reviewer
    Sanyam Jain
    View all 2 answers on this topic

    Git

    Git 8.5
    Based on 22 answers
    I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.

    Read full review

    Nate Dillon | TrustRadius Reviewer
    Nate Dillon
    View all 22 answers on this topic

    Implementation Rating

    Backlog

    No score
    No answers yet
    No answers on this topic

    Git

    Git 9.0
    Based on 2 answers
    It's easy to set up and get going.

    Read full review

    Anonymous | TrustRadius Reviewer
    Verified User
    View all 2 answers on this topic

    Alternatives Considered

    Backlog

    Backlog has all of the top-notch features to increase productivity, visibility, and project tracking. Backlog is easy to use. I first just logged in to the platform and it was [ready] to go. I easily started working on it and it started giving me the bugs’ details on our project. Always available for queries. Listen to the queries very attentively and try to give a solution on the go if applicable. Otherwise, take some time and respond with the advanced workable solution in the limited time frame.

    Read full review

    Carol Aleman | TrustRadius Reviewer
    Carol Aleman
    View all 2 answers on this topic

    Git

    I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
    The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
    It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.

    Read full review

    Matthew Mariner | TrustRadius Reviewer
    Matthew Mariner
    View all 35 answers on this topic

    Return on Investment

    Backlog

    • Software interns get easily used to this tool.
    • One who works in the SDLC gets recognized and it's easy to track rank board.

    Read full review

    Sanyam Jain | TrustRadius Reviewer
    Sanyam Jain
    View all 2 answers on this topic

    Git

    • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
    • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
    • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.

    Read full review

    Joel Tanzi | TrustRadius Reviewer
    Joel Tanzi
    View all 35 answers on this topic

    Screenshots

    Git

    —

    Add comparison