I use the on-prem deployment model. Our primary use case is for application life cycle management, DevOps, and all the application requirements.
I use the on-prem deployment model. Our primary use case is for application life cycle management, DevOps, and all the application requirements.
You can see the work ticket and you can circulate that within the teams. You can define your flows, customize according to your needs, and you can create dashboards and create the reports according to your needs. The version is not a distributed version of those systems. I think after requiring the kit by Microsoft most of the parties who are already using different ALM tools, they are moving towards Azure DevOps. Microsoft should be dedicated to moving the teams, creating new features, and making the Azure DevOps most straight-form independent. I have been using Siemens Polarion for three years but I haven't found out a way that you can use it in your own methodology for content management systems. If you were to say that everything is integrated and it's a complete solution, I would say it's not.
The most important thing for them to improve should be platform-independent features. They should also provide extensive pipelines and release pipelines that we can define and we can work on.
Another area of improvement is integration with external tools and external platforms like Linux, Mac, and other stuff. Most of the teams are basically moving towards faster development. Everything should be flexible. All the tasks you can see in AWS and Azure, you would just need to drag and drop and release into the pipeline.
Right now, if you can evaluate the tools, then I think that as for the cost differences and for the usability, and other things concerned, so I will rate AWS at the first, Azure second, and then Atlassian tools and then Siemens would be fourth or fifth.
It has worked well. Communication, dashboarding, reporting, content management, workflows, and you are creating user stories and you'll communicate within teams creating different divisions, mapping, queuing; for these kinds of things, that is good.
Scalability is good. It's easy to expand it.
The initial setup was straightforward as far as the installation and management. It's easy to establish, setup, and deploy.
The deployment took two to three hours.
I would rate it a five out of ten. I would like to see better integration and better extensivity of tasks. The costs are not proportionate to the features it offers.