Why the 13 SDLC Phases Are a Customizable Enterprise Superset

This chapter explains why the IF4IT phase model is deliberately comprehensive and how enterprises adapt it without weakening required outcomes.

A Comprehensive Reference Model

A detailed superset exposes responsibilities that shorter models often hide, including supplier evaluation, training, staging, operational readiness, ongoing maintenance, Technical Debt, and retirement. The enterprise can then select a proportionate Path rather than pretending omitted responsibilities do not exist.

Customization Mechanisms

Customization should occur through standard SDLC Paths, Release-specific Utilization Profiles, risk-based depth, approved alternative methods, and explicit exceptions. Tailoring is not an undocumented decision to skip work.

Simplify Mechanisms, Preserve Obligations

Smaller or lower-risk work may use concise records, combined Activities, inherited evidence, shared Environments, and delegated Gates. The governing rule is: simplify the mechanism before eliminating the obligation.

This simplification scales with maturity. A Crawl-maturity enterprise might satisfy the superset for a low-risk Release with a single combined Planning-and-Requirements record and evidence inherited from a similar prior Release. The same class of Release at Walk maturity would use a standard Path with defined roles, a dedicated Utilization Profile, and tracked Gate decisions. At Run maturity, phase applicability and depth would be recommended automatically from Solution characteristics and simply confirmed by an accountable owner.

Example

A minor SaaS workflow configuration may use Planning, Requirements Capture, configuration validation, UAT, PROD, and OPS. A regulated data pipeline may also require Design, SIT, data-quality validation, migration rehearsal, security review, and audit evidence. An AI-assisted underwriting service may require Research and Prototyping, model validation, bias testing, human-override design, monitoring, and drift controls. The 13 phases provide an enterprise superset: each initiative selects the phases needed for its risks and outcomes rather than treating every phase as mandatory in identical form.

Common Antipatterns

Enterprises should avoid assuming every one of the 13 phases must be used at full depth for every Release. The 13 phases form a comprehensive enterprise superset meant to be tailored down through approved Paths and Utilization Profiles, not a mandatory checklist every Release must satisfy identically; assuming full-depth application everywhere creates unnecessary ceremony for low-risk work.

Connections to Related IF4IT Practices and Inventories

The IF4IT Enterprise Model, Enterprise Capability Models, and the Capabilities Inventory and Attributes keep this chapter’s decisions and responsibilities connected to enterprise structure, capability ownership, and measurable business outcomes. Use Application Portfolio Management (APM) Best Practices and the Applications Inventory and Attributes to place this SDLC decision in the context of application ownership, portfolio value, lifecycle state, and dependencies.

For Why the 13 SDLC Phases Are a Customizable Enterprise Superset, IT leaders and managers should establish explicit decision rights, accountable ownership, proportional controls, evidence expectations, performance measures, and continuous-improvement feedback tied to enterprise value.