environments matched Prod. They fixed forward, but changes not put back into version control. Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE 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 everyone in the value stream iii iii. Everything, everything, everything is checked into version control 1. Application code & dependencies 2. Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated

lie outside the control of the government program manager and his team. In the government context, Agile represents a good development approach when customizing an existing system or commercial off-the-shelf 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 the operational baseline. Several large acquisition programs, such as the Global Combat Support System-Joint (GCSS-J), have adopted Agile methods to build a future increment or block of capability.

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 2. Controlled “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 and behavior of libraries and components ii. Test suite becomes the living documentation of the system specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED

advance, and that we have a way to (try to) control them.  The relationship between uncertainty, risk, and change is far too complicated for such control when delivering IT systems, where complexity “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 consequences. In the plan-driven model, quality was easier to understand.  We specified what the system should do, and then measured quality as adherence to that specification.  The opposite of a defect

GIT is a version control system that is used for software development and other version control tasks. As a distributed revision control system it is aimed at speed, data integrity, and support for

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 TESTING INTO OUR RELEASE i. A/B testing requires fast CD to support ii. Use feature toggles to control experiments, cohort creation, etc. iii. Use telemetry to measure outcomes iv. Etsy open-sourced

Unlimited. Key Concepts The Three Ways [2] The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department. The outcomes of putting degradation, always seeking to increase flow, and always seeking to achieve profound understanding of the system (as per Deming). The Second Way is about creating the right to left feedback loops. The goal of daily work, creating rituals that reward the team for taking risks, and introducing faults into the system to increase resilience. Four Types of Work 1. Business projects 2. IT projects 3. Changes 4

dominated the IT world because it appears to offer predictability, control, and efficiency, the key values of the contractor-control model. But it doesn’t. Requirements: Requirements are a way of controlling used to set boundaries for developers when they began a project. In other words, a vehicle for control. But standardization also imposes costs by:  limiting agility and adding bureaucratic waste: exceptions 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

Kanban for the People! 2 Steve Miller Crucial Conversations (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 Adam Raggett Agile Transparency 1 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

approaches – is a confusion about how to deal with uncertainty and risk. What I call the “contractor-control paradigm” – is really about trying to make risk go away, when risk really the essence of what we 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