Training and Education (TRN/EDU) Phase of the Systems Development Lifecycle (SDLC)

Defines the IF4IT SDLC phase in which employees, consultants, suppliers, administrators, operators, support teams, and other affected stakeholders are prepared to use, operate, govern, support, secure, maintain, and sustain the approved Solution and Release.

Purpose

The Training and Education phase prepares the people and functions affected by the Release to perform their responsibilities competently when the Solution enters Production and Operations. It converts approved workflows, controls, procedures, support models, and technical knowledge into role-appropriate learning and readiness outcomes rather than treating training as a final communication activity.

Typical Inputs

Inputs may include the accepted Solution baseline, approved business and operational processes, role and access models, user and administrator procedures, support and escalation models, Security and Privacy obligations, accessibility needs, supplier materials, known limitations, Release timing, and UAT findings.

Core Activities

Identify affected audiences and required competencies; perform training-needs analysis; define learning objectives; create or adapt role-based materials; prepare instructors and support personnel; configure representative training Environments and data; deliver instruction, demonstrations, exercises, simulations, and knowledge transfer; evaluate understanding and task performance; remediate gaps; and update authoritative procedures and support knowledge.

Training Quality and Validation

Training should reflect the approved Release and active role responsibilities, use accessible and representative materials, distinguish awareness from demonstrated competence, and avoid exposing sensitive Production information. Validation may include knowledge checks, task demonstrations, simulations, supervised practice, attendance only where appropriate, support-readiness exercises, and confirmation that practitioners can perform critical duties without relying on undocumented personal knowledge.

Outputs and Evidence

Outputs may include the training and education plan, audience and competency matrix, curricula, instructor and participant materials, demonstrations, exercises, attendance and completion records, assessment results, remediation actions, updated procedures, knowledge-transfer records, support-readiness evidence, and identified post-Production learning needs.

Decision and Exit Criteria

Exit requires that required audiences have received or have scheduled governed preparation, critical roles demonstrate sufficient readiness, materials align with the approved Release, unresolved competence gaps are owned and risk-governed, operational and support teams can perform required tasks, and continuing education or post-Production reinforcement is planned where needed.

Application Across Solution Types and Methods

For Custom-Built Solutions, training should address enterprise-specific workflows, administration, support, and engineering knowledge. For Acquired Solutions, supplier content should be adapted to the enterprise configuration, integrations, controls, and operating model. Composite Solutions require end-to-end learning across component and supplier boundaries. Waterfall may deliver planned training waves; Agile and Hybrid delivery may use incremental learning while preserving Release-level readiness.

Crawl-Walk-Run Maturity

At Crawl maturity, identify affected roles, provide current materials, prepare critical operators and users, and record completion. At Walk maturity, use competency-based curricula, representative exercises, reusable role paths, and integrated support-readiness validation. At Run maturity, use continuously updated learning, telemetry-informed reinforcement, embedded guidance, automated content synchronization, and measured competence outcomes.

Common Antipatterns

Enterprises should avoid treating training as a one-time communication rather than demonstrated readiness. Sending an announcement or a slide deck about an upcoming change does not confirm that the people who must operate, support, or use the Solution can actually perform their new responsibilities.

Connections to Related IF4IT Practices and Inventories

Use the IF4IT Enterprise Model together with Enterprise Capability Models and the Capabilities Inventory and Attributes to anchor this chapter’s decisions in 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.

Apply Service Management Best Practices and Service Catalog Best Practices to define operational ownership, support models, service levels, monitoring, knowledge transfer, and customer-facing service commitments before and after Production.

Use Release Management guidance alongside IT Operating Environments Best Practices and Agile, Waterfall, or Hybrid: An IF4IT Framework for Choosing Delivery Methodology to govern how Release scope, environment progression, deployment evidence, cutover, rollback, and closure are actually managed.