定義雲端採用方案的工作負載並設定其優先順序Define and prioritize workloads for a cloud adoption plan

建立清楚且可採取動作的優先順序是成功採用雲端的其中一項秘密。Establishing clear, actionable priorities is one of the secrets to successful cloud adoption. 自然的誘惑是花時間在定義雲端採用期間可能會受到影響的所有工作負載。The natural temptation is to invest time in defining all workloads that could potentially be affected during cloud adoption. 但這是這些,特別是在採用過程中。But that's counterproductive, especially early in the adoption process.

相反地,我們建議您的小組將焦點放在全面排列前10個工作負載的優先順序和記錄。Instead, we recommend that your team focus on thoroughly prioritizing and documenting the first 10 workloads. 開始採用計畫的實施之後,小組可以維護接下來10個最高優先順序工作負載的清單。After implementation of the adoption plan begins, the team can maintain a list of the next 10 highest-priority workloads. 這種方法會提供足夠的資訊來規劃接下來的幾個反覆運算。This approach provides enough information to plan for the next few iterations.

將方案限制為10個工作負載,可在商務準則變更時促進彈性和一致的優先順序。Limiting the plan to 10 workloads encourages agility and alignment of priorities as business criteria change. 這種方法也會讓雲端採用小組瞭解並改善估價。This approach also makes room for the cloud adoption team to learn and to refine estimates. 最重要的是,它會移除廣泛的規劃,以做為有效的商務變更。Most important, it removes extensive planning as a barrier to effective business change.

什麼是工作負載?What is a workload?

在雲端採用的環境中,工作負載是 IT 資產的集合, (伺服器、Vm、應用程式、資料或設備) ,共同支援定義的進程。In the context of a cloud adoption, a workload is a collection of IT assets (servers, VMs, applications, data, or appliances) that collectively support a defined process. 工作負載可支援一個以上的進程。Workloads can support more than one process. 工作負載也可相依于其他共用資產或較大的平臺。Workloads can also depend on other shared assets or larger platforms. 但是,工作負載應該已定義相依資產的界限,以及相依于工作負載的進程。However, a workload should have defined boundaries regarding the dependent assets and the processes that depend upon the workload. 通常,您可以藉由監視 IT 資產之間的網路流量來視覺化工作負載。Often, workloads can be visualized by monitoring network traffic among IT assets.

必要條件Prerequisites

必要條件清單中的策略性輸入可讓您更輕鬆地完成下列工作。The strategic inputs from the prerequisites list make the following tasks much easier to accomplish. 如需收集本文所討論之資料的協助,請參閱 必要條件For help with gathering the data discussed in this article, review the prerequisites.

初始工作負載優先順序Initial workload prioritization

在累加 式合理化的過程中,您的小組應該同意 10 種方法的強大功能,包括10個優先權的工作負載。During the process of incremental rationalization, your team should agree on a Power of 10 approach, consisting of 10 priority workloads. 這些工作負載可作為採用規劃的初始界限。These workloads serve as an initial boundary for adoption planning.

如果您決定不需要數位資產的合理化,建議雲端採用小組和雲端策略小組同意10個應用程式的清單,以作為遷移的初始焦點。If you decide that a digital estate rationalization isn't needed, we recommend that the cloud adoption teams and the cloud strategy team agree on a list of 10 applications to serve as the initial focus of the migration. 我們建議您進一步瞭解,這10個工作負載混合使用簡單的工作負載, (獨立部署中的10個以上的資產) 和更複雜的工作負載。We recommend further that these 10 workloads contain a mixture of simple workloads (fewer than 10 assets in a self-contained deployment) and more complex workloads. 這10個工作負載將會啟動工作負載的優先順序處理。Those 10 workloads will start the workload prioritization process.

注意

