Changes

* 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 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 Roleroles, 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.  

[[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 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.

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 [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 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 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 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.