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 all of the DoD’s IT acquisition challenges, but offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint force will be smaller and never know less than on the day you begin your new project. Each incremental delivery / review cycle adds knowledge and provides insights that the team could have never known when initial requirements

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

have to make:  Option 1: These techniques, if we use them correctly, enable a fast try-and-learn cycle in which developers can produce something, get feedback, and then adjust what they have produced opportunity for, um, “vigorous discussion.”  Every quarter, I would do something I called a release cycle review , and then we would go back to the Star Chamber for an update discussion. How to

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

platforms up to date.  There is a deeper problem at the root of this dysfunctional transformation cycle. It lies, I believe, in our distinction between the development of a system and its operation and capabilities at least match those of the legacy system. Because this usually takes a while, the first release of the new system doesn’t come for quite some time, which works against the Agile principle of delivering

and outages.  Trying things out is a way of learning in the Agile world; it is a kind of feedback cycle that lets us make good decisions in the normal course of work.  Let’s say that we are deciding at: https://git.io/Jejqb Share Your Feedback As we've come to learn on our agile journey, short cycle times and rapid feedback are the lifeblood of Lean and Agile software development practices. After

bowl. How many matches do you think we can move through the line each time we go through the cycle? 3.5 is the average of the 6 numbers on the dice. Make it interesting. Let’s say that everyone

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