10種方法的威力是做為規劃的初始界限,以將能源和投資集中在早期階段分析中。The Power of 10 approach serves as an initial boundary for planning, to focus the energy and investment in early-stage analysis. 不過,分析和定義工作負載的動作可能會在優先順序工作負載清單中造成變更。However, the act of analyzing and defining workloads is likely to cause changes in the list of priority workloads.

將工作負載新增至雲端採用方案Add workloads to your cloud adoption plan

在先前的「 雲端採用方案」和「Azure DevOps」一文中,您已在 Azure DevOps 中建立雲端採用方案。In the previous article, Cloud adoption plan and Azure DevOps, you created a cloud adoption plan in Azure DevOps.

您現在可以在雲端採用方案中,以10個清單的功能來表示工作負載。You can now represent the workloads in the Power of 10 list in your cloud adoption plan. 最簡單的方式是透過 Microsoft Excel 進行大量編輯。The easiest way to do this is via bulk editing in Microsoft Excel. 若要準備工作站進行大量編輯,請參閱 使用 Microsoft Excel 大量加入或修改工作專案To prepare your workstation for bulk editing, see Bulk add or modify work items with Microsoft Excel.

該文章中的步驟5會告訴您選取 輸入清單Step 5 in that article tells you to select Input list. 請改為選取 查詢清單Instead, select Query list. 然後,從 [ 選取查詢 ] 下拉式清單中,選取 工作負載範本 查詢。Then, from the Select a Query drop-down list, select the Workload Template query. 該查詢會將單一工作負載遷移的所有相關工作載入您的試算表中。That query loads all the efforts related to the migration of a single workload into your spreadsheet.

載入工作負載範本的工作專案之後,請遵循下列步驟來開始加入新的工作負載:After the work items for the workload template are loaded, follow these steps to begin adding new workloads:

  1. 複製在最右側資料行中具有 工作負載範本 標記的所有專案。Copy all the items that have the Workload Template tag in the far right column.
  2. 將複製的資料列貼到資料表中的最後一行專案下方。Paste the copied rows below the last line item in the table.
  3. 將新功能的 [標題] 儲存格從 [ 工作負載範本 ] 變更為新工作負載的名稱。Change the title cell for the new feature from Workload Template to the name of your new workload.
  4. 將新的工作負載名稱資料格貼入新功能下所有資料列的標記資料行中。Paste the new workload name cell into the tag column for all rows below the new feature. 請小心不要變更與實際 工作負載範本 功能相關的標記或資料列名稱。Be careful to not change the tags or name of the rows related to the actual Workload Template feature. 當您將下一個工作負載新增至雲端採用方案時,您將需要這些工作專案。You will need those work items when you add the next workload to the cloud adoption plan.
  5. 請跳到大量編輯指示中的步驟8,以發佈工作表。Skip to step 8 in the bulk-editing instructions to publish the worksheet. 此步驟會建立遷移工作負載所需的所有工作專案。This step creates all the work items required to migrate your workload.

針對10個清單中的每個工作負載,重複步驟1到5。Repeat steps 1 through 5 for each of the workloads in the Power of 10 list.

定義工作負載Define workloads

在定義初始優先順序並將工作負載新增至方案之後,每個工作負載都可以透過更深入的定性分析來定義。After initial priorities have been defined and workloads have been added to the plan, each of the workloads can be defined via deeper qualitative analysis. 在雲端採用方案中包含任何工作負載之前,請嘗試為每個工作負載提供下列資料點。Before including any workload in the cloud adoption plan, try to provide the following data points for each workload.

商務輸入Business inputs

