backlog during an initial planning session, identifying all features the team considers relevant to building the product. The program backlog serves as the primary source for all program requirements and development approach when customizing an existing 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 the acquisition leadership, contracting, test, Certification and Accreditation (C&A), the user community, external systems, and cost and financial support.11 Figure 5: Potential Agile Team Construct

within the plan by itemizing potential risks, actively working to prevent them, and, if necessary, building slack into the plan to manage the potential impact of the risk on schedule.  Such an approach course of work.  Let’s say that we are deciding between two different open source products for building a piece of the system and do not know enough of their impacts to make the choice. In the old-school working support a community approach to IT, where IT leaders achieve their objectives by mobilizing the skills and passions of a broad community and encourage the members of that community to work together

we do. Complex Adaptive Systems: Fourth and last, that the business should be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led and managed through an inspect-and- pattern: a way to incrementally modernize a legacy system as defined by Martin Fowler.  Instead of building an entirely new system, we take a small piece of the legacy system and rebuild it in a way that working support a community approach to IT, where IT leaders achieve their objectives by mobilizing the skills and passions of a broad community and encourage the members of that community to work together

cases, wrong. The economics of software development have changed: Changed in a way that now favors “building” over “buying.” There are now ways of custom-developing systems that preserve many of the advantages working support a community approach to IT, where IT leaders achieve their objectives by mobilizing the skills and passions of a broad community and encourage the members of that community to work together

troubleshooting and encourages technical learning.  How we need to improve  Sharing ideas, code, Community of Practice, etc.  Test Driven Infrastructure  Blue – green deployments  Combining DevOps

been most fruitful in the past, we discover that each attacked a different major difficulty in building software, but they have been the accidental, not the essential, difficulties.”Solutions to Accidental software • Great designersRequirements refinement and rapid prototyping • The hardest single part of building a software system is deciding precisely what to build • The most important function that software

organizational performance d. MAKE INFRASTRUCTURE EASIER TO REBUILD THAN TO REPAIR i. Quickly building enables quickly re-creating on demand rather than repairing ii. Bill Baker, Microsoft distinguished environment 4. Environments can be more production-like in a consistent and repeatable wayiii. Building a deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and

CREATE SHARED SERVICES TO INCREASE DEVELOPER PRODUCTIVITY i. Enable Dev teams to spend more time building functionality, as opposed to created infrastructure ii. Automation – across the board iii. Create

entire Amazon AWS US-EAST availability zone went down; Netflix was unaffected. Since 2008 they were building and testing with the Chaos Monkey; they architected for failure, tested for failure, and evolved