記錄我的成功計畫Document my success plan

本文概要說明正確記錄雲端語音部署的需求。This article gives an overview of the requirements for properly documenting your cloud voice deployment. 您可以在規劃雲端語音部署時,定義並記錄所有決策點及後續步驟,以確保所有的專案關係人與專案小組成員都能在提供成功的結果上進行調整。By defining and documenting all decision points and next steps while planning your cloud voice deployment, you can make sure all stakeholders and project team members are aligned on delivering successful outcomes.

執行規劃Execution planning

在定義如何在貴組織中使用通話方案解決方案來實現音訊會議或電話系統之後,您必須規劃實施專案的執行。After defining how you’ll implement the Audio Conferencing or Phone System with Calling Plan solution in your organization, you need to plan for the execution of the implementation project.

如果您的組織只有一或兩個網站,您可能不需要完成本文中所提供的所有詳細資料,但您應該通讀它以引導您的方法。If your organization has only one or two sites, you might not need to complete all the details provided in this article, but you should read through it to guide your approach.

部署模型Deployment model

就像任何轉換組織在組織中運作方式的技術實施一樣,選擇適當的方式來執行部署將會大大影響雲端語音實現的成功率。As with any technology implementation that transforms the way people work in your organization, choosing the right way to undertake the deployment will greatly influence the success of your cloud voice implementation.

可能的部署模型包括下列各項:Potential deployment models include the following:

  • 每個網站: 此模型適合您的組織在地理位置分散,且分支機搆擁有大量員工的情況。Per site: This model is suitable for cases where your organization is geographically dispersed, and branches have significant numbers of employees. 不過,此部署模型可能會中斷部門員工分佈在多個位置的部門中的通訊。However, this deployment model can potentially disrupt communication within departments where department employees are spread across several locations.

  • 每個部門:此模型通常是適用于中型企業的更佳選項,可確保參與的部門擁有相同的體驗。Per division: This model is usually the better option for medium-size companies and ensures that departments involved have the same experience.

  • 一次完成整個公司: 這個模型通常是小型公司的最佳選項,其中所有員工都能從該部署的第一天獲得相同的體驗。Whole company at once: This model is typically the best option for small companies, where all employees get the same experience from day one of the deployment.

An icon depicting decision points
決策點Decision points
  • 決定適用于您組織的小組部署執行模型。Decide the Teams deployment execution model that’s applicable to your organization.
An icon depicting the next steps
後續步驟Next steps
  • 記錄您所選取的團隊部署執行模型,並包含業務和技術論證。Document the Teams deployment execution model you’ve chosen, and include business and technical justifications.

RACI 模型RACI modeling

若要確保您在專案中擁有哪些人員的明確性,請使用責任分派矩陣(又稱為 RACI,即負責、責任、諮詢及獲悉)矩陣)。To ensure that you’ve got clarity for who is responsible for what in your project, use a responsibility assignment matrix (also known as a RACI—responsible, accountable, consulted, and informed—matrix). 列出負責處理每項工作的人員或群組,以及要在決策制定程式中提供的專案關係人,以及每個決策和動作在專案執行期間收到的資訊。List the person or group who is responsible and accountable for each task, along with stakeholders to be consulted in the decision-making process, and stakeholders to be informed of each decision and action throughout the project execution.

下列是雲端語音實現的 RACI 矩陣範例。The following is an example of a RACI matrix for a cloud voice implementation.

活動/角色Activity/Role 專案主管Project Lead 共同作業主管/架構師Collaboration Lead/Architect 顧問Consultant 變更管理/採用專家Change Management/Adoption Specialist 公司單位代表Business Unit Representatives
計畫簡報動員會通話Program presentation kickoff call R、AR, A CC
設定通話品質儀表板Set up Call Quality Dashboard 如有定義,此命令會判斷兩位使用者是否可以登入系統,如果可以,則可以交換立即訊息。I CC R、AR, A
在動員通話期間共用探索問卷Share the Discovery Questionnaire during kickoff call 如有定義,此命令會判斷兩位使用者是否可以登入系統,如果可以,則可以交換立即訊息。I CC R、AR, A
構想階段動員會Envision phase kickoff R、AR, A CC
商務用案例研討會Business use cases workshop AA RR CC
查看探索問卷Review the Discovery Questionnaire R、AR, A CC
體系結構研討會Architecture workshop 如有定義,此命令會判斷兩位使用者是否可以登入系統,如果可以,則可以交換立即訊息。I R、AR, A CC
採納使用者案例構想階段研討會Adoption user scenarios Envision phase workshop CC 如有定義,此命令會判斷兩位使用者是否可以登入系統,如果可以,則可以交換立即訊息。I AA RR
採納成功研討會Adoption success workshop R、AR, A CC
用戶端與裝置就緒討論會Client and device readiness workshop 如有定義,此命令會判斷兩位使用者是否可以登入系統,如果可以,則可以交換立即訊息。I R、AR, A CC
An icon depicting decision points
決策點Decision points
  • 決定與雲端語音實現專案相關的活動/角色。Decide the activities/roles relevant to the cloud voice implementation project.
  • 決定指派給雲端語音實現專案之責任指派矩陣(RACI 矩陣)的團隊或人員。Decide the teams or people to be assigned to the responsibility assignment matrix (RACI matrix) of the cloud voice implementation project.