資料點Data point 描述Description 輸入Input
工作負載名稱Workload name 此工作負載的名稱為何?What is this workload called?
工作負載描述Workload description 在一個句子中,此工作負載的作用為何?In one sentence, what does this workload do?
採用動機Adoption motivations 哪些雲端採用動機受此工作負載影響?Which of the cloud adoption motivations are affected by this workload?
主要贊助者Primary sponsor 對於受影響的專案關係人,誰是要求前述動機的主要贊助者?Of those stakeholders affected, who is the primary sponsor requesting the preceding motivations?
業務影響Business impact 此工作負載的業務影響為何?What is the business impact of this workload?
應用程式影響Application impact 此應用程式對商務程式有何影響?What impact does this application have on business processes?
資料影響Data impact 資料對企業有何影響?What impact does the data have on the business?
業務單位Business unit 哪個業務單位負責此工作負載的成本?Which business unit is responsible for the cost of this workload?
商務程式Business processes 工作負載的變更將會影響哪些商務處理常式?Which business processes will be affected by changes to the workload?
商務小組Business teams 哪些商務小組會受到變更的影響?Which business teams will be affected by changes?
商務專案關係人Business stakeholders 是否有任何企業會受到變更影響的主管?Are there any executives whose business will be affected by changes?
業務成果Business outcomes 企業將如何衡量這項工作的成功?How will the business measure the success of this effort?
計量Metrics 哪些計量將用來追蹤成功?What metrics will be used to track success?
法規遵循Compliance 此工作負載是否有任何協力廠商合規性需求?Are there any third-party compliance requirements for this workload?
應用程式擁有者Application owners 誰負責任何與此工作負載相關聯之應用程式的業務影響?Who is accountable for the business impact of any applications associated with this workload?
企業凍結期間Business freeze periods 企業是否有任何時間不允許變更?Are there any times during which the business will not permit change?
地理位置Geographies 任何受此工作負載影響的地理位置嗎?Are any geographies affected by this workload?

技術輸入Technical inputs

資料點Data point 描述Description 輸入Input
採用方法Adoption approach 這種採用是否適合用於遷移或創新?Is this adoption a candidate for migration or innovation?
應用程式 ops 負責人Application ops lead 列出負責此工作負載效能和可用性的合作物件。List the parties responsible for performance and availability of this workload.
SLASLAs 列出任何 (RTO/RPO 需求) 的服務等級協定。List any service-level agreements (RTO/RPO requirements).
重要性Criticality 列出目前的應用程式重要性。List the current application criticality.
資料分類Data classification 列出資料敏感度的分類。List the classification of data sensitivity.
營業地理位置Operating geographies 列出工作負載是或應該託管的任何地理位置。List any geographies in which the workload is or should be hosted.
應用程式Applications 指定此工作負載中包含的任何應用程式的初始清單或計數。Specify an initial list or count of any applications included in this workload.
VMVMs 指定工作負載中包含的任何 Vm 或伺服器的初始清單或計數。Specify an initial list or count of any VMs or servers included in the workload.
資料來源Data sources 指定工作負載中所包含之任何資料來源的初始清單或計數。Specify an initial list or count of any data sources included in the workload.
相依性Dependencies 列出未包含在工作負載中的任何資產相依性。List any asset dependencies not included in the workload.
使用者流量地理位置User traffic geographies 列出具有大量使用者流量集合的地理位置。List geographies that have a significant collection of user traffic.

確認優先順序Confirm priorities

根據組合的資料,雲端策略小組和雲端採用小組應該符合以重新評估優先順序。Based on the assembled data, the cloud strategy team and the cloud adoption team should meet to reevaluate priorities. 對商務資料點的澄清可能會提示變更優先順序。Clarification of business data points might prompt changes in priorities. 技術複雜度或相依性可能會導致與人員配置、時程表或技術工作順序相關的變更。Technical complexity or dependencies might result in changes related to staffing allocations, timelines, or sequencing of technical efforts.

複習之後,這兩個小組都應該熟悉確認產生的優先順序。After a review, both teams should be comfortable with confirming the resulting priorities. 這組記載、驗證和確認的優先順序是優先採用的雲端採用待辦專案。This set of documented, validated, and confirmed priorities is the prioritized cloud adoption backlog.

下一步Next steps

針對已排定優先順序的雲端採用待處理專案中的任何工作負載,小組現在已準備好 調整資產For any workload in the prioritized cloud adoption backlog, the team is now ready to align assets.