i Approved for Public Release; Distribution Unlimited. 14-0391ii Executive Summary The Department of Defense (DoD) needs an acquisition framework for information technology (IT) that and their application in DoD programs. The foundational structure of an Agile program is: Release - Capability delivered to users, composed of multiple sprints Sprint - Priority capabilities developed activities and assess progress and impediments3 A release comprises a series of sprints. As an example, consider Figure 2, which depicts a six-month release with a series of one-month sprints. During each

Deployment & Release are distinct with different purposes ii. Deployment – installing a specified version to a given environmentiii. Release – when a feature is made available to customers. 1. Release of functionality actions, release becomes a business decisions, not a technical decision v. Environment-based Release Pattern – multiple environments available, only one is receiving live traffic. Release performed Application-based Release Pattern – modify application to selectively release functionality by small configuration changes. Feature flags, dark launching h. ENVIRONMENT-BASED RELEASE PATTERNS i. Enables

Even so, the program must maintain a big picture, long-term view and focus on the next six-month release.  DO epics and user stories to concisely define the desired system functions and provide the foundation reviews during the release planning phases. To demonstrate functionality and provide insight into the program’s progress, these reviews should focus on the relatively small scope of a release and how it aligns aligns to the enterprise architecture. Similar technical reviews can be decomposed to the release level.  DO continuous planning at every levelSystems Engineering Role Program leaders must encourage

Team  Cross functional  Scrum  Release cadence  HIP Program  Built on Scrum, except scaled up  self-organizing, self-managing team-of-agile-teams  release trains  working off a single backlog backlog of features, driven by vision and roadmap  product and release management, release planning  program psi objectives  common sprint lengths - system continuous integration  architectural runway management, enterprise architect  value streams  investment themes - provide operating budgets for release trains SAFe v3.0 - late July 2014  develop on cadence, deliver on demand  strategic themes

(Agile Book Club!) 0 Nick Tuck Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Ray Page Release Planning 2 Darin Plum Agile Coaching 5 Nick Wenner Clean Coder (book review) Book Overview 2 Brandon McAllister Automation 2 Ron Horner Kanban for the People! 2 Ray Page Release Planning 2 Nick Wenner Clean Coder (book review) 2 Scott Grimes Agile Certifications 2 Jason Smith Eric Collins The Servant: Agile Book Club 1 Nick Tuck Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Agile Transformation Agility Health Radar 1 Steve Barr DevOps: A Horse's

defense.gov/Portals/0/Documents/DoD%20Enterprise%20DevSecOps%20Reference %20Design%20v1.0_Public%20Release.pdf?ver=2019-09-26-115824-583 DevSecOps – Defined by DoD CIO DevSecOps is an organizational software monitor, and apply security at all phases of the software lifecycle: plan, develop, build, test, release, deliver, deploy, operate, and monitor. In DevSecOps, testing and security are shifted to the left application can be deployed into the production environment. Deployment frequency: how often a new release can be deployed into the production environment. Production failure rate: how often software fails

If negative results, ideally feature toggle off and fix-forward or use other Blue- Green, Canary release patterns b. DEV SHARES PAGER ROTATION DUTIES WITH OPS i. Complex systems will inevitably have unexpected also increase maintenance costs and identify opportunity costs. d. INTEGRATE A/B TESTING INTO OUR RELEASE i. A/B testing requires fast CD to support ii. Use feature toggles to control experiments, cohort great metric to publish widely is how many meetings and work tickets are mandatory to perform a release – the goal is to relentlessly reduce the effort required for engineers to perform work and deliver

Development has worked on is released to production deployment. Like in manufacturing, this large batch release creates sudden, high levels of WIP and massive disruptions to all downstream work centers, resulting Successful Brownfield transformations 1. CSG – COBOL mainframe and supporting applications a. They 2X release frequency b. Resulted in increased application reliability c. Reduced deployment lead time from ensuring service levels are met v. Infosec – team responsible for securing systems and data vi. Release Managers – the people responsible for coordinating the production deployment processes vii. Technology

Acquisition) https://www.acq.osd.mil/evm/ Incremental process, i.e. Rolling Wave Planning; Agile Release/Program Increment Planning. Scenario describes one method of how Agile can underpin EVM progress SW program implementing an Agile development process • The scenario has defined a single product Release which is tracked using Earned Value • Shows alignment of EVM WBS elements to the Agile products

Version Control Comparison Dr Mark Roth Release It (Agile Book Review) Aug 2014 Ray Page Release Planning Darin Plum Agile Coaching Nick Wenner