An icon depicting the next steps
後續步驟Next steps
  • 記錄 RACI 矩陣。Document the RACI matrix.

季度執行方案Quarterly execution plan

若要在可管理的工作區塊中執行雲端語音部署,建議您根據您的目標鍵結果(OKRs)、您所選擇的部署模型,以及貴組織的專案執行功能,來建立季度執行方案。To execute the cloud voice deployment in manageable chunks of work, we recommend that you create a quarterly execution plan based on your objective key results (OKRs), the deployment model you’ve chosen, and the project execution capability of your organization.

如此一來,您可以在每個季度追蹤進度、根據需要修正方案,以及根據貴組織的執行容量來部署雲端語音功能。This way you can track progress on a quarterly basis, revise the plan if needed, and deploy cloud voice capabilities based on your organization’s capacity to execute.

如果您的組織只有一或兩個網站,您可能不需要每季執行方案,因為您預計會在一小段時間內完全部署。If your organization has only one or two sites, you might not need a quarterly execution plan because you’d expect to be fully deployed in a short period of time.

下列是雲端語音實現構想階段的季度執行方案範例。The following is an example of a quarterly execution plan for the Envision phase of a cloud voice implementation.

網站/部門Site/division 員工人數Number of employees 音訊會議Audio Conferencing 電話系統Phone System 要執行的季度Quarter to execute
美國:紐約US: New York 20002000 Yes 含有通話方案的電話系統Phone System with Calling Plans Q1 CY2018Q1 CY2018
愛爾蘭:都柏林Ireland: Dublin 300300 Yes 含有通話方案的電話系統Phone System with Calling Plans Q1 CY2018Q1 CY2018
奧地利:維也納Austria: Vienna 500500 Yes 電話系統直接路由Phone System Direct Routing 第2季度 CY2018Q2 CY2018
義大利: MilanItaly: Milan 200200 Yes 不適用N/A 第2季度 CY2018Q2 CY2018
南美:巴西South America: Brazil 15001500 Yes 電話系統直接路由Phone System Direct Routing 第2季度 CY2018Q2 CY2018
印度:新德里India: Delhi 70007000 Yes 不適用N/A CY2018 年3季度Q3 CY2018
An icon depicting decision points
決策點Decision points
  • 決定要達到目標金鑰結果的季度執行方案(OKRs)。Decide the quarterly execution plan to achieve the objective key results (OKRs).
An icon depicting the next steps
後續步驟Next steps
  • 記錄季度執行方案。Document the quarterly execution plan.

溝通與管理方案Communications and governance plan

若要讓專案討論干係人與部署進度保持在最新狀態,您需要建立一個方案,讓您瞭解如何在核心專案小組成員和專案關係人之間進行通訊,以針對已建立的 KSIs、運營指標及戰略目標,與專案的狀態相關的專案、主要里程碑、封鎖程式及各種不同的評論。To keep project stakeholders up to date with the progress of the deployment, you need to establish a plan for how communications will take place among the core project team members and with the stakeholders to discuss matters relating to status of the project, key milestones, blockers, and various reviews of the project against established KSIs, operational metrics, and strategic goals.

以下是您可以在雲端語音實現專案中利用的通訊與管理方案範例。The following is an example of a communications and governance plan that you can leverage in your cloud voice implementation project.

類型Type 目標Goals 參與者Participants 天數/時間Days/time 位置Location 會議擁有者Meeting owner
Project standup 通話Project standup calls [同步處理] 專案的狀態、追蹤重要的里程碑及封鎖程式Sync on status of the project, track key milestones and blockers TBATBA 星期一、星期二、星期三、星期四 5 PM PSTMonday, Tuesday, Wednesday, Thursday 5 PM PST VirtualVirtual TBATBA
每週籌畫指導委員會Weekly steering committee 查看雲端語音專案的狀態、向主管人員報告,提出需要主管協助解決的問題Review status of the cloud voice project, report to executives, raise issues that require executive help to resolve TBATBA 每個星期五上午11點(PST)Every Friday 11 AM PST VirtualVirtual TBATBA
每月專案商務/運作審查Monthly project business/operational review 使用延伸的股東、主要聯絡人及主管發起者來檢查項目狀態;審查部署規劃、KSIs 及操作度量單位Check project status with extended stakeholders, main points of contact, and executive sponsors; review the deployment plan, KSIs, and operational metrics TBATBA 每個月的第二個星期二Second Tuesday of month [虛擬] 或 [人員]Virtual or in person TBATBA
季度商業考評(QBR)Quarterly business review (QBR) 根據戰略目標、KSIs 及操作衡量標準,檢查項目狀態並查看進度;必要時重新仲裁者案Check project status and review progress against strategic goals, KSIs, and operational metrics; revisit plans if required TBATBA 每季的最後一個週四Last Thursday of every quarter 在人員中In person TBATBA
An icon depicting decision points
決策點Decision points
  • 決定通訊與監管方案,包括定期狀態更新的頻率([每天]、[每週]、[每月] 或 [季度])、執行狀態更新會議的方法,以及每個會議的擁有者。Decide the communications and governance plan, including the frequency of regular status updates (daily, weekly, monthly, or quarterly), methods for conducting the status update meetings, and the owner of each meeting.
