Open Discussion on Project Planning Planning in an Agile Environment Key Tenets  Planning should focus strongly on the near term  Eliminate waste caused by planning for eventualities that never come

typically structured as:1. Standardized Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every exercise and new piece Meetups! f. CREATE INTERNAL CONSULTING AND COACHES TO SPREAD PRACTICES i. Capital One – SMEs hold open office hours ii. Google Testing Grouplet and Testing on the Toilet periodical 1. Started Test Certified for risk-based decisions d. INTEGRATE SECURITY INTO DEFECT TRACKING AND POST-MORTEMS i. Track all open security issues in the same backlog to ensure visibility and enable prioritization ii. Conduct post-mortems

greatest uncertainty—the beginning of the initiative.  Working in an Agile way, we can leave options open and be prepared to accommodate a range of scenarios as the future unfolds.  Jez Humble and his decisions under uncertainty, and then have the courage to face the consequences. In the plan-driven model, quality was easier to understand.  We specified what the system should do, and then measured quality 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 to be deployed

and are subsequently transmitted to receiving equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy what’s up or down. ii. Modern Monitoring architecture 1. Data Collection at business logic, application, & environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and systems need to be more available and scalable than the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry as part of their

“NoOps” f. Myth—DevOps 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 vs BROWNFIELD SERVICES i. DevOps is not just for Greenfield ii. Important Predictor – Is the application architected (or could be re- architected) for testability and deployability? iii. Successful Brownfield mainframe and supporting applications a. They 2X release frequency b. Resulted in increased application reliability c. Reduced deployment lead time from 2 weeks to <1 day 2. Etsy a. “Barely survived

new requirement to be delivered and deployed. Deployment speed: how fast a new version of the application can be deployed into the production environment. Deployment frequency: how often a new release emulation of common infrastructure components to achieve consistent and predictable resultConceptual Model DevSecOps LifecycleDevSecOps Pillars DevSecOps EcosystemDevSecOps Software Factory DevSecOps MVP correlated and centralized logs, container security, east/west traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based continuous

appears to offer predictability, control, and efficiency, the key values of the contractor-control model. But it doesn’t. Requirements: Requirements are a way of controlling the development team by constraining investments reduce cost and risk.  Custom code is almost not custom these days. A developer incorporates open source frameworks, uses standardized design patterns, and orchestrates services that are already 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 a model should have in order to both take advantage

False，如果有一个为 True，则返回 True。元素除了是 0、空、FALSE 外都算 TRUE ⑥其他 eval() 函数用来执行一个字符串表达式（为python表达式），并返回表 达式的值 open() 函数用于打开一个文件，并返回文件对象 ascii() 函数类似 repr() 函数, 返回一个表示对象的字符串, 但是对于字符 串中的非 ASCII 字符则返回通过 repr() 函数使用 \x try: raise MyError("xx") # 抛出异常 except MyError as err: # to do ★第10章、文件操作 使用内置函数open()打开一个文件，返回file对象，再调用此对象的相 关方法进行读写操作 ★文件打开模式 模 式 文 本 二 进 制 指 针 位置 是 否 覆盖 含义 只 读 r rb 开头 a+ ab+ 末尾 否 读写，写时追加；若文件不存在 则新建 例： fileobj = open("test.txt", "r") fileobj.close() # 关闭文件 ★处理打开文件时的异常 try: fileobj = open("test.txt", "r") # to do fileobj.close()

Major contributing cause of issues stems from releases representing the first time we see how an application behaves in a production-like environment ii. Don’t just document the environment specifications the value stream iii. Everything, everything, everything is checked into version control 1. Application code & dependencies 2. 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 also includes pre-production and build processes 9. Tools iv. 2014

once a week to everyday  Expanded Sphere of Influence  Machine Imaging  DEG and 3rd Party Application Installations  Route Adds – requires heightened security access  Database Data Script Execution