Mastering Cloud Adoption Framework: Quick Start Backlog essentials 💪

The Microsoft Cloud Adoption Framework is a comprehensive set of guidelines, best practices, tools, and documentation. But, this comprehensiveness can render the framework complex and potentially overwhelming for individuals and organizations, most notably for those with limited cloud expertise. As an attempt to offset the complexity I created a ready to use quick start backlog for the Design Areas sub-section of the Microsoft Cloud Adoption Framework . Via this blog post I want to share it, explain the composition and guide you on how import it into your own Azure DevOps organization within minutes.

Live demo and download of the backlog

In case you want to go right ahead with the backlog, please use the following links. If you want to know more about the backlog, please continue reading the rest of the post :)

Live demo - The DevJevNL Cloud Adoption Plan backlog
Download - The DevJevNL Cloud Adoption Plan backlog

Backlog composition

The backlog uses the scrum template and hold a total of 268 backlog items! These 268 items are divided into different work item types as shown below:

  • Epics: 9
  • Features: 59
  • Product Backlog Items: 172
  • Tasks: 28

Each epic represents a Design Areas topic with the exception of the Security topic. The sub-topic Securing privileged access for hybrid and cloud deployments in Azure AD is covered by a dedicated epic to emphasize it’s size and complexity.

Backlog and Cloud Adoption framework topics

Next each epic is devided into features where each feature represent a sub-topic of the epic in question.

Backlog and Cloud Adoption framework sub-topics

The features are then further divided into product backlog items which represent the actionable items that need to be completed to achieve the feature in question. In some cases the product backlog items are further divided into tasks to make the work more manageable. Combine result looks like shown below.

Backlog and Cloud Adoption framework product backlog items
companion to it.

How to import the backlog into your Azure DevOps organization

To import the backlog into your Azure DevOps organization, you need to use the Azure DevOps Demo Generator . The Azure DevOps Demo Generator is a community project that helps with the creation of Azure DevOps projects with pre-populated (sample) content that includes source code, work items, iterations, etc… It leverages the Azure DevOps REST API to provision data. For more details of this tool please check my previous blog post Use Azure DevOps Demo Generator to create a new Project in Azure DevOps .

To import the backlog into your Azure DevOps organization, follow the steps below.

  1. Navigate to the Azure DevOps Demo Generator website.
  2. Click on the Sign in button in the top right corner of the page.
    Azure DevOps Demo Generator - Sign in
  3. Sign in with your Azure DevOps credentials (make sure the account in question has the correct permissions ) to create Azure DevOps projects.
  4. Click on the Choose template button.
    Azure DevOps Demo Generator - Create a new project
  5. In the choose template page, select the private option.
  6. Select the radio button GitHub and enter the following URL: . Finish by clicking submit.
    Azure DevOps Demo Generator - Select the template
  7. Now click submit and wait for the import to complete.
    Azure DevOps Demo Generator - Importing
  8. Once the import is completed, click on the Navigate to project button to review the imported backlog.
    Azure DevOps Demo Generator - Finished importing
  9. To make the whole structure visible select the Epics option from the backlog item type filter (if the option is missing click on hte cogwheel next to it and ensure hte checkbox in from of Epics is visible).
    Azure DevOps Demo Generator - Set the correct view level
  10. Enjoy your backlog! It should looks something like this.
    Azure DevOps Demo Generator - Success!

Wrapping up

I hope you find the The DevJevNL Cloud Adoption Plan backlog backlog useful. If you are interested in the reference material used to make this post, please visit the following links.

As always, a big thanks for reading this post. If you liked it, don’t be shy and have a look at my other posts .