Changes

* Increase security

* Increase security

* Increase quality  

* Increase quality  

This guide does not instruct an organization how to undertake its modernization journey, but instead is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting roles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.  

This guide is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting roles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.  

While some organizations have started this journey years ago and are ready to go "all in" on cloud and the workforce are DevOps practitioners, others have not begun the journey.  

While some organizations have started this journey years ago and are ready to go "all in" on cloud and the workforce are DevOps practitioners, others have not begun the journey.  

For those who have not yet begun a modernization journey the choice may be take this opportunity to start that journey. For others, they may decide to simply sustain operations as-is.

For those who have not yet begun a modernization journey the choice may be take this opportunity to start that journey. For others, they may decide to simply sustain operations as-is. Here is a simple visual for plotting your cloud adoption .

[[Image:Cloud maturity map .png]]

[[Image:Cloud maturity map .png]]

A simple visual for plotting you cloud adoption maturity can be found here. Most organizations start small with a few low risk applications. A team of willing and keen developers from within your existing workforce would lead an initative to migrate those low risk workloads to the cloud. From these experiences they would use their learnings to train others to do the same. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. An organization should review the [insert roles and reap document here] to ensure your organization is ready to undertake the required roles to support cloud services.

Start small with a few low risk applications. A team of developers from within your existing workforce would lead an initative to migrate those low risk workloads to the cloud. The build from these experiences and learnings to train others to do the same. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. An organization should review the [insert roles and reap document here] to ensure your organization is ready to undertake the required roles to support cloud services.

A [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] has been devised to assess low risk workloads for cloud migration. This scorecard is meant to provide you a short list from which to further decide where to start. Any application can be migrated to the cloud with enough time and effort. The scorecard is meant to identify low risk and low effort migrations.

See the [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] to assess low risk workloads for cloud migration. It provides you a short list to help with the decision as to where to start and to identify low risk and low effort migrations. Any application can be migrated to the cloud with enough time and effort.  

 

For organizations that desire to forego modernization opportunities, the decision to rehost the entire application portfolio to a new data centre provides that opportunity.

==== <big>Determine Rationalization and Retirement Opportunities</big> ====

==== <big>Determine Rationalization and Retirement Opportunities</big> ====

===== <u>Obsolete Applications</u> =====

===== <u>Obsolete Applications</u> =====

Your application portfolio rates the business value of applications. Review low business value applications. Assess whether these applications remain needed:

Your application portfolio rates the business value of applications. Review low business value applications. Assess whether these applications are still needed:

* Use access/update logs to identify applications that have received few updates in the past two years.

* Use access/update logs to identify applications that have received few updates in the past two years.

* Identify the most recent users and inquire as to the business value of the application. 

* Identify the most recent users and inquire as to the business value of the application. 

====== '''Replace (Repurchase)''' ======

====== '''Replace (Repurchase)''' ======

This is an opportunity to determine if Software-as-a-Service solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.

This is an opportunity to determine if Software-as-a-Service (SaaS) solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.

===== '''<u>Choose Your Migration Target</u>''' =====

===== '''<u>Choose Your Migration Target</u>''' =====

===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====

===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====

Request that TBS generate a dashboard of your application portfolio. This will ensure your decisions have been correctly reflected. A sample of the dashboard that is generated is found here:

Request that TBS generate a dashboard of your application portfolio. This will ensure your decisions have been correctly reflected. A sample of the dashboard that is generated is found here:  

[[File:SamplePortfolioAnalysis.png|1000x1000px|center|alt=Sample Application Portfolio Analysis]]

[[File:SamplePortfolioAnalysis.png|1000x1000px|center|alt=Sample Application Portfolio Analysis]]

=== ''Document Cost Estimates'' ===

=== ''Document Cost Estimates'' ===

An [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|App Mod Cost estimates template]] has been devised to identify cost estimates. A Memorandum of Understanding between the GC CIO and the Deputy Head of a department will be agreed upon by both parties to secure the funding for execution phase. The MoU generic template can be found here (insert template).

An [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|App Mod Cost estimates template]] has been devised to identify cost estimates. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the Deputy Head of a department will be agreed upon by both parties to secure the funding for execution phase.  

=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===

=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===

The [https://gccollab.ca/file/view/2649702/engeneric-wlm-app-mod-gcearb-gate1-discoveryfr generic template] for the presenting your discovery analysis and funding approval to move to execution.

The [https://gccollab.ca/file/view/2649702/engeneric-wlm-app-mod-gcearb-gate1-discoveryfr generic template] for the presenting your discovery analysis and funding approval to move to execution.

As part of the GC EARB a CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy requirement (requirement 6.4.2) and meeting requirement 6.1.1 of the Directive..

As part of the GC EARB a CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy requirement (requirement 6.4.2) and meeting requirement 6.1.1 of the Directive.

If and when endorsement is provided by GC EARB, approval will be requested from the GC CIO. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.

If and when endorsement is provided by GC EARB, approval will be requested from the GC CIO. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.

[https://youtu.be/OJeoNYvsoT4 DPI - Charting a path to success for Workload Migration: Approaches and Best Practices]

[https://youtu.be/OJeoNYvsoT4 DPI - Charting a path to success for Workload Migration: Approaches and Best Practices]

====== '''TB Policies & Standards''' ======

====== '''TB Policies & Standards''' ======