which its policies are expressed as code.” c. CREATE A SINGLE, SHARED SOURCE CODE REPOSITORY FOR OUR ENTIRE ORGANIZATION i. Firm-wide shared source code repository is powerful way to share local discoveries discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards and tools, including security 4. Deployment pipeline DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components ii. Test suite becomes the living documentation of the system specification and

sharing information to better enable the organization to achieve its mission. Responsibilities are shared throughout the value stream, and failure results in reflection and genuine inquiry. iv. INSTITUTIONALIZE forming of new institutional learning 2. Enables experimentation with less impact d. AGREE ON A SHARED GOAL i. Define a measurable goal with a clearly defined deadline approximately 6 months to 2 years reinforce desired behavior - anthropologists describe tools as a cultural artifact iii. Create shared backlogs and reporting 9. Ch. 7 How to design Our Organization and Architecture with Conway’s Law

SINGLE REPOSITORY OF TRUTH FOR THE ENTIRE SYSTEM i. ALL parts (code & environments) of the system are shared in a version control repository ii. Version control is for everyone in the value stream iii. Everything monitoring, logging, and other tools in pre-production environments as in production v. Dev & Ops gain shared mastery of application & environment interactions 3. Ch. 10 Enable Fast and Reliable Automated Testing

This requires the team to build relationships that promote trust, collaboration, transparency, and shared responsibility. The Government Accountability Office (GAO) report on “Effective Practices and stories/backlogs maintained in a central repository accessible by a broad user base, and is content shared at user forums?  Does the product owner regularly communicate with the development team about metrics be collected and used? What types of decisions will be made as a result?  What metrics are shared with program stakeholders? With senior leadership?  What contractor incentives are tied to these

of Feedback 1. Introduction a. Goal – Implement fast feedback loops i. Enable working towards shared goals ii. See problems as they occur iii. Enable quick detection & recovery iv. Ensure features