ability to focus on capability delivery. Figure 11 Capstone Documentation Example Appendix D lists required DoDI 5000.02 and BCL acquisition documents, and contains a table that identifies the applicability development team during sprints. Programs use work elements (e.g., story points, staff hours, task lists, etc.), burn-down charts, and velocity to track progress and measure productivity, costs, schedule PPP Program Protection Plan PWS Performance Work Statement RDP Requirements Definition Package SAE Service Acquisition Executive SEP Systems Engineering Plan TEMP Test and Evaluation

by producing its Agile interpretation of what the overseers were asking for. That might include lists of user stories, burndowns, definitions of done, product roadmaps, and, well, in the government,

developers 2. Segregated processes so we know the dependencies – eliminates “worked on my machine” 3. Package the application to enable repeatable installation and configuration into an environment 4. Environments deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and code quality (static analysis, coverage, style, etc.) 2. Package the code only once – use the same packages

Manager for the development of the IBM System/360 family of computers and the OS/360 software package • In 1975, published The Mythical Man-Month: Essays on Software Engineering • In 1987, authored