Cloud Adoption Policy Addendum

The Quickest way to FAIL a Project

Posted May 1, 2021 9:32 PM

Good Evening Class;

This will be the most important message you will read in the course, so please read it carefully, take special note of the bold and underline statements,  then read it again .  Understanding these key points will make you successful and save you from having to re-work projects.

Each project consists of templates and competencies.  Templates are the structure of the project, the major themes to address, the order in which to provide section headings in papers, etc.  Students often spend a lot of time making sure their papers are painstakingly accurate with the requirements of the template.  They make sure to include every section, and present a well written, graphically pleasing, professional looking project.  --- And they Fail!  --- 

Specifically, they receive an “NP” Grade (Does Not Meet Expectations) and have to re-work the project and re-submit.  The reason this happens is because  students sometimes ignore (or overlook) the Competencies that are required to be addressed .  Every project has a list of competencies that  must  be addressed, and I am required to show that you have addressed every one of them to at least a “Meets Expectations” level.  My grading Rubric is specifically laid out to review the competencies, so if you do not address even one of the required competencies,  I cannot pass the project .   

Furthermore, Students “assume” that all of the competencies are mentioned in the template and as long as you follow the outline, you are good.   ABSOLUTELY WRONG!   There are many competencies that do not show up in the outlines of the assignments.  You must therefore understand and address all the competencies.  How you address the competencies is up to you, but I must see that you have included them, specific enough so that they stand out and have clearly been addressed. 

The competencies for the projects are clearly listed at the bottom of each set of Project instructions.   Pay Attention to and Address ALL of them  and you will easily pas on your first submission. 

https://digitalprinciples.org/resource/howto-secure-private-data-cloud/

CCA 630 Project 1 learning Objectives

5.1: Evaluate the business IT needs of an organization.

5.1.1: Articulate the business model and value chain of the organization in the context of the organization's mission and vision.

5.1.2: Map business processes of the organization.

5.1.3: Evaluate and articulate opportunities where key IT business processes can be improved.

5.1.4: Quantify business process improvements using metrics valuable to the organization.

5.2: Propose strategies the organization can employ using cloud solutions to enhance organizational effectiveness.

5.2.1: Identify gaps and challenges in existing organizational infrastructure.

5.2.2: Articulate cloud services or technology offerings that address gaps and challenges.

5.2.3: Propose a specific cloud service or technology to address each gap and challenges most effectively.

5.2.4: Justify the proposed cloud service or technology to appropriate audiences.

5.3: Evaluate cloud adoption as a viable solution based on cost benefits and desired outcomes.

5.3.1: Describe the cost model of the cloud solution.

5.3.2: Differentiate the charging model from several cloud providers.

5.3.3: Prepare an annual budget for the cloud solution.

5.3.4: Articulate other nonfinancial benefits of the cloud solution.

5.3.5: Conduct cost-benefit analysis of the cloud solution.

5.4: Articulate insights to leadership on the appropriate course of direction on the identified IT business needs.

5.4.1: Describe cloud technologies in audience-appropriate terms.

5.4.2: Propose a realistic course of actions to achieving the benefits.

5.4.3: Identify and measure performance metrics that are indicators of a successful deployment.

5.4.4: Prepare a financial analysis of the cloud adoption proposal.

5.4.5: Articulate the value of the solution to the organization in the context of the organization's mission and vision.

8.1: Assess liability issues associated with cloud adoption.

8.1.1: Identify liability issues related to cloud adoption.

8.1.2: Describe challenges to mitigate those issues.

8.1.3: Propose solutions to minimize the liabilities.

8.3: Assess management and operational risks associated with cloud.

8.3.1: Assess and select a framework to be used for risk management.

8.3.2: Document risks associated with sensitive data.

8.3.3: Document risks associated with regulatory compliance.

8.3.4: Document a disaster recovery plan, including a disaster recovery testing plan.

8.3.5: Determine risks associated with a vendor, including potential acquisition.

8.3.6: Perform a risk/benefit analysis of a cloud solution.

9.1: Develop a plan for cloud implementation / migration.

9.1.1: Identify business goals to achieve through cloud adoption.

9.1.2: Identify internal and external constraints.

9.1.3: Delineate steps for cloud implementation.

9.1.4: Apply relevant design processes and techniques in producing effective cloud infrastructure.

9.3: Develop documentation (plans, policies, and procedures) to support a cloud operation.

9.3.1: Identify operational areas needing documentation.

9.3.2: Identify subject matter experts (including editors).

9.3.3: Develop the documentation.

9.3.4: Perform a quality review of the documentation.

11.7: Develop disaster recovery/business continuity plans.

11.7.1: Identify failure points.

11.7.2: Propose mitigation techniques.

11.7.3: Propose plans and procedures.

11.7.4: Implement steps to prepare stakeholders to carry out the plans and procedures.

11.7.5: Document the plans and procedures.

11.8: Prepare contingency plans when changing cloud providers or closing down a cloud architecture.

11.8.1: Identify affected systems after changing cloud providers or closing down the cloud infrastructure.

11.8.2 Configure the cloud infrastructure to minimize the impact.

11.8.3: Propose plans and procedures.

11.8.4: Document the plans and procedures.