ECMM

Enterprise Cloud Maturity Model

The ECMM is intended as a template tool for enterprise organizations planning large-scale Cloud adoption and transformation. It is an aggregated composite of maturity models for Cloud adoption, intended to provide a simplified summary of their combined recommendations, across a lifecycle of three main Transform Journeys, also described in an actionable form through the Transform Roadmap.

Transform Roadmap

  • Digital Organization - From CIO to Chief Digital Officer
  • Enterprise DevOps - Going Going Cloud Native, adoption of containers and Continuous Deployment practices.
  • Cloud Aware Applications - From Monolith to Microservices - Reengineering software in line with new microservices principles.

Capability Level 1 Level 2 Level 3 Level 4
       
Digital Organization Utility Provider – IT is involved in the organization only as an operational department. Outsourcing Contractor - Expansion through traditional ICT outsourcing and some IaaS. Process Optimizer – Purposeful improvement of business processes through targeted applications of IT solutions. Revenue Enabler – Proactively drives business growth through leveraging technology as a strategic asset.
Enterprise DevOps Poor collaboration methods and infrequent, unreliable releases. Siloed automation with no central infrastructure, processes are managed but not standardized Some automation of IT operations Collaborative - Collaboration and shared decision making, central automated processes across the application lifecycle, processes are standardized across the organization. Frequent fully automated releases Business Capability Teams - Agile, product-centric teams Fully automated deployment and issue management
Cloud Aware Applications Virtualized - The basic process of virtualizing applications to internal hypervisors (as many are today). Loosely Coupled - Application is composed of loosely coupled services. Abstracted - Services are stateless and infrastructure agnostic. Adaptive - Apps can self-migrate across multiple Cloud providers.

1. Digital Organization Maturity

The overall maturity of the IT organization including the CIO can be assessed through a context of business alignment, how operational vs strategic is the focus and how skilled and equipped is the team for Digital Transformations.

Capability Level 1 - Repeatable Level 2 - Defined Level 3 - Optimizing Level 4 - Visionary
Digital CIO Utility Provider – IT is involved in the organization only as an operational department, typically reporting to the CFO. Outsourcing - Expansion through traditional ICT outsourcing and some IaaS. Process Optimizer – Purposeful improvement of business processes through targeted applications of IT solutions.CIO is sought out by department leaders to address their needs. Revenue Enabler –Proactively drives business growth through leveraging technology as a strategic asset.CIO and CEO work hand in hand to devise technology-enabled disruptive strategies.
Business Architecture Very little if any formal Business Architecture planning is involved in IT decisions. Traditional EA methods only are used for planning Cloud adoption. The IT organization has an explicit method of linking business strategy to IT decisions. Digital Transformation Roadmaps - An end-to-end 'toolchain' caters for the full innovation lifecycle from ideas through DevOps and implementation.

Reference Documents

  1. CBPN.io - Digital Business Architecture 1)http://cbpn.io/ebooks/digital-business/
  2. IT Process Institute – IT Strategy Alignment. 2)IT Process Institute: http://itpi.3dcartstores.com/IT-Strategic-Alignment-Executive-Summary_p_36.html
  3. ISACA – Enabling the Strategy­ focused IT organization.

2. Enterprise DevOps

Enterprise DevOps encompasses the 'toolchain' aspects of Cloud Native computing as well as the surrounding team dynamics and organizational performance goals.

Capability Level 1 - Repeatable Level 2 - Defined Level 3 - Optimizing Level 4 - Visionary
Collaboration Maturity Silo-based IT organizationPoor ad­hoc communication, no automation and unpredictable reactive processes. Siloed automation with no central infrastructure, processes are managed but not standardized. Collaboration and shared decision making, central automated processes across the application lifecycle, processes are standardized across the organization. Business Capability Teams - Structured, agile PLM practices married with a new organizational team model based on BCTs - Business Capability Teams.Collaboration processes are measured, automated processes metrics are collected realizing predictability of performance.
Automation and Continuous Deployment A manual process for infrequent and unreliable releasesEnvironments are manually provisioned Painful infrequent but reliable releasesAutomated provisioning of environments Frequent fully automated releasesChanges to datastores automatically performed as part of the deployment process Automated problem isolation and issue resolutionSelf­-service automation, self­learning using analytics and self­remediation enabling process, risk and cost optimization

Reference Documents

  1. IBM DevOps Maturity Model3)IBM: http://www.ibm.com/developerworks/library/d-adoption-paths/

  2. HP DevOps Maturity Model4)HP: https://community.hpe.com/t5/All-About-the-Apps/DevOps-and-OpsDev-How-Maturity-Model-Works/ba-p/6042901

  3. Arug Gupta, VP Couchbase - Continuous Integration, Delivery, Deployment and Maturity Model5)Arun Gupta blog: http://blog.arungupta.me/continuous-integration-delivery-deployment-maturity-model/


3. Cloud Native Applications

Cloud Native Applications deals specifically with the maturity of the software being developed, defining maturity through the level of adaptation into the overall Cloud ecosystem.

Capability Level 1 - Repeatable Level 2 - Defined Level 3 - Optimizing Level 4 - Adaptive
Cloud Aware Applications Virtualization only. Application is composed of loosely coupled services. Services are stateless and infrastructure agnostic. Apps can self-migrate across multiple Cloud providers.
SDN/NFV Network services are not yet virtualized, they are able to run on standard IA/64 based server ‘bare metal’ hardware, occupying the server but not sharing the environment with hypervisor or virtual machines. Network services run within a virtual machine and can co­reside with other VM functions, but require dedicated IO access, limiting the flexible orchestration of the component and thus restricting its full elasticity. Network services run within VMs and are able to utilize virtual IO ports, enabling flexible orchestration of the component Network services are able to be orchestrated at a lifecycle level as a deployable runtime component, and during runtime to accept dynamic reconfiguration commands, to scale up/down and establish new IO resource connections.

References

  1. ODCA - Cloud Aware Applications6)ODCA: https://opendatacenteralliance.org/article/open-data-center-alliance-best-practices-architecting-cloud-aware-applications-rev-1-0-2/

  2. TMF ZOOM Program - Procurement Toolkit7)TMF: https://www.tmforum.org/resources/suite/ig1133-nfv-procurement-survival-kit-r15-0-1/

References   [ + ]

1. http://cbpn.io/ebooks/digital-business/
2. IT Process Institute: http://itpi.3dcartstores.com/IT-Strategic-Alignment-Executive-Summary_p_36.html
3. IBM: http://www.ibm.com/developerworks/library/d-adoption-paths/
4. HP: https://community.hpe.com/t5/All-About-the-Apps/DevOps-and-OpsDev-How-Maturity-Model-Works/ba-p/6042901
5. Arun Gupta blog: http://blog.arungupta.me/continuous-integration-delivery-deployment-maturity-model/
6. ODCA: https://opendatacenteralliance.org/article/open-data-center-alliance-best-practices-architecting-cloud-aware-applications-rev-1-0-2/
7. TMF: https://www.tmforum.org/resources/suite/ig1133-nfv-procurement-survival-kit-r15-0-1/
Reset Password
Compare items
  • Total (0)
Compare
0