visualization, trending, alerting, & other good things b. Enable threshold-based alerting & health checks iii. Transform logs/events into metrics to enable statistical analysis iv. Adrian Cockcraft – “Monitoring 6. Ch. 18 – Create Review and Coordination Process to Increase Quality of Our Current Work a. Goal – enable Development and Operations to reduce risk before production CHANGES i. Require peer reviews, not external board approval ii. Peer review help improve overall quality, provide cross-training, learning, and skill improvements. iii. Keep batch sizes of reviews small

expensive and risky transformation effort, FOC is in no sense a “final” operating capability. Quality It is difficult for IT to gain a seat at the table when IT is always failing, but on the other hand face the consequences. In the plan-driven model, quality was easier to understand.  We specified what the system should do, and then measured quality as adherence to that specification.  The opposite Probably not that, either.  We are constantly making quality decisions, especially in a Continuous Delivery model, as we decide whether the quality of each individual feature is adequate for the feature

framework includes the concept of “Done,” which constitutes a critical aspect of ensuring high-quality software. To be considered potentially releasable, a piece of functionality must adhere to a common team of software developers, including software and security engineers, data specialists, testers, quality assurance, and configuration managers. Ideally these participants are co-located in the same also write user stories to cover underlying characteristics of security, technical performance, or quality. Interfaces with other systems are usually captured as user stories. User stories require little

manufacturing lead time required to convert raw materials into finished goods was the best predictor of quality, customer satisfaction, and employee happiness 2. one of the best predictors of short lead times flow that cascade through the entire manufacturing plant. The result is long lead times and poor quality 3. Consider when we have an annual schedule for software releases, where an entire year’s worth of WIP and massive disruptions to all downstream work centers, resulting in poor flow and poor quality outcomes. This validates our common experience that the larger the change going into production

purchasing? Employing good people? High technology? Producing products? Producing high quality products? Selling quality products? Capturing market share? After much reflection, Alex realizes: The goal bottleneck produces in that time. And that makes an enormously expensive lunch break” Story - Quality control Jonah: “Make sure the bottleneck works only on good parts by weeding out the ones that

monitoring, and management tested continuously. Steve Barr steve.barr@csgi.com @srbarr1 Overall Quality improvements, “it” goes in better, and with less issues.  Maintenance window changed from once recurring maintenance.  Do define a primary purpose and measure it.  Do process map.  Do focus on Quality first.  Do start a book club. Book List  Scaling Lean & Agile Development: Thinking & Organizational

Perspective 1 Kyle Baardson Scrum - Doing Twice the Work, in Half the Time 1 Nick Tuck Assuring Quality 3 Toby Flint Lean Startup Book Review 0 Mark Staroska Story Points 4 Jason Smith Empowering Teams SAFe: Scaled Agile Framework 3 Josh Sagucio Collaborative Work Environments 3 Nick Tuck Assuring Quality 3 Josh Wade Cyber Security through Agile 2 Nick Tuck Maximizing Retrospectives 2 Nick Wenner

deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and code quality (static analysis, coverage, style, etc.) 2. Package the code only once – use the same packages throughout reliance on manual testing ii. Elisabeth Hendrickson – “Although testing can be automated, creating quality cannot. To have humans executing tests that should be automated is a waste of human potential.”

Synchronizes alignment, collaboration and delivery for large numbers teams Core values:  Code quality - can't scale crappy code  Program execution  Alignment  Transparency House of Lean: "We

Scrum - Doing Twice the Work, in Halfthe Time Mar 2015 Nick Tuck Assuring Quality Toby Flint Lean Startup Book Review Dec 2014 Mark Staroska