Application Lifecycle Management (ALM) Suites Forum

Rhea Rapps
Content Specialist
IT Central Station
Sep 07 2018
One of the most popular comparisons on IT Central Station is IBM Rational Team Concert (IBM ALM) vs JIRA. One user says about IBM Rational Team Concert (IBM ALM), "I value links from stories/defects to use for coding via tasks and change sets." Another user says about JIRA, "Multiple features make this product a delight to use. Using it for backlog prioritization is the key to either Kanban or Scrum processes. JIRA does a great job of articulating the story, adding elements to the story and helping with prioritization."In your opinion, which is better and why?
Nitin KaushikRTC is strong in traceability across the lifecycle, Support for cross-platform development, Cross-project planning , Embedded Source Code Management ( while JIRA requires additional Atlassian product - Bitbucket), Continuous Integration (Build Engine) , easy Integration between SCM and CI, seamless integration with Requirements Management , Quality Management, Design Management, whilst JIRA has very flexible Marketplace with extensions and plugin, Number of available extensions and plugins, simplicity of extending the product functionality (developing plugin or extension), ease of Software as a Service, Recognition by analytics groups (for Agile Planning).
Yals KeethaALM is the test management tool and end users can able check manual their application flows. It was follows waterfall model. Jira is a defect tracking tool. It is finding the one release has how many defects are closed and how many pending so using for the agile.
Christopher GallivanOur HP ALM tool serves the test management function. Jira is not a test management tool. I don’t really see the comparison. A project that only uses Jira loses a lot in my opinion.
Ariel Lindenfeld
Sr. Director of Community
IT Central Station
Aug 15 2018
Let the community know what you think. Share your opinions now!
it_user358428The ability to version control all database artifacts, and the ability to perform CI-triggered, automated database artifact deployment.
Diego Caicedo Lescano1. Easy of automation 2. Integration with functional and no functional solutions 3. Dashboards for governance
Nitin KaushikAdaptability, scalability, seamless collaboration with external tools along with near native interface for requirement, design, test and ccm activities within the collaborative suite. Process governed along with level of simplicity covers ALM as suite.
Rhea Rapps
Content Specialist
IT Central Station
Apr 18 2018
One of the most popular comparisons on IT Central Station is JIRA vs TFS  https://www.itcentralstation.c... Which of these two solutions would you recommend for Application Lifecycle Management (ALM) and why? Thanks! --Rhea
Rene De VleeschauwerFirst of all Jira is not an ALM solution. Yes it is part of it, but his main task is issue mgt. The corresponding TFS feature are TFS workitems. For real ALM you need to start from requirements, dev environment , versioning, build, quality assurance and finally production. If you are a pure Microsoft shop go for TFS, if not Jira might be a better choice (for issue tracking..)
Juan-PerazaFor complete ALM, I would consider MicroFocus ALM Octane? I have worked at a shop where I used and was an administrator of JIRA. As Rene stated, it's not an ALM solution. Take a look at this Octane demo - https://www.goconsensus.com/app/view/p/q33mf86w?autoplay=false
Claudette SteynbergWe use both. It depends on your application and your budget. For us, the Atlassian suite of tools required to do end-to-end ALM processing is very expensive (currency conversions also does not help). We, therefore, only use JIRA as an incident/support/planning tool. We are a Microsoft partner and hence the VSTS/TFS tool suite is much more affordable to us. The visibility of this tool from backlog item to code, build test and released into production is amazing, but it lacks some of the basic admin capabilities that are well automated in JIRA e.g. as tasks are moved, the status of parent items/stories/epics are not automatically updated in VSTS. This adds a lot of admin overhead for product owners, scrum masters and team members. If it weren’t for budget, the Atlassian suite will be my first choice. If you combine, JIRA, Bitbucket, and Bamboo you would get the same visibility. We also use Confluence extensively as all our documentation are done Wiki style. We found SharePoint just becomes a repository and not a knowledge share platform. Hope this helps! Shout if you have questions.

Sign Up with Email