Application Lifecycle Management

Purpose

Application Lifecycle Management (ALM) is one of the four pillars of ConfigCompare.

It focuses on managing configuration changes as they progress through the software delivery lifecycle, from development through test, UAT, and production.

This chapter describes the pillar in practice, applying the concepts introduced in Chapters 03 to 10. The four pillars are introduced together in Chapter 02.

This chapter describes concepts and behaviour; step-by-step operating guidance sits outside this reference.

Configuration progression

Configuration changes occur continuously throughout the development and deployment lifecycle.

Rather than treating each environment as independent, ALM governance validates configuration as it moves through the lifecycle in a controlled and predictable manner.

Typical ALM scenarios

ALM addresses Configuration Governance questions including:

Did configuration promote correctly from DEV to TEST?
Was TEST configuration as expected before UAT began?
Is UAT configuration aligned with approved GOLD configuration?
Did production deployment complete successfully?
Are post-deployment results as expected?
Has an environment refresh maintained configuration consistency?
Were production values left in place that should have been changed?
Did the release validation pass governance gates?

Environment-to-environment validation

ALM uses ConfigCompare to validate configuration at each stage of the deployment pipeline:

DEV to TEST validation: confirm configuration promotion before test begins.
TEST to UAT validation: confirm test configuration is ready for business users.
UAT to PROD validation: validate that approved UAT configuration moved to production.
Post-deployment validation: confirm production configuration matches deployment expectations.
Gold configuration promotion: verify that reference configurations are promoted correctly across regions or business units.
Environment refresh validation: verify that refreshed environments retain required configuration.

Implementation-phase validation

Configuration Governance applies from the earliest stages of an implementation, before a deployment pipeline is in regular use:

Business process workshops and reviews: validate that configuration matches the business process requirements agreed during design.
ISV assessment: capture a Snapshot before and after installing an ISV solution to establish exactly what the solution changed.
Conference room pilot preparation: verify configuration ahead of a pilot, and compare the start and end of the pilot to see everything that changed during it.
Mock go-live: rehearse cutover against verified configuration rather than assumed configuration.
Go-live: transition on evidence that the production environment holds the configuration that was signed off.
Global rollout: keep configuration consistent as it is extended to further legal entities, regions and production environments, including geo-restricted and cross-tenant implementations.

Governance gates

ALM enables organisations to establish governance gates throughout the deployment lifecycle.

Gates confirm that configuration meets approval requirements before advancing to the next phase:

Pre-deployment gate: configuration must pass validation against approved baselines.
Deployment gate: release can proceed only after configuration is confirmed ready.
Post-deployment gate: environment can be released to users only after validation is complete.

Gates reduce deployment risk by preventing problematic configurations from reaching production or user environments.

Business outcomes

ALM governance is typically adopted to deliver:

Reduced deployment risk: configuration is validated before each promotion.
Fewer deployment failures: configuration issues are detected early rather than during deployment.
Lower deployment costs: rollbacks and post-deployment fixes are avoided.
Faster deployments: promotion through environments proceeds on validated evidence.
Improved confidence: stakeholders know configuration has been validated at each stage.
Release discipline: clear gates and validation criteria apply throughout the pipeline.
Audit readiness: evidence exists that configuration changes followed controlled processes.

ConfigCompare in ALM

ConfigCompare provides the deterministic evidence that ALM governance requires.

By comparing configuration at each stage of the lifecycle, ConfigCompare enables organisations to:

Validate promotion correctness
Identify unexpected Differences before they reach critical environments
Identify undesired Matches, such as production endpoints remaining in a downstream environment such as UAT after a database restore
Provide evidence of controlled change
Support consistent configuration across similar deployments
Make informed go/no-go decisions at deployment gates