What to look for in application change management [New tech brief]

Application change management is all about demonstrating that you have control over the change process in your organization.

That’s a tall order in an Oracle or PeopleSoft environment, where your coworkers are constantly making changes — code modifications, versioning, migrations — that affect your applications.

Of course, we’re past the day when you can track all that change manually or in spreadsheets, which is why application change management software exists: to track the reason for the change, who requested it, who authorized it and exactly what changed.

We’ve put together a new tech brief called Mastering the Art of Version Control and Migration Management with Stat. It takes you through five of the most important application change management features to look for and shows you how we implement them in Stat.

  1. Issue tracking and automated workflows – Every change, including code changes and user activity, needs to be captured and tracked as an issue. As each issue progresses from initial request through production, automated workflows ensure that the correct people approve and act on the request when needed. Workflows also prevent changes from being deployed before they’re ready.
  2. Security around the change process – How do you ensure that only authorized staff can make and approve changes? Proper application change management calls for different privileges and roles in the change process, with adequate password protection.
  3. Segregation of duties – By transferring ownership of the issue at each stage in the change lifecycle, you enforce the healthy segregation of duties needed for compliance. Specifying status and transfer rules lets you control the issue at any given stage.
  4. Version control and object management – Oracle applications are filled with exceptions: customizations and extensions needed for user requirements, seeded objects with interdependencies on other objects, changes to application setups, and Application Object Library (AOL) objects not covered by most version control tools. Being able to version such a wide variety of objects is important.
  5. Protection against overwrites – The essence of change management is preventing developers from overwriting one another’s code. By locking and reserving objects, the change management software ensures that a single developer is working on them at any time.

Read our tech brief to round out your checklist of what to look for in application change management. You’ll find enough details and screenshots on Stat to see whether it meets your organization’s needs.