tailored processes and strategies. The blue boxes presented throughout the guide pose a series of key questions to help acquisition professionals think critically about the Agile processes for a program certification staff, as well as DoD leadership and oversight. Program managers must engage these key stakeholders to garner their endorsement and feedback and to build an Agile culture that can be sustained some small scale developments the program manager may fulfill the role of the project manager. Key Questions to Validate Agile Teams/Roles:  Are the major stakeholder roles and responsibilities

integration, and security testing - this is a key DevSecOps differentiator since security and functional capabilities are tested and built simultaneously. Key Measures Mean-time to production: the average Mean-time to recovery: how long it takes applications in the production stage to recover from failure. Key Principles to implementing a successful DevSecOps approach  Remove bottlenecks (including human ones) container level. Zero trust requires strict controls, never trust anything by default and always verify. Key aspects of zero trust at the container level include mutual Transport Layer Security authentication

Open Discussion on Project Planning Planning in an Agile Environment Key Tenets  Planning should focus strongly on the near term  Eliminate waste caused by planning for eventualities that never come reviews, this less formal approach does not equate to less rigor. Instead, greater frequency allows key decision makers and other stakeholders to become more familiar and comfortable with processes in the environment, which enables a more collaborative and productive review process.  Provide information to all key stakeholders on a consistent, regularly scheduled basis, either through design reviews or program

something that isn’t moving yet, just in case it decides to make a run for it…Tracking everything is key to moving fast, but the only way to do it is to make tracking anything easy…We enable engineers to well-designed and executed experiments that were designed to improve a key metric, only about one-third were successful at improving the key metric!” iii. A/B testing helps reduce zero or negative value add

can more easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow is performing work in small batch sizes. 2. Large batch processes, or review processes 2. Places where significant rework is generated or received. iii. Key metrics in value stream 1. Lead Time 2. Process time 3. Percent Complete & Accurate (%C/A) c.

malicious binaries 4. Source code integrity and code signing – all contributors should have their own key and sign all commits to version control. All created packages should be signed and hash recorded for lead times 3. Urgent changes: emergency and potentially high-risk that must be done immediately. Key goal of DevOps – streamlined normal process that is suitable for emergency changes b. RE-CATEGORIZE

culture, metaprocess, process, entropy  Actively discourage email: it is exclusive Where there any key themes?  Real User Monitoring: more valuable than any other metric  Web Performance: 2 seconds

interdepartmental communications, and effectively serve the other business functions at Parts Unlimited. Key Concepts The Three Ways [2] The First Way emphasizes the performance of the entire system, as opposed

have an understanding on how my input and feedback will enter into their process.  What are the key risks to delivery? What assumptions are contained in the plans? How will the team move quickly to

has 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