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 code quality (static analysis, development, 78% reduction in cost per program c. SMALL BATCH DEVELOPMENT AND WHAT HAPPENS WHEN WE COMMIT CODE TO TRUNK INFREQUENTLY i. Branching Strategies 1. Optimize for individual productivity – everyone difficult 2. Optimize for team productivity – everyone works in common area, simpler commits, but each commit can break the entire project ii. When merging is difficult, less able to refactor due to potential

users and development team. Sprint planning, during which the development team and product owner commit to a specific set of user stories, then addresses the tactical-level details. During sprint planning is ready to commit to full-scale Agile adoption. However, when a program has decided to “go Agile” and formally adopt the methodology as a development approach, the government must commit to making changes

“What’s a good compromise? It seems that the best course might be to give people an opportunity to commit up front to their preferred path of action. This approach might not be as effective as the dictatorial

Review Guidelines 1. Everyone must have someone review their changes2. Everyone should monitor the commit stream of their fellow team members to identify issues 3. Define changes which qualify as high-risk