do yesterday? 2. What are you going to do today? 3. What obstacles are in your way? At the end of each sprint, the development team demonstrates the functionality to users and other stakeholders representatives and end users are able to frequently engage throughout development. User Involvement Users cannot support frequent interaction with the development team or the target end user cannot required to develop program elements. Program can leverage test infrastructure and automated tests, and testers are active throughout development. Test Environment Extensive development and operational

future). Build Versus Buy: In a world where IT capabilities were delivered as a single “product” at the end of a project, a “product” that then only required a bit of maintenance now and then, the economics the feature is ready for deployment when it passes all of its tests. But is quality a simple yes-or-no attribute? If it passes its tests, is it high quality? And how can we assess the quality of something separate the concepts of deployability and quality. A feature is simply deployable when it passes its tests; that is a yes-or-no question independent of quality.  Once the feature is in production, we can

Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This struggling with changes – Hard line: no changes would be accepted into GWS without accompanying automated tests. Spread Testing Grouplet team approach. Google – single, share repository of billions of files. 50% of code is changed each month. 40K code commits/day, 120K automated test suites, 75M tests cases/day e. CONTINUOUSLY BUILD, TEST, AND INTEGRATE OUR CODE AND ENVIRONMENTS i. Create automated test

every Google property d. SPREAD KNOWLEDGE BY USING AUTOMATED TESTS AS DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components ii Designing for fast flow, deployability, and operations will derive NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring of assurance for confidentiality, integrity, and availability b. Don’t inspect security in at the end, it’s integrated as part of our daily work i. Make security part of everyone’s jobii. Integrate preventative

built automatically using Continuous Integration, and it is tested automatically through scripted tests.  It is deployed automatically with automated deployment tools onto infrastructure that can be well, in the government, about 100 different piles of paper.  Now, I believe that this was a dead end: it was a Waterfall solution to the problem. A Better Way - Develop an Agile oversight process incrementally: that values skills and contributions. Exhortation and Table Manners: There’s nothing left to do but end on a message of hope. And that’s what this book is meant to be, really. About the Author Mark Schwartz

Mike Ballou Notes from Velocity 1 Chris Krull Technical Humility 1 Jason Wohlgemuth Agile Front-end Automation 4 Nik Kalantjakos "Coaching Agile Teams" - Book Club 0 Ray Page CA Clarity PPM software Delivery 4 Mike Ballou Pomodoro Technique 4 Mark Staroska Story Points 4 Jason Wohlgemuth Agile Front-end Automation 4 Kyle Baardson SAFe: Scaled Agile Framework 3 Josh Sagucio Collaborative Work Environments

Ballou Notes from Velocity Chris Krull Technical Humility Jul 2015 Jason Wohlgemuth Agile Front-end Automation Nik Kalantjakos "Coaching Agile Teams'" - Book Club Ray Page CA Clarity PPM software

Yak Shaving - the phenomenon where one task leads to another, which leads to another, until you end up working on something that seems completely unrelated to the original problemExample of Yak Shaving

that values skills and contributions. Exhortation and Table Manners: There’s nothing left to do but end on a message of hope. And that’s what this book is meant to be, really. About the Author Mark Schwartz

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 slower and more tedious 2. Tends towards increasing