Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

Defines a governed method for selecting Waterfall, Agile, Hybrid, or another delivery approach according to the work rather than habit or fashion.

Best Practice: Establish the Governing Principle for Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

Select delivery methodology according to uncertainty, risk, dependencies, reversibility, evidence needs, sourcing, stakeholder context, and operational consequences while preserving required SDLC outcomes.

Benefits: Selecting methodology based on uncertainty, reversibility, and stakeholder context — while still preserving required SDLC outcomes — means the choice actually fits the work’s real characteristics, rather than defaulting to whichever methodology happens to be organizationally fashionable at the moment.

Best Practice: Define Required Lifecycle Treatment for Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

Benefits: Allowing different components of a Composite Solution to use different methods, rather than forcing one label across the whole Solution, means each component’s delivery approach can actually match its own uncertainty and coordination needs instead of compromising to fit a single enterprise-wide choice.

Best Practice: Apply Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work Throughout the SDLC

Apply this discipline across the full lifecycle, from Intake through Retirement. Establish applicability and ownership during Planning, translate it into testable requirements and decisions during Design and Build, generate decision-ready evidence through SIT, UAT, and Staging, verify and monitor it in Production and Operations, and close out remaining obligations at Retirement.

Benefits: Establishing the chosen methodology’s implications as early as Intake and Planning means downstream phases inherit clear expectations about cadence and evidence generation, rather than discovering mid-Release that the methodology choice was never actually translated into concrete lifecycle treatment.

Best Practice: Govern Decisions and Preserve Evidence for Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

Assign clear ownership — an enduring Solution owner, Release Owner, discipline owner, evidence producers, and Risk Owner — and scale rigor to the work’s criticality, complexity, and reversibility. Record Risks, exceptions, and Technical Debt in authoritative systems, not narrative status. Generative AI may assist with analysis and evidence organization, but only accountable roles may approve outcomes, accept Risk, or authorize Production.

Benefits: Scaling rigor to criticality and reversibility regardless of chosen methodology keeps governance depth tied to actual Risk, preventing a fast-moving Agile team from mistakenly assuming methodology speed also reduces the evidence and accountability a high-consequence Release genuinely requires.

Best Practice: Advance Maturity Deliberately for Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

At Crawl maturity, select delivery methodology informally based on the Release Owner’s judgment and team familiarity, documented briefly in the Utilization Profile. At Walk maturity, apply published selection criteria consistently, with the rationale recorded and reviewed against similar prior Releases. At Run maturity, generate an initial methodology recommendation from Solution characteristics and historical outcomes, with an accountable owner confirming or overriding it before it governs the Release.

Benefits: Informal, judgment-based selection at Crawl maturity is enough to make a reasonable choice without requiring a formal selection framework the enterprise doesn’t yet have. Applying published criteria consistently at Walk maturity means similar work receives genuinely comparable methodology treatment instead of depending on whoever happens to be the Release Owner. Generating an initial recommendation from historical outcomes at Run maturity accelerates routine selection while keeping a human owner accountable for confirming it actually fits the work.

Best Practice: Avoid Common Antipatterns in Select Delivery Methodology for the SDLC Based on the Characteristics and Risks of the Work

Enterprises should avoid treating Agile as inherently more mature than Waterfall. Delivery methodology should be selected based on the characteristics and risks of the specific work, not treated as a maturity hierarchy; assuming Agile is always the more advanced or preferable choice can lead to selecting a methodology poorly suited to the work’s actual uncertainty, reversibility, and coordination needs.

Benefits: Avoiding this antipattern keeps methodology selection grounded in what the work actually needs, not in organizational fashion. It ensures a genuinely sequential, high-coordination effort gets appropriately planned treatment instead of an Agile label applied for its own sake.

Connections to Related IF4IT Practices and Inventories

Use Technology Portfolio Management (TPM) Best Practices, the Software Technologies Inventory and Attributes, and IT Operating Environments Best Practices to connect the decisions and responsibilities addressed in this chapter to governed technology choices, platform lifecycle, and environment controls.

Apply Release Management guidance together with IT Operating Environments Best Practices to govern Release scope, environment progression, deployment evidence, cutover, rollback, and closure regardless of the selected delivery methodology.