Rocket ChangeMan ZMF (formerly a Micro Focus product) vs Visual Studio Team System comparison

"Scalability is great. It has absolutely met every need for us so far. We do have some concurrent development paths and we're able to flexibly assign variables. At the same time, our skeletons assemble where we want them to, so the scalability is very good."

"We audit once a year for our ChangeMan access, accurate financial programs, and all of that. Auditors really love ChangeMan for how easy it is to get through and how tight the security is on it. Our internal auditors, external auditors, and SOX editors love this solution. We're in the healthcare business, so HIPAA regulations and all such things are a big deal, and this makes all that really simple."

"Microsoft makes great products. They are quite robust."

"Stability-wise, I rate the solution a nine out of ten...Every month there is an increase in the number of users. It is a scalable solution."

"IntelliSense and CodeLens are helpful because they can show you details about your function, such as how many times it is called from other places within the code."

"The solution is scalable, stable and has allowed us to upgrade our frameworks."

"The solution’s fast performance is its most valuable feature."

"The product helps with version control. I can build, develop, test and deploy applications from a single platform."

"The product is efficient."

"Visual Studio Team System is the most powerful IDE available in the market."

"I would like to see them enable parallel development for online. It's available now for batch stuff on the mainframe. Jenkins, IBM, and Rocket all supposedly already have safe and workable version of Git for the mainframe. With that in mind, we need to know where our feature is."

"As such, there's nothing wrong with the product. It is great, but there are small things that can be better to make it much more friendly. The way you navigate through fields can be improved. If I'm going to stage a component over something that exists and that I've created in another library, and I want to pull it in and write it over what I've got there in my package, I've got to type in that data set name every time. That can be aggravating. It is not a big deal. The way things are sorted can also be improved. If you're doing a delete of a bunch of components, you can't sort those out by type or anything. Some things are just standard, and you can't look at them in a way that would be helpful."

"The overall customer support needs to improve."

"The stability of the product could be better."

"I would say compared to some more modern tools which are made to work offline, with this solution you have to be connected all of the time and with a central server. In our case, it's not a big problem because we all work on-premises, but it can be an issue if you have teams in different locations."

"Accessibility switches available on the desktop should also be available on mobile devices for coding or developing on the go."

"The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved."

"The technical support could be better."

"I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see."

"The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms."

"It's on a yearly basis. I am not aware of any additional costs."

"The price could be better."

"It is an open-source product from Microsoft."

"The tool's licensing costs are yearly."

"You can choose pricing from a variety of options. I would rate the product's pricing a six out of ten."

"There is no fee for the solution's community version."