A question re. Change Request and CI selection - new business app scenario

[Tom Sienkiewicz]

Hi Everyone,

I would like to ask if there is a general best-practice for handling Changes - especially for creating new (business) applications. 

Let's imagine we need to create a new Business App to handle new functionality. This App would have DEV, QA, PROD environments.

Firstly, a Demand will be raised for this new app creation, assuming it is approved, then a Change gets created. Here's my questions:

What would you typically select as CI on such a change? As I am assuming the App Service for this business app does not exist yet. Would you have one change request record referring to the entire app somehow (e.g. an "empty" App service record), or would you create multiple changes and e.g. have one change to set up the server, another change for the DB instance, another one to create an interface to another app etc? Also would you have separate set of change tickets per each environment, or rather handle the migration to higher environments as part of one change lifecycle?

Looking for everyone's thoughts on this. Many thanks!

[Dr Atul G- LNG]

Hi @Tom Sienkiewicz 

Greetings!!

I worked as `change manager and ajppy to share my througtts

Firstly, a Demand will be raised for this new app creation, assuming it is approved, then a Change gets created. Here's my questions:

Atul: Yes, right process.

What would you typically select as CI on such a change? As I am assuming the App Service for this business app does not exist yet.

Atul:We first create a request (REQ) to request the creation of a new CI, AS, or other components. Once that has been created, we log a change. In the change, we include tasks for production deployments.

Also would you have separate set of change tickets per each environment, or rather handle the migration to higher environments as part of one change lifecycle?

Atul: We only use one change and three tasks for three different environments. Additionally, we added approval after each task to ensure everything goes smoothly and that the approver is kept informed.