Manufacturing industry mixed type project management system and method
Through a hybrid project management system combining traditional and agile project management methods, the problem of insufficient refinement of project demands and frequent changes in scope in the digital transformation of manufacturing industry is solved, and the full process management and control of hybrid projects in manufacturing industry is achieved.
Patent Information
- Application Number
- CN202410986549.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-15
AI Technical Summary
Mixed projects in the digital transformation of manufacturing industry lack experience in similar projects, resulting in insufficient refinement of project requirements and frequent changes in project scope, and traditional and agile project management methods cannot meet their management needs.
Provide a hybrid project management system for manufacturing, combining project basic management module, predictive management module and agile management module, respectively, for predictable and iterative parts, including predictive scope, progress, and cost management, Cost submodules and agile scope, progress, and cost submodules integrate project full process management.
The comprehensive management of hybrid projects in manufacturing is achieved, the scope, progress and cost control is ensured, the management needs of hybrid projects are met, and the complete process and flexibility are provided.
Smart Images

Figure CN118967020A_ABST
Abstract
Description
Technical Field
[0001] The disclosed embodiments relate to the technical field of project management, and in particular to a hybrid project management system and method for manufacturing industry. Background Art
[0002] With the in-depth advancement of digitalization and informatization in various industries, the traditional manufacturing industry has an urgent need for digital transformation. Traditional project management is mainly a predictive life cycle, which determines the scope, schedule and cost in the early stage of the project, and strictly manages the project scope changes during the project to ensure that the scope of the project is not creeping, the project is delayed, and the project benefits are ensured. In the Internet industry, most of the scope of its related projects needs to be frequently refined and changed to flexibly respond to changes in demand or the market, as well as light assets. Agile project management is mainly used in the agile life cycle. Frequent delivery of interim results that are valuable to the demand side during the project iteration stage emphasizes the control of project risks and costs through the manifestation of demand and constraints.
[0003] However, hybrid projects for the digital transformation of manufacturing have their own unique characteristics. For example, digital transformation projects in the manufacturing industry often lack experience in similar projects, resulting in insufficient refinement of project requirements. The scope of the project will change frequently based on market changes, but the large fixed asset investment in the project will make the hardware iteration cost high during the implementation process. Whether using traditional project management or agile project management methods, there are major limitations and they cannot meet the management needs of hybrid projects. Summary of the invention
[0004] The embodiments of the present disclosure provide a hybrid project management system and method for manufacturing industry to solve or alleviate one or more of the above technical problems in the prior art.
[0005] According to one aspect of the present disclosure, there is provided a manufacturing hybrid project management system, comprising: a project basic management module, a project forecast management module and a project agile management module;
[0006] The project forecast management module includes a forecast scope submodule, a forecast schedule submodule, and a forecast cost submodule, and is used for the management of the scope, schedule, and cost of the forecastable part of a hybrid project;
[0007] The project agile management module includes an agile scope submodule, an agile progress submodule, and an agile cost submodule, and is used for the scope, progress, and cost management of the iterative parts in hybrid projects.
[0008] In a possible implementation, the predictive scope submodule is used for demand collection, scope setting, work breakdown structure creation and scope control in the predictive lifecycle management part of a hybrid project.
[0009] In a possible implementation, the predictive schedule submodule is used for task definition, task sorting, task duration estimation, task total duration estimation, and schedule control in the predictive lifecycle management part of a hybrid project.
[0010] In a possible implementation, the predictive cost submodule is used for cost estimation, budget formulation and cost control of the predictive life cycle management part in a hybrid project.
[0011] In a possible implementation, the agile scope submodule is used for requirements collection and agile backlog management in the agile lifecycle control part of a hybrid project.
[0012] In a possible implementation, the agile progress submodule is used for estimating the priority, story points, and iteration information of the agile backlog in the agile lifecycle management part of a hybrid project.
[0013] In a possible implementation, the agile cost submodule is used for cost estimation and budget formulation of the agile lifecycle management part in a hybrid project.
[0014] According to one aspect of the present disclosure, a hybrid project management method for manufacturing industry is provided, based on the above-mentioned hybrid project management system for manufacturing industry, comprising:
[0015] During the project initiation phase: call the project basic module to conduct project economic feasibility analysis and identify stakeholders.
[0016] In a possible implementation, it includes:
[0017] During the project planning phase:
[0018] Call the project basic module and formulate a project management plan;
[0019] Call the predictive scope submodule to collect predictive requirements, formulate scope, and create a work breakdown structure;
[0020] Call the agile scope submodule to collect agile requirements and output the agile backlog, integrate the work breakdown structure with the agile backlog, and generate a project scope baseline;
[0021] Call the predictive schedule submodule to perform task definition, task sorting, task duration estimation, and total task duration estimation in the predictive lifecycle management part of the hybrid project;
[0022] Call the Agile Progress submodule to estimate the priority, story points, and iteration information of the Agile Backlog in the Agile Lifecycle Management part of the hybrid project;
[0023] Integrate the total task duration in the predictive schedule submodule with the iteration information in the agile schedule submodule to generate a project schedule baseline;
[0024] Call the predictive cost submodule to perform cost estimation and budget formulation for the predictive lifecycle control part of hybrid projects;
[0025] Integrate the project budget of the forecast part in the forecast cost submodule with the project budget of the agile part in the agile cost submodule to generate a project cost baseline.
[0026] In a possible implementation, it includes:
[0027] During the project execution phase:
[0028] Call the project basic module to obtain project resources;
[0029] Call the predictive scope submodule, predictive schedule submodule and predictive cost submodule to control the scope, schedule and cost of the predictable part of the mixed project;
[0030] Call the agile scope submodule to perform agile backlog management;
[0031] At the end of the project:
[0032] Call the project basic module to conduct acceptance and handover, summarize, update and archive.
[0033] The exemplary embodiments of the present disclosure have the following beneficial effects: the exemplary embodiments of the present disclosure ensure the integrity of the entire hybrid project management process through the project basic management module; manage the scope, progress, and cost of the predictable part of the hybrid project through the project forecast management module; manage the scope, progress, and cost of the iterative part of the hybrid project through the project agile management module; meet the management needs of hybrid projects and can comprehensively manage hybrid projects in the manufacturing industry.
[0034] The details of one or more embodiments of the present application are presented in the following drawings and descriptions. Other features and advantages of the present application will become apparent from the accompanying drawings. It should be understood that the above general description and the detailed descriptions below are only exemplary and explanatory and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.
[0036] Figure 1 It is a schematic diagram of the overall framework of hybrid project management in this exemplary embodiment;
[0037] Figure 2 is a schematic diagram of the hybrid project management process in this exemplary embodiment;
[0038] Figure 3 A schematic diagram of the process of implementing overall change management in the forecast management module of the project execution phase in this exemplary embodiment;
[0039] Figure 4 It is a schematic diagram of the iterative process in the agile management module during the project execution phase in this exemplary embodiment. DETAILED DESCRIPTION
[0040] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.
[0041] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware units or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.
[0042] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined, so the actual execution order may change according to the actual situation.
[0043] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein, for example.
[0044] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or sub-modules is not necessarily limited to those steps or sub-modules explicitly listed, but may include other steps or sub-modules not explicitly listed or inherent to these processes, methods, products, or apparatuses.
[0045] Figure 1 Schematic diagram of the overall framework of hybrid project management in this exemplary embodiment; Figure 1 As shown, an exemplary embodiment of the present disclosure provides a hybrid project management system for manufacturing industry, including: a project basic management module, a project forecast management module and a project agile management module; the project basic management module is used to ensure the integrity of the entire hybrid project management process.
[0046] The project forecast management module includes a forecast scope submodule, a forecast schedule submodule, and a forecast cost submodule, and is used for the management of the scope, schedule, and cost of the forecastable part of a hybrid project;
[0047] The project agile management module includes an agile scope submodule, an agile progress submodule, and an agile cost submodule, and is used for the scope, progress, and cost management of the iterative parts in hybrid projects.
[0048] Specifically, the predictive scope submodule is used for demand collection, scope formulation, work breakdown structure creation and scope control in the predictive lifecycle management part of hybrid projects.
[0049] In this embodiment, the predictive scope submodule is used for demand collection, scope formulation, WBS creation and scope control in the predictive lifecycle management part of hybrid projects. Among them, demand collection refers to the collection of all predictable requirements from project stakeholders based on achieving project goals, and the output of predictive demand documents. Scope formulation refers to the formulation of deliverables corresponding to all requirements based on the predictive demand document. All deliverables must be clearly defined to form the project scope of the predictive part. WBS refers to Work Breakdown Structure. WBS creation refers to the decomposition of all deliverables in the project scope of the predictive part into smaller units and manageable work packages. The work packages are summarized to form the project WBS. Scope control refers to the need to monitor the status of the project scope during the project execution phase to ensure that scope changes of all predictive parts of the project are maintained through the implementation of overall change control to maintain the maintenance of the project scope.
[0050] Specifically, the predictive schedule submodule is used for task definition, task sorting, task duration estimation, task total duration estimation and schedule control in the predictive lifecycle management part of hybrid projects.
[0051] In this embodiment, the predictive schedule submodule is used for task definition, task sorting, task duration estimation, total task duration estimation and progress control in the predictive lifecycle management part of hybrid projects. Among them, task definition refers to decomposing the work package of the forecast part into the work tasks required to complete the work package, that is, completing the deliverables of the corresponding work package through the defined work tasks. Task sorting refers to sorting the logical relationships of the work tasks and outputting the project schedule network diagram. Task duration estimation refers to the estimation of the working time required to complete a single task, the lead time and the lag time required for each task. Total task duration estimation refers to the total duration estimation based on the project schedule network diagram and task duration estimation. Progress control refers to the need to monitor the project progress status during the project execution phase to ensure that the progress changes of all forecast parts of the project are maintained through the implementation of overall change control to maintain the maintenance of the project progress.
[0052] Specifically, the predictive cost submodule is used for cost estimation, budget formulation and cost control of the predictive life cycle management part in hybrid projects.
[0053] In this embodiment, the predictive cost submodule is used for cost estimation, budget formulation and cost control of the predictive lifecycle management part in hybrid projects. Among them, cost estimation refers to the individual estimation of the resource cost required to complete the work required for a single task. Budget formulation refers to the layer-by-layer summary of the individually estimated costs and the formulation of emergency reserves for the identified risks, so as to obtain the project budget for the predictive part. Cost control refers to the need to monitor the project cost status during the project execution phase to ensure that all cost changes of the project are controlled through the implementation of overall change control to maintain the maintenance of project costs.
[0054] Specifically, the agile scope submodule is used for demand collection and agile to-do list management in the agile lifecycle control part of hybrid projects.
[0055] In this embodiment, the agile scope submodule is used for demand collection and agile backlog management in the agile lifecycle control part of the hybrid project. Demand collection refers to the collection of all unpredictable requirements from project stakeholders based on achieving project goals, and outputting an agile backlog. Agile backlog management refers to the continuous refinement of the content, availability and priority of the agile backlog during the iteration of the agile part.
[0056] Specifically, the agile progress submodule is used for estimating the priority, story points and iteration information of the agile backlog in the agile lifecycle management part of the hybrid project.
[0057] In this embodiment, the agile progress submodule is used for the estimation of the priority, story points and iterations of the agile backlog in the agile lifecycle control part of the hybrid project. Among them, all requirements in the agile backlog must be sorted from high to low according to priority, and the priority determines the requirements that need to be developed immediately in each iteration. Story point refers to the smallest unit used to measure the workload of tasks in the agile backlog. Iteration includes the estimation of the time to achieve the iteration condition T0, the unit iteration cycle T and the number of iterations i, and the determination of the standard story points that the development team can complete in a single iteration.
[0058] Specifically, the agile cost submodule is used for cost estimation and budget formulation of the agile lifecycle management part in hybrid projects.
[0059] The agile cost submodule is used for cost estimation and budgeting of the agile lifecycle control part of the hybrid project. Cost estimation refers to estimating the cost of the work resources required to complete a single story point. Budgeting refers to summarizing the estimated costs of all story points according to the agile backlog and making emergency reserves for identified risks to obtain the project budget for the agile part.
[0060] Figure 2 Schematic diagram of hybrid project management process in this exemplary embodiment; Figure 2 As shown, an exemplary embodiment of the present disclosure provides a manufacturing hybrid project management method, based on the above-mentioned manufacturing hybrid project management system, comprising the steps of:
[0061] During the project initiation phase: call the project basic module to conduct project economic feasibility analysis and identify stakeholders.
[0062] Specifically, the hybrid project management method for manufacturing industry includes the following steps:
[0063] During the project planning phase:
[0064] Call the project basic module and formulate a project management plan;
[0065] Call the predictive scope submodule to collect predictive requirements, formulate scope, and create a work breakdown structure;
[0066] Call the agile scope submodule to collect agile requirements and output the agile backlog, integrate the work breakdown structure with the agile backlog, and generate a project scope baseline;
[0067] Call the predictive schedule submodule to perform task definition, task sorting, task duration estimation, and total task duration estimation in the predictive lifecycle management part of the hybrid project;
[0068] Call the Agile Progress submodule to estimate the priority, story points, and iteration information of the Agile Backlog in the Agile Lifecycle Management part of the hybrid project;
[0069] Integrate the total task duration in the predictive schedule submodule with the iteration information in the agile schedule submodule to generate a project schedule baseline;
[0070] Call the predictive cost submodule to perform cost estimation and budget formulation for the predictive lifecycle control part of hybrid projects;
[0071] Integrate the project budget of the forecast part in the forecast cost submodule with the project budget of the agile part in the agile cost submodule to generate a project cost baseline.
[0072] Specifically, the hybrid project management method for manufacturing industry includes the following steps:
[0073] During the project execution phase:
[0074] Call the project basic module to obtain project resources;
[0075] Call the predictive scope submodule, predictive schedule submodule and predictive cost submodule to control the scope, schedule and cost of the predictable part of the mixed project;
[0076] Call the agile scope submodule to perform agile backlog management;
[0077] At the end of the project:
[0078] Call the project basic module to conduct acceptance and handover, summarize, update and archive.
[0079] The specific implementation methods of each module of this embodiment will be described in detail below in conjunction with the flowchart of this embodiment. In this embodiment, all modules need to be appropriately adjusted and tailored in different manufacturing digital transformation projects in combination with enterprise project management habits. The process introduced in this embodiment is a full process management method.
[0080] like Figure 2 As shown, during the project startup phase, the project basic module needs to be called.
[0081] Prioritize the project basic module to conduct economic feasibility analysis and stakeholder identification. Economic feasibility analysis requires defining high-level project goals, schedules, and budgets, and conducting business needs analysis and cost-benefit analysis to output project charters. Stakeholder identification refers to identifying all stakeholders involved in the project, classifying them according to their impact on the project, and outputting a stakeholder rating list.
[0082] This phase ends with the stakeholder register and project charter. If the stakeholder register and project charter are completed, it will enter the next phase, the project planning phase.
[0083] like Figure 2 As shown, all modules need to be called during the project planning phase.
[0084] Prioritize the project basic module and formulate a project management plan. The project management plan refers to a management guide document for project scope, schedule, cost, resources, communication, risk, quality, etc.
[0085] Prioritize, call the predictive scope submodule to collect predictive requirements, formulate scope, and create WBS. Predictive requirement collection refers to the collection of all predictable requirements from project stakeholders based on achieving project goals, and outputting predictive requirement documents. Scope formulation refers to formulating deliverables corresponding to all requirements based on the predictive requirement document. All deliverables must be clearly defined to form the project scope of the forecast part. WBS refers to Work Breakdown Structure. WBS creation refers to breaking down all deliverables in the project scope of the forecast part into smaller units and manageable work packages. The work packages are summarized to form the project WBS.
[0086] Prioritize the agile scope submodule to perform agile requirements collection, where agile requirements collection refers to collecting all unpredictable requirements from project stakeholders based on achieving project goals and outputting an agile to-do list.
[0087] Integrate the WBS in the Forecast Scope submodule with the Agile Backlog in the Agile Scope submodule to generate a project scope baseline.
[0088] Prioritize calling the predictive schedule submodule to perform task definition, task sorting, task duration estimation, and total task duration estimation for the predictive lifecycle control part of the hybrid project. Among them, task definition refers to decomposing the work packages of the forecast part into the work tasks required to complete the work packages, that is, completing the deliverables of the corresponding work packages through the defined work tasks. Task sorting refers to outputting the project schedule network diagram by sorting the logical relationships of the work tasks. Task duration estimation refers to the estimation of the working time required to complete a single task, the lead time and the lag time required for each task. Total task duration estimation refers to the total duration estimation based on the project schedule network diagram and task duration estimation.
[0089] Prioritize the Agile Schedule submodule to estimate the priority, story points, and iterations of the Agile Backlog in the hybrid project using the Agile Lifecycle Management part. All requirements in the Agile Backlog must be sorted from high to low in terms of priority, and the priority determines the requirements that need to be developed immediately in each iteration. Story points refer to the smallest unit used to measure the workload of tasks in the Agile Backlog. Iterations include the estimation of the time to achieve the iteration condition T0, the unit iteration cycle T, and the number of iterations i, as well as the determination of the standard story points that the development team can complete in a single iteration.
[0090] Integrate the total task duration in the forecast management module with T0+T*i in the agile management module to generate a project progress baseline.
[0091] Prioritize the use of the predictive cost submodule for cost estimation and budgeting of the predictive lifecycle control part of the hybrid project. Cost estimation refers to the individual estimation of the cost of resources required to complete a single task. Budgeting refers to the aggregation of the individual estimated costs layer by layer, and the formulation of emergency reserves for the identified risks, so as to obtain the project budget for the predictive part.
[0092] Prioritize the Agile Cost submodule to estimate and budget the cost of the Agile Lifecycle Control part of the hybrid project. Cost estimation refers to estimating the cost of the work resources required to complete a single story point. Budgeting refers to summarizing the estimated costs of all story points according to the Agile Backlog, and making contingency reserves for identified risks, to obtain the project budget for the Agile part.
[0093] Integrate the project budget of the forecast part in the forecast cost submodule with the project budget of the agile part in the agile cost submodule to generate a project cost baseline.
[0094] This stage ends with the project approval review. If the review is passed, it will enter the next stage, the project execution stage.
[0095] like Figure 2 As shown, all modules need to be called during the project execution phase.
[0096] Prioritize calling the project basic module to obtain project resources. Acquiring project resources includes human resources and material resources, and building and managing the human resources team.
[0097] Prioritize the use of the predictive scope, schedule and cost submodule to perform scope, schedule and cost control. Scope, schedule and cost control means that during the project execution phase, the project scope, schedule and cost status must be monitored to ensure that all changes to the project are implemented through overall change control to maintain the scope, schedule and cost of the project. Figure 3 As shown, change control is implemented in the following order: record the changes, evaluate the impact of the changes, submit change requests for review by the change control committee, update the project management plan, and notify the relevant parties.
[0098] Prioritize the Agile Scope submodule to perform Agile Backlog Management. Agile Backlog Management refers to the continuous refinement of the content, availability, and priority of the Agile Backlog during the iteration of the Agile part. Figure 4As shown, the following sequence is followed during each iteration: the agile to-do list is updated; the to-do items are assigned standard story points, and the to-do list for this round of iterations can be output based on the team's story point completion rate; an iteration planning meeting is held; the deliverables for this round are output; relevant parties are invited to participate in the iteration review meeting; an iteration retrospective meeting is held based on the conclusions of the iteration review meeting.
[0099] This phase takes the deliverables as the final node, including: the deliverables after implementation and change control corresponding to the predictive requirements; the iteratively completed deliverables version i corresponding to the agile requirements. If the verified deliverables have been output, the next phase will be entered, the project closing phase.
[0100] like Figure 2 As shown, at the end of the project, the project basic module needs to be called.
[0101] Prioritize the project basic module, conduct acceptance and handover, and summarize, update and archive. Acceptance and handover means ensuring that the verified deliverables are accepted by the relevant parties after reviewing the project management plan, and handing them over to the designated relevant parties. Summarize, update and archive means summarizing and recording the lessons learned in the four major stages of the project, updating the enterprise organizational process assets and archiving the knowledge files.
[0102] The above are only preferred implementations of the present disclosure, and the protection scope of the present disclosure is not limited to the above embodiments. All technical solutions under the concept of the present disclosure belong to the protection scope of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present disclosure should be regarded as the protection scope of the present disclosure.
Claims
1. A hybrid project management system for manufacturing industry, characterized in that: include: Project basic management module, project forecast management module and project agile management module; The project forecast management module includes a forecast scope submodule, a forecast schedule submodule, and a forecast cost submodule, and is used for the management of the scope, schedule, and cost of the forecastable part of a hybrid project; The project agile management module includes an agile scope submodule, an agile progress submodule, and an agile cost submodule, and is used for the scope, progress, and cost management of the iterative parts in hybrid projects.
2. The manufacturing hybrid project management system according to claim 1, characterized in that: The predictive scope submodule is used for demand collection, scope setting, work breakdown structure creation and scope control in the predictive lifecycle management part of hybrid projects.
3. The manufacturing hybrid project management system according to claim 1, characterized in that: The predictive schedule submodule is used in hybrid projects for task definition, task sorting, task duration estimation, task total duration estimation, and schedule control in the predictive lifecycle management part.
4. The manufacturing hybrid project management system according to claim 1, characterized in that: The predictive cost submodule is used for cost estimation, budget formulation and cost control of the predictive life cycle management part in hybrid projects.
5. The manufacturing hybrid project management system according to claim 1, characterized in that: The agile scope submodule is used for requirement collection and agile backlog management in the agile lifecycle control part of hybrid projects.
6. The manufacturing hybrid project management system according to claim 1, characterized in that: The agile progress submodule is used for estimating the priority, story points and iteration information of the agile backlog in the agile lifecycle management part of the hybrid project.
7. The manufacturing hybrid project management system according to claim 1, characterized in that: The agile cost submodule is used for cost estimation and budget formulation of the agile lifecycle management part in hybrid projects.
8. A hybrid project management method for manufacturing industry, characterized in that: The manufacturing hybrid project management system according to any one of claims 1 to 7 comprises: During the project initiation phase: call the project basic module to conduct project economic feasibility analysis and identify stakeholders.
9. The manufacturing hybrid project management method according to claim 8, characterized in that: include: During the project planning phase: Call the project basic module and formulate a project management plan; Call the predictive scope submodule to collect predictive requirements, formulate scope, and create a work breakdown structure; Call the agile scope submodule to collect agile requirements and output the agile backlog, integrate the work breakdown structure with the agile backlog, and generate a project scope baseline; Call the predictive schedule submodule to perform task definition, task sorting, task duration estimation, and total task duration estimation in the predictive lifecycle management part of the hybrid project; Call the Agile Progress submodule to estimate the priority, story points, and iteration information of the Agile Backlog in the Agile Lifecycle Management part of the hybrid project; Integrate the total task duration in the predictive schedule submodule with the iteration information in the agile schedule submodule to generate a project schedule baseline; Call the predictive cost submodule to perform cost estimation and budget formulation for the predictive lifecycle control part of hybrid projects; Integrate the project budget of the forecast part in the forecast cost submodule with the project budget of the agile part in the agile cost submodule to generate a project cost baseline.
10. The manufacturing hybrid project management method according to claim 8, characterized in that: include: During the project execution phase: Call the project basic module to obtain project resources; Call the predictive scope submodule, predictive schedule submodule and predictive cost submodule to control the scope, schedule and cost of the predictable part of the mixed project; Call the agile scope submodule to perform agile backlog management; At the end of the project: Call the project basic module to conduct acceptance and handover, summarize, update and archive.
