Sitecore MCP 2.0 Roles and Responsibilities Matrix Decoder

TL;DR

I built an app to help me understand the differences in roles and responsibilities between MCP 1.0 and MCP 2.0, and I think it may be helpful for others.  I wanted an easy way to search or browse the different roles and responsibilities and get a clear answer. 

Check it out here:

Sitecore MCP 2.0 Roles and Responsibilities Matrix Decoder App

Navigating the complexities of the Sitecore Managed Cloud PaaS 2.0 roles and responsibilities matrix isn't particularly exciting, especially for those new to the platform or customers moving from MCP 1.0. While I discovered that the roles and responsibilities in MCP 1.0 and MCP 2.0 are fundamentally similar, MCP 2.0 introduces more detailed and specific tasks related to modern cloud infrastructure management and security enhancements.

This week, I built a learning/reference app to help Sitecore customers, developers, architects, operations administrator/support teams, and account/project managers (and myself 😏) easily reference the different roles and responsibilities defined in MCP 2.0. 

The tool sets out to simplify the process of familiarizing oneself with new tasks and responsibilities, making searching and browsing through the matrix far more digestible. Whether transitioning from MCP 1.0 or diving into MCP 2.0 for the first time,

First, let's highlight the key differences between MCP 1.0 and MCP 2.0 roles and responsibilities I noted during my research. 

The RACI Model

The MCP roles and responsibilities matrix is structured using the RACI model, a framework that defines various stakeholders' involvement in completing project tasks or deliverables. Understanding this model is important for effectively navigating the roles and responsibilities within Sitecore Managed Cloud PaaS 2.0.

What is the RACI Model?

RACI stands for Responsible, Accountable, Consulted, and Informed. Each role in the matrix is assigned one or more of these labels to specify their level of involvement in a given activity. 

• Responsible (R): The person or people who do the work to complete the task. They are responsible for action/implementation. Responsibility can be shared.
  
  
• Accountable (A): The person who is ultimately answerable for the correct and thorough completion of the task. This role is often called "the one who signs off on the work," and only one person can be assigned to this role for each task.
  
  
• Consulted (C): The people who provide information for the project and with whom there is two-way communication. These are typically subject matter experts.
  
  
• Informed (I): The people who are kept up-to-date on progress, often only on completion of the task or deliverable, and with whom there is just one-way communication.

Applying the RACI Model in Sitecore Managed Cloud PaaS

Sitecore applies the RACI model to delineate roles and responsibilities among Sitecore, customers, and partners within the MCP 2.0 environment to ensure all stakeholders understand their part of the bargain.

Here are some examples of how the RACI model is applied:

• Activation and Termination: For activating the Sitecore Managed Cloud, Sitecore is Accountable (A) and Responsible (R), while the customer/partner is Informed (I).
  
  
• Provisioning of Environments: Sitecore is Responsible (R) and Accountable (A) for creating new environments while the customer/partner is Consulted (C).
  
  
• Application Design and Implementation: The customer/partner is Responsible (R) and Accountable (A) for planning Sitecore software upgrades, while Sitecore is Informed (I).
  
  
• Infrastructure and Server Management: Sitecore handles the initial provisioning checks as Responsible (R) and Accountable (A), with the customer/partner being Informed (I).

Key Differences Between MCP 1.0 and MCP 2.0 Roles and Responsibilities

While both MCP 1.0 and MCP 2.0 maintain a similar structure and overall responsibilities, MCP 2.0 introduces several new and detailed tasks that reflect advancements in cloud infrastructure management and security. Here are the main differences:

Provisioning of Sitecore Environments

MCP 1.0:

• Create new environment, installation, and initial set up: Sitecore (R, A)
• Delete existing environment: Sitecore (R, A)
• Reset existing environment: Sitecore (R, A)

MCP 2.0:

• Provision Sitecore Managed Cloud production Hub-spoke environment(s): Sitecore (R, A)
• Provision Sitecore Managed Cloud non-production environment(s): Sitecore (R, A)
• Provision Sitecore Managed Cloud disaster recovery Hub-spoke environments(s): Sitecore (R, A)
• Provision Sitecore Managed Cloud “custom customer-owned” Spoke environment: Sitecore (R, A)
• Delete existing environment: Sitecore (R, A)
• Reset existing environment: Sitecore (R, A)

Infrastructure and Server Management

MCP 1.0:

