Define and enforce an application lifecycle - Proposed, Active, Deprecated, Retired

Overview

Applications without a defined lifecycle are applications managed by inertia rather than intention. They are added when someone requests them and they persist indefinitely unless a crisis demands their removal. They accumulate in the portfolio without discipline, consuming license, infrastructure, support, and operational resources long after their business value has declined below any rational justification for continued investment. The portfolio grows without deliberate management, becoming progressively more expensive, more operationally complex, and more difficult to govern with each ungoverned addition.

Best Practice

Define and enforce a formal application lifecycle with at minimum four stages, each with clearly defined characteristics and governance requirements. Proposed: identified as a need and under evaluation or development but not yet available for operational use. Active: approved, deployed, and available for its intended users and business purposes. Deprecated: scheduled for retirement and available for current users but no new adoption is permitted; a retirement date and user transition plan are defined and in progress. Retired: decommissioned and no longer available for operational use. Each stage transition requires defined criteria, formal governance approval, and appropriate stakeholder communication before execution.

Alongside the current lifecycle stage itself, capture the specific dates and milestones that mark each transition — when an application entered Proposed, when it went Active, when it was marked Deprecated, and its planned or actual Retired date. These dates make lifecycle velocity measurable (how long applications typically spend in each stage) and make overdue transitions visible (an application marked Deprecated for years without progressing toward retirement is itself a governance finding worth surfacing).

Together with the maturity staging addressed elsewhere in this document, this lifecycle model is the closest thing to a formal application portfolio management process or methodology that this document defines - deliberately distributed across governance, data, and maturity chapters rather than compressed into a single rigid procedure.

Benefit(s)

A formal application lifecycle gives the organization deliberate, governed control over the composition of its application portfolio at every stage. Applications enter and exit through governed processes rather than ungoverned accumulation and abandonment. The portfolio remains focused on applications actively delivering value in their current lifecycle stage. Resources are not indefinitely consumed by applications that have passed their useful operational life. Leadership has a clear, current view of what is in the pipeline, what is active, what is being phased out, and what has been retired - enabling better planning, resource allocation, and financial forecasting.