stories to concisely define the desired system functions and provide the foundation for Agile estimation and planning. o They describe what the users want to accomplish with the resulting system. User programmatic 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 continue to refine it as they learn more from the development sprints and releases. Cost Estimation  Cost estimation in an Agile environment is challenging  The challenge within DoD is often a resistance

 Experiment: Economist Subscription, Errands for Pen and Suit  Agile tie-in: Size and cost estimation – does anyone really know in absolute terms how many SLOC it will take a build a product or capability

BUILD, TEST, AND INTEGRATE OUR CODE AND ENVIRONMENTS i. Create automated test suites to increase frequency of integration and testing of code & environments from periodic to continuously ii. Create build 5. Ch. 12 Automate and Enable Low-Risk Releases a. Just like we reduce batch size and increase frequency of feedback during development and testing, we now apply same concepts to releasing to production

fast a new version of the application can be deployed into the production environment. Deployment frequency: how often a new release can be deployed into the production environment. Production failure rate:

performance for stability (MTTR, change fail rate) and throughput (deployment lead time, deployment frequency) e. ENABLE COORDINATION AND SCHEDULING OF CHANGES i. Loosely coupled architectures enable greater

Brownfield transformations 1. CSG – COBOL mainframe and supporting applications a. They 2X release frequency b. Resulted in increased application reliability c. Reduced deployment lead time from 2 weeks