Just a quick post today to highlight a neat Azure DevOps Demo related to how to create a Cloud Adoption Framework Plan.
As part of the CAF Plan documentation on Microsoft Docs comes a really useful Azure DevOps Deployment configuration to help and guide you and your organisation to develop that plan:
Use the cloud adoption plan
The cloud adoption plan organizes activities by activity type:
- Epics: An epic represents an overall phase of the cloud adoption lifecycle.
- Features: Features are used to organize specific objectives within each phase. For instance, migration of a specific workload would be one feature.
- User stories: User stories group work into logical collections of activities based on a specific goal.
- Tasks: Tasks are the actual work to be done.
At each layer, activities are then sequenced based on dependencies. Activities are linked to articles in the Cloud Adoption Framework to clarify the objective or task at hand.
The clearest view of the cloud adoption plan comes from the Epics backlog view. For help with changing to the Epics backlog view, see the article on viewing a backlog. From this view, it’s easy to plan and manage the work required to complete the current phase of the adoption lifecycle.
Align the cloud adoption plan
The overview pages for the Strategy methodology and the Plan methodology each refer to the strategy and plan template. That template organizes the decisions and data points that will align the template for the cloud adoption plan with your specific plans for adoption. Considering completing the exercises in the Strategy methodology and the Plan methodology before aligning your new project.
The following articles support alignment of the cloud adoption plan:
- Workloads: Align features within the cloud migration epic to capture each workload to be migrated or modernized. Add and modify those features to capture the effort to migrate your top 10 workloads.
- Assets: Each asset (virtual machine, application, or data) is represented by the user stories under each workload. Add and modify those user stories to align with your digital estate.
- Rationalization: As each workload is defined, the initial assumptions about that workload can be challenged. This might result in changes to the tasks under each asset.
- Create release plans: Iteration paths establish release plans by aligning efforts with various releases and iterations.
- Establish timelines: Defining start and end dates for each iteration creates a timeline to manage the overall project.
These five articles help with each of the alignment tasks required to start managing your adoption efforts. The next step gets you started on the alignment exercise.
My Main ReadMe Page is all set up with a bit about me!
The guys at 100DaysofCloud have set up the GitHub repo to be cloned and also have a great repo containing ideas and areas to collaborate on: https://github.com/100DaysOfCloud/100DaysOfCloudIdeas
My Github Journey tracker can be found here: https://github.com/jonnychipz/100DaysOfCloud
Please Watch/Star my repo and feel free to comment of contribute to anything I push! I really look forward to hearing from anyone who is going to jump on the journey around the same time as me! Lets see where I get to in 100 days!
I would encourage others to jump on this journey, I’m not sure that I will be able to commit every day for 100 days, but as long as I can complete 100 days that will be great!