Cloud Computing Business Case

When change needs to happen in an organization, a business case is used to justify the change.  On page 464 in your textbook is a generic business case template.  The template is intended as a generic starting point that needs further customization to better match organization requirement and preferences.  The template also acts as a checklist of considerations that pertain to adoption.  The business case can be used to have healthy conversations around the legitimacy of the cloud or any technology adoption in the preliminary planning stages. For this assignment, please complete business case sections G.3 and G.4 in the attached document

 

G.1. BUSINESS CASE IDENTIFICATION

This section provides information that specifies the details of the business case, such as the following:

• Business Case Name

• Description – A brief summary of the business case’s purpose and goals.

• Sponsor – Identification of business case stakeholders.

• List of Revisions (optional) – Revisions by date, author, and approval if control or historical logging is required.

G.2. BUSINESS NEEDS

The expected benefits and requirements that are to be addressed and fulfilled by cloud adoption are detailed in this part of the template:

• Background – A description of relevant historical information that spurred on the motivation for the business case.

• Business Goals – A list of the tactical and strategic business objectives that are associated with the business case.

• Business Requirements – A list of the business requirements that are expected to be fulfilled by the achievement of the business goals.

• Performance Objectives – A list of any relevant performance objectives related to the business goals and business requirements.

• Priorities – Business goals, business requirements, and performance objectives listed in order of priority.

• Affected On-Premise Solutions (optional) – A detailed description of current and planned on-premise solutions that are to be migrated, or that will otherwise be affected by the adoption effort.

• Target Environment – A description of the anticipated outcome of the adoption of the project, including a high-level overview of cloud-based solutions that are to be built in support of the business case.

G.3. TARGET CLOUD ENVIRONMENT

The cloud deployment and delivery models expected to be utilized as part of the cloud adoption effort are listed and briefly described, along with other available information regarding planned cloud services and cloud-based solutions:

• Cloud Deployment Model – Reasons for the choice of models, advantages, and disadvantages are provided to help communicate the rationale.

• Cloud Characteristics – A description of how the planned target state relates to and supports cloud characteristics.

• Cloud Service Candidates (optional) – A list of candidate cloud services and corresponding usage estimates.

• Cloud Provider Candidates (optional) – A list of potential cloud providers and a comparison of costs and features.

• Cloud Delivery Model – The cloud delivery model that is presumably required to meet the business goals of the business case is documented.

G.4. TECHNICAL ISSUES

This section highlights requirements and limitations related to common technical concerns:

• Solution Architecture

• SLA

• Security Requirements

• Governance Requirements

• Interoperability Requirements

• Portability Requirements

• Regulatory Compliance Requirements

• Migration Approach (optional)

G.5. ECONOMIC FACTORS

This section comprises considerations related to the economics of the business case, involving the pricing, costs, and formulaic tools that are used for calculation and analysis. See Chapter 15 for a broad range of financial metrics, formulas, and considerations that can be incorporated into this section.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *