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 represent working ORGANIZATIONAL GOALS i. Balance team productivity against organizational goals; let operations influence components used in production or have the ability to not be responsible for unsupported platforms ii. Systematically assembling applications from third-party components and integrating them with our business logic. We inherit the vulnerabilities of these 3rd party components ii. Examine dependencies for known vulnerabilities

organizational commitment and collaboration practices for Agile implementations:  Ensure all components involved in projects are committed to the organization’s Agile approach  Identify an Agile architecture captures the operational and technology environments as well as current processes, components, interfaces, and other features. An effective architecture is one where the big picture is clearly As individual development efforts complete their tasks, testing must ensure that the separate components align with the roadmap and conform to the overarching technical architecture. The following items

Implement Feature Toggles 1. Selectively enable/disable features without code deployments 2. Wrap UI or application logic in conditional statements or strategy patterns 3. Support easy roll back 4

deployed components are replaced in their entirety, rather than being updated in place. Deploying immutable infrastructure requires standardization and emulation of common infrastructure components to achieve