I have been using Atlassian ALM for twenty-five years. It used to be called Quality Center, and I first used it in 2000 and 2001. The company changed, but the product remained. Atlassian ALM has not benefited my workflow regarding the use of third-party plugins.
That is not correct; I would recommend Atlassian ALM for cases at the right scale. I have been implementing FDA regulated medical or medicine development with Atlassian ALM. The whole requirement management chain with Jira and Confluence means that auditors accepted everything and it was fine. It is possible to do, but it is totally on the upper limit. If you develop a SaaS service or business-to-business CRM, then it is definitely enough to use for requirements. Still, you need to have requirements. For example, if you handle payments or need proper formal requirement management to get reports, you can do that with Jira with some applications such as Requirements for Jira, which R4J is one of them. You can extend Jira so it has traceability, baselining, and reports. However, it is not really scalable, so if you want to use it for anything larger or plan to use it for product portfolios, then it starts to be problematic. Definitely, it is much easier to use, and if you can spend the little effort to configure Jira to support your more complex requirements management, then you can concentrate everything in one tool. You do not need an additional requirements management tool and the whole company tool chain is simplified in architecture and all.
The most common use case is for software development teams. Some clients also use it for their service teams, like the service desk. Additionally, we have some clients from the sales team who use it as a sales enablement tool.
Our primary use case is to have as an ALM Software. We develop Software, so we need to have a solution that supports the full cycle of the software development, starting from the requirements to work management, to source code management, to being tested. And on top of that, we have sharing capabilities with Confluence.
How to use Atlassian to manage application lifecycle: Atlassian builds software to pull together all the elements of application lifecycle management. Product management, developers, Q/A, dev ops, and business stake holders all have their own ways of interacting with application lifecycle management and Atlassian splits up the process into a few buckets.
1) Collaborate to plan and envision work
Atlassian's Confluence is a collaboration platform for building and driving consensus. Call stake...
I have been using Atlassian ALM for twenty-five years. It used to be called Quality Center, and I first used it in 2000 and 2001. The company changed, but the product remained. Atlassian ALM has not benefited my workflow regarding the use of third-party plugins.
That is not correct; I would recommend Atlassian ALM for cases at the right scale. I have been implementing FDA regulated medical or medicine development with Atlassian ALM. The whole requirement management chain with Jira and Confluence means that auditors accepted everything and it was fine. It is possible to do, but it is totally on the upper limit. If you develop a SaaS service or business-to-business CRM, then it is definitely enough to use for requirements. Still, you need to have requirements. For example, if you handle payments or need proper formal requirement management to get reports, you can do that with Jira with some applications such as Requirements for Jira, which R4J is one of them. You can extend Jira so it has traceability, baselining, and reports. However, it is not really scalable, so if you want to use it for anything larger or plan to use it for product portfolios, then it starts to be problematic. Definitely, it is much easier to use, and if you can spend the little effort to configure Jira to support your more complex requirements management, then you can concentrate everything in one tool. You do not need an additional requirements management tool and the whole company tool chain is simplified in architecture and all.
The most common use case is for software development teams. Some clients also use it for their service teams, like the service desk. Additionally, we have some clients from the sales team who use it as a sales enablement tool.
Our primary use case is to have as an ALM Software. We develop Software, so we need to have a solution that supports the full cycle of the software development, starting from the requirements to work management, to source code management, to being tested. And on top of that, we have sharing capabilities with Confluence.
The primary use of this solution is agile application life cycle management.