develop software. The values and 12 principles of the Agile Manifesto can be distilled into four core elements:  Focusing on small, frequent capability releases  Valuing working software over amount of work the team estimates it can deliver in a sprint Development teams, aided by cross-functional representatives, analyze each user story and use measures known as story points to estimate the limited to the application layer while using existing infrastructure. Program Scope Program spans core capabilities and underlying platform or infrastructure. The government is responsible for primary

steward the asset that is the total of all of the enterprise’s IT capabilities—an asset that has functional capabilities (how it is used today) but also latent capabilities (how it will support future agility is the point at which we are finished investing and just need to “maintain.” But unless we want functional and technical debt, a lumpy EA, and a need to do an expensive and risky transformation effort the feature is ready for deployment when it passes all of its tests. But is quality a simple yes-or-no attribute? If it passes its tests, is it high quality? And how can we assess the quality of something

Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This struggling with changes – Hard line: no changes would be accepted into GWS without accompanying automated tests. Spread Testing Grouplet team approach. Google – single, share repository of billions of files. 50% of code is changed each month. 40K code commits/day, 120K automated test suites, 75M tests cases/day e. CONTINUOUSLY BUILD, TEST, AND INTEGRATE OUR CODE AND ENVIRONMENTS i. Create automated test

every Google property d. SPREAD KNOWLEDGE BY USING AUTOMATED TESTS AS DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components ii FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast flow, deployability, and operations will derive NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS issues unaddressed due to schedule and budget constraints ii. Automate as many security controls and tests as possible and incorporate into the pipeline iii. Enable fast feedback on potentially insecure

Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE, CHRONIC CONFLICT i. Among them are the two following goals, which must be pursued simultaneously: generate measurable improvement or actionable data within weeks f. RESERVE 20% OF CYCLES FOR NON-FUNCTIONAL REQUIREMENTS AND REDUCING TECHNICAL DEBT i. Don’t just make the interest payments, pay down the b. ORGANIZATIONAL ARCHETYPES i. Functional-oriented 1. Optimized for expertise, division of labor, or reducing cost ii. Matrixed-oriented 1. Combines functional and market orientation 2. Often results

practices at enterprise scale Synchronizes alignment, collaboration and delivery for large numbers teams Core values:  Code quality - can't scale crappy code  Program execution  Alignment  Transparency have time to change their minds" - Mary PoppendieckTeam -> Program -> Portfolio Team  Cross functional  Scrum  Release cadence  HIP Program  Built on Scrum, except scaled up  self-organizing

shifted to the left through automated unit, functional, integration, and security testing - this is a key DevSecOps differentiator since security and functional capabilities are tested and built simultaneously favor small, incremental, frequent updates over larger, more sporadic releases.  Apply the cross-functional skill sets of Development, Cybersecurity, and Operations throughout the software lifecycle, embracing

David Genn (IG) @david_genn  Separate deployment from release  Automate everything  Trust your tests  Conversations are way better than project proposals  Start small, be brave quickly  Seize

built automatically using Continuous Integration, and it is tested automatically through scripted tests.  It is deployed automatically with automated deployment tools onto infrastructure that can be

for Defense Agile Coaching by Darin Plum Aug 6, 2014 1 My Take on Agile Coaching  The core to all Agile is maximizing each individuals potential through autonomy and mastery  Agile is a journey