rigorous testing such as regression testing, certification, product owner approval, and release build. The “definition of done” does not change during a sprint, but should be reviewed periodically and the government context, Agile represents a good development approach when customizing an existing system or commercial off-the-shelf (COTS) product, or building a small-scale or self-constrained application into an existing operational baseline, system, or platform. Although it may not be the easiest approach, the government can also use Agile to build a large IT system from the ground up; however, in this

document the environment specifications 1. Create a common build mechanism to create it on demand 2. Codified in automated environment build process iii. Environments will be stable, reliable, consistent consistent, & secure c. CREATE OUR SINGLE REPOSITORY OF TRUTH FOR THE ENTIRE SYSTEM i. ALL parts (code & environments) of the system are shared in a version control repository ii. Version control is for documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops was the highest

them.” 2. Accidents are due to the inevitable design problems in complex systems that we build; they are system problems – not individual problems iii. Effective practices 1. Blameless post-mortems interested in attending the meeting iv. Guidance 1. Pull all factual evidence (chat logs, etc.) to help build the timeline; any specific metrics observed, investigative paths taken, results, and other resolutions “could have” a. These are counterfactual statements b. Frames the problem as the system as imagined rather than the system that actually exists 4. Focus on – “Why did it make sense to me when I took that

said it?Frederick Brooks Jr. • Joined IBM in 1956 • Manager for the development of the IBM System/360 family of computers and the OS/360 software package • In 1975, published The Mythical Man-Month: the essence of the software problem • Buy versus build • Requirements refinement and rapid prototyping • Incremental development – grow, not build, software • Great designersRequirements refinement refinement and rapid prototyping • The hardest single part of building a software system is deciding precisely what to build • The most important function that software builders do for their clients is the

and last, that the business should be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led and managed through an inspect-and- adapt, feedback-and-vision-oriented approach dysfunctional transformation cycle. It lies, I believe, in our distinction between the development of a system and its operation and maintenance.  Dividing our IT spending into development and maintenance buckets way to incrementally modernize a legacy system as defined by Martin Fowler.  Instead of building an entirely new system, we take a small piece of the legacy system and rebuild it in a way that lets it

Logging Levels 1. Debug – anything that happens in the program 2. Info – user driven actions or system specific 3. Warn – conditions that could become an error and will likely trigger an alert 4. Error GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data access 3. System and application changes, especially privileged changes 4. Data changes (CRUD) 5. Invalid business model or product idea is to build the complete product to see whether the predicted demand actually exists.” ii. How to build a feature: 1. Ask, “Should we build it, and why?” 2. Perform cheapest

tools in place.  It is coded in a way that resists hard-to-find defects like concurrency errors. Build Versus Buy Everyone knows that in every case under the sun, in any example one can imagine, when making decisions, if an IT product can be acquired “off the shelf,” it is better to do so than to build it. This obvious fact is neat, plausible, and in most cases, wrong. The economics of software development systems that preserve many of the advantages of buying off the shelf.  The risk of developing a system incrementally and altering it based on user feedback is often lower than that of buying a finished

capabilities (how it will support future agility and how it will offer options in the future). Build Versus Buy: In a world where IT capabilities were delivered as a single “product” at the end of a risk, we should think of something we can do that will help us gain information to mitigate it. We build something, measure results, and thereby learn enough to cope with the uncertainty. “The purpose of “finished” late.  This, as we know, is based on the outdated idea that we define the scope of the system ahead of time and keep working until we deliver it. That is precisely what we do not do in an Agile

organization iii. ENABLING ORGANIZATIONAL LEARNING AND A SAFETY CULTURE 1. When we work within a complex system, by definition it is impossible for us to perfectly predict all the outcomes for any action we processes, often to help individual departments maintain their “turf.” Failure is processed through a system of judgment, resulting in either punishment or justice and mercy. c. Generative organizations OF RECORD AND SYSTEMS OF ENGAGEMENT i. Gartner Bi-modal IT 1. Type 1 – System of Record – “Doing it right” 2. Type 2 – System of Engagement – “Doing it fast” ii. DevOps helps reject the bi-modal IT

concisely define the desired system functions and provide the foundation for Agile estimation and planning. o They describe what the users want to accomplish with the resulting system. User stories help ensure One benefit of Agile is that once a budget has been established the program can be structured to “build to budget.” The funding that the program receives then drives the number of releases it can manage