IT Transformation in the Public Sector
•Als PPTX, PDF herunterladen•
5 gefällt mir•5,104 views
As organizations begin their journey to the cloud, they often ask us what changes they need to make in their organizations in order to sustainably adopt cloud services. This webinar will educate attendees on charting their own cloud adoption journey by leveraging the AWS Cloud Adoption Framework (CAF) to sequence the transformational activities. We will go through the 7 key perspectives of the CAF that will shape your people, process, and technology strategy, and how they guide you through the 8-step journey into the cloud through the process of IT Transformation.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie IT Transformation in the Public Sector
Ähnlich wie IT Transformation in the Public Sector (20)
Mehr von Amazon Web Services
Mehr von Amazon Web Services (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
IT Transformation in the Public Sector
- 1. IT Transformation in the Public Sector (‘A How To Guide’) Sanjay Asnani, IT Transformation Sr. Consultant AWS Professional Services World-Wide Public Sector November 19, 2015
- 2. Focus on Every Aspect of Cloud Adoption Prescriptive guidance and implementation assistance across the stack: • IT Transformation leads focus on the business aspects of cloud adoption • Application Architects help developers build AWS-aware applications • Big Data / Analytics Specialists help you design and deploy your analytics platform • Infrastructure Architects take your unique landscape of application, network, and security needs to the cloud • Security Leads provide well-proven designs to meet your compliance needs • Operational Integration Specialists help you successfully adopt DevOps practices Application Optimization Big Data & Analytics Infrastructure Architecture Security,Risk& Compliance Operational Integration IT Transformation
- 3. Government Agencies and Educational Institutions Use AWS Worldwide 3
- 4. AWS Partners Focused on Public Sector 4
- 5. The Many Reasons Organizations are Moving to the Cloud Current • Fixed Costs • Capital Intensive • High Maintenance and Run Costs • Legacy Applications • Outdated • Capital Light - ‘Pay by the Drink’ • Cost Savings & Flexibility • Responsive & Agile • Continual Iteration & Innovation • New Technologies Future The Agile Enterprise
- 6. Moving to the Cloud can be a challenge for large Organizations Large cloud transformation programs are complex undertakings which: Multiple work streams and inter-dependencies. Can have significant impact on current IT Operating Model, procedures, tools, and standards Results in change to how applications and infrastructure services are developed and delivered Complexities due to thousands of applications, multiple Data Centers, suppliers, existing contracts, and compliance needs Present technical integration challenges and complexities that need to be addressed
- 7. The Journey Brings Fast Learning & Early Wins TransformExpandExplore Adopt Non- Production Existing Web Workloads New Capability Workloads Legacy Migration
- 8. Technology Alone is Not the Answer AWS Cloud Adoption Framework (CAF) Comprehensive framework that helps bring together people, process and technology to reduce the time and cost of deployment consistent proven repeatable
- 9. AWS Cloud Adoption Framework Perspectives Delivery Explore Prepare Migrate/Dev. Iterate Discovery Baseline Gap Strategy Activities AWS Partner/s BusinessObjectivesComprehensive framework that helps bring together people, process, and technology to drive efficient, effective, and secure cloud adoption, based on defined business objectives Comprised of: • 4 step Discovery phase • 7 perspectives (business, platform, maturity, people, process, security, and operating) • 4 step Delivery phase
- 10. AWS Cloud Adoption Framework The AWS CAF organizes and describes the perspectives in planning, creating, managing, and supporting a modern IT service. Offers practical guidance and comprehensive guidelines for establishing, developing and running AWS cloud-enabled environments. It provides a structure where business and IT can work together towards common strategy and vision, supported by modern IT automation and process optimization. People Perspective Process Perspective Security Perspective Maturity Perspective Platform Perspective Operations Perspective Business Perspective
- 11. CAF Core Perspectives Process Perspective Managing portfolios, programs and projects to deliver expected business outcome on time and within budget, while keeping risks at acceptable levels. People Perspective Defining and acquiring the skills needed to adopt the AWS cloud platform. Examples guidance include role descriptions, training, certification and mentoring. Maturity Perspective Defining the target state architecture of the organization and creating the required blueprints and roadmaps. Platform Perspective Represents the technology services of the AWS cloud platform. Provides patterns, guidance, and tools for optimal use of the technology services and services to implement. Operations Perspective Represents the ongoing management of the functioning IT environment of AWS. Provides process, guidance and tools for optimum operational service management of the AWS environment. Security Perspective Defining and implementing the required levels of security, governance, and risk management to achieve compliance. Business Perspective Identifying, delivering, and measuring business impact using architectural approaches that align technical delivery to business imperatives.
- 12. Sample Cloud Adoption Roadmap Discovery Workshop Cloud Business Case Define Security Requirements Define Network Environment Define Governance Structure Operational Integration Security Operations Playbook Cloud Environment Optimization Application Portfolio Analysis Cost and Billing Analysis Training and Certification Define Cloud Environments Define EA Policies and Practices
- 13. Transformation Process – An Overview1. Establish Common Understanding Observations: Cloud Adoption requires an organization to take on a new method of providing IT services and involves change at many different levels. Successful transformations require strong executive sponsorship early in the process, and a commitment from the organization. Proper planning and communication of the process are vital parts of the process. It is important to determine the overall benefits to the organization, provide training for staff, develop the foundational architecture, assess the environment , and develop security controls part of the overall transformation. Total Value of Ownership Understand the value of AWS for the organization in terms of agility, availability, disaster recovery, cost and reach. A high-level value analysis will align with the objectives and support the mission of the organization. Cost-Benefit Analysis AWS provides a Total Cost of Ownership (TCO) analysis that helps organizations develop the business case for adopting cloud services The transformation requires a move from CapEx to OpEx and allows organizations to only pay for what they utilize Reallocation of Resources Optimal cloud adoption requires a plan to refocus IT resources to meet customer demand, align to organizational objectives and support business strategy. An Enterprise Agreement (EA) can be completed between AWS and the organization to ensure that the appropriate contracting provisions exist. Enterprise organizations can either sign a unilateral or bilateral Non-Disclosure Agreement (NDA) with AWS. An Implementation Services Addendum (ISA) is attached to the enterprise agreement for contracting with AWS Training or Professional Services (ProServe). A Business Associate Agreement (BAA) is used to protect personal health information (PHI) with HIPAA guidelines. 3. Build Knowledge and Capacity 2. Identify Benefits to the Organization 4. Complete Enterprise Agreements 7. Application Migration 8. Institute Cloud Operating Model Application Portfolio Assessment A detailed assessment of all workloads is essential for understanding resources, dependencies, licensing, etc. Assessed workloads can be placed into phases for migration based on pre-determined patterns and dependencies. Migration Factory Migration Factory refers to the group(s) designated to assist in the planning and migration of in-scope workloads to AWS. The factory includes processes, procedures and tools. Amazon Partner Network (APN) partners are uniquely skilled at migrating workloads in the most effective and efficient manner possible. AWS provides services to help organizations move to a continuous integration / continuous delivery model to increase agility. AWS includes integrated tools such as OpsWorks, Trusted Advisor (below), CloudTrail and CloudWatch that help measure, track, monitor, alarm and operate the cloud environments in an optimal manner to drive continuous improvement. There are many 3rd party tools that are specifically developed to help operate your AWS cloud in the most efficient way possible. 5. Conduct Enterprise Maturity Assessment Detailed design of security controls and processes Best-practices design of the virtual private cloud (VPC) environment Establishment of network connectivity and integration Architecting for high-availability and disaster recovery Development of application patterns for the migration of current state workloads to AWS Decoupling of enterprise-class workloads for migration to AWS 6. Design Cloud Infrastructure The maturity of key IT service management processes are assessed to ensure that the cloud transformation is sustainable, supportable and systemic. Training and Documentation AWS provides different levels of support and training for customers ranging from free, self-help videos to instructor-led training. All services include detailed documentation. AWS Self-Paced Training Introduction to AWS videos AWS Essentials Training Instructor-Led Training Architecting on AWS Architecting on AWS – Advanced Concepts Developing on AWS Systems Operations on AWS Advanced Operations on AWS Specialty Training Big Data Technology Fundamentals Big Data on AWS Version 1.0 (01/15/2015)
- 14. Business Perspective Business Perspective Value Management IT Strategy Portfolio Governance Cost Management Risk Management Benefit Management Manage financial aspects and optimum IT investments Manage costs by focus on sourcing on IT capability as a whole rather than the individual components Measure and optimize value to the business from IT investments Practices for IT governance are integrated with overall business governance Manage IT risk in alignment with overall risk management IT strategy is aligned with the Business strategy and includes the Cloud Strategy
- 15. Platform Perspective Conceptual Architecture Logical Architecture Implementation Architecture Application Migration Patterns Cloud design principles and patterns Detailed definitions of technology solutions to achieve the desired state High-level roadmap for desired state of the technology–enabled organization (‘Enterprise Architecture’) Best practices for migrating existing non-cloud applications Design principles and patterns for cloud solutions for consistency and reuse Intermediate definitions of technology solutions to achieve the desired state Platform Perspective Architecture OptimizationOptimization of architectures to derive value from cloud’s proposition of agility and cost savings
- 16. Application Disposition Model Discover/Assess/Prioritise Applications Use Migration Tools Transition Production Retain / Not Moving Redesign Application/ Infrastructure Architecture App Code Development Purchase COTS/ SaaS & licensing Test Modify underlying Infrastructure Full ALM / SDLC Manual Config Manual Deploy Manual Install Retire / Decommission Determine Migration Path Automated Manual Install & Setup Integration
- 17. Diagram Account , VPC Structure & Network Identify SSO & Key Management Processes Week 1 Week 2 Determine Security Variances IA Sign-Off Identify Environment Exceptions, Integrations & Partners Validate VPC Infrastructure Determine Environment Exceptions & Integrations Identify Necessary Roles/Credentials Implement Account Structure Implement IDM/SSO & Account Federation Implement VPC & Security Groups Configure Admin/Security Logging & Alerting Implement Exceptions & Integrations Validate AWS Monitoring & Alerting Validate Integrations Determine Migration Processes Engage Authorization Process Create CF Template Discover Design BuildKey Infrastructure & Migration PreparationInfrastructure Migration
- 18. Maturity Perspective Cloud Readiness Assessment Cloud Maturity Heat-map Assessment Target Platform Capabilities Application Portfolio Analysis Roadmap sequencing IT Management Assessment Summarizes information on maturity aspects for decisions and prioritization Determine how ready the organization is to move to the cloud – IT systems and processes Review the portfolio of applications and data and assess suitability for the cloud Determine what changes are needed in IT management Identifies new or changed technology platforms and services for cloud Determine sequencing of initiatives for cloud adoption, and dependencies Maturity Perspective
- 19. Process Perspective Portfolio Management Service Delivery Management Program & Project Management Continuous Integration/ Continuous Delivery Process Automation Quality Management Delivers services that meet Service- Level Agreement (SLA) and Operational-Level agreement (OLA) standards Programs and projects for cloud adoption are managed systematically and metrics used to monitor processes Delivery processes are automated, including creation of infrastructure stacks from scripted definitions IT services are managed as a portfolio to deliver maximum business value Iterative software lifecycles deliver incrementally with process automation Quality standards are defined and practiced at all stages of the lifecycle Process Perspective
- 20. Operations Perspective Cloud Service Management SLA/OLA Strategy Business Continuity Planning Incident & Problem Management Change and Configuration Management Performance & Operational Health Sets out the strategy and policies to define and meet SLA and OLA standards, including during disasters Plans are made for the business to be able to cope with unexpected IT situations, including IT disaster recovery Configuration Items are recorded and change is managed systematically Caters for service management and control of cloud solutions Manages incidents and problems in running solutions; identifies and removes root causes Proactively monitors cloud solutions and resources to ensure that the desired level of performance is met Operations Perspective
- 21. People Perspective Organizational Structures Roles and Job Descriptions Training Certification Readiness Manage Staffing Organizational Change Management Skills and Competencies Each role has a job description with details of qualifications, knowledge and experience Set up optimum organizational model s for cloud adoption – both Business & IT Identify gaps in competencies and provide training; encourage certification Support people in adapting to changes, e.g., new processes and culture of work Define skills and competencies required and plan career development of staff. Evaluate staffing against requirements and address gaps People Perspective
- 22. On-Premise Role On-Prem Public Cloud Comments Planning and Design No Change or Increased No Change or Increased In hybrid environments IaaS represents one more option with numerous instance types to choose from. Less time is spent on hardware configurations, however. Hardware Move/Add/Change No change Eliminated No more rack & stack for public cloud apps. Software Distribution No change Decreased You still have to distribute applications and most OS patches, but hypervisor and (optional) DBMS patching are done by the provider. Support No change Decreased Hardware support moves to the provider. Hardware Maintenance No change Eliminated You don’t own the hardware, and you don’t need to manage or work with the hardware vendors that fix it. Monitoring & Supervision No change No Change or Decreased Monitoring service is available, but with automated failover you may not need it as much. System Administration No Change or Increased No Change or Increased You’ll spend less time configuring servers, but more time managing hybrid cloud systems. Backup & Restore No Change No Change Archival No Change No Change Batch Procession & Scheduling No Change No Change Database No Change Decreased DBMS patching and tuning is done by the provider when using their database service. Middleware No Change No Change Security No Change No Change Multi-tenancy adds requirements, but those are handled by the provider. Disaster Recovery No Change No Change Still have to plan and test. Methods & Tools No Change No Change Procurement No Change Decreased No more data center hardware to buy. Premises No Change Eliminated No more physical facility requirement.
- 23. Security Perspective Security Reference Architectures Governance, Risk, Compliance Governance, Risk, Compliance DevSecOps Principles Security Operations Playbooks Security Strategy Lifecycle Security Capabilities Published as standard patterns for different types of solutions; promotes consistency, reduces oversights Manages authority and accountability; minimizes and manages risks; ensures policies and regulations are met Tactics, techniques and procedures to consistently operate securely Articulates security principles, standards, measures and processes. Specifies capabilities required to implement security for the solution Support to implement security in agile iterative lifecycles Security Perspective
- 24. High Level Transformation Roadmap Kickoff – Initiative Setup & Logistics Identify & Assemble Core “Incubator” Team Weeks 1-2 Weeks 3-4 Weeks 5-6 Weeks 7-8 Weeks 9-10 Weeks 11-12 Weeks 13-14 Weeks 15-16 Skills Assessment Train Incubator Train extended team Ongoing Customer Initiative Releases EstablishPortfolio Governance Training & Skills Development Jumpstart – Design & Build Platform Weeks 17-18 See Detailed Plan Weeks 19-20 Execute Cloud Governance in Budget Planning & IT Optimization Initiative Design New Workload Patterns Integrate roadmap outputs as scope for existing & new workloads. This will maximize value by aligning adoption with natural initiative release cycles. Integrate & Improve Operations Processes Integrate & Improve InfoSec Operations Integrate Integrate Improve Improve Capability – Product Workload 1 Phase 1 Capability – Product or Workload 2 Phase 1 Phase 3Phase 2 Quarterly Review & Revision of Roadmap & Plan
- 25. Next Steps/Key Takeaways Schedule a 1-day IT Transformation Workshop with executive stakeholders Create Cloud Adoption Roadmap Define and confirm customer success criteria (Business strategy) Conduct discovery workshop and develop/refine the cloud strategy Develop the people model (teams, roles & responsibilities) Conduct an application portfolio assessment Begin migration of workloads Implement cloud operating model
Hinweis der Redaktion
- Welcome to the IT Transformation in the Public Sector Webinar or as I’d like to call it “a How to Guide”. This is the first webinar in a series of 3 webinars scheduled (today, Dec 8th, and Dec 15th). My name is Sanjay Asnani, and I lam part of a World Wide Professional Services team that leads the IT Transformation initiatives for our strategic enterprise customers in the public sector space. ProServe is a global team with consultants across APAC, Americas and EMEA. AWS Professional Services is a partner and trusted advisor in your journey with skills in technical areas around security, architecture, analytics, etc. But our overarching role is to serve as strategy consultants to enable customers and partners – and share the collective knowledge/best practices from our global deliveries worldwide. And our primary GOAL is to ACCELERATE the adoption and shorten the time to value for customers. Today’s webinar is to share insights about the IT Transformation process, the challenges customer face when they start the journey into the cloud, and how they can leverage the AWS Cloud Adoption Framework (CAF) and map those to an actionable transformation plan. I’d share the 7 key CAF perspectives in detail, which hopefully educates you on how you can leverage the same framework to envision your own transformation experience.
- ProServe focuses on Prescriptive guidance and implementation assistance across the full stack. At the top level is the IT Transformation Process which is focused on addressing the key questions as you build your cloud adoption roadmap, thinking through the business strategy, Governance, Operations & Change Management; and assist customers with operational integration and developing their security policies and procedures based on proven designs to meet compliance requirements. And we also offer our expertise in areas such as application optimization, big data, and infrastructure architecture.
- AWS has been around since 2006, and has more than a million active customers in 190 countries, including nearly 2,000 government agencies, 5,000 education institutions and more than 17,500 nonprofits. Here’s a snapshot of a few customers spread across the globe, using AWS in every imaginable use case you can think of. For example - Transport for London: has created an open data ecosystem with Amazon Web Services University of Notre Dame migrated its website and global student/faculty authentication stores to AWS, and plans to move 80% of its workloads in the next three years. As a result, Notre Dame has saved 40% on its annual IT operations by moving to AWS thus far. City of McKinney started their IT transformation journey this year to Deliver More and Better IT Services for their tax payers with less money.
- AWS has a deep and broad Partner Network (APN) which includes tens of thousands of consulting/systems integrator and technology/ISV partners, and has grown over 50% over the past 12 months. For example: Accenture has been a key global partner for long time, Accenture and AWS announced creation of a new business group a month ago to help enterprises migrate to and run their business in the AWS Cloud. Datapipe - is an AWS Premier Consulting Partner and provides managed cloud services for AWS. Cloudnexa - Cloudnexa deploys and manages cloud infrastructure for clients who want to realize the full power of Amazon Web Services Acquia - provides a wide variety of commercial products, services, and support that help organizations build and manage Websites on the Drupal open source social publishing platform. SumoLogic - Sumo Logic started provides expertise and solutions in log management, scalable systems, Big Data, and security.
- Organizations are faced with this unique proposition and opportunity to move to cloud in a massive IT paradigm shift which has been occurring for the last decade or so in their quest to become more AGILE. Customers are looking to move away from fixed costs, capital intensive IT, with high maintenance and overheads TO more pay-as-you go, innovate faster in responsive and agile fashion, and bring products to market faster approach…..
- With the opportunity, however comes the challenges - rightfully so - due to the investments made over the last 25 years in infrastructure, applications, architectures, and above all – people and skills.
- Most customers tend to dip their toe in exploration mode, where they run non-production workloads mostly with the intent of proving out the concept (POC) and building their comfort level with cloud/AWS, and then graduate to migrating existing workloads, and onto developing new applications with “cloud first” strategy. And complete transformation occurs gradually when legacy workloads get migrated in droves with the conscious effort to move away from DCs completely.
- Our customers have told us over and over, especially in the public sector and large enterprises as well - technology alone is rarely the challenge! We need to address the problem more holistically – people, process, and of course technology together. Hence - to guide the journey to a new IT operating model, we use the AWS Cloud Adoption Framework (CAF). It helps an organization develop and execute a comprehensive plan by separating complex IT environments into manageable areas of focus: business strategy and process organizational structure and skills And, Operations. The CAF is supported by a knowledgebase of reusable assets, including tools to reduce the time and cost of deployment.
- So, what is the AWS Cloud Adoption Framework or CAF? It is a comprehensive framework that helps bring together people, process, and technology to drive efficient, effective, and secure cloud adoption, based on defined business objectives Just like any journey, you start with your core business objectives – your core mission – is it agility, is it cost savings, is it more responsiveness to your constituents and taxpayers needs, and then take a plunge into discovery phase Understand business strategy and market drivers to incorporate the requirements in development of your cloud strategy and targeted rate of adoption (experiment, test & development, production, all-in). Engage key stakeholders from the start in developing a cloud strategy 2) Setting the baseline or I refer to it as Rapid discovery: This incorporates the cloud adoption strategy, baseline 3) Which then leads to gap analysis 4) And path to developing CAF activities matrix. These activities are basically a matrix to inform and drive the development of a comprehensive and prioritized cloud adoption roadmap for your initial 6-9 month delivery Next STEP is go deep into CAF Perspectives: The AWS CAF Perspective provide guidance on seven key focus areas required to develop a comprehensive activities matrix and adoption roadmap. The benefits of looking at the IT Transformation process through the lens of these perspectives are: - Comprehensive understanding of cloud strategy & delivery Cloud adoption approach that incorporates more than technology And above all – it ties in all the components of the IT eco-system into the cloud adoption Then the framework flows into the Delivery or as I like to call it - Execution piece of the plan or really the Framework: With AWS and Partners to help support throughout the process, we see it as a continuous cycle of 4 phases, with sort of DevOps approach of automate, measure, and improve each iteration of the cloud adoption Explore - why do it, what business value, gap analysis Prepare - project plan for activity, training, establish platform, establish operations, establish security Migrate/Develop - Move an existing application to the cloud or develop a new cloud native application Iterate - measure and identify opportunities to improve
- So, let’s do a deep dive into the core perspectives (the colored hexagons) The framework organizes the areas of focus that will need to be addressed into seven perspectives that can be overlaid against the organization IT lifecycle to create strategy for orchestrating the actions of the people in the organization that are focused on different portions of delivering and operation solutions that provide customer value. This approach is based on lessons learned from thousands of successful customer engagements. AWS offers a comprehensive set of technologies and content describing best practices on how they can be leveraged, this framework explores other areas that need to be address to align IT delivery and operation with business-related imperatives. By considering each perspective, determining the current state and creating a time-sensitive roadmap to the achieved target state, consistent and repeatable success on projects associated with cloud adoption can be achieved. For example: while going through people perspective, you may ask yourself: What skills and capabilities are required? How to compose adoption team? Or under Operations perspective: What tooling do we need? What is the new ITSM cycle? Or in security perspective: you need answers to: Will risk increase? Can we run cloud secure and compliant? The importance and prioritization of action against the perspectives will be based on the unique circumstances of the customer. By comparing insights gained through the Maturity Perspective and Business Perspective, a rough strategy and roadmap can be organized and used to inform assessment of the remaining perspectives. We have seen organizations form a small core team with each member having responsibility for a perspective, which allows better communications across the organization as interactions are targeted to a specific viewpoint. Leveraging the agile approaches described in this framework, the core team can collect and share information, enabling directional shift as circumstances change and information is gathered. As insight is gained for each perspective, greater defined roadmaps can be created that reflect initiatives that must be accomplished across all of the perspectives and will be executed by different teams across the organization. Dependencies can be mapped inside of the perspective by members of extended team and the core team can identify and mitigate dependencies across perspectives.
- The various perspectives are aligned with the respective industry standard frameworks and are optimized for cloud adoption and modern IT environments. Examples include Benefit Management for value realization, TOGAF for enterprise architecture, ITIL for operations, MSP/Prince2 for management, and COBIT for governance. The importance and prioritization of the perspectives will be based on the unique circumstances of the organization.
- In the example shown, the core team laid out a strategy to complete a business case to justify a value uplift through a cloud-based solution. The team then decided to conduct a discovery workshop, and from the workshop, three core team members started separate initiatives; one defining the requisite governance structure, another defining the network environment, and a third analyzing the application portfolio. Since the core team was meeting regularly to provide updates on their areas the team was able to work together to determine prioritization based on the insights discovered. This example shows the information collected during application portfolio analysis and from defining the network environment led to next steps of defining security requirements as a top prioritization because of the concern the leadership team expressed, defining the cloud environments so skills gaps could be better determined, and training and certification solutions identified and work started because the core team was informed lead time to delivery would be longer than other initiatives. An initiative with the operations team was started to plan delivery of new capability, train staff, determine monitoring requirements, and formalize measurement and reporting against service level agreements (SLAs). A member of the core team also work with finance and procurement on cost and billing, another team member focused on reviewing and updating Enterprise policies and practices, and a plan for monitoring and optimization of the cloud environment was defines.
- Apologies for the small font here, but I kept this slide in here to show how this Framework brings it together in a step by step fashion all the way from your business strategy to instituting a cloud operating model.
- The Business Perspective allows assessment for identifying, analyzing, and measuring the effectiveness of IT investments that generate optimal business value. Business case creation and valuation are completed using cost and billing analysis techniques, as well as total cost of ownership (TCO) and cost benefit analysis (CBA) techniques per initiative. Initiatives in the portfolio are compared and prioritized then an IT strategy is created. Governance and account planning is completed and measurement information created and defined as part of the functional requirements for each initiative. to analysis. A brief explanation of each subcategory for the Business Perspective follows: Value Management/ - evaluate your current business case creation and evaluation practices and supplement with additional areas that provide worse case/best case insight and actuary graphing of expected results. Additionally will be used to create functional requirements for metric-based tooling required to capture and analyze actual versus expected business impact of cloud based solutions. IT Strategy – used to develop an IT strategy roadmap for cloud adoption based on business language and meant to reflect a business viewpoint. Cost and Billing Analysis – used to capture cost information for current solutions, estimated future on premise and cloud-based solutions, and is used for business case creation. Cost Management/Benefit management – To capture cost and benefit information as well as assumptions used to provide consistent and equal evaluation of various initiatives. Information from this sub process area is used to complete business case creation. Portfolio Governance – used to capture delta between required and current processes for capturing, measuring, and monitoring business costs and financial recording, as well as broader account planning alignment required for successful cloud adoption.
- The Platform Perspective allows assessment of current state environment and strategy for decomposing and identifying workloads that will shift to cloud-based delivery. A brief explanation of each subcategory for the Platform Perspective follows: Conceptual Architecture – used to describe IT delivery environment using current business context and ideal business context, and is based on a balanced approach to addressing short and long term business concerns, goals, and initiatives. Indicates current versus future business capabilities and delta with roadmap to achieve future state vision. Cloud Design Principles and Patterns – used as guidance to reflect overall principles adhered to during solution development, guidance on categorization of information that systems will consume, modify, or reference, and known styles and patterns the organization will leverage. Logical Architecture – used to describe the IT delivery environment using current technology context and ideal technology context, and is based on a balanced approach to addressing short and long term technology concerns, goals, and initiatives. Indicates current versus future technology capabilities and delta with roadmap to achieve future state vision. Application Migration Patterns – used as guidance to reflect overall principles adhered to during solution development, guidance on best practices needed to operationalize solutions using modern, cloud-based development patterns. Implementation Architecture – used define the physical and operational IT environment using current and ideal technology context, and is based on a balanced approach to addressing short and long term technology concerns, goals, and initiatives. Indicates current versus future technology capabilities and delta with roadmap to achieve future state vision.
- As we just discussed, platform perspective allows assessment of current state environment and strategy for decomposing and identifying workloads that will shift to cloud-based delivery. This slide reflects a decision tree as you’re looking into your portfolio of workloads and making decisions as to which route gets you to the future state with your objectives in mind. For example, re-hosting – it’s probably the fastest route to get into the cloud, but if your applications are not architected in cloud-optimized fashion (e.g. loosely coupled), you may not be able to take advantage of all that cloud has to offer; but you get into AWS faster and gets you out data center business. Refactoring on the other side of the spectrum, however, is probably slower but from timing perspective it may be the best if your strategy calls for re-writing/refactoring due to the market requirements and challenges…
- Once you have gone through the application portfolio assessment and made decisions on right path whether it’s rehosting, refactoring, or repurchasing SaaS based solutions, you’re ready to chart your infrastructure plan with specific tasks such as designing your VPC and network components, identifying the roles and responsibilities and translating those into Identity and Access Management service of AWS.
- The Maturity Perspective allows assessment to determine readiness for cloud adoption. The focus is on understanding the level of rigidness in the existing portfolio and understanding the approach to managing the IT environment. The greater the decoupling and decomposition of existing solutions the lower the delta to adopt the AWS cloud and the lower the risk. The greater the experience of the operations team to manage the environment remotely the easier the transition to managing a hybrid environment. These will also provide key insights and input for the other perspectives. A brief explanation of each subcategory for the Maturity perspective follows: Cloud Readiness Assessment – used to determine compute/network, storage, information/database levels and needs, performance/capacity, service catalog, GRC level, change management maturity, executive sponsorship level. Application Portfolio Analysis – used to determine systems of record, systems of integration, correlation to business capabilities, condition of application, expected life span, user adoption, business value. IT Management Assessment – used to determine CMMI Maturity Level, lifecycle maturity levels for cost/value, process, and people. Target Platform Capabilities – used to determine ideal platform state, current/future state delta, platform, and platform service duplication and requirements. Cloud Maturity Heat-map Assessment – used to consolidate and collate the information gathered in the maturity perspective to determine rough prioritization of cloud adoption, cost, business impact. Roadmap Sequencing – used to capture and describe order of initiatives, dependencies, success/failure business impact.
- Process is a key piece in any technology project implementation, let alone when the organization as a whole is migrating to cloud. In almost every phase starting from Strategy and all the way to Operations and Improvements, process is at the center of it. Throughout the cloud lifecycle – customers need to evolve their processes around planning, iterative development, and operations and optimization phase. The Process Perspective allows assessment to determine what processes are in place, and what processes will need to be modified or created to drive successful cloud adoption. Core to process assessment and modification should be a common set of principles all adhere to that reflect Lean-Agile and/or iterative/incremental approach principles. Part of the value of cloud environments is the ability to leverage agile and incremental methodologies for development and operations, therefore the entire IT lifecycle must share agile principles. Some perspectives to consider include maintaining a customer focus, delivering small/iterative releases, collecting and providing fast and constant feedback, agreeing to operational as the end point for the entire IT organization, and making quality of customer experience everyone’s responsibility. A brief explanation of each subcategory for the Process Perspective follows: Portfolio Governance and Planning – used to establish scope and authority of governance, identify core team members and stakeholders, value and measurement, funding, prioritization, and dependencies of portfolio. If portfolio governance and planning are already established, principles and practices must be modified to reflect updated overall principles. Quality Assurance – used to align level of decomposition for solution space to testing/validation strategy, define and monitor approach to testing from envision through operations, set principles and governance aspects to enable an effective quality assurance process. Program and Project Management – used to drive and track business capability delivery into operations and customer adoption, and apply learnings from development and solution usage to guide modification to the system. Requires identification, metrics, and monitoring of success criteria prior to project start. Service Delivery Management – used to set strategy for enabling creation, delivery, and management of services. Aligns to overall governance principles in the operations of services to deliver as service level agreement (SLA) and operational level agreement (OLA) levels that meet or exceed customer expectations. Process Automation – used to establish a strategy for achieving business value goals, and enabling highly scalable and virtualized data centers through process automation. Informs approach for defining common and unique workloads to determine priority and value of workload automation. Continuous Integration/Continuous Delivery – used to enable automation and improvement of software delivery through automated testing, continuous integration, and continuous deployment. Provides plan for delivering business value through the ability to rapidly, reliably, and repeatedly deliver capability and innovation.
- The Operating Perspective allows assessment to determine current operating procedures and identification of process changes and training that will be needed to allow successful cloud adoption. A brief explanation of each subcategory for the Process Perspective follows: Cloud Service Management – Caters for service management and control of cloud solutions SLA/OLA Agreements – Sets out the strategy and policies to define and meet SLA and OLA standards, including during disasters Business Continuity Planning - Plans are made for the business to be able to cope with unexpected IT situations, including IT disaster recovery Incident and Problem Management - Manages incidents and problems in running solutions; identifies and removes root causes Change Configuration Management – Configuration Items are recorded and change is managed systematically Performance and Operational Health - Proactively monitors cloud solutions and resources to ensure that the desired level of performance is met
- This is one of the key perspectives of the framework - The People Perspective - allows assessment of the current organizational structure and development of a change management strategy that drives successful cloud adoption. The focus is on identifying people and organizational reporting structure changes needed, determining the skills gap for delivering customer value through cloud-based solutions. Strategies for training and readiness, sourcing and partnering, and change management are created and deliverables from the assessments. A brief explanation of each subcategory for the Process Perspective follows: Cloud Roles and Job Description – used to define roles and job descriptions required to deliver cloud-based solutions using lean and agile approaches. Organizational Structures – used to identify current reporting structure and model optimized organizational structure for delivery and operation of cloud-based solutions. Skills and Competencies – used to map industry-specific and cloud solution specific skills and competencies required per role for successful cloud adoption. Training and Readiness – used to define assessment, readiness, and training resources available and needed, as well as assessment approaches required to evaluate current level skills and achievement of required levels of skills to deliver expected service and business value, as well as expected customer value. Sourcing and Partnering Structures – used to map skills gap between existing and required levels of staff skill and create alternate skills sourcing approaches for internal and long term staffing mitigation. Change Management – used to create strategy and high level tactical plan to generate urgency, provide steps for driving required organizational change needed to successful cloud adoption.
- Perhaps the most interesting slide in People Perspective is coming up with a matrix like this – where you can contrast and compare and share across the organization how the roles will evolve; migrating to cloud is rarely losing jobs or people – as much as freeing them up to focus the higher mission of the business with shedding the burden of undifferentiated heavy lifting. In fact, we frequently hear from customers that sometimes merely changing the title with “cloud” embedded in people’s roles has been a morale booster and a retention enabler.
- The Security Perspective allows assessment of current governance, compliance, and risk assessment practices to determine approach to maintaining security, privacy, regulatory compliance, and risk avoidance at an acceptable level to meet or exceed customer expectations. A brief explanation of each subcategory for the Security Perspective follows: Security Strategy - Articulates security principles, standards, measures and processes. Security Reference Architecture - Published as standard patterns for different types of solutions; promotes consistency, reduces oversights GRC Role Separation - Manages authority and accountability; minimizes and manages risks; ensures policies and regulations are met Service Security Lifecycle - Specifies capabilities required to implement security for the solution Security Operational Playbook - Tactics, techniques and procedures to consistently operate securely DevSecOps - Support to implement security in agile iterative lifecycles
- And ultimately, what you’re aiming for through this exhaustive and comprehensive exercise is creating something like this example – a high level transformation map. We are working with a medium size city government customer that was facing the challenge of migrating about 250 VM servers, with half their environment in a collocation and half on-prem. Costs are high, provisioning server takes days if not weeks, IT gets bogged down in capacity planning and procuring storage and networking gear years in advance, and every hardware refresh cycle creates more work in terms of dealing with RFPs, vendors, etc. – most of which not adding value to this city’s ability to serve its utility, police, EMS, or parks department. So, we engaged earlier this year and crafted this roadmap. Starting with an IT Transformation workshop, where CIO and the entire team got together for 1-day and went through all components of CAF, and walked out with a plan -
- The first in a list of recommended next steps has already been completed through this ITTW. From this, a high-level cloud adoption roadmap will also be available. Some additional steps are noted here.