5 FAM 690

INCREMENTAL DEVELOPMENT POLICy

(CT:IM-203; 11-08-2017)

(Office of Origin: IRM/BMP/SPO/PMD)

5 FAM 691 SCOPE

(CT:IM-203; 11-08-2017)

This policy applies to all Department information technology (IT) acquisitions for both major and non-major IT investments. The policy provides requirements for modernization efforts of the Department's software, hardware, or IT services. This policy is designed to align to 5 FAH-5 H-210, Managing Department of State Projects.

5 FAM 692 AUTHORITIES

(CT:IM-203; 11-08-2017)

The authorities establishing this policy include:

(1) Public Law 104-106, Information Technology Management Reform Act of 1996 (ITMRA) (Clinger-Cohen Act);

(2) Public Law 107-347, E-Government Act of 2002;

(3) Capital Programming Guide, Supplement to OMB Circular A-11, Part 7: Planning Budgeting, Acquisition and Management of Capital Assets

(4) OMB Memorandum (M-15-14); Management and Oversight of Federal Information Technology); and

(5) Federal Information Technology Acquisition Reform (FITARA) is Title VIII Subtitle D Sections 831-837 of Public Law 113-291 - Carl Levin and Howard P. "Buck" McKeon National Defense Authorization Act for Fiscal Year 2015.

5 FAM 693 DEFINITIONS

(CT:IM-203; 11-08-2017)

Capability: System functionality is defined by the government to meet a specific required need. All capabilities should have clearly defined objective technical completion criteria. Capabilities are typically found at or above the control account level of the work breakdown structure (WBS) and are usually composed of multiple features.

Control account: Term used to describe the lowest element of the work breakdown structure (WBS) assigned to discrete scope/schedule/budget.

Functionality: Refers to a group of features that are traceable to the technical and operational requirements of the product being delivered.

Incremental development: A development process in which hardware and/or software capability is delivered in increments, recognizing up front the need for future improvements. Each increment is functionally useful and a supportable operational capability. Each increment goes through the entire design cycle of prototyping, testing, and release. A production release containing useable functionality is normally provided at least every 6 months as per OMB capital planning guidance.

Modular-based development: A design in which hardware and software components are designed to be independently sustainable. The goal is for each module to stand on its own and interface to the required components via a standard set of Application Programming Interfaces (APIs).

System Development Lifecycle (SDLC): A framework for developing, maintaining, and replacing IT systems. This framework ensures operations in accordance with security policies and performance as defined by stated requirements.

5 FAM 694 General POLICY FOR INCREMENTAL DEVELOPMENT

(CT:IM-203; 11-08-2017)

a. Project managers must pursue IT acquisitions and/or in-house IT development that uses an incremental approach to delivery of IT products and services. IT acquisitions must include a clause requiring incremental development during any modernization or enhancement efforts.

b. Adequate Incremental Development is the delivery of a fully tested and releasable increment of software or services to the end users every 6 months or less after the start of the development phase. This releasable increment must provide defined value to end users through additional or enhanced functionality.

c. The Chief Information Officer (CIO) certification of incremental development methodology is required and achieved as part of the certification process for the Department's IT portfolio administered by the E-Gov Program Board 5 FAM 914.

d. For non-incremental IT solutions, CIO approval is required as part of the capital planning selection phase to ensure risk is identified up front and assessed appropriately 5 FAM 914.

e. For the purposes of reporting and the control of IT investment (5 FAM 1043):

(1) A specific capability must be identified for each release; and

(2) Production-ready releases must be reported as distinct milestones to support Earned Value Management (EVM) assessment.

f. For all deployments, a Post Implementation Review (PIR) must be completed and posted in iMATRIX to validate benefits to project stakeholders and the Department (5 FAM 1044.1).

5 FAM 695 THROUGH 699 UNASSIGNED