capabilities faster and responding more effectively to changes in operations, technology, and budgets. This guide provides DoD acquisition professionals with details on how to adopt Agile practices within each element apply. Agile requires a set of processes, roles, and culture that will take time to employ. This guide is intended to show how the DoD could tailor the Defense Acquisition Framework to benefit from Agile but don’t know how to apply Agile within the unique and complex DoD acquisition environment. This guide seeks to adapt proven principles of Agile development specifically to the DoD context. More and

data are collected at remote points and are subsequently transmitted to receiving equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring architecture 1. Data Collection at business logic, application, & environments layer a. Events logs/events into metrics to enable statistical analysis iv. Adrian Cockcraft – “Monitoring is so important that our monitoring systems need to be more available and scalable than the systems being monitored

Seize opportunitiesGreat, you're now a software company. Now what? Patrick Lightbody (New Relic)  Monitoring evolved from servers and networks to applications to what users do with applications Reflections 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 is the magic number Whom did

Development, Cybersecurity, and Operations throughout the software lifecycle, embracing a continuous monitoring approach in parallel instead of waiting to apply each skill set sequentially.  Security risks traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based continuous scanning using Common Vulnerabilities and Exposures (CVEs), runtime

Deployment tools 3. Testing standards and tools, including security 4. Deployment pipeline tools 5. Monitoring and analysis tools 6. Tutorials and standards ii. Google – Single repository with over 1B files demand 2. Help them understand the visibility and transparency that’s provided by telemetry and monitoring systems

frequent intervals iii. Demonstrated in a production-like environment iv. Ideally, use the same monitoring, logging, and other tools in pre-production environments as in production v. Dev & Ops gain shared failure stops or rolls back 2. Cluster Immune Strategy a. Expands upon Canary. Links production monitoring with release process to automatically roll back when metrics deviations, outside of expected

Environment homogenization and assimilation – no snowflakes  Deployment methodologies, automation, monitoring, and management tested continuously. Steve Barr steve.barr@csgi.com @srbarr1 Overall Quality

a longer break What does this buy me? 1. Find out how much effort an activity requires you by monitoring how many Pomodoros you need in order to accomplish a specific task 2. Learn to protect your Pomodoro

• an automated Certificate Authority, and for more security I need… • a Container scanning and monitoring service, and to monitor it more I need… • a Log Aggregation and Search service, but to install

test suite, so that new development does not cause expensive break-fix activity.  It has good monitoring tools in place.  It is coded in a way that resists hard-to-find defects like concurrency errors