Please enable JavaScript.

Coggle requires JavaScript to display documents.

Accelerate - 1: what we found - Coggle Diagram

- - - - maturity models focus on helping an organization “arrive” at a mature state and then declare themselves done with their journey, whereas technology transformations should follow a continuous improvement paradigm.
      - maturity models are quite often a “lock-step” or linear formula, prescribing a similar set of technologies, tooling, or capabilities for every set of teams and organizations to progress through.
      - capability models are multidimensional and dynamic, allowing different parts of the organization to take a customized approach to improvement, and focus on capabilities that will give them the most benefit based on their current context and their short and long-term goals.
      - capability models focus on key outcomes and how the capabilities, or levers, drive improvement in those outcomes—that is, they are outcome based.
      - maturity models define a static level of technological, process, and organizational abilities to achieve.
      - what is good enough and even “high-performing” today is no longer good enough in the next year:
        
        teams and organizations to focus on developing the skills and capabilities needed to remain competitive.
    - - 24 keys
        
        Cultural
        
        Transformation leadership
        
        Collaboration Among teams
        
        Support Learning
        
        Westrum Org Culture
        
        Lean management and monitoring
        
        Visualising work
        
        WIP Limits
        
        Proactive Notification
        
        Monitoring
        
        Change approval
        
        Product and Process
        
        Team Experimentation
        
        Working in small batches
        
        Value Stream
        
        Customer Feedback
        
        Architecture
        
        Empowered teams
        
        Loosely coupled arch
        
        Continuous Delivery
        
        Continuous Delivery
        
        Shift Left Security
        
        Test data management
        
        Test automation
        
        Trunk Based Dev
        
        Continuous Integration
        
        Deployment automation
        
        Version Control
        
        The Keys:
        
        more frequent code deployments ;
        
        faster lead time from commit to deploy;
        
        faster mean time to recover from downtime
        
        lower change failure rate (1/5 as likely for a change to fail)
      - Dealing with Competition
        
        delivery of goods and services to delight their customers;
        
        engagement with the market to detect and understand customer demand;
        
        anticipation of compliance and regulatory changes that impact their systems;
        
        and response to potential risks such as security threats or changes in the economy.
    - - 46x more code deployment
      - 440 times faster lead time commit
      - 170 times faster for recovery
- - - - Delivery
      - Lead time
        
        2 parts
        
        Shorter product delivery lead times are better since they enable faster feedback on what we are building and allow us to course correct more rapidly.
        
        Time to deliver the feature to customers.
        
        The time it takes to design and validate a product or feature;
      - Deployment frequency
      - Time to restore service
      - Change fail rate