operating as designed and outcomes are being achieved. iii. Logging Levels 1. Debug – anything that happens in the program 2. Info – user driven actions or system specific 3. Warn – conditions that could their services in production before they become eligible for Ops group to manage. 1. Define launch requirements (Launch Readiness Reviews, LRR) that must be met before interaction with real customers Increase Quality of Our Current Work a. Goal – enable Development and Operations to reduce risk before production changes are made. Keep the reviews and approvals close to those whom are knowledgeable

intensive suites, performance tests, IA, execute as frequently as possible i. WRITE OUR AUTOMATED TESTS BEFORE WE WRITE THE CODE (“TEST DRIVEN DEVELOPMENT”) i. TDD – Kent Beck as part of Extreme Programming delays due to integrating late in the lifecycle. Downward spiral of pain b. HP LaserJet Firmware –i. Before CI: 2 releases per year. 5% of effort supporting new features, 20% on detailed planning, 25% on programs under development, 78% reduction in cost per program c. SMALL BATCH DEVELOPMENT AND WHAT HAPPENS WHEN WE COMMIT CODE TO TRUNK INFREQUENTLY i. Branching Strategies 1. Optimize for individual productivity

take advantage of, caught up as we are in the contractor-control model of IT. Shadow IT is what happens when the IT organization is unable to meet the needs of a part of the company, perhaps due to capacity author of The Art of Business Value and A Seat at the Table: IT Leadership in the Age of Agility. Before joining AWS he was the CIO of US Citizenship and Immigration Service (part of the Department of

because it will always remain starved, waiting for work from the bottleneck. And any improvements made before the bottleneck merely results in more inventory piling up at the bottleneck.” Resource Utilization of time. Let’s call it one hour. So, on average, our task would wait in the queue for one hour before it gets worked. On the other hand, if a resource is ninety percent busy, the wait time is ‘ninety

rather than standing in judgment of them.Characteristics of an Agile governance and oversight model: Before we dive into an Agile governance and oversight model, let’s think about what characteristics such author of The Art of Business Value and A Seat at the Table: IT Leadership in the Age of Agility. Before joining AWS he was the CIO of US Citizenship and Immigration Service (part of the Department of

and someone from each tent must check in, else your tent moves to the back of the line, 48 hours before game time, when air horn sounds every study must check in  Experiment: What would the students

author of The Art of Business Value and A Seat at the Table: IT Leadership in the Age of Agility. Before joining AWS he was the CIO of US Citizenship and Immigration Service (part of the Department of

CONTINUALLY IDENTIFY AND ELEVATE OUR CONSTRAINTS 1. If we improve a work center that is positioned before the constraint, work will merely pile up at the bottleneck even faster, waiting for work to be