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

lexicon for this guide. Later sections will present more detail on the Agile processes and their application in DoD programs. The foundational structure of an Agile program is: Release - Capability system or commercial off-the-shelf (COTS) product, or building a small-scale or self-constrained application. In other words, Agile works well when the program needs to modify software for government purposes team or the target end user cannot be accessed. Program scope is mostly limited to the application layer while using existing infrastructure. Program Scope Program spans core capabilities and

typically structured as:1. Standardized Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every exercise and new piece Meetups! f. CREATE INTERNAL CONSULTING AND COACHES TO SPREAD PRACTICES i. Capital One – SMEs hold open office hours ii. Google Testing Grouplet and Testing on the Toilet periodical 1. Started Test Certified for risk-based decisions d. INTEGRATE SECURITY INTO DEFECT TRACKING AND POST-MORTEMS i. Track all open security issues in the same backlog to ensure visibility and enable prioritization ii. Conduct post-mortems

greatest uncertainty—the beginning of the initiative.  Working in an Agile way, we can leave options open and be prepared to accommodate a range of scenarios as the future unfolds.  Jez Humble and his decisions under uncertainty, and then have the courage to face the consequences. In the plan-driven model, quality was easier to understand.  We specified what the system should do, and then measured quality that, either.  We are constantly making quality decisions, especially in a Continuous Delivery model, as we decide whether the quality of each individual feature is adequate for the feature to be deployed

and are subsequently transmitted to receiving equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy what’s up or down. ii. Modern Monitoring architecture 1. Data Collection at business logic, application, & environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and systems need to be more available and scalable than the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry as part of their

“NoOps” f. Myth—DevOps is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE vs BROWNFIELD SERVICES i. DevOps is not just for Greenfield ii. Important Predictor – Is the application architected (or could be re- architected) for testability and deployability? iii. Successful Brownfield mainframe and supporting applications a. They 2X release frequency b. Resulted in increased application reliability c. Reduced deployment lead time from 2 weeks to <1 day 2. Etsy a. “Barely survived

new requirement to be delivered and deployed. Deployment speed: how fast a new version of the application can be deployed into the production environment. Deployment frequency: how often a new release emulation of common infrastructure components to achieve consistent and predictable resultConceptual Model DevSecOps LifecycleDevSecOps Pillars DevSecOps EcosystemDevSecOps Software Factory DevSecOps MVP correlated and centralized logs, container security, east/west traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based continuous

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 the development team by constraining investments reduce cost and risk.  Custom code is almost not custom these days. A developer incorporates open source frameworks, uses standardized design patterns, and orchestrates services that are already Characteristics of an Agile governance and oversight model: Before we dive into an Agile governance and oversight model, let’s think about what characteristics such a model should have in order to both take advantage

Maximizing Retrospectives 2 Ray Page Open Agile Topics 0 Jason Beranek Application Transparency 0 Ed Snodgrass Awesomeness through Stable Teams 0 Mike Ballou Open Discussion on Project Planning 1 Mike in Half the Time 2 Jerry Koske The Process of Innovation 2 Nick Tuck XP Prctices 1 Mike Ballou Open Discussion on Project Planning 1 Adam Raggett Agile Transparency 1 Eric Collins The Servant: Agile Tek Agile Trends in the Industry 1 Mike Ballou Agile Principles 0 Ray Page Open Agile Topics 0 Jason Beranek Application Transparency 0 Ed Snodgrass Awesomeness through Stable Teams 0 Mike Ballou

experiences that influence us in ways we don’t understand Developed by David SnowdenFramework A model tries to represent reality Framework is a way of looking at reality Not a modelCategorization constraints that naturally exist Codify them & make them teaching storiesManaging in a Complex Domain • Open discussion - need interactive communication, try crowd-sourcing or positive deviance - allow people