• Perform initial provisioning check: Sitecore (R, A)
• Scale infrastructure services (Web App, Solr, Azure SQL, Redis cache, and so on): Sitecore (R)
• Initial Web Application Firewall - deployment and configuration: Sitecore (R)
• Set up initial security (Azure SQL firewall): Sitecore (R, A)
• Set up network firewalls and post-deployment security: Customer/Partner (R, A)
• Set up third-party services (DevOps tools, CDN, databases, and so on): Customer/Partner (R, A)
• Custom domain setup: Customer/Partner (R, A)
• Initial setup and configuration of backup services (blobs, database): Sitecore (R, A)
• Customization of backup schedules and services: Customer/Partner (R)
• Consolidation of billing: Sitecore (R, A)
• Infrastructure performance optimization: Customer/Partner (R, A)

MCP 2.0:

• Initial Azure Front Door with Web Application Firewall - deployment and configuration: Sitecore (R)
• Network security groups and initial security setup (Azure SQL firewall): Sitecore (R, A)
• Network firewalls and post-deployment security setup (Azure SQL firewall): Customer/Partner (R, A)
• Set up third-party services (DevOps tools, CDN, databases, and so on): Customer/Partner (R, A)
• Custom domain setup: Customer/Partner (R, A)
• Initial setup and configuration of backup services (blobs, database): Sitecore (R, A)
• Customization of backup schedules and services: Customer/Partner (R)
• Consolidation of billing: Sitecore (R, A)
• Infrastructure performance optimization: Customer/Partner (R, A)

Security: Azure Platform

MCP 1.0:

• Configure encryption at rest and in motion: Sitecore (R, A)
• Configure and perform disaster recovery: Sitecore (R, A)
• Configure host security - hardened OS: Sitecore (R, A)
• Operating system (PaaS): Sitecore (R, A)
• Sitecore Cloud operations change management (via ServiceNow): Sitecore (R, A)
• Azure DDoS standard initial setup: Sitecore (R, A)
• Azure DDoS standard post-provisioning: Customer/Partner (R)
• Define basic Web Application Firewall requirements - rule management: Customer/Partner (R, A)
• Initial deployment security hardening of Sitecore product: Sitecore (R, A)
• Ongoing security hardening of Sitecore product: Customer/Partner (R, A)

MCP 2.0:

• Configure encryption at rest and in motion: Sitecore (R, A)
• Configure infrastructure security logging via Azure Defender for Cloud: Sitecore (R, A)
• Configure and perform disaster recovery: Sitecore (R, A)
• Configure CD App service for Azure Zone Redundancy: Sitecore (R, A)
• Configure host security - hardened OS: Sitecore (R, A)
• Configure initial network security – Network security groups: Sitecore (R, A)
• Configure initial network security – VNET and subnets: Sitecore (R, A)
• Configure initial network security – private link / private endpoint (App service, SQL, Key Vault): Sitecore (R, A)
• Configure Azure Bastion service: Sitecore (R, A)
• Implementation of Azure S2S VPN: Sitecore (R, A)
• Ongoing S2S VPN configuration and client-side management: Customer/Partner (R, A)
• Operating system (PaaS): Sitecore (R, A)
• Sitecore Cloud operations change management (via ServiceNow): Sitecore (R, A)
• Azure DDoS standard initial setup: Sitecore (R, A)
• Azure DDoS standard post-provisioning: Customer/Partner (R)
• Define basic Web Application Firewall requirements - rule management: Customer/Partner (R, A)
• Implement initial Web Application Firewall configuration and rule management (Front Door): Sitecore (R, A)
• Initial deployment security hardening of Sitecore product: Sitecore (R, A)
• Ongoing security hardening of Sitecore application: Customer/Partner (R, A)

Why I Built This App

The roles and responsibilities matrix is a critical component of the Sitecore Managed Cloud PaaS 2.0 offering, providing essential information about the tasks and duties of different team members. However, the sheer volume of information can be overwhelming. 

My goal was to create an intuitive and user-friendly tool that would streamline familiarizing oneself with these roles, ultimately enhancing productivity and understanding.

Key Features of the App

The web app is designed to be straightforward and efficient, offering several key features:

• Search Functionality: Users can quickly search for specific roles or responsibilities using keywords. This feature significantly reduces the time spent sifting through documents.
• Browse Capability: For those who prefer to explore, the app allows users to browse through the roles and responsibilities in a structured manner, making it easy to find relevant information.

How to Use the App

Using the app is straightforward. Simply visit Sitecore MCP 2 Roles and Responsibilities Matrix Decoder, where you can start searching or browsing through the various roles and responsibilities.

Conclusion

Whether you are a new user trying to understand your role or an experienced professional looking for specific responsibilities, this tool is designed to help you find the information you need quickly and easily.

For a detailed look at the roles and responsibilities, refer to the official Sitecore documentation provided in the app. Feel free to reach out if you have any feedback or suggestions for improvement.