the failures 3. Enable and encourage people who do make mistakes to be the experts who educate the rest of the organization on how not to make the mistakes in the future 4. Accept that there is always suite becomes the living documentation of the system specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast changes through pair programming or code review 3. Instrument the repository to detect suspicious code (API calls from certain types of test code) 4. Ensure every CI process is in an isolated container 5

always been framed in terms of control—the underlying theme of interactions between IT leaders and the rest of the business has been to “keep your people under control, provide good customer service, deliver control, is the ability to manage through influence. The CIO needs to sell his or her ideas to the rest of the organization—to influence the use of technology in areas he or she does not directly control

take a small piece of the legacy system and rebuild it in a way that lets it interoperate with the rest of the legacy system. We launch that piece into production and have users use it seamlessly as if

Trimble assert the need for dedicated transformation teams that are able to operate outside the rest of the organization 1. Enables the forming of new institutional learning 2. Enables experimentation

that could become an error and will likely trigger an alert 4. Error – error conditions such as API failures, internal issues 5. Fatal – forces a termination iv. Examples of potentially significant Use telemetry to measure outcomes iv. Etsy open-sourced their experimentation framework – Feature API e. INTEGRATE A/B TESTING INTO OUR FEATURE PLANNING i. Product owners should consider each feature

Coined by Martin Fowler in 2004 ii. Strangler Application 1. Put existing functionality behind an API 2. New functionality implemented in new services with new architecture 3. Make calls to old system