⚫ "Core Concepts" of Project Scope Management (P131)
Project scope management involves doing all the work and only doing it.
Product Scope - The features and functions that a product, service, or result possesses.
Project Scope - The work that must be done to deliver a product, service, or result with specified features and functions.
⚫ "Core Concepts" of Project Scope Management (P131)
Comparing Scope Management for Predictive and Adaptive Lifecycles
⚫ "Development Trends and Emerging Practices" of Project Scope Management (P132)
-
Requirements have always been the focus of project management. Organizations are beginning to realize how to use business analysis to improve competitive advantage by defining, managing and controlling demand activities.
-
Business analysis activities can begin prior to project initiation and the appointment of a project manager. Focus on working with business analytics professionals.
-
The requirements management process begins with needs assessment and ends with requirements closure.
-
The relationship between project managers and business analysts is a partnership.
--Business analysts are responsible for activities related to requirements management
--The project manager is responsible for ensuring that these activities are scheduled in the project management plan, completed on time and within budget, and can create value
⚫ Factors to consider in an agile and adaptive environment (P133)
-
Deliberately shorten the time to define and negotiate scope early in the project and prolong the time to create a process for ongoing exploration and clarity of scope.
-
Prototypes are built and reviewed with purpose, and requirements are clarified through multiple releases. List requirements as open items.
⚫ One of the project scope management processes "planning scope management" (planning process group) P134
Planning Scope Management——The process of creating a scope management plan to document how to define, confirm, and control the project scope and product scope. The role of this process: Provide guidance and direction on how to manage scope throughout the project.
⚫ Planning Scope Management—Output: Scope Management Plan (P137)
Scope Management Plan—Describes how the project scope will be defined, developed, monitored, controlled, and validated.
Points to note: 1. The scope management plan has no scope (the scope is in the scope baseline)
2. Scope management plans can be formal or informal, highly detailed or highly generalized.
⚫ Planning Scope Management—Output: Demand Management Plan (P137)
Requirements Management Plan (Business Analysis Plan)—Describes how project and product requirements will be analyzed, documented, and managed.
Points to note: 1. The requirements management plan has no requirements (the requirements are in the requirements document)
2. The content includes configuration management activities, requirements prioritization process, measurement indicators, etc.
⚫ Project Scope Management Process 2 "Collect Requirements" (Planning Process Group) P138
Gather requirements—the process of determining, documenting, and managing the needs and demands of interested parties in order to achieve objectives.
What this process does: Provides the basis for defining product scope and project scope.
⚫ What is a requirement? (P140)
Requirements - Conditions or capabilities that must be met by a product, service, or result in accordance with a specific agreement or other mandatory specification.
Requirements include the quantified and documented needs and expectations of sponsors, customers and other interested parties.
⚫ Gather Requirements—Input: Project Document (P141)
◆Register of interested parties--used to understand which interested parties can provide information on demand, and record the needs and expectations of interested parties for the project.
⚫ Gather requirements--input: business documents (P141)
The business document that affects the process of gathering requirements is the business case, which describes the required, expected, and optional criteria that should be met to meet business needs.
⚫ Collect requirements -- input: agreement (P141)
Agreements will contain project and product requirements.
⚫ Collect Requirements--Tools and Techniques (P142-P144)
⚫ Collect Requirements--Tools and Techniques (P144-P147)
⚫ Gather requirements—output: requirements document (P147)
Requirements document----describes how various single requirements will satisfy the business requirements related to the project.
⚫ Only requirements that are clear (measurable and testable), traceable, complete, and mutually coordinated, and that the main stakeholders are willing to approve can be used as a baseline.
⚫ Classification of needs:
-
Business Requirements: The high-level needs of the entire organization
-
Solution Requirements: The features, functions, and characteristics that a product, service, or result must have in order to meet business needs and stakeholder needs. Divide functional requirements and non-functional requirements
-
Project Requirements: Actions, processes, or other conditions that need to be met by the project, such as milestone dates, contractual obligations, constraints.
-
Stakeholder needs: the needs of interested parties or groups of interested parties
-
Transition and readiness requirements: Temporary capabilities required to transition from the "current state" to the "future state". Example: data transformation and training needs
-
Quality Requirements: Any conditions or criteria used to confirm the successful completion of deliverables or the fulfillment of other project requirements, such as testing, certification, validation
⚫ Collect Requirements—Output: Requirements Traceability Matrix (P148)
Requirements Traceability Matrix - A form that links product requirements from their sources to the deliverables that will satisfy them.
-
Linking each requirement to business or project goals helps ensure that each requirement has business value.
-
Provides a way to trace requirements throughout the project lifecycle (forward and backward)
-
Helps ensure that every requirement approved in the requirements document can be delivered at the end of the project.
-
Requirements documents and requirements traceability matrices produced when collecting requirements do not represent the true scope of the project
-
Further clarification is needed on what is included and what is excluded from the scope of the project. (definition range)
Notes for each