this lack of well-documented research and of historical examples that other programs could use as models, we sought the views of experts representing diverse acquisition disciplines on how to appropriately Description of functionality a user wants, small enough to complete in a single sprint Epic – A large user story often defined for a release that spans multiple sprints Theme – A grouping of user stories discussion and agreement among the members. Teams may use a Fibonacci series, ideal days, or small-medium-large as units for assigning story points. Over time, as the teams accumulate performance data, this iterative

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

difficulties.”Solutions to Accidental Difficulties • High-level languages • The most a high-level language can do is to furnish all the constructs the programmer imagines in the abstract program • Time-sharing are they remainders of our accidental difficulties?”Silver bullets? • Ada and other high-level language advances • Object-oriented programming • Artificial intelligence • Expert systems • “Automatic” content, automatic programming has always been a euphemism for programming with a higher-level language than was presently available to the programmer • In essence, it is the solution method, not the

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