An icon depicting the next steps
後續步驟Next steps
  • 記錄通訊與管理方案。Document the communications and governance plan.

完成我的成功方案Finalize my success plan

成功方案是您在構想階段所建立之檔的摘要。A success plan is the summary of the documentation you created in the Envision phase.

成功計畫可讓專案小組(包括 FastTrack 或部署合作夥伴)擁有足夠的資訊來實現貴組織的目標,以使用通話方案服務來實現音訊會議或電話系統。The success plan gives the project team—which can include FastTrack or a deployment partner—sufficient information to realize your organization’s goals with implementing the Audio Conferencing or Phone System with Calling Plan service.

一般來說,成功計畫包含下列主要區段,許多都是透過構想階段來處理:In general, a success plan contains the following main sections, many which you will have worked on through the Envision phase:

  • 商務案例Business case

  • 服務就緒性Service readiness

  • 服務決策Service decisions

  • 執行方案Execution plan

  • 採納方案Adoption plan

  • 運營計畫Operational plan

商務案例Business case

商務使用案例中,股東、OKRs 及 KSIs、風險登記及專案時程表的清單通常會構成商業案例所需的大量資訊。Business use cases, the list of stakeholders, OKRs and KSIs, risk registers, and project timelines typically make up the bulk of information required for a business case. 您應該將這些作為成功方案的一部分加以記錄。You should document these as part of your success plan.

服務就緒性Service readiness

您的環境評估會提供初始資訊,以判斷貴組織的技術就緒情況,以使用通話方案來實現音訊會議和/或電話系統。Your environmental assessment provides the initial information required to determine your organization’s technical readiness to implement Audio Conferencing and/or Phone System with Calling Plan.

這裡包含您的服務準備情況評估,以及針對您透過環境評定所發現之需要修正之區域的方案。Included here is your service readiness assessment and the plan to address areas that need remediation that you discovered through environmental assessment.

服務決策Service decisions

記錄如何為您的組織規劃音訊會議或電話系統,以及如何使用通話方案服務的技術實現。Document how you planned the Audio Conferencing or Phone System with Calling Plan service technical implementation for your organization.

執行方案Execution plan

記錄如何在整個組織中規劃專案的執行以實現方案。Document how you planned the execution of the project to implement the solution throughout your organization.

採納方案Adoption plan

在您執行採用準備就緒評量評估之後,專案小組需要建立一組完整的溝通方案、訓練方案,以及預先啟動、啟動及啟動後的採納活動計劃。After you perform your adoption readiness assessment, the project team needs to come up with a comprehensive set of communication plans, a training plan, and plans for pre-launch, launch, and post-launch adoption activities.

找出支援採納活動(例如傳單、歡迎電子郵件及訓練資料)的資源,以及您將需要符合組織需求的任何自訂專案。Identify resources to support adoption activities such as flyers, welcome emails, and training materials, along with any customizations you’ll need to meet your organization’s requirements.

Microsoft 團隊客戶成功套件下載適用于採納活動的範本。Download templates for adoption activities from the Microsoft Teams Customer Success Kit.

運營計畫Operational plan

對應操作角色的做法將會建立角色和職責,以及指派給每個操作角色的小組,您需要支援音訊會議的實現。The exercise of mapping operational roles will establish roles and responsibilities, and the teams assigned to each operational role, that you’ll need to support the implementation of Audio Conferencing.

您必須完成這項作業,並將作業方案納入成功方案中,以確保解決方案的可執行情況。You need to complete this and include the operational plan as part of the success plan to ensure operational readiness of the solution.

An icon depicting decision points
決策點Decision points
  • 決定如何記錄您的整個成功方案,以提供您的雲端語音工作負載。Decide how you will document your entire success plan for delivering your cloud voice workloads.
An icon depicting the next steps
後續步驟Next steps
  • 確認所有成功方案元件都已記錄。Confirm all components of your success plan have been documented.
  • 將您的成功計畫的個別元件匯總成單一摘要檔(選用)。Aggregate individual components of your success plan into a single summary document (optional).