A $100-billion Fortune 200 consumer packaged goods company recently partnered with CapTech to commercialize Microsoft Azure's Platform as a Service (PaaS) as an enterprise service offering. This blog is the third in a ten-part series of blogs. The purpose of this post is to cover the recommended skills and resources an organization might need for cloud computing. It is intended for anyone interested in gaining insight into the major bodies of work and considerations involved in commercializing cloud services for large enterprises.
Dedicated Skills and Resources
One of the biggest challenges many organizations will face in utilizing the various available cloud offerings is finding resources with the right skillset. Cloud technologies are so new and they change at such a rapid pace that finding people experienced in working with these technologies can be very challenging. Our project team was made up of four dedicated resources that made up the "core" project team. This team met more regularly to discuss progress and plan execution for the next steps in the project. Here is a diagram that lists the dedicated resources for the project and their responsibilities.
This core project team was responsible for determining what offerings were available, which offerings were going to be implemented, and how to best implement each offering. This team accomplished this by assessing the various tools, in some cases working on Proof of Concepts (POC's), and documenting each tool or offering.
Supporting Skills and Resources
Along with the dedicated team another supporting team was utilized to execute some of the tasks that were generated by the smaller dedicated team. This team was made up of various people that had domain-specific knowledge that was needed to make the project a success. This supporting team met with the core dedicate team less frequently, usually once a week, to discuss the overall project state and specific work streams and tasks for the supporting roles. Some examples of the types of roles that were utilized for this project were the client network architect, and the client operations manager. While these people were not responsible for the overall implementation of a cloud solution, they were responsible for shepherding and implementing a particular area of the overall cloud solution.
This third post in the ten-part series described some of the roles and responsibilities that we utilized to commercialize Azure with this Fortune 200 CPG client. These roles are not necessarily a one size fits all listing of all the roles that you might need to implement a cloud solution, but can be used as a representative list of the roles you might need to work with the cloud. Due to the ever changing nature of the cloud, be prepared to reach out to many different resources to help out with something you might be unfamiliar with as an organization.
The entire series:
- Commercializing Azure Part 1 - Context and Business Needs
- Commercializing Azure Part 2 - Helpful Pre-Requisite Concepts
- Commercializing Azure Part 3 - Recommended Skills and Resources
- Commercializing Azure Part 4 - Conducting Cloud Security Assessment
- Commercializing Azure Part 5 - Establishing MPLS Connectivity
- Commercializing Azure Part 6 - Designing Solution Architecture
- Commercializing Azure Part 7 - Defining Governance Model
- Commercializing Azure Part 8 - Facilitating Enterprise Adoption of Service
- Commercializing Azure Part 9 - Transitioning to Support
- Commercializing Azure Part 10 - Summary of Benefits
In the next post we are going to talk about conducting a cloud security assessment to satisfy your organization's security requirements.