to run in parallel ii. Enable different test categories to run in parallel iii. Generally, limit manual testing if automated tests haven’t passed iv. For resource intensive suites, performance tests, new and old code to make it well structured” j. AUTOMATE AS MANY OF OUR MANUAL TESTS AS POSSIBLE i. Reduce the reliance on manual testing ii. Elisabeth Hendrickson – “Although testing can be automated features, 20% on detailed planning, 25% on porting code amongst branches, 10% integrating, 15% manual testing. ii. Implemented Trunk-based development & CI iii. After CI: 40% effort on new features

DOING MORE MANUAL TESTING AND CHANGE FREEZES i. When testing failures occur, adding more testing could backfire, especially if the testing is at the end of a project and/or manual 1. Manual testing is

Extra features: d. Task switching: e. Waiting: f. Motion: g. Defects: h. Nonstandard or manual work:i. Heroics: d. The Second Way: The Principles of Feedback 27 i. KEEP PUSHING QUALITY CLOSER ineffective quality controls include: a. Requiring another team to complete tedious, error-prone, and manual tasks that could be easily automated and run as needed by the team who needs the work performed

Principles to implementing a successful DevSecOps approach  Remove bottlenecks (including human ones) and manual actions.  Automate as much of the development and deployment activities as possible.  Adopt common

CATEGORIZED AS NORMAL CHANGES i. If change approval board is required, aim for quick deployment even if manual steps are required ii. Use tooling to generate the artifacts needed for approval. Share evidence