Project Scope Management

2021/03/06 (更新內容)
2021/03/29 (更新內容)

概念

專案範疇(Scope)管理包括專案範疇的定義、確認產出與範疇一致、控管範疇的更動。

Work Breakdown Structure

• Work Breakdown Structure

• Applying the work breakdown structure to the project management lifecycle

• What is a Work Breakdown Structure?

  • 大致上分兩種WBS

    • Deliverable-Based Work Breakdown Structure

    • Phase-Based Work Breakdown Structure

• What is a Work Breakdown Structure - WBS? PM in Under 5 (6:44) **

• 建立工作分解結構

• WBS製作方法(一)：建立「專案管理流程」的工作分解架構

• WBS製作方法(二)：建立「產出導向(deliverable-oriented)」的工作分解架構

• 專案管理]如何展開WBS、排定時程與規劃資源？

• 用WBS 簡化複雜專案

• 拆解WBS的9個注意事項

  • 形式不拘，寫下來就好

  • 以「可交付成果」為拆解導向

  • 要符合百分百原則

  • WBS拆解要符合報告流程好

  • WBS怎麼拆解都行

  • WBS拆解前要多溝通，徵得利害關係人同意

  • 記得要編撰WBS字典

  • 專案的WBS是可變動的

  • WBS的拆解不要倒因為果

雛型

雛型是需求確認的好工具，現在製作雛型越來越簡單了，Axure RP是一個很強大的工具，提供教育免費版本，可以很容易的製作出一個很像是已經完成的網站。Figma是另一個類型的雛型工具，互動的程度沒有Axure RP這麼好，但是，容易上手

• Axure RP

  • Axure RP (吳濟聰老師企業資訊策略教材)

• Figma

  • Figma (吳濟聰老師企業資訊策略教材，簡略介紹)

  • Figma (吳濟聰老師使用者經驗設計教材，較詳細)

PMBOK

• Balancing Stakeholder Requirements

• Scope Management Overview

• 專案範疇管理 / Project Scope Management

• 計畫階段

  • 規劃範疇管理 (Plan Scope Management)

    • Outputs: Scope management plan、Requirement management plan

    • Scope Management Plan

    • 規劃範疇管理

    • 在專案計畫書中描述如何進行範疇管理

      • 通常公司或組織會有既定的範疇管理流程，如:收集需求、定義範疇、產生WBS、確認範疇、控制範疇，不過，可以依照專案的性質，調整流程

  • 收集需求 (Collect Requirements)

    • Outputs: Requirements documentation、Requirement traceability matrix

    • Scope Management Process

    • 蒐集需求

      • 需求分析 (Requirement Analysis) (吳濟聰老師系統分析與設計課程教材)

    • 需求文件

      • 可使用Use Case (UML) 或 User Story (吳濟聰老師的敏捷軟體開發課程網站)

  • 定義範疇 (Define Scope)

    • Outputs: Project scope statement、Project documents updates

    • Project Scope Statement

    • 定義範疇

  • 產生Work Breakdown Structure/WBS (Create WBS)

    • Outputs: Scope baseline、Project documents updates

• 在監控階段

  • 確認範疇 (Validate Scope)

    • Outputs: Accepted deliverables、Work performance information、Change requests、Project documents updates

    • 確認範疇

  • 範疇控管 (Control Scope)

    • Outputs: Work performance information、Change requests、Project management plan update、Project documents updates

    • 控制範疇

    • 在後續的監控中就必須進行範疇的控制，當需求有變更時，必須要進行控管，以避免專案失控，並且要更新相關文件

  • Issue Management

    • 監控階段會有一些待完成事項(issue)，必須指派負責人，並且定期跟催。通常會透過一些工具來跟催，如:

      • Jira

      • Redmine

      • Bugzilla (open source)

      • Mantis Bug Tracker (open source)

CMMI

在CMMI裡，範疇管理則分屬於需求開發與管理(RDM)、估測(EST)、計畫(PLAN)、監控(MC)等流程領域。

• Doing

  • Ensuring Quality (ENQ)

    • Requirement Development & Management (RDM)

      • Level 1

        • RDM 1.1 Record requirements.

      • Level 2

        • RDM 2.1 Elicit stakeholder needs, expectations, constraints, and interfaces or connections.

        • RDM 2.2 Transform stakeholder needs, expectations, constraints, and interfaces or connections into prioritized customer requirements.

        • RDM 2.3 Develop an understanding with the requirements providers on the meaning of the requirements.

        • RDM 2.4 Obtain commitment from project participants that they can implement the requirements.

        • RDM 2.5 Develop, record, and maintain bidirectional traceability among requirements and activities or work products.

        • RDM 2.6 Ensure that plans and activities or work products remain consistent with requirements.

      • Level 3

        • RDM 3.1 Develop and keep requirements updated for the solution and its components.

        • RDM 3.2 Develop operational concepts and scenarios.

        • RDM 3.3 Allocate the requirements to be implemented.

        • RDM 3.4 Identify, develop, and keep updated interface or connection requirements.

        • RDM 3.5 Ensure that requirements are necessary and sufficient.

        • RDM 3.6 Balance stakeholder needs and constraints.

        • RDM 3.7 Validate requirements to ensure the resulting solution will perform as intended in the target environment.

    • Verification & Validation

      • Level 1

        • VV 1.1 Perform verification to ensure the requirements are implemented and record and communicate results.

        • VV 1.2 Perform validation to ensure the solution will function as intended in its target environment and record and communicate results.

      • Level 2

        • VV 2.1 Select components and methods for verification and validation.

        • VV 2.2 Develop, keep updated, and use the environment needed to support verification and validation.

        • VV 2.3 Develop, keep updated, and follow procedures for verification and validation.

      • Level 3

        • VV 3.1 Develop, keep updated, and use criteria for verification and validation.

        • VV 3.2 Analyze and communicate verification and validation results.

• Managing

  • Planning and Managing Work (PMW)

    • Estimation (EST)

    • Planning (PLAN)

    • Monitor & Control (MC)

      • Level 1

        • MC 1.1 Record task completions.

        • MC 1.2 Identify and resolve issues.

          • Issue Management

            • 監控階段會有一些未完成事項，通常會透過一些工具來跟催，如:

              • Jira

              • Redmine

              • Bugzilla (open source)

              • Mantis Bug Tracker (open source)

      • Level 2

        • MC 2.1 Track actual results against estimates for size, effort, schedule, resources, knowledge and skills, and budget.

        • MC 2.2 Track the involvement of identified stakeholders and commitments.

        • MC 2.3 Monitor the transition to operations and support.

        • MC 2.4 Take corrective actions when actual results differ significantly from planned results and manage to closure.

      • Level 3

        • MC 3.1 Manage the project using the project plan and the project process.

        • MC 3.2 Manage critical dependencies and activities.

        • MC 3.3 Monitor the work environment to identify issues.

        • MC 3.4 Manage and resolve issues with affected stakeholders.