雲端遷移功能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. 每日會議的目標是要快速更新待處理專案,並傳達已完成的工作、今天要做什麼,以及封鎖的專案,需要額外的外部支援。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. 但每個反復專案的一到四周範圍似乎是平均持續時間。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. 您也可以在每個短期衝刺結束時以小組的形式達成,並以卓越或雲端治理小組雲端中心來保持一致,以掌握共同工作和支援的任何需求。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 – 個月輪替一次,以避免員工滿意度問題並維持相關的技能。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

為了獲得最佳的共同作業和效率,我們建議雲端採用小組的平均小組人數為六人。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. 我們強烈建議這些小組也包括專案管理專長,以及敏捷式、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. 這可能是雲端採用的重要參與者,其成為雲端代理人和創新和企業彈性的合作夥伴。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.

深入瞭解 組織反模式:定址接收器和領域Learn more about organizational antipatterns: silos and fiefdoms.