New Fudging some of the numbers above to be rounder, because by the time this is presented to anyone, those PSM I, PSD I, and PSPO I numbers will have been hit. Through 8/31/2016: PSD I: 2,990 passed of 4,147 taken PSM I: 69,727 passed of 97,299 taken PSM II: 510 passed of 880 taken PSM III: 389 passed of 632 taken PSPO I: 9,971 passed of 12,978 taken PSPO II: 95 passed of 122 taken SPS: 377 passed of 475 taken Opens: 1,030,112 taken
Through 7/31/2016: PSD I: 2,909 passed of 4046 taken PSM I: 67,714 passed of 94,644 taken PSM II: 475 passed of 803 taken PSM III: 381 passed of 623 taken PSPO I: 9,622 passed of 12,530 taken PSPO II: 94 passed of 121 taken SPS: 357 passed of 453 taken Opens: 988,843 taken
Through 6/30: PSD I: 2,797 passed of 3,902 taken PSM I: 65,428 passed of 91,590 taken PSM II: 3636 passed of 596 taken PSPO I: 9,182 passed of 12,014 taken PSPO II: 92 passed of 119 taken PSP: 85 passed of 161 taken SPS: 323 passed of 408 taken Opens: 951,185 taken (963,891 as of 7/11/16)
Through 5/31: PSD I: 2,697 passed of 3,775 taken PSM I: 63,195 passed of 88,621 taken PSM II: 359 passed of 588 taken PSPO I: 8,713 passed of 11,466 taken PSPO II: 89 passed of 114 taken PSP: 83 passed of 159 taken SPS: 303 passed of 384 taken Opens: 917,510 taken
90% - Forrester research data https://www.forrester.com/How+Can+You+Scale+Your+Agile+Adoption/fulltext/-/E-res110444#AST962998 2013
Traditional, slower, more methodical approaches no longer work Ten years ago we weren’t talking about cloud computing on the massive scale we are today Cloud computing and trends such as BYOD, BYOA, BYOI, mobile, wireless have prompted a paradigm shift IT must meet the accelerated demand We can’t sacrifice quality, however, to go faster
Explain that it used to be CAMS but recently Lean was recognized as a critical value.
: Acknowledge that while there are increasing job posting for DevOps Engineers and that the number of DevOps teams is on the rise, DevOps is not a title or team Both have deviate from the intent of DevOps which is to improve communication and collaboration by creating yet another silo The term ‘NoOps’ was initially coined by Adrian Cockcroft, Director of Cloud Systems Architecture for Netflix, to describe his IT organization as having little need for operations staff, partly because the company has shifted to the cloud, where it can automate many former functions of the staff The article sparked a great deal of debate It’s worth mention that Ops responsibilities are much broader than those only related to software deployment DevOps is also not the wild west where developers can do whatever they want whenever they want
1. Built-in instability – Clear goal, but nothing else. 2. Self-organizing project teams - autonomy, self-transcendence (pushing the limits), and cross-fertilization. 3. Overlapping development phases – iterations. 4. “Multilearning” – learning by doing. 5. Subtle control – a few very minor controls (such as a sprint review) 6. Organizational transfer of learning – wanting to share (osmosis)
We should use this as a lead in to this section so show that we are constrained by our communication failures within IT – particularly with isolated initiatives such as Scrum and DevOps.
Run this as a guided discussion – display the slide and ask the class to identify sources of waste and delay. These should include: Requirements implemented but never used, or requiring significant rework Large batch sizes Handoffs between people Inadequate automation in: Build automation Environment provisioning Testing Deployment Finding out about something late Legal requirements Security requirements Scaling problems Lack of skills Lack of the right people, or enough people …
Ask who has read the Phoenix Project The ‘Three Ways’ are introduced in ‘The Phoenix Project: A Novel About It, DevOps, And Helping Your Business Win.’ The First Way Emphasizes the performance of the entire system (vs. a single silo or department) Focuses on all business value streams enabled by IT These core values will be discussed in greater detail later in this course in the context of DevOps practices
Look up Forrester’s definition of MTTI (Mean Time to Identify - detect) and MTTK (Mean Time to Know – Root Cause). MTBF – mean time between failures
The foundation of Modern IT / DevOps is Agile (maybe Scrum). Based on that foundation are the four domains of Development with Scrum, Continuous Delivery, security, and continuous operations (ITIL stuff). That is built on automation (DevOps express) and then measurement.