There are many ways to engage with customers when it comes to Azure cloud usage. We've put this in a structured lightweight framework. What does the framework include:
- A structured approach
- Complete workshop formats including material and procedure
- Methods and tools from business consulting
- Various templates and templates (currently under construction)
- Notes and experiences
In lot of frameworks you see the approach of delivering the value in a step-by-step process. Having after every step a delivered value and start a new iteration to deliver the next value is one of main ideas of a agile project approach. Each iteration we have divided into four phases:
| Phase | Explanation |
|---|---|
| assess | Determine the maturity of the customer |
| commit | Get the commitment on the goals of the engagement |
| deliver | Deliver the workshop or engagement to the customer |
| ensure | Ensure that the goal of the engagement are reached and next steps are defined |
Overview of the maturity level model:
In the assess phase the maturity of the customer should be determent, to deliver the wright type of engagement to the customer. We defined four maturity levels:
| Level | Explanation |
|---|---|
| Cloud affine | The customer has hardly had any contact with Azure so far and wants to get to know the platform and discover potential use cases. |
| Cloud is an option | The customer knows Azure, however, wants to get deeper and have first experiences in a topic. |
| Cloud is a solution | The customer is aware of his use case in Azure and wants to prove the feasibility of the solution and, if necessary, to support it with a business case. |
| Cloud is in use | Customer already operates an Azure environment but sees further potential in his business or wants to improve his operation. |
Depending on the level of the customer, there is variety of engagement to choose from in every level.
- Microsoft Cloud Workshops
- Azure Governance Workshop
- Deliver a Architecture Design Session (ADS)
- Start a pilot or PoC
In this phase it is important to generate a common sense about the goals of the engagement to deliver. Especially in cloud engagements it is important to create a statement of work before any steps in the engagement are made. Both sides in the engagement must be sure what to expect as outcome of the engagement.
for more ideas around the commitment we have collected some samples in the commit folder.
At the end of the deliver phase it is important to reference back to the committed goals and proof the execution of the engagement against the agreed goals. Even if not all goals are achieved, at this point next steps can be defined and can be used to start the next iteration in this model and assess the maybe new maturity and commit the next goals to achieve.
Some samples for documenting the proof of execution refer to the ensure folder.