Intake and Strategizing Phase of the Systems Development Lifecycle (SDLC)

Defines the first IF4IT SDLC phase, in which an enterprise identifies a need or opportunity, establishes strategic context, determines preliminary ownership and lifecycle scope, evaluates whether action is warranted, and authorizes or rejects further investigation.

Purpose

The Intake and Strategizing phase converts an idea, problem, mandate, Incident trend, technology opportunity, supplier event, obsolescence condition, or retirement need into a governed lifecycle candidate. It establishes why the work matters, which enterprise outcomes may be affected, who owns the decision, and whether the enterprise should invest in Research and Prototyping, Planning, immediate remediation, or no further action.

Typical Inputs

Inputs may include stakeholder needs, strategy and capability gaps, regulatory or contractual obligations, operational Problems, Security or Privacy concerns, customer feedback, Technical Debt, supplier changes, technology obsolescence, audit findings, market opportunities, and proposed Product or Service changes. Existing inventories, Architecture, roadmaps, metrics, and lifecycle records should be consulted before creating duplicate or conflicting initiatives.

Core Activities

Clarify the need and intended outcomes; identify affected capabilities, Assets, Products, Services, Systems, Applications, Solutions, data, stakeholders, and suppliers; assign a preliminary sponsor and enduring owner; classify the likely Solution and sourcing path; identify major constraints, assumptions, Risks, dependencies, urgency, and strategic alignment; consider reuse, acquisition, change, replacement, or Retirement options; and determine the next governed action.

Outputs and Evidence

Outputs may include an intake record, problem or opportunity statement, preliminary scope, strategic alignment, stakeholder and ownership record, affected-inventory links, initial Risk and dependency view, candidate Solution classification, preliminary success measures, decision rationale, and authorization for the next phase. The detail should be proportionate and should not imitate a completed business case or Design.

Decision and Exit Criteria

The authorized decision should approve further research or planning, route the need into an existing Product or operational backlog, require immediate corrective action, combine it with related work, defer it with ownership and triggers, or reject it with rationale. Exit requires a clear problem or opportunity, accountable ownership, an identified next path, and preserved decision evidence.

Application Across Solution Types and Methods

For Custom-Built work, Intake should test whether new development is justified and whether reusable capabilities exist. For Acquired Solutions, it should identify market and supplier implications without prematurely selecting a Product. For Composite Solutions, it should identify likely component paths and end-to-end accountability. Waterfall, Agile, and Hybrid methods begin only after the enterprise has established enough context and authority to govern the work.

Crawl-Walk-Run Maturity

At Crawl maturity, use a controlled intake form, named owner, basic classification, and explicit decision. At Walk maturity, integrate intake with Architecture, portfolio, Product, Risk, and inventory systems. At Run maturity, use enterprise knowledge, metrics, dependency analysis, and automated routing to identify reuse, duplication, strategic conflicts, and likely lifecycle obligations while retaining human decision authority.

Common Antipatterns

Enterprises should avoid treating Intake as a rubber stamp rather than a governance decision. Approving a request without establishing real ownership, scope, or affected capabilities lets poorly framed work enter the lifecycle, where the cost of correcting a wrong assumption grows with every phase that follows.

Connections to Related IF4IT Practices and Inventories

Use the Designing, Building, and Maintaining Comprehensive and Usable Enterprise Capability Models guidance and the Capabilities Inventory and Attributes to connect proposed work to capability gaps, strategic outcomes, affected value streams, and investment priorities. Apply Application Portfolio Management (APM) Best Practices and consult the Applications Inventory and Attributes when evaluating reuse, modernization, acquisition, investment priority, ownership, and portfolio dependencies.

Apply Release Management guidance together with IT Operating Environments Best Practices and Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology to keep Release scope, environment progression, deployment evidence, cutover, rollback, and closure properly governed.

Each Release should read authoritative lifecycle records and update affected inventories, identifiers, relationships, ownership, status, evidence, configuration, and retirement information as governed outputs, per Enterprise Inventory Management Best Practices.