Software Change Requests

How do you currently manage software change requests?

Software Developers send software change requests by email and paper, creating confusion. Application Support teams then must evaluate and forward the requests to the correct group. Each location has a unique set of services, making change requests difficult to assign to the right party. Approvals for updates and versions have no structure in place, often delaying a release with no repository for status updates and documented approvals.

Streamlining and automating the process

Using Nutrient Workflow, the software change management and approval process  can be completely automated. Developers use a web browser to submit and check on the status of software change requests. They know who is handling the request and who approved it.

Nutrient Workflow uses business rules to determine the group responsible for the technologies or services and routes the request automatically through the proper approval channel. The Application Support team receives the approved request for fulfillment.

click for larger

Implementing software change management

The company assigns administrators to Nutrient Workflow to implement the process rules and any forms that will be used to gather information. Nutrient Workflow automatically sends the web and email approval notifications to the appropriate personnel, reducing the chances of confusion while maintaining the current status of the request.

For example, an employee needs to submit a request to receive approval on an application change. The request goes directly through the pre-defined approval process via e-mail. All approvals are documented. Meanwhile, the company’s QA team is notified for testing and debugging. Nutrient Workflow notifies the employee and provides status updates as the process goes through approvals and testing. Nutrient Workflow supports any comments or information that is added to the request by anyone involved in the software change management process.