BMC Compuware ISPW Previous Solutions
BM
Brenda Martin
Sr Consultant Project Manager with 10,001+ employees
Standardization was a key reason for switching. It was critical to standardize all of the development processes under a common Source Statement Management system. Before we converted to ISPW we were running 3 different systems at 3 different affiliates to manage source code. We converted those 3 affiliates to ISPW so that we could interchange our development resources without having to retrain personnel. Also, the old systems that we were using were very expensive and ISPW's price point was extremely attractive. It gave us more flexibility in being able to more development resources from one affiliate to another and the ability to standardize processes which allowed us to cut down on the number of people needed to maintain the different systems.
View full review »RJ
Mainframfb71
Mainframe Architect at a financial services firm with 5,001-10,000 employees
We used Serena/Micro Focus ChangeMan for this functionality and we switched for cost and functionality reasons. There is a lot more functionality with ISPW and there is clearly a lot more effort in the continued development of ISPW. ChangeMan was somewhat languishing. They didn't really update it much.
View full review »We used LCM: Life Cycle Manager (ASG: Allen Software Group). We changed production because the support and evolution of the product were in risk and because it was not available in Eclipse IDE.
View full review »Buyer's Guide
BMC Compuware ISPW
April 2024
Learn what your peers think about BMC Compuware ISPW. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
768,578 professionals have used our research since 2012.