您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

云迁移功能Cloud migration functions

云迁移团队是技术实施团队或项目团队的现代日期。Cloud migration teams are the modern-day equivalent of technical implementation teams or project teams. 但云的性质可能需要更流畅的团队结构。But the nature of the cloud may require a more fluid team structure. 某些迁移团队专门关注云迁移,而另一些则侧重于利用云技术的创新。Some migration teams focus exclusively on cloud migration, while others focus on innovations that take advantage of cloud technologies. 其中包括完成大量采用工作所需的广泛的技术专业知识,例如完整的数据中心迁移,而其他人则具有更严格的技术焦点,并可能在项目之间移动以实现特定目标,例如,一组可帮助将 SQL Vm 转换为 SQL PaaS 实例的数据平台专家。Some include the broad technical expertise required to complete large adoption efforts, like a full datacenter migration, while others have a tighter technical focus and may move between projects to accomplish specific goals, for example, a team of data platform specialists who help convert SQL VMs to SQL PaaS instances.

无论云迁移团队的类型或数量如何,这些团队通常都为 IT、业务分析或实施合作伙伴提供了主题专业知识。Regardless of the type or number of cloud migration teams, these teams generally provides subject matter expertise for IT, business analysis, or implementation partners.

先决条件Prerequisites

  • 创建 azure 帐户:使用 azure 的第一步是创建帐户。Create an Azure account: The first step to using Azure is to create an account.
  • Azure 门户:浏览 Azure 门户功能和服务,并自定义门户。Azure portal: Tour the Azure portal features and services, and customize the portal.
  • Azure 简介: azure 入门。Introduction to Azure: Get started with Azure. 在云中创建和配置第一个虚拟机。Create and configure your first virtual machine in the cloud.
  • Azure 基础:了解云概念、了解基本策略的优点、比较和对比,并探索 Azure 中可用的服务的广度。Azure fundamentals: Learn cloud concepts, understand the benefits, compare and contrast basic strategies, and explore the breadth of services available in Azure.
  • 查看 迁移方法Review the Migrate methodology.

最小范围Minimum scope

所有云采用工作的核心都是云迁移团队。The nucleus of all cloud adoption efforts is the cloud migration team. 此团队推动了支持采用的技术更改。This team drives the technical changes that enable adoption. 根据采用工作量的目标,此团队可能会包括一系列不同的团队成员,这些成员处理一系列技术和业务任务。Depending on the objectives of the adoption effort, this team may include a diverse range of team members who handle a broad set of technical and business tasks.

团队范围至少包括:At a minimum, the team scope includes:

投递Deliverable

任何云迁移团队的主要可交付成果是使用可用的技术、工具和自动化解决方案,通过采用计划中概述的技术解决方案的及时、高质量实现。The primary deliverable from any cloud migration team is the timely, high-quality implementation of the technical solutions outlined in the adoption plan, in alignment with governance requirements and business outcomes, using the technology, tools, and automation solutions that are available.

日常每月任务Ongoing monthly tasks

团队节奏Team cadence

我们建议将提供云采用功能的团队投入时间全职。We recommend that teams providing cloud adoption capability be dedicated to the effort full-time.

对于这两个团队而言,最好是通过自我组织方式满足日常要求。It's best if these teams meet daily in a self-organizing way. 每日会议的目标是快速更新积压工作(backlog),并传达完成的任务、今天要完成的工作以及阻止的内容,需要额外的外部支持。The goal of daily meetings is to quickly update the backlog, and to communicate what has been completed, what is to be done today, and what things are blocked, requiring additional external support.

发布计划和迭代持续时间对每个公司都是唯一的。Release schedules and iteration durations are unique to each company. 但每次迭代的时间范围为1到4周,就好像是平均持续时间。But a range of one to four weeks per iteration seems to be the average duration. 无论迭代或发布节奏如何,我们都建议团队在每个发布结束时满足所有支持团队的需要,以传达发布的结果,并调整即将到来的工作量。Regardless of iteration or release cadence, we recommend that the team meets all supporting teams at the end of each release to communicate the outcome of the release, and to reprioritize upcoming efforts. 在每个冲刺(sprint)结束时,将以团队的形式满足这一团队的要求,使 云中心成为优秀云治理团队 ,使其保持一致,同时满足共同工作和任何支持。It's also valuable to meet as a team at the end of each sprint, with the cloud center of excellence or cloud governance team to stay aligned on common efforts and any needs for support.

与云采用相关的某些技术任务可能会重复。Some of the technical tasks associated with cloud adoption can become repetitive. 团队成员应每 3 – 6 个月轮换一次,以避免员工满意度问题并维持相关技能。Team members should rotate every 3–6 months to avoid employee satisfaction issues and maintain relevant skills. 在优秀或云治理团队云中心旋转座位,可以为员工提供全新的机会,并提供新的创新。A rotating seat on cloud center of excellence or cloud governance team can provide an excellent opportunity to keep employees fresh and harness new innovations.

基线功能Baseline capability

根据所需的业务成果,提供完整的云采用功能所需的技能包括:Depending on the desired business outcomes, the skills needed to provide full cloud adoption capabilities could include:

  • 基础结构实施人员Infrastructure implementers
  • DevOps 工程师DevOps engineers
  • 应用程序开发人员Application developers
  • 数据科学家Data scientists
  • 数据或应用程序平台专家Data or application platform specialists

为了获得最佳协作和效率,建议云采用团队的平均团队大小为6人。For optimal collaboration and efficiency, we recommend that cloud adoption teams have an average team size of six people. 从技术执行的角度来看,这些团队应该是自我组织的。These teams should be self-organizing from a technical execution perspective. 我们强烈建议这些团队还包括项目管理专业知识,其中包含 agile、Scrum 或其他迭代模型的丰富经验。We highly recommend that these teams also include project management expertise, with deep experience in agile, Scrum, or other iterative models. 此团队在使用平面结构进行管理时最有效。This team is most effective when managed using a flat structure.

超出范围Out of scope

可能需要来自现有 IT 人员的其他支持。Additional support from existing IT staff may be needed. 这是一种针对云采用的重要贡献因素,因为成为了云 broker,并成为了创新和业务灵活性合作伙伴。IT can be a valuable contributor to cloud adoption by becoming a cloud broker and a partner for innovation and business agility.

后续步骤What's next

采用情况非常好,但 ungoverned 采用可能会产生意外的结果。Adoption is great, but ungoverned adoption can produce unexpected results. 云治理团队 保持一致,以加快采用和最佳做法,同时降低业务和技术风险。Align with the cloud governance team to accelerates adoption and best practices, while reducing business and technical risks.

这两个团队跨云采用工作创建了平衡,但被视为 MVP,因为它可能不是可持续实现的。These two teams create balance across cloud adoption efforts, but is considered an MVP because it may not be sustainable. 每个团队都佩戴了许多头衔,如负责人、有 责任、咨询、通知 (RACI) 图表中所述。Each team is wearing many hats, as outlined in the responsible, accountable, consulted, informed (RACI) charts.

详细了解 组织对立模式:小仓库和 fiefdomsLearn more about organizational antipatterns: silos and fiefdoms.