conditions of tremendous uncertainty, your choices will often turn out to be wrong.Agile and plan-driven models have very different ways of dealing with uncertainty. Plan driven approaches, even Waterfall, have that this is something to be ashamed of or that they need to be controlled, learn to speak the language of the business, or start wearing jackets and ties.The CIO’s Place at the Table IT leadership

Another key component to creating smooth and fast flow is performing work in small batch sizes. 2. Large batch sizes result in skyrocketing levels of WIP and high levels of variability in flow that cascade that Development has worked on is released to production deployment. Like in manufacturing, this large batch release creates sudden, high levels of WIP and massive disruptions to all downstream work rubber stamp their approvals c. Creating large volumes of documentation of questionable detail which become obsolete shortly after they are written d. Pushing large batches of work to teams and special

Software Agility: Best Practices for Large Enterprieses (2007) Implementing agile practices at enterprise scale Synchronizes alignment, collaboration and delivery for large numbers teams Core values:  Code

a book club. Book List  Scaling Lean & Agile Development: Thinking & Organizational Tools for Large-Scale Scrum, Craig Larman  Continuous Delivery: Reliable Software Releases through Build, Test

understanding of the desired functions. They offer a far more dynamic approach to managing requirements than large requirements documents.  DON’T treat planning as a one-time up front activity o In lieu of CDDs

issues 3. Define changes which qualify as high-risk and require SME review 4. If a change is too large to reason about, split it up g. POTENTIAL DANGERS OF DOING MORE MANUAL TESTING AND CHANGE FREEZES

INSTITUTE GAME DAYS TO REHEARSE FAILURES i. Game Days – exercise designed to increase resilience through large-scale fault injection across critical systems ii. Simulate and rehearse accidents for practice

TRUNK-BASED DEVELOPMENT PRACTICES i. CI and Trunk-based development (TBD) are countermeasures to large batch size ii. TBD enables: 1. Frequent commits 2. Runs of automated tests of the integrated system

 Option 2: Compare that to the risk of buying a vendor’s product, where the investment is one large lump sum—and a commitment to future maintenance payments. Then, of course, there is the risk of the

跳转到鼠标指定的函数定义处 Shi� + F10 运行程序 Ctrl + R 查找替换 ★设置字体颜色 File → Se�ngs → Editor → Color Scheme → Language Defaults → 选中目 标Scheme ★设置背景颜色 File→Se�ngs→Editor→Color Scheme→Console Colors→Scheme → 选 择