A Seat at the Table – IT Leadership in the Age of Agility – Part 2 By Mark Schwartz “To the talented and hard-working government employees, so resilient in the face of impediments, criticism, and abuse the enterprise’s needs precisely. Risk is low, because the team is constantly adjusting.  Option 2: Compare that to the risk of buying a vendor’s product, where the investment is one large lump sum—and doesn’t have financial incentives to supportyou. Text “1” to @obvious if you like the first option, or “2” to @/dev/null if you prefer the second. Governance and Oversight Governance has traditionally been

........................... 1 2 Agile Development Fundamentals ................................................................................................... 2 II. Implementing an Agile Approach and process owners can reach the full potential of Agile development. Agile Acquisition Guide2 This document is structured to provide an overview of Agile development and recommendations for DoD guide also includes dozens of hyperlinks to external sources for further research and information. 2 Agile Development Fundamentals Agile development emerged in 2001, when 17 leading software developers

improvement, and learning ii. Create mechanism to rapidly spread learning throughout the organization 2. Ch. 19 – Enable and Inject Learning into Daily Work a. Complex systems are impossible to predict for beyond it b. ESTABLISH A JUST, LEARNING CULTURE i. Unjust responses to incidents 1. Impede safety 2. Promote fear over mindfulness 3. Create bureaucracy rather than carefulness 4. Cultivate secrecy of troubles; instead, human error is a consequence of the design of the tools that we gave them.” 2. Accidents are due to the inevitable design problems in complex systems that we build; they are system

The DevOps Handbook – Part 1 & 2 1. Preface xi a. Myth—DevOps is Only for Startups: b. Myth—DevOps Replaces Agile c. Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE, CHRONIC CONFLICT i which must be pursued simultaneously: 1. Respond to the rapidly changing competitive landscape 2. Provide stable, reliable, and secure service to the customer b. THE BUSINESS VALUE OF DEVOPS i. Code

architecting for low-risk releases b. Integrating objectives of QA & Operations to improve outcomes 2. Ch. 9 – Create the Foundations of Our Deployment Pipeline a. Enterprise Data Warehouse program by control. Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE ON-DEMAND CREATION OF DEV, TEST, AND PRODUCTION ENVRIONMENTS i. Major contributing cause document the environment specifications 1. Create a common build mechanism to create it on demand 2. Codified in automated environment build process iii. Environments will be stable, reliable, consistent

So your company is making 36% more money? No Was your plant able to ship even one more product per day? I’m not sure… Did you lay anyone off or reduce operating expenses? No, there is a union… Did your the process? STEP 1 IDENTIFY the systems’ constraint (bottleneck at the NCX10 machine) STEP 2 Decide how to EXPLOIT the constraint (Machines should not take lunch breaks) STEP 3 SUBORDINATE die is a 4, 5, or 6 then record - respectively - a gain of .5, 1.5, or 2.5. And if the roll is a 1, 2, or 3, then record a loss of -2.5, -1.5, or -.5. The deviations have to be cumulative.Notes Questions

Struts2 Struts2-005 Struts2-008 Struts2-009 Struts2-013 Struts2-016(实际上,很多都⽼系统都漏补了这个洞,成功率较⾼) Struts2-019 Struts2-020 Struts2-devmode Struts2-032 Struts2-033 Struts2-037 Struts2-045 Struts2-046 Struts2-046 Struts2-048 Struts2-052 Struts2-053 Struts2-057 weblogic CVE-2019-2725 CVE-2019-2729 CVE-2018-3191 CVE-2018-2628 CVE-2018-2893 CVE-2018-2894 CVE 2017 3506 CVE-2017-3506 CVE-2017-10271 Glassfish 任意⽂件读取 [ 低版本 ] 控制台弱⼝令,部署webshell IBM Websphere Java 反序列化 控制台弱⼝令,部署webshell Axis2 任意⽂件读取 ⽬录遍历 Apache ActiveMQ 未授权访问,5.12 之前的版本 fileserver存在 PUT任意写 CVE-2015-5254 Apache Solr

clients is the iterative extraction and refinement of the product requirements • Much of present-day software acquisition procedures rests upon the assumption that one can specify a satisfactory system

achieve organizational goals 2. Ch. 14 – Create Telemetry to Enable Seeing and Solving Problems a. Fact – Things will go wrong in Operations! i. 2001 Microsoft Operation Framework study found the best-performing best-performing organization were better at diagnosing & fixing service incidents. 1. “Culture of Causality” 2. Used disciplined approach to solving problems using telemetry to understand contributing factors and environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and delete 2. Event router responsible for storing our events and metrics a. Enables visualization, trending, alerting

incremental change. Anderson provides four rules for implementing Kanban: 1. Start with existing processes 2. Pursue incremental, evolutionary change 3. Respect the current process, roles, responsibilities, and transformation cycle. It lies, I believe, in our distinction between the development of a system and its operation and maintenance.  Dividing our IT spending into development and maintenance buckets leads to some