GitHub vs. IBM Rational ClearQuest

I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.

Incentivized

Well Suited - If your project is running in waterfall model and other IBM tools are widely used for various purposes, Clear Quest is a good tool to have. It gives you seamless capability to create defeccts and query the defects for various scenarios. If you are a project manager or a test engineer trying to create defect metrics, this tool can help immensely. Less Appropriate - In this Agile world, everyone uses Jira or some other agile tracking tool. All the agile tracking tools have already built in defect tracking capabilities and can integrate with the work very well. If your project is running on agile or don't use IBM tools that much, then Clear Quest doesn't always add value.

Incentivized

• Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
• Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
• Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.

• IBM Rational ClearQuest records and workflow are highly customizable. As a result, ClearQuest implementations can be tailored to any organization's methodologies.
• IBM Rational ClearQuest Integration with IBM Rational ClearCase provides traceability between work records and source code changes, expanding the SDLC scope of the toolset.

Incentivized

• Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
• Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
• Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
• While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.

• Lot of defect management tools are out there and are free to use
• In agile world, teams use Jira or other tools and they have the defect tracking capability builtin
• Don't really see the need to use this tool in agile world

Incentivized

GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.

Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.

Incentivized

GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.

Incentivized

Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data

Incentivized

It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.

Incentivized

IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties

Incentivized

It was pretty simple.

Incentivized

GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular tool many other platform provide easy integration with the platform and make first choice for many tools architects.

Incentivized

IBM Doors could be better at document management for a higher price. If you need more complex traceabilily, Doors is the way to go. If you need less, free and simple management, a common SVN is ok for you.

Incentivized

• GitHub has made branching much easier for our dev team. Easy branching makes it easier for us to gain all the benefits of source control while giving us the flexibility to decide what features/branches we want to go in any particular release.
• Integration with third-party tools like Azure DevOps has allowed us to streamline workflows and gain the benefits of automated testing whenever a commit is made.
• GitHub has also raised visibility with its integration with our Sprint boards. We can easily jump to a commit from a work item.

Incentivized

• Positive: Quality product that adheres industry best practices for a considerably cheaper cost.
• Negative: Maintenance of more than one tool for overall project management.

Incentivized