and resources. Leveraging a common infrastructure enables portfolios to test and certify their component programs more effectively and efficiently. This also reduces infrastructure and staffing costs exploratory testing, scenario testing, usability testing, user acceptance testing, unit testing, component testing, performance and load testing, security testing, maintainability testing, interoperability approved at the lowest possible level, likely a Program Executive Officer or related official. SAEs/Component Acquisition Executives, and if necessary the OSD level, should conduct their reviews at the portfolio

powerful way to share local discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards and tools, including 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 CODE REPOSITORIES AND SHARED SERVICES i. Add mechanisms & tools ii. Add security’s pre-blessed libraries, implementations, etc. iii. Collaborate with any shared services to provide prebuilt, secured platforms

easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow is performing work in small batch sizes. 2. Large batch sizes