10th June 2020

Manage change, no sweat!

Manage change, no sweat!

Using tools from Remain Software like TD/OMS and Gravity can make it easy to manage change throughout the development lifecycle.

TD/OMS and Gravity are Remain Software’s signature ALM and workflow solutions. They make the process of handling all aspects of development changes smooth and intuitive.

Both applications have been engineered to work the way developers think. They are a pair of robust tools, that facilitate exceptional collaboration, communication, transparency, oversight and fluidity. This pair of solutions from Remain Software pertain to:

  • Audit capabilities
  • Source archiving
  • Easy comparisons of source changes
  • Transfer and object histories,
  • and much more.

Manage Change, No Sweat!

Watch this video, presented by the Laura Hamway, MD of our Partners Remain Software, to understand how Remain’s TD/OMS and Gravity work together to help you easily manage change. In the video, you’ll see a walk through demonstration of TD/OMS and Gravity working together through the development lifecycle.

The demonstration outlines:

  • How easy and intuitively you can manage change through TD/OMS and Gravity
  • How TD/OMS and Gravity increase collaboration across all your teams – wherever they’re located
  • How effectively and efficiently you deploy applications and updates
  • Every step in the development lifecycle is also audited throughout the change management process.

 

The development lifecycle

When an end-user runs into a problem with their software, they open a ticket on their help desk, in this demonstration using Gravity.

Once the help desk receives the ticket, they’ll research the problem. This will involve going into TD/OMS to do an impact analysis, and gauge exactly how big of a change might be required.

It is then passed on to the developer, who will use Remain Software’s change management ALM tool, TD/OMS, to go through the development lifecycle, pick out the affected objects, and put those into development. They’ll do any programming changes, test it, and then signal the end-user to ratify or sign-off of the change.

Once sign-off is received, the objects are moved into production.

Posted by Joe on 10th June 2020.