Application Modernization
Departmental Journey[edit | edit source]
Prioritization[edit | edit source]
 Assess Legacy Data Centres
|
 Recommend Priority Data Centre Closures
|
 Gate 1: GC EARB Endorsement of DC Closures
|
 Notify Impacted Departments
|
 MoU for funds to support departmental discovery
|
Discovery[edit | edit source]
|
Application Portfolio Analysis
|
 Engage SSC PM and WLM Factory suppliers
|
 Document Project Milestones
|
 Document Cost Estimates
|
 TBS Oversight Team review of costs, plan, and portfolio analysis
|
Gate 2: GC EARB Endorsement. MoU to Release Execution Funds
|
Execution[edit | edit source]
 Staff project team
|
 Configure Cloud Platform
(e.g. Landing Zone) |
 Launch Security Assessment & Authorization process
|
 Develop test plans
|
 Execute migrations, security assessments, & testing
|
 Report status to TBS Oversight Team
|
Decommission legacy data centre
|
Discovery
Application Porfolio Analysis
Determine Modernization Vision for the Organization
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; 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 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 security
- Increase quality
This guide does not instruct an organization how to undertake its modernization journey, but instead 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.
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.
cloud maturity map will be inserted here
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 imitative 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.
A simple scorecard link to scorecard here 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.
For organizations that desire to forego modernization opportunities, the decision to rehost the entire application portfolio to a new data centre provides that opportunity.
