Focusing on small, frequent capability releases  Valuing working software over comprehensive documentation  Responding rapidly to changes in operations, technology, and budgets  Actively involving Programs can adopt Agile practices within current policy by tailoring program processes and structure to deliver releases every 6–12 months. The DoD can apply Agile practices to the full range of IT Program managers should evaluate the environment, constraints, and objectives to determine the right structure and methods to apply. Agile requires a set of processes, roles, and culture that will take time

AUTOMATED TESTS AS DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components ii. Test suite becomes the living documentation of the system continuous inspection, automated testing to achieve outcomes intended with controls. e. ENSURE DOCUMENTATION AND PROOF FOR AUDITORS AND COMPLIANCE OFFICERS i. DevOps challenges the traditional notions

 Use Dan Pink’s Autonomy, Mastery, Purpose to create an engaged organization  Organizational Structure: Coach should have ability to interact freely with all levels of an organization Coach to your

Planning DOs and DON’Ts  DO establish some high-level planning, requirements, processes, and structure; however, activities focus on what teams can develop and field in the next few releases.  DON’T

attractors - phenomena that arise when small stimuli & probes resonate with people. They provide structure & coherence as they gain momentum. • Encourage dissent & format debate - allow rigorous review

i. Don’t practice “Mean Time until Declared Innocent” – culture of blame encourages limited documentation, hiding telemetry, deflection 1. Prevents creation of institutional knowledge about incidents incidents 1. Bad pull requests – typically doesn’t have enough context for the reader, little documentation of the changes intended outcome, or explanation of the thought process behind the change 2.

potential implications, or to merely rubber stamp their approvals c. Creating large volumes of documentation of questionable detail which become obsolete shortly after they are written d. Pushing large

3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and