The 13 Phases of the IF4IT Systems Development Lifecycle (SDLC) - Systems Development Lifecycle (SDLC) Best Practices
The 13 Phases of the IF4IT Systems Development Lifecycle (SDLC)
(Chapter 16 of Systems Development Lifecycle (SDLC) Best Practices)
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| 13-Phase SDLC | The complete IF4IT enterprise lifecycle superset. |
| Lifecycle Superset | A complete model from which approved Release-specific paths are selected. |
| Methodology Neutrality | Support for Agile, Waterfall, Hybrid, and supplier-led delivery without losing lifecycle outcomes. |
Quick Q&A
Question: Must every Release execute all 13 phases separately?
Question: Does the model apply to acquired SaaS?
Read More Below
This chapter defines the canonical 13-phase IF4IT SDLC as a complete enterprise lifecycle from initial need through retirement. It explains that the phases form a comprehensive superset that may be tailored through approved Paths and Utilization Profiles.
The Canonical 13-Phase Model
The IF4IT SDLC makes all major lifecycle responsibilities visible so enterprises can deliberately select proportional mechanisms rather than omit obligations informally. The model applies to Custom-Built, Acquired, and Composite Solutions and is neutral to Agile, Waterfall, and Hybrid delivery.
| # | Phase | Primary purpose |
|---|---|---|
| 1 | Intake & Strategizing | Qualify the need, opportunity, ownership, alignment, and authorization. |
| 2 | Research & Prototyping | Investigate feasibility, alternatives, suppliers, technologies, risks, and uncertainty. |
| 3 | Planning | Define the Path, Utilization Profile, resources, dependencies, Environments, evidence, and governance. |
| 4 | Requirements Capture | Establish stakeholder, functional, non-functional, operational, data, security, privacy, and acceptance requirements. |
| 5 | Design | Translate requirements into coherent architecture and detailed designs. |
| 6 | Implementation/Build | Build, acquire, configure, integrate, document, and prepare Release content. |
| 7 | Systems Integration Testing (SIT) | Verify integrated technical behavior, interfaces, data flows, dependencies, and controls. |
| 8 | User Acceptance Testing (UAT) | Validate acceptability for intended business and user use. |
| 9 | Training & Education (TRN/EDU) | Prepare users, administrators, Operations, Support, and other stakeholders. |
| 10 | Pre-Production Staging (PSTG) | Rehearse migration, cutover, rollback, support, and operational readiness. |
| 11 | Production (PROD) | Deploy or activate the approved Release and verify Production behavior. |
| 12 | Operations & Maintenance (OPS) | Operate, monitor, support, maintain, secure, improve, and close Releases. |
| 13 | Retirement, Decommissioning & Disposal | End capability use and obligations in a controlled, secure, compliant manner. |
How the Phases Work Together
Phases organize governed objectives and outcomes. Work may overlap, iterate, or occur concurrently, but dependencies, evidence, ownership, and progression decisions should remain explicit. Production is not the end of the lifecycle; Operations & Maintenance and Retirement remain essential.
Tailoring and Maturity
Not every Release needs equal formality, separate Environments, or identical Artifacts. The approved SDLC Path and Utilization Profile determine applicability and depth. Crawl uses minimum viable but controlled practices; Walk standardizes and makes them repeatable; Run integrates, automates, measures, and continuously improves them.
Connections to Related IF4IT Practices and Inventories
Connect the decisions and responsibilities addressed in this chapter to enterprise structure, capability ownership, and measurable business outcomes using the IF4IT Enterprise Model, Enterprise Capability Models, and the Capabilities Inventory and Attributes. 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.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. The 13 Phases of the IF4IT Systems Development Lifecycle (SDLC) | Systems Development Lifecycle (SDLC) Best Practices. https://if4it.org/best-practices/systems-development-lifecycle-sdlc/the-13-phases-of-the-if4it-systems-development-lifecycle-sdlc/ (accessed 2026-08-24).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers