on 08-09-2017 11:08 PM
Hi everyone-
I am looking to find out what are the explicit benefits of using the Requirements Management process in SOLMAN 7.2 instead continuing to use the 'traditional' requirements process such as (in our case) SharePoint and Excel. I am looking to make a business case to my managers on why switching over to SOLMAN for requirements management is a good idea, but so far it seems everything Requirement Management does is already available in these or other third party tools. Could someone please provide me with a rundown on what makes Requirements Management in SOLMAN 7.2 so unique it would be worth the initial cost of switching over to a new way of doing something? Thank you!
Hi Kelsey. Please find several benefits below:
As a result, by implementing Requirements Management in Solution Manager you will get following value:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Rodion- I appreciate the help.
I'd like to confirm the use of Project Management and Requirements Management areas of SOLMAN are not required in order to use SOLMAN's other features, specially the Change Management functional area and our ability to manage transports. I understand PPM/Requirements Management are integrated processes/functional areas and I want to be sure that any changes we put through can start by us creating a request for change (in response to an incident) or by directly creating a change document for new requirements if needed. Your thoughts on this would be appreciated- thank you!
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.