Changes

Jump to navigation Jump to search
m
no edit summary
Line 57: Line 57:  
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment.  
 
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment.  
   −
If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program. Departments are required to complete the [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template] and engage your Departmental Architecture Review Board before being brought forward to request endorsement by governance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group], [[GC EARB]], ADM CEPP, and DM CEPP). The request for endorsement is a department’s opportunity to make a strong business case for investment to address at-risk technologies.
+
If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program. Departments are required to complete the [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template] and engage your Departmental Architecture Review Board before being brought forward to request endorsement by governance:
 +
* [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group]
 +
* [[GC EARB]]
 +
* ADM CEPP
 +
* DM CEPP)
    
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework, and the modernization strategy that will be used (rehost, replatform, refactor, replace and to which hosting platform; data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services)
 
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework, and the modernization strategy that will be used (rehost, replatform, refactor, replace and to which hosting platform; data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services)
Line 96: Line 100:  
* [https://gccollab.ca/file/view/3088763/engeneric-wlm-app-mod-business-casefr| Business case template].   
 
* [https://gccollab.ca/file/view/3088763/engeneric-wlm-app-mod-business-casefr| Business case template].   
   −
Partner departments are provided guidance/assistance to provide an accurate list of applications by updating the APM and prepare for the [https://wiki.gccollab.ca/File:WLM_Governance.png governance] endorsement.   
+
Partner departments are provided guidance/assistance to provide an accurate list of applications by updating the APM and to prepare for the [https://wiki.gccollab.ca/File:WLM_Governance.png governance] endorsement.   
 
* [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group]
 
* [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group]
 
* [[GC EARB]]
 
* [[GC EARB]]
Line 102: Line 106:  
* DM CEPP)
 
* DM CEPP)
   −
Once endorsed by governance, the Government of Canada’s Chief Information Officer (GC CIO) and the Deputy Head of a department signs the  [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr| Memorandum of Understanding].
+
Once endorsed, the Government of Canada’s Chief Information Officer (GC CIO) and the Deputy Head of a department signs the  [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr| Memorandum of Understanding].
 
<!-- END OF ENGAGEMENT -->
 
<!-- END OF ENGAGEMENT -->
   Line 114: Line 118:     
==== <big>Determine Modernization Vision for the Organization</big> ====
 
==== <big>Determine Modernization Vision for the Organization</big> ====
By the end of this step, you should have discussed with leadership how far you want to take your modernization journey. This will be the vision for your organization. Those who will be performing the subsequent portfolio analysis steps should understand that vision.
+
This is an opportunity to determine the direction for the organization and ensure those performing the subsequent portfolio analysis steps understand the vision to modernize and be more transformative! Perhaps your organization has already begun a modernization journey. In today's IT environment [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary:      
 
+
* Deliver IT faster
This is an opportunity to determine the direction for the organization; is it to largely sustain current operations and culture, or does the organization desire to modernize and be more transformative. Perhaps your organization has already begun a modernization journey. In today's IT environment [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary     
  −
* deliver IT faster
  −
 
   
* Increase reliability
 
* Increase reliability
 
* Increase security
 
* Increase security
 
* Increase quality  
 
* Increase quality  
This guide is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting Roleroles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.  
+
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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre 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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre 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. Here is a simple visual for plotting your [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] adoption .
+
Here is a simple visual for plotting your [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] adoption .
    
[[Image:Cloud maturity map .png]]
 
[[Image:Cloud maturity map .png]]
   −
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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre 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 [https://gccollab.ca/file/view/3691530/engc-cloud-rr-matrixfr GC Cloud R&R Matrix] to ensure your organization is ready to undertake the required roles to support [https://wiki.gccollab.ca/GC_Cloud_Infocentre 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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud]. The build from these experiences and transfer these skills to train others. 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. Review the [https://gccollab.ca/file/view/3691530/engc-cloud-rr-matrixfr GC Cloud R&R Matrix] to ensure your organization is ready to undertake the required roles to support [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services.
   −
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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] with enough time and effort.  
+
See the [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] to assess low risk workloads for cloud migration. It provides 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 [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] with enough time and effort.  
    
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
 
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
213

edits

Navigation menu

GCwiki