Combined with the Enovia Project Management module

1. The core knowledge areas:

Overall management, scope management, schedule management, cost management, quality management, information security management

2. Guarantee domain:

Human resource management, contract management, procurement management, risk management, information (document) management, configuration management, intellectual property management, laws and regulations, standards and norms management, professional ethics

3. Project life cycle:

It is usually divided into stages from a technical point of view: requirements analysis, system design, system construction, system operation
phases by management activity: start, plan, execute, close
whether it is a technical phase or a management phase, each phase of the project contains at least technical or administrative work

4. The following tasks are often considered in the project life cycle

what technical work should be done at each stage
when should the deliverables be generated at each stage
how each deliverable is reviewed, validated, and validated
who is involved at each stage
how to control and approve each stage

5. The relationship between the project life cycle and the product life cycle

a project delivers specific products, outcomes, services.
a project lifecycle defines the beginning and end of a project.
the product lifecycle defines the development, operation, and demise of a product
the life cycle of a product is longer than the life cycle of a project.
for example, the development and testing of a prototype system can be a separate project before the final product is determined to be developed.
care should be taken to distinguish between the product life cycle and the project life cycle.
in new product development or software development, organizations consider the project lifecycle as part of the product lifecycle.

a typical "information systems project" life cycle includes: feasibility analysis, business process optimization or change, information system planning, requirements analysis, system design, system implementation, system testing, system implementation, system commissioning, acceptance.
typical "information system" life cycle: in addition to the previous project life cycle, it also includes the stages of coordinated operation and maintenance after acceptance, system decommissioning, etc

6. Scope management

wbs: it is the basis of project scope management, as well as the basis of schedule, budget, and resource allocation
the wbs is a further grouping of project elements based on deliverables, which summarizes and defines the entire scope of work of the project.
at the heart of the planning process, wbs is an important foundation for developing schedules, resource requirements, cost budgets, risk management plans, procurement plans, etc., as well as controlling project changes

methods of wbs decomposition:

method 1: decompose the project lifecycle into the first layer and the project deliverables into the second layer.
for example, the first layer is requirements, design, development, testing, etc.; the second layer is the requirements research report, requirements analysis report, and requirements confirmation form

method 2: take the important deliverables of the project as the first layer
for example, the first layer is the home page design, the background management page design, the statistical page design, and the second layer is logo design, graphic design, and programming design

method 3: take the subproject as the first layer

THE ACTIVITY DEFINITION PROCESS IS AT THE LOWEST LEVEL OF THE WBS
THE LOWEST LEVEL OF WORK UNIT IN WBS IS THE WORK PACKAGE, AND THE INDUSTRY WILL COMPLETE THE WORK DONE BY 1 PERSON IN 2 WEEKS INTO A WORK PACKAGE, OR THE WORK THAT 1 PERSON CAN COMPLETE IN 80 HOURS INTO A WORK PACKAGE
SCOPE BENCHMARK: PROJECT SCOPE SPECIFICATION, WBS, WBS DICTIONARY
scope control: controls changes
range control tools:
deviation analysis
re-plan
change control system or change control committee
configure the management system

7. Schedule management

THE ACTIVITY DEFINITION PROCESS IS AT THE LOWEST LEVEL OF THE WBS

8. Enovia project management module

PROJECT MANAGEMENT AND PRODUCT MANAGEMENT ARE IN AN APP INTERFACE, INDICATING THAT PROJECT MANAGEMENT AND PRODUCT MANAGEMENT ARE CLOSELY LINKED

the scope of product management is greater than project management, and the output of project management is a product, or just an intermediate product in the product maturity model
the product feasibility study can be a project, the bidding can be a project, the software development can be a project, the operation and maintenance can be a project;
from a project perspective, putting multiple projects together can reflect the management process of the product life cycle.
the difference between the status of a project and the life cycle of the project:
the life cycle of the project is reflected in the division of the project stage, and the life cycle of the project reflects the maturity of the product to a certain extent
The status of the project is the need of the software design of the Enovia project management module, which is used to control the use of the software, reflecting the level of Enovia's project management implementation, and cannot reflect the maturity of the product or the progress of the project

9. Training

PROJECT VS PROJECT MANAGEMENT
Let's take a look at how Enovia does project management
entry point: wbs, and wbs and schedule management are carried out simultaneously, skipping the previous market research, project identification, project demonstration, contract signing, including scope confirmation

the iron triangle of project management: scope, schedule, cost