Wondershare EdrawMind
EdrawMindProject scope management work breakdown notes mind map
MindMap Gallery Project scope management work breakdown notes mind map
- 7
Project scope management work breakdown notes mind map
Project scope management work breakdown notes mind map, interested friends can take a look together.
Edited at 2023-02-23 21:21:21- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
Project scope management work breakdown notes mind map
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
- Recommended to you
- Outline
Project scope management work breakdown notes mind map
scope
Product Range
The characteristics and functions of a certain product, service or achievement, and whether the product scope is completed are measured by the product requirements specification.
Project scope
The scope statement defines the work and processes that must be completed to deliver products and services with specified features and functionality.
Whether the project scope is completed is measured by the project management plan, project scope statement, WBS and WBS dictionary. The project scope comes from a clear project goal or specific needs of the project investor or customer.
Project scope confirmation is the formal recognition of the project scope by project stakeholders and runs throughout the entire project life cycle.
Project scope is the only way to effectively manage demand changes. With a clear project scope, only the business processes within the scope can be analyzed to establish system functional requirements. When customer needs change, the scope can be effectively managed.
The project scope and functional requirements are not provided by the customer. The customer only knows what goals the requirements complete. The project team members obtain the functional requirements after understanding the customer analysis.
project scope management
Refers to the process of defining and controlling what is and is not included in the project. This process is used to ensure that the project team and project stakeholders have a common understanding of the project products and the processes used to produce these products.
Obtain project requirements through demand development, determine the scope of the project on this basis, and conduct project scope management. Demand management manages the full life cycle of project requirements, including demand management definition, demand management process, formulating demand management plans, and managing demand. and implementation suggestions; for project requirements, they can be met step by step or in phases according to the urgency and importance of the requirements. Determining the requirements of each period will provide the basis for scope management of this period. Demand management handles changes in requirements, which will cause changes in the project scope.
Fundamental contents
Determine project requirements (requirements proposal), define project scope, implement scope management, scope change control management, and scope verification
5 processes
Gathering requirements, scope definition (the process of developing a detailed description of the project and product), creating a work breakdown structure (the process of breaking down project results and work into smaller, more manageable components), scope confirmation (formal acceptance that the project is complete deliverables), scope control (the process of monitoring the scope status of projects and products, and managing changes to the scope baseline)
Gather requirements
Requirements refer to the quantified and documented needs and expectations of sponsors, customers, and other stakeholders. Collecting requirements refers to the process of defining and managing customer expectations.
Once a project begins, requirements should be explored, analyzed, and documented in sufficient detail to allow for measurement at a later date
Requirements are the basis of WBS. Cost, schedule and quality planning are also based on these requirements. Requirements development begins with the analysis of relevant information in the project charter and stakeholder register.
requirements document
Describe how various single requirements will meet the business requirements related to the project. Only requirements that are clear, traceable, complete, coordinated with each other, and recognized by major stakeholders can be used as a baseline.
include
Business needs, shortcomings of the current situation and reasons for starting the project
Trackable business goals and project goals, functional requirements, non-functional requirements, quality requirements, acceptance criteria, business rules, impact on other areas of the organization such as call center, sales force, need for support and training, requirements-related Assumptions and constraints
demand management plan
Describe how requirements are analyzed, documented, and managed throughout the project life cycle. Relationships between departments at each stage of the life cycle have a strong impact on how requirements are managed
include
How to plan, track and report various requirements activities, configuration management activities, requirements prioritization process, product measurement indicators and the rationale for using these indicators
Requirements Tracking Matrix
Is a table that connects requirements to their sources so that requirements can be tracked throughout the project life cycle
Linking each requirement to business goals or project goals helps ensure that each requirement has business value
Record the relevant attributes of each requirement (identification mark, requirement description, reason for inclusion, owner, source, priority, version, status and implementation date)
technology
Interviews, focus groups, guided workshops, group innovation techniques, group decision-making techniques, questionnaires, observations, prototyping
Delphi technique: A group of selected experts answer questionnaires and give feedback on the results of each round of requirements gathering. Expert responses can only be given to the moderator to maintain anonymity. Multiple controlled feedback, where experts are all equal, can avoid any individual having an undue exaggerated impact on the results.
Brainstorming: A technique used to generate and collect multiple ideas for project requirements and product requirements
Concept/mind mapping: Connect the ideas obtained from brainstorming with a simple diagram to reflect the commonalities and differences between these ideas, thereby guiding new ideas
scope management plan
Specifies how to define, confirm, and control the project scope, and how to develop the work breakdown structure (WBS)
enter
Enterprise environmental factors, organizational process assets, project charter, preliminary project scope statement, project management plan
technology
Expert judgment, work breakdown templates, change control forms, standards in organizational processes
output
scope management plan
How to prepare a detailed scope statement, how to create a WBS, how to confirm and accept deliverables, and how to apply for changes
Based on the needs of the project, the scope management plan can be formal or informal, very detailed or high-level
Scope definition
Develop a detailed project scope statement that serves as the basis for future project decisions. The project scope statement should be prepared based on the key deliverables, assumptions, and constraints documented during project initiation.
enter
Organizational process assets (templates), project charter, preliminary project scope statement, project scope management plan, approved change requests (occurs during the project execution phase)
technology
Product analysis (an effective tool for projects with products as deliverables, including product decomposition, systems analysis, requirements analysis, systems engineering, value engineering analysis), alternative identification (techniques that propose different execution methods) , expert judgment method, project stakeholder analysis
output
Project Scope Detailed Description
It describes the deliverables and the work that produces the deliverables. It establishes a consensus on the project scope among project stakeholders. The scope boundary is closed and can clearly indicate which work does not belong to the scope of this project. The scope statement enables the team to carry out more detailed work. planning and guiding team work
content
Project objectives, product scope description, project requirements, project deliverables, product acceptance criteria, project constraints, project boundaries and exclusions project assumptions, initial project organization, initial risks, schedule low mileage, funding Constraints, cost estimates, configuration management requirements, project specifications, approved requirements
change request
Changes to the project management plan and subplans
project management plan
Changes to the scope management plan impact the project management plan
Create a work breakdown structure
significance
After the project is decomposed, the relevant personnel can understand the project at a glance
Ensures the systematicness and integrity of the project structure (preventing work that should be done from being omitted and gilded)
Establish a complete project guarantee system
Clarify the working interface of all parties to facilitate the division and implementation of responsibilities
As a tool for schedule planning and control
Provide a basis for establishing project communication management
It is the basis and basis for the formulation of project plans and control measures.
Representation
hierarchical tree structure
Clear hierarchy, strong structure, not easy to modify, suitable for small and medium application projects
tabular form
There are many content categories, large capacity, poor intuitiveness, reflecting all work elements, and suitable for large and complex projects.
enter
The hierarchical structure is a decomposition of the project work required to complete the project goals into small, manageable fragments, which organizes and defines all the work within the entire project scope. The lowest-level work package has clear and verifiable deliverables. , which cannot be divided logically, is the basis for schedule arrangement, cost estimation and monitoring. Each layer of WEB needs to be encoded.
Organizational process assets, project scope statement, project scope management plan, approved change requests (the WBS may need to be updated during the execution phase)
technology
work breakdown structure template
break down
Rolling planning - the project management team refines the WBS as information becomes richer
step
Identify project deliverables and related project work
Analysis range specification
Organize the structure of the WBS
Put major project deliverables and subprojects as the first layer
Outsourced sub-project structure
Treat the project life cycle as one layer and the deliverables as the second layer
Adopt different decomposition methods for each WBS branch
Decompose WBS
Assign identifiers or numbers to work units at various levels in the WBS
Check the current level of decomposition to ensure it is necessary and detailed
in principle
Maintain project integrity at all levels
A work unit can only belong to one upper-level unit
Work units at the same level apply the same properties
Work units should be able to separate different responsible persons and different work contents
Facilitate management needs for project management planning and control
The lowest level work should be comparable, manageable, and quantitatively checkable
Should include project management work, including subcontracted work
WBS coding design
Each level of the structure represents a digit of coding. One item element at any level is the sum of all other sub-level item elements.
output
Project scope statement (updated), work breakdown structure, WBS dictionary, scope baseline (the baseline is formed after the WBS is approved), project management plan, change request (change scope statement passes overall change control)
scope confirmation
The process of formal acceptance of the completed project scope by project stakeholders. The deliverables and work results need to be reviewed to ensure that all work in the project has been completed accurately and satisfactorily. Throughout the project, there are acceptable issues related to the work results, usually in quality control. proceed later
enter
project scope statement
The scope statement describes the product scope and its acceptance criteria (defining the project, listing the characteristics and project boundaries of the project and its related products, services, and methods for scope control and acceptance)
WBS Dictionary
part of the project scope statement
project scope management plan
Deliverables
technology
Check to achieve scope confirmation
output
Deliverables accepted
Change Request
Recommended corrective actions
scope control
content
Factors causing scope changes and requested changes are handled according to the overall project change control and managed when scope changes actually occur. Scope changes are modifications to the agreed upon WBS-defined project scope.
Reason for change
Changes in the external environment of the project, incomplete and detailed project scope planning, emergence of new technological means, changes in the implementation organization, and changes in customer requirements for project products and services
Focus
Influence the factors that cause scope changes to ensure unanimous buy-in, confirm that scope changes have occurred, and manage the actual changes when they occur
enter
scope statement
The project scope statement, WBS and WBS dictionary constitute the scope baseline of the project and specify the scope of the product.
Work breakdown structure, WBS dictionary, project scope management plan
performance report
Project completion status
Approved change request
job performance information
technology
change control system
The application is flexible and not rigid, and different control points are set up. Changes that do not need to be resolved through the process can be completed on-site, and the change control system related to cost and progress is resolved.
Receive scope change requests, estimate the impact on the project (impact on goals, cost, schedule, resources), implement the change process, revise other plans and 6 goals, and notify project stakeholders
Deviation analysis
Determine the cause of range deviation and decide whether to perform corrections
Replanning
Trigger planning work every time a change occurs
configuration management system
output
Project scope statement, WBS and WBS dictionary, scope baseline, change request, approved corrective actions, organizational process assets, project management plan
Scope management methods at each stage
start up
Phased implementation - large projects have a wide scope, long cycle and complex business. The core business will be realized in the first phase and comprehensively promoted in the second phase.
Establish a project organizational structure including user managers, business managers, and key users - fully understand the scope of the project and avoid discrepancies
Adequate demand analysis and research--is the basis for determining the scope of the project and preparing a user demand specification
plan
Develop a scope management plan - develop a scope statement to determine the project scope, deliverables at each stage, implementation methods to be used, and functional descriptions
Scope definition – using a top-down approach to divide WBS
implement
Regular project meeting system-confirm project scope and results
Project weekly and monthly report system--analysis and summary of system progress
Project supervision system-supervision company participation