Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
OpenText Solutions Business Manager
Score 5.7 out of 10
N/A
OpenText™ Solutions Business Manager, formerly from Micro Focus is enterprise-scale business process automation software. It helps IT quickly create, adapt, deploy, and govern process-based apps and workflows for humans and systems across the organization.
N/A
Pricing
Azure DevOps Services
OpenText Solutions Business Manager
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
How many users will be using the system? What part of the organization will own the product? Serena is a great workflow tool. It can be tailored to fit in any scenario and so I dont believe there is any situation where it would be inappropriate.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
One of my favorite capabilities within the Serena user interface is the reporting. Detailed searches into the workflows allow the users to create reports containing any field that is in the workflow. Users here use the reporting during review time to pull metrics on tickets they have worked during the year. From a process perspective, the system provides a specific report with details around how long the items have been in various states. I use this information to measure my process peformance and to identify bottlenecks within the processes themselves. The reports are fairly easy to use but they can also be very complex too. Reports can be set up and shared across groups. Generic reports can also be set up so that query at run time fields can be entered.
Developing new processes in Serena Business Manager is relatively easy and does not necessarily need to be done by a developer. Serena has added some key features that reduces the need to add Java scripts. Serena Business Manager is a blank slate and it can be as complex or as simple as you make it. The forms are the same. I have seen some very simple designs and some very complex and beautiful form designs.
From a user perspective, it is fairly simple to just pick up and start using. I introduce our new hires to the systems in a thirty minute session. Most users are more confused by which process to use for what than by how to use the system.
Serena's documentation for the product is well written but it can be a bit challenging because it is often missing key components, best practices or tips and tricks that you get when you call into their customer support. It is also very frustrating to have their release notes refer back to their knowledge base to have their customers figure out what they fixed in their releases.
Serena Business Manager manages their users in an Administrator function. Any changes made in this part of Serena is only logged in the database. It would be nice to have some reporting out of of this system. When you have multiple administrators of a system, it would be a nice feature to have some reporting here rather than having to go into the database.
The notification feature within Serena can be a bit challenging and time consuming. You can't copy the notifications so if you want to duplicate a notification you had previously created you have to recreate it again. The notifications have three levels to them and they can be a bit tricky to get them to work just right.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
We have been using Serena for eight years and I don't believe I can answer this question since it was so long ago that we made the decision to purchase Serena.
We use Serena to standardize our business processes to ensure a more efficient work day experience for our employees. By having the employees use Serena for the processes we can ensure the process is completed the same way every time.
By having our key processes in Serena we are able to measure our processes at any time. Some of those key metrics include a 90% reduction in rework and a 47% reduction in overall process time. With the ability to measure processes at any time, we can react to process problems and correct them quickly. Serena Business Manager is flexible enough to allow quick development and rapid promotion when necessary.
Serena is very ingrained in our culture and the culture has taken on the "ticket" mentality unfortunately. With everyone trying to measure their work and justify their body counts through ticket counts, having a ticket opened for every act of work has become the standard.
