Project plan management method, equipment and computer program product

Abstract

The embodiment of the invention provides a project plan management method and device and a computer program product. The method can comprise the steps that plans of at least two levels are set for a target project; starting from a root level plan, responding to a template association instruction aiming at the current level plan layer by layer, and according to a mapping relation between project management elements in the current level plan and project management elements in a plan template of a corresponding level, establishing a corresponding level of project management elements according to the project management elements in the current level plan and the project management elements in the plan template of the corresponding level; inserting a task set under each project management element in the plan template into a corresponding project management element in the current level plan to obtain a structure tree of the current level plan; and arranging the structure trees of the hierarchical plans in the at least two hierarchies according to a hierarchical relationship to obtain a project plan of the target project. The method is more friendly and more flexible to change the project plan.

Description

Technical Field

[0001] This document relates to the field of project management, and in particular, to a project plan management method, device, and computer program product. Background Art

[0002] In order to improve the efficiency of project plan compilation, some project management software has emerged in the industry to assist in generating project plans.

[0003] With the increase in project scale and complexity, the current project plan generation solutions often show problems of being unfriendly to changes and lacking flexibility. Due to the complex and changeable nature of projects, the initial plan can often only build the most basic framework and direction. Therefore, many details need to be gradually clarified and adjusted in a timely manner during the project progress. However, due to the large size and complexity of the project plan, any change may trigger a large amount of revision work, resulting in low change efficiency and reducing the response speed of project management.

[0004] Therefore, there is an urgent need to propose a project plan generation solution that is more friendly to changes and more flexible. Summary of the Invention

[0005] Embodiments of the present application provide a project plan management method, device, and computer program product to solve the problems of the current project plan generation solutions being unfriendly to changes and lacking flexibility.

[0006] To solve the above technical problems, the embodiments of the present application are implemented as follows: In a first aspect, a project plan management method is provided, and the method includes: Set at least two levels of plans for the target project, where each plan has project management elements. The root-level plan in the at least two levels is used for the overall planning of the target project, and other level plans are used to decompose the target project into at least one level of sub-plans; Starting from the root-level plan, layer by layer, in response to a template association instruction for the current level plan, according to the mapping relationship between the project management elements in the current level plan and the project management elements in the corresponding level of plan template, insert the tasks set under each project management element in the plan template under the corresponding project management element in the current level plan to obtain the structure tree of the current level plan; Arrange the structure trees of the plans at each level in the at least two levels according to the hierarchical relationship to obtain the project plan of the target project.

[0007] In a second aspect, a project plan management device is provided, and the device includes: A planning framework setting module is used to set plans with at least two levels for a target project. Among them, project management elements are set in each plan. The root-level plan in the at least two levels is used for the overall planning of the target project, and other-level plans are used to decompose the target project into sub-plans with at least one level. A template association module is used to start from the root-level plan, layer by layer, in response to a template association instruction for the current-level plan. According to the mapping relationship between the project management elements in the current-level plan and the project management elements in the plan template of the corresponding level, the tasks set under each project management element in the plan template are inserted under the corresponding project management element in the current-level plan to obtain the structure tree of the current-level plan. A plan generation module is used to arrange the structure trees of the plans at each level in the at least two levels according to the hierarchical relationship to obtain the project plan of the target project.

[0008] In a third aspect, an electronic device is provided, including: A processor; A memory for storing instructions executable by the processor; Among them, the processor is configured to execute the instructions to implement the method as described in the first aspect.

[0009] In a fourth aspect, a computer-readable storage medium is provided. When the instructions in the storage medium are executed by the processor of an electronic device, the electronic device can execute the method as described in the first aspect.

[0010] In a fifth aspect, a computer program product including instructions is provided. When a computer runs the instructions of the computer program product, the computer executes the method as described in the first aspect.

[0011] In the embodiments of the present application, since a project plan framework with at least two levels is set hierarchically from top to bottom, where the root-level plan in the at least two levels is used for the overall planning of the target project, and other-level plans are used to decompose the target project into sub-plans with at least one level; and the task insertion of each level of plan is realized by associating templates to obtain the structure tree of each level of plan, and finally the structure trees of each level of plan are arranged according to the hierarchical relationship to obtain the project plan of the target project, rather than generating the project plan as a whole at one time. Therefore, it is more friendly to the change of the project plan, enabling project managers to add, delete sub-plans and implement plan changes more flexibly. Description of the Drawings

[0012] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0013] Figure 1 It is a schematic flowchart of a project plan management method provided by an embodiment of the present application.

[0014] Figure 2 It is a schematic flowchart of compiling a plan template in a project plan management method provided by an embodiment of the present application.

[0015] Figure 3 It is a schematic diagram of plan template classification provided by an embodiment of the present application.

[0016] Figure 4 It is a schematic flowchart of the plan template association process in a project plan management method provided by an embodiment of the present application.

[0017] Figure 5 It is a schematic diagram of the task insertion relationship in the association of the first-level plan template provided by an embodiment of the present application.

[0018] Figure 6A It is a schematic diagram of the task insertion relationship in the association of the second-level plan template provided by an embodiment of the present application.

[0019] Figure 6B It is a schematic diagram of the project plan for completing the association of the first-level plan template and the second-level plan template provided by an embodiment of the present application.

[0020] Figure 7 It is a schematic flowchart of the project plan review process provided by an embodiment of the present application.

[0021] Figure 8 It is a schematic flowchart of a project plan management method provided by another embodiment of the present application.

[0022] Figure 9 It is a schematic flowchart of a project plan management method provided by another embodiment of the present application. Figure 10 It is a schematic diagram of the state transition during the plan change provided by an embodiment of the present application.

[0023] Figure 11 It is a schematic flowchart of a project plan management method provided by another embodiment of the present application.

[0024] Figure 12It is a schematic diagram of the project plan review process provided by another embodiment of the present application.

[0025] Figure 13 It is a schematic diagram of the process of a project plan management method provided by another embodiment of the present application. Figure 14 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present application.

[0026] Figure 15 It is a schematic diagram of the structure of a project plan management device provided by an embodiment of the present application.

[0027] Figure 16 It is a schematic diagram of the structure of a project plan management device provided by another embodiment of the present application.

[0028] Figure 17 It is a schematic diagram of the structure of a project plan management device provided by another embodiment of the present application. Detailed implementation manners

[0029] In order to enable those skilled in the art of the present technology to better understand the technical solutions in the embodiments of the present application, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in one or more embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of this document.

[0030] The terms "first", "second", etc. in the present application and the claims are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in the present application and the claims means at least one of the connected objects, and the character " / " generally means that the associated objects before and after are in an "or" relationship.

[0031] The project plan generation methods in the related art include two types: 1) generating a complete project plan at one time. This method generates a detailed plan for the entire project at the initial stage of the project, covering all tasks, time nodes, and resource allocations. However, this method is not flexible enough when it comes to later changes and adjustments. Because of the enormity and complexity of the complete plan, any change may trigger a large amount of revision work, reducing the response speed of project management. 2) Generating multiple independent sub-plans based on the project: This method divides the project into multiple sub-plans, each of which is managed independently. Although this method enables each module to operate independently, it is not conducive to the overall management and tracking of the entire project. Managers may have difficulty obtaining a clear view of the overall progress and cannot coordinate the dependencies between different sub-plans in a timely manner, resulting in a lack of consistency and coordination during the project execution and gradually deviating from the top-level goals of the project.

[0032] Therefore, it is particularly important to improve the change-friendliness and flexibility of project plan compilation. Managers need an efficient tool and method that can quickly supplement and modify sub-plans to flexibly respond to changes.

[0033] For this reason, this application proposes a project plan management method, device, and computer program product. The method can be executed by an electronic device or software installed in an electronic device. Among them, the electronic device includes but is not limited to any one of intelligent devices such as smartphones, personal computers (PCs), laptops, tablets, e-readers, Internet TVs, and wearable devices.

[0034] The project plan management method proposed in this application can gradually generate a detailed plan, making the management of complex projects easier; it can also flexibly adjust and quickly supplement sub-plans without deviating from the top-level goals and the full life cycle framework of the project to effectively respond to project plan changes.

[0035] The following will describe a project plan management method provided by an embodiment of this application with reference to the accompanying drawings.

[0036] A project plan management method provided by an embodiment of this application, as Figure 1 shown, the method may include: Step 101, set at least two levels of plans for the target project. Among them, each plan is provided with project management elements. The root-level plan in the at least two levels is used for the overall planning of the target project, and the other level plans are used to decompose the target project into at least one level of sub-plans.

[0037] The target project can be any project for which a project plan is to be generated. The project management elements can include, but are not limited to, one or more of project phases, milestones, and risk management. Among them, project phases and milestones are often mandatory project management elements in project management.

[0038] Through step 101, a project framework for the target project can be constructed first. At least two levels of plans are set in this project framework. Among them, there is usually only one root-level plan (also called the first-level plan or the top-level plan), and each plan in other levels can be one or multiple. And multiple plans in a certain other level are usually in a parallel relationship. In this project framework, from top to bottom, the root-level plan is used for the overall planning of the entire life cycle of the target project, including the determination of key phases and milestones, to summarize the main progress nodes and overall framework of the target project; the plans in the second level are used to decompose the target project into multiple sub-plans, that is, to decompose the complex target project into smaller and manageable parts for subsequent supplementation, change, and management. According to the granularity requirements of project management, it can be further subdivided on the basis of the second level to generate sub-plans at the third level, such as plans with a smaller granularity. In the embodiments of the present application, the number of levels in the project framework is not limited.

[0039] Step 102, starting from the root-level plan, layer by layer in response to a template association instruction for the current-level plan, according to the mapping relationship between the project management elements in the current-level plan and the project management elements in the plan template at the corresponding level, insert the tasks set under each project management element in the plan template under the corresponding project management element in the current-level plan to obtain the structure tree of the current-level plan.

[0040] Optionally, before step 102, Figure 1 The method shown can also include: in response to a compilation instruction for plan templates at different levels, compiling plan templates for different levels. Among them, in the plan template at any level, at least one project phase corresponding to the any level is set, at least one task and at least one milestone are respectively set under the at least one project phase, and at least one task can be set under the milestone, or no task is set under the milestone. In any of the plan templates, the task includes a task identifier and task content, where the task content can include the processes and steps for achieving the project goal.

[0041] In order to provide a standardized framework and improve the efficiency of plan generation, before generating the project plan, it is necessary to determine plan templates at different levels and define the project phases, milestones, and tasks (also called activities) in the plan templates. The specific steps are as Figure 2As shown in the figure. It should be noted that in a defined project plan template, the relationship between project phases, milestones, and tasks can be as follows: milestones and tasks are included under a project phase. A milestone can exist independently or can include tasks. Among them, a task is the smallest unit.

[0042] As Figure 2 shown, when preparing project plan templates for different levels, it can include: Step 201, define the classification of the project plan template.

[0043] Due to the different characteristics and requirements of project level division, it is necessary to classify the project plan templates by level so that the templates at each level can be accurately matched when generating a project plan.

[0044] Since project plans need to be generated hierarchically later, plans at different levels often have different characteristics and requirements. Therefore, in order to facilitate template matching when generating plans hierarchically, it is necessary to classify the project plan templates by level. As an optional implementation method, as Figure 3 shown, it can be divided into first-level project plan templates, second-level project plan templates, third-level project plan templates, and so on. It should be noted that this classification method is based on levels. The first-level project plan template is the root-level project plan template, usually used to define the overall framework of a project, while the second-level and third-level project plan templates are subordinate templates of the first-level project plan template, usually used to define the plans (also called sub-plans) of each branch (such as the software part and the hardware part in computer product development belong to two different branches) and each part of the project. In the second-level and third-level project plan templates, if necessary, the project plan templates can be further subdivided under the plan template types at this level. Different project plan templates at the same level are in a parallel relationship.

[0045] Step 202, define the project management elements in the project plan templates at each level and the tasks under the project management elements, and clarify the order and hierarchical relationship between different project management elements.

[0046] For example, define the project phases, milestones, and task names in each project plan template, and clarify the order and hierarchical relationship among the three to form a structured task arrangement. It should be noted that the project phases and milestones here are only used as the basis for organizing and arranging tasks, rather than the project phases and milestones in an actual project.

[0047] Step 203, define the task content in the project plan templates at each level.

[0048] As mentioned above, the task content can include the processes and steps to achieve the project goals. In addition, in Step 203, it is necessary to ensure that the relationship and order among the tasks in each project plan template meet the project management requirements, laying a foundation for subsequent plan generation.

[0049] In step 102, the template association instructions are executed layer by layer. According to the mapping relationship between the project management elements in the current level plan and the project management elements in the plan templates of the corresponding level, the tasks set under each project management element in the plan template are inserted (or mounted) under the corresponding project management element in the current level plan, obtaining the structure tree of the current level plan. For example, in response to the template association instruction for the root level plan, the root level plan template is selected, and according to the mapping relationship between the project phases and milestones in the root level plan and the root level plan template, the tasks in the root level plan template are mounted one by one to the root level plan; after entering the second level, in response to the template association instruction for the second level sub-plan, the corresponding task content is mounted under the plan of this level. This process is executed sequentially according to the hierarchical structure to ensure that the plans at each level can be configured with the corresponding task content according to the standard template and progress layer by layer, so it can support the multi-level management of complex projects.

[0050] Specifically, as Figure 4 shown, step 102 may include: Step 401, in response to the template association instruction for the current level plan, select the target plan template to be associated with the current level plan in the plan template library.

[0051] Step 402, map the project management elements in the current level plan to the project management elements in the target plan template.

[0052] Specifically, according to the project phase name, map the project phases in the current level plan to the project phases in the target plan template; and according to the milestone name, map the milestones in the current level plan to the milestones in the target plan template. It should be noted that due to the different types of projects, the naming methods of project phases for each project are different. Therefore, in addition to automatically mapping and matching according to the name of the project phase, the user can also manually select to determine the mapping relationship between the project management elements in the current level plan and the target plan template.

[0053] Step 403, according to the mapping relationship between the project management elements in the current level plan and the project management elements in the target plan template, insert the tasks set under each project management element in the project plan template under the corresponding project management element in the current level plan, obtaining the structure tree of the current level plan.

[0054] Optionally, if there is a parent-child relationship between the tasks in the target plan template, the parent-child relationship of the tasks needs to be mounted to the current level plan together. If there are tasks under the milestone of the target plan template and there is the same milestone in the current level plan, mount the tasks under the milestone of the target plan template under the milestone of the current level plan.

[0055] The following uses examples to separately illustrate the template association process for the root-level plan and the target-level plan.

[0056] 1) Template association of the root-level plan (first-level plan) First, in response to the template association instruction for the root-level plan, select the root-level plan template in the plan template library to be associated with the root-level plan.

[0057] Second, map the project management elements in the root-level plan to the project management elements in the root-level plan template.

[0058] Then, according to the mapping relationship between the project management elements in the root-level plan and the project management elements in the root-level plan template, insert the tasks set under each project management element in the root-level plan template under the corresponding project management elements in the root-level plan. After mounting the tasks at the root level, obtain the structure tree of the root-level plan. Optionally, if there is a parent-child relationship among the tasks in the root-level plan template, the parent-child relationship of the tasks needs to be mounted to the root-level plan together. If there are tasks under the milestone of the root-level plan template and there is the same milestone in the root-level plan of the target item, mount the tasks under the milestone in the root-level plan template to the milestone in the root-level plan of the target project.

[0059] Exemplarily, as Figure 5 shown, the project phase a in the project plan (i.e., the first-level plan or the root-level plan) is mapped to the project phase 1 in the first-level plan template, and the project phase b in the project plan is mapped to the project phase 2 in the template. Therefore, task 1 can be mounted under phase a, task 5 can be mounted under phase b, and tasks 2 under milestone 1, tasks 3 under milestone 2, and tasks 7 under milestone 5 can be mounted under the corresponding milestones in the project plan.

[0060] 2) Template association of the second-level plan First, in response to the template association instruction for the second-level plan, select the second-level plan template in the plan template library to be associated with the second-level plan.

[0061] Second, map the project management elements in the second-level plan to the project management elements in the second-level plan template.

[0062] Then, according to the mapping relationship between the project management elements in the secondary plan and the project management elements in the secondary plan template, insert the tasks set under each project management element in the secondary plan template under the corresponding project management element in the secondary plan. After mounting the tasks under the secondary plan, obtain the structure tree of the secondary plan. Optionally, if there is a parent-child relationship among the tasks in the secondary plan template, the parent-child relationship of the tasks needs to be mounted to the project plan as well. If there are tasks under the milestone of the secondary plan template and there is the same milestone in the secondary plan of the target project, mount the tasks under the milestone of the secondary plan template under the milestone of the secondary plan of the target project.

[0063] Exemplarily, as Figure 6A shown, after selecting the associated secondary plan template, Task 2.1, Task 2.2, and Task 2.2.1 are all mounted under the secondary plan, and Task 2.3, Task 2.3.1, and Task 2.4 are all mounted under Milestone 1. In addition, the project plan after completing the association of the primary plan template and the secondary plan template is as Figure 6B shown.

[0064] The association process of the plan templates at other levels is similar to the association process of the above secondary plan template. By analogy, it will not be elaborated here. After completing the association of the plan templates of all levels of plans, a complete project plan can be generated.

[0065] Optionally, after inserting the tasks set under each project management element in the plan template corresponding to the current level plan under the corresponding project management element in the current level plan, update the template association status of the current level plan from unassociated to associated. For example, as Figure 5 shown, after completing the association of the primary plan template, update the status of the project plan (primary plan) to "template associated". As shown in Figure 6, after completing the association of the secondary plan template, update the status of the secondary plan to "associated" as well.

[0066] Step 103: Arrange the structure trees of the plans at each level in the at least two levels according to the hierarchical relationship to obtain the project plan of the target project.

[0067] A project plan management method proposed in an embodiment of the present application. Since a project plan framework including at least two levels is set hierarchically from top to bottom, where the root-level plan in the at least two levels is used for the overall planning of the target project, and the other level plans are used to decompose the target project into sub-plans of at least one level; and the task insertion of each level plan is realized through an associated template to obtain the structure tree of each level plan, and finally the structure trees of each level plan are arranged according to the hierarchical relationship to obtain the project plan of the target project, rather than generating the project plan as a whole at one time. Therefore, it is more friendly to the change of the project plan, enabling the project manager to more flexibly add, delete sub-plans and implement plan changes, making the compilation of the project plan always based on the top-level project life cycle and consistent with the management objectives of the project, thereby optimizing the project management process and improving the success rate and response speed of the project.

[0068] In some embodiments, during the process of generating the project plan of the target project, before the project plan of the target project comes into effect, the current state of the project plan of the target project is set to "configuring".

[0069] Optionally, after step 103, a project plan management method proposed in an embodiment of the present application may further include: when the current state of the project plan is in the configuring state, in response to an instruction to assign the project plan to a first user, assign the project plan to the first user for task adjustment, where the task adjustment includes at least one of task trimming, supplementing, and modifying.

[0070] For example, after layer-by-layer associating the plan templates, a trimmer can be assigned to trim the tasks of the project plan to ensure that the tasks are within the scope and objectives of the target project.

[0071] In some embodiments, after step 103, or after the first user finishes adjusting the project plan, a project plan management method proposed in an embodiment of the present application may further include one or more of the following: Send the project plan to an audit platform for auditing; Update the current state of the project plan to pending audit; In response to the current state of the project plan being updated to audit passed, update the current state of the project plan to effective.

[0072] In other embodiments, after step 103, or after the first user finishes adjusting the project plan, a project plan management method proposed in an embodiment of the present application may further include one or more of the following: Send the project plan to an audit platform for auditing; Update the current state of the project plan to pending audit; In response to the current status of the project plan being updated to approved for review, submit the project plan to the reviewer for review; Update the current status of the project plan to pending review; In response to the current status of the project plan being updated to approved after review, update the current status of the project plan to effective.

[0073] That is to say, in order to ensure that the generated project plan meets the project objectives and specification requirements in terms of content, after the project plan is generated, the plan can be submitted to the relevant department for review, or for review and re-review. After the relevant department's review or re-review is passed, the project plan comes into force formally and thus enters the actual execution stage. This step ensures that all the generated project plan content undergoes compliance review, avoids deviation from the project objectives, and maintains the overall project plan.

[0074] Figure 7 shows a possible review process for the project plan. As Figure 7 shown, this process may include: After the project manager generates an initial project plan based on the associated plan template, assign a trimmer; after the trimmer trims the redundant tasks in the project plan, the process node transfers to the project manager; the project manager confirms whether the trimming is completed, if not, re-assign the trimmer, if so, initiate a review and select a reviewer; The reviewer reviews the rationality of the tasks configured in the project plan, and the current status of the project plan is updated to "pending review"; if the reviewer believes that there are unreasonable situations in the task configuration of the project plan and need to be modified or re-evaluated, then select the reviewer to reject and reject the unreasonable activities back to the project manager for modification; if the reviewer cannot judge the rationality of some activities, the activities can be submitted to the re-reviewer for re-review; if the reviewer believes that the activity configuration in the project plan meets the project requirements, scope, objectives, etc., then select the reviewer to agree, the project plan comes into force formally, and the status of the project plan is updated to "passed", and the project plan comes into force formally; After the reviewer submits for re-review, the current status of the project plan flips to "pending re-review", and the re-reviewer re-reviews the activities of the project plan; if the re-reviewer believes that there are unreasonable situations in the task configuration of the project plan and need to be modified or re-evaluated, then select the re-reviewer to reject; if the re-reviewer believes that the configuration is reasonable, then select the re-reviewer to agree, and the status of the project plan is updated to "passed", and the project plan comes into force formally.

[0075] The following uses a detailed embodiment to illustrate the process of project plan generation and review for applying a project plan management method proposed in this application. In this detailed embodiment, the target project is a project including software and hardware development plans.

[0076] As Figure 8 shown, in this detailed embodiment, a project plan management method proposed in this application may include: Step 801, define the first-level plan template.

[0077] Determine the basic structure of the first-level plan template, which is used to define the key project phases and milestones at the project global level. The first-level plan template, as the core reference for the overall project framework, includes the main phases, key nodes, and corresponding standardized activity processes of the whole project. That is, Template_L1 = {Concept Phase {Milestone 概念 , Task 概念}, Planning Phase {Milestone 计划 , Task 计划}, Development Phase {Milestone 开发 , Task 开发}, Maintenance Phase {Milestone 维护 , Task 维护}}.

[0078] Step 802, define the second-level plan template.

[0079] After determining the first-level plan template, further define the second-level plan template to support more refined management of the project. The second-level plan template is used to further subdivide the phases of the first-level plan template and is applicable to specific modules or sub-plans of the project. That is, Template_L2 = {Milestone L2 , Task L2}.

[0080] Step 803, create the project framework of the target project, and this project framework includes two levels of plans.

[0081] Plan_L1 = {Concept Phase {Milestone 概念}, Planning Phase {Milestone 计划}, Development Phase {Milestone 开发}, Maintenance Phase {Milestone 维护}, Plan_L2 = {Milestone L2}}.

[0082] Step 804, in response to the first-level plan template association instruction, associate the first-level plan template.

[0083] Select to associate Template_L1, then Plan_L1 = Template_L1 = {Concept Phase {Milestone 概念 , Task 概念}, Planning Phase {Milestone 计划 , Task 计划}, Development Phase {Milestone 开发 , Task 开发}, Maintenance Phase {Milestone 维护 , Task 维护}, Plan_L2 = {Milestone L2}}.

[0084] Step 805, in response to the secondary plan template association instruction, associate the secondary plan template.

[0085] Select to associate Template_L2, then Plan_L2 = Template_L2 = {Milestone L2 , Task L2}}.

[0086] Step 806, in response to the instruction to assign the project plan to the first user, assign the project plan to the first user for task adjustment.

[0087] For example, perform trimming, supplementation, or modification on {Task 概念 , Task 计划 , Task 开发 , Task 维护 , Task L2}}.

[0088] Step 807, submit it to the reviewer for review.

[0089] Submit Plan_L1 = {Concept Phase {Milestone 概念 , Task 概念}}, Planning Phase {Milestone 计划 , Task 计划}}, Development Phase {Milestone 开发 , Task 开发}}, Maintenance Phase {Milestone 维护 , Task 维护}}, Plan_L2 = {Milestone L2 , Task L2}} completely to the reviewer for review.

[0090] Step 808, submit it to the re-reviewer for re-review.

[0091] The reviewer then submits Plan_L1 to the re-reviewer for review.

[0092] Step 809: After the review is passed, determine that the project plan of the target project becomes effective.

[0093] After the reviewer approves the review, the status of Plan_L1 = Passed, the status of Plan_L2 = Passed, and Plan_L1 and Plan_L2 are officially invalidated.

[0094] Optionally, a project plan management method proposed in any embodiment of the present application may further include steps for changing the generated project plan.

[0095] In some embodiments, such as Figure 9 shown, a project plan management method proposed in any embodiment of the present application may further include: Step 104: In response to a change instruction for the target-level plan among the plans of the at least two levels, update the current status of the target-level plan and the subordinate plans of the target-level plan to In Configuration.

[0096] Specifically, the target-level plan to be changed can be determined first. The embodiments of the present application can generate a project plan based on levels, and can change the plans of each level separately. On the basis of flexibly supplementing the plan content, it does not affect the configuration of other level plans. Then, in response to the change instruction, trigger the status flip of the target-level plan and roll back to the In Configuration status. It should be noted that the change instruction can simultaneously trigger the status flip of the target-level plan and the subordinate sub-plans, without affecting the status of the upper-level plans. Usually, the subordinate plans depend on the goals and frameworks set by the upper-level plans. Therefore, when the upper-level plan changes, the subordinate plans need to make corresponding changes synchronously. And the change of the subordinate plans needs to ensure that the change is within the goals and frameworks set by the upper-level plans. Therefore, the change of the subordinate plans does not affect the upper-level plans. Exemplarily, as Figure 10 shown, all the project plans have been approved. At this time, if a change is initiated for the secondary plan A, the status of the secondary plan A and the tertiary plans A.1 and A.2 will roll back from Passed to In Configuration.

[0097] Step 105: In response to a template association instruction for the target-level plan, delete the tasks attached to the target-level plan, and according to the mapping relationship between the project management elements in the target-level plan and the project management elements in the corresponding plan template, re-insert the tasks set under each project management element in the corresponding plan template under the corresponding project management elements in the target-level plan to obtain the structure tree of the target-level plan.

[0098] Among them, the corresponding plan template re-associated with the target-level plan can be a revised version of the plan template previously associated with the target-level plan, or a new plan template.

[0099] Optionally, before re-associating a plan template with the target hierarchical plan, first determine whether the target hierarchical plan has already been associated with a plan template. If not, directly insert the activities in the selected template into the plan. If so, first delete the tasks attached to the target hierarchical plan, retain the framework content of the target hierarchical plan, and insert the tasks in the newly selected plan template into the plan.

[0100] In some embodiments, if there is a situation of adding or deleting sub-plans, such as Figure 11 shown, a project plan management method proposed in any embodiment of the present application may further include: Step 106, determine the superior plan for which a plan needs to be added or deleted.

[0101] The superior level of the sub-plan to be changed can be located by retrieving the hierarchical structure of the project plan to ensure the accuracy of the addition or deletion operation.

[0102] Step 107, in response to a plan addition instruction for the superior plan, insert a new subordinate plan under the superior plan, and / or, in response to a plan deletion instruction for the superior plan, delete the subordinate plan under the selected superior plan.

[0103] Optionally, in response to a plan addition instruction for the superior plan, and / or, in response to a plan deletion instruction for the superior plan, trigger a state flip of the superior plan, roll back to the configured state, and make the superior plan enter a stage allowing modification to prepare for subsequent addition or deletion operations.

[0104] In step 107, in response to a plan addition instruction for the superior plan, in response to an instruction to add or delete a plan, mount the newly added sub-plan under the plan at the lower level and remove the sub-plan to be deleted. That is, receive specific addition or deletion instructions and adjust the sub-plans of the superior plan according to the instructions. When the addition instruction takes effect, the system mounts the newly added sub-plan into the lower-level structure of the superior plan; when the deletion instruction takes effect, the system removes the specified sub-plan from the superior plan. This step ensures the structural dynamics of the superior plan while maintaining the logical relationship between hierarchical plans.

[0105] Optionally, for the changed project plan, processes such as adjustment, review, and re-review can also be carried out. The specific processes are similar to the adjustment, review, and re-review processes described above. For example, as Figure 12 shown, after the review is passed, the changed project plan comes into effect officially, and the updated plan structure is archived and incorporated into the overall project management system. This step ensures that all change operations are strictly reviewed to ensure the accuracy and legality of plan changes.

[0106] The following continues with a detailed example mentioned above to illustrate the process of project plan change and review for a project plan management method proposed in this application.

[0107] As Figure 13 shown, based on the process Figure 8 shown, a project plan management method proposed in this application may further include: Step 810, initiate a secondary plan change in response to a secondary plan change instruction.

[0108] For example, initiate a change to Plan_L2 = {Milestone L2 , Task L2}.

[0109] Step 811, trigger the flipping of the current state of the secondary plan.

[0110] Flip the current state of Plan_L2 to being configured.

[0111] Step 812, re-associate the secondary plan template in response to a template association instruction for the secondary plan. For example, Plan_L2 = Template_L2 = {Milestone L2 , Task L2}.

[0112] Step 813, add a tertiary plan under the secondary plan in response to a plan addition instruction for the secondary plan. For example, Plan_L2 = {Milestone L2 , Task L2 , Plan_L3 = {Milestone L3}}.

[0113] Step 814, associate the tertiary plan template in response to a template association instruction for the tertiary plan.

[0114] For example, select the tertiary plan template Template_L3, then Plan_L3 = Template_L3 = {Milestone L3 , Task L3}.

[0115] Step 815, assign the project plan to the first user for task adjustment in response to an instruction to assign the project plan to the first user.

[0116] For example, perform trimming, supplementation, or modification on {Task L2 , Task L3}.

[0117] Step 816: Submit the project plan to the reviewer for review.

[0118] For example, submit Plan_L2 = {Milestone L2 , Task L2 , Plan_L3 = {Milestone L3 , Task L3} in its entirety to the reviewer for review.

[0119] Step 817: Submit the project plan to the re-reviewer for re-review.

[0120] For example, the reviewer then submits Plan_L2 and Plan_L3 to the re-reviewer for re-review.

[0121] Step 818: After the re-review is passed, determine that the changed project plan comes into force officially.

[0122] For example, after the re-review is passed, Plan_L2 status = passed, Plan_L3 status = passed, and Plan_L2 and Plan_L3 become invalid officially.

[0123] A project plan management method proposed in an embodiment of this application provides significant flexibility and efficiency for the management of complex projects by generating and changing plans in a top-down hierarchical manner. First, by defining and hierarchically setting plan templates, detailed plans can be gradually generated at different levels of the project, including project phases, milestones, tasks, etc., enabling managers to clearly grasp the overall layout of tasks at each stage. Second, it allows for flexible adjustment and supplementation of sub-plans without deviating from the overall project objectives and the project full-life cycle framework to quickly respond to changes in the project process. When it is necessary to change a plan or sub-plan at a certain level, the status flip can be triggered, roll back to the configuration state, and regenerate the updated plan according to the associated template to ensure the continuity and consistency of the plan. After each change, it can come into force officially through the review mechanism, further enhancing the rigor and control of the project plan. In summary, a project plan management method proposed in an embodiment of this application provides a more agile and efficient project management method, effectively improving the response speed and success rate of the project in dealing with changes and significantly optimizing the management process of complex projects.

[0124] The above describes specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order from that in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0125] Figure 14 This is a schematic structural diagram of an electronic device according to an embodiment of the present application. Please refer to Figure 14 , at the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include internal memory, such as high-speed random access memory (Random-Access Memory, RAM), and may also include non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0126] The processor, network interface, and memory can be interconnected through an internal bus, and the internal bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 14 only a bidirectional arrow is used in

[0127] The memory is used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include internal memory and non-volatile memory, and provide instructions and data to the processor.

[0128] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs it, forming a project plan management device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations: Set at least two levels of plans for the target project. Among them, each plan is provided with project management elements. The root-level plan in the at least two levels is used for the overall planning of the target project, and other level plans are used to decompose the target project into at least one level of sub-plans; Starting from the root-level plan, layer by layer in response to a template association instruction for the current-level plan, according to the mapping relationship between the project management elements in the current-level plan and the project management elements in the corresponding-level plan template, insert the tasks set under each project management element in the plan template under the corresponding project management element in the current-level plan to obtain the structure tree of the current-level plan; Arrange the structure trees of the plans of each level in the at least two levels according to the hierarchical relationship to obtain the project plan of the target project.

[0129] The above, such as in the present application Figure 14 The method executed by the project plan management device disclosed in the embodiments shown can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0130] The electronic device can also execute Figure 1 the method and implement the functions of the project plan management device in Figure 1 the embodiments shown. The embodiments of the present application will not be elaborated here.

[0131] Of course, in addition to the software implementation method, the electronic device of the present application does not exclude other implementation methods, such as a logical device or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logical unit, and can also be hardware or a logical device.

[0132] The embodiments of the present application also propose a computer-readable storage medium that stores one or more programs. The one or more programs include instructions that, when executed by a portable electronic device including a plurality of target application programs, can cause the portable electronic device to execute Figure 1 the method of the illustrated embodiment, and specifically used to execute a project plan management method proposed by the embodiments of the present application.

[0133] Figure 15 is a schematic structural diagram of a project plan management device 1500 according to an embodiment of the present application. Please refer to Figure 15 , in a software implementation manner, the project plan management device 1500 may include: a plan framework setting module 1501, a template association module 1502, and a plan generation module 1503.

[0134] The plan framework setting module 1501 is configured to set plans with at least two levels for a target project. Among them, each plan is provided with project management elements. The root-level plan in the at least two levels is used for the overall planning of the target project, and other-level plans are used to decompose the target project into at least one level of sub-plans.

[0135] The target project can be any project for which a project plan is to be generated. The project management elements may include, but are not limited to, one or more of project phases, milestones, and risk management. Among them, project phases and milestones are often mandatory project management elements in project management.

[0136] Through the plan framework setting module 1501, a project framework of the target project can be constructed first. At least two levels of plans are set in the project framework. Among them, there is usually only one root-level plan (also called a first-level plan or a primary-level plan), and each level of plan in other levels can be one or more. And multiple plans in a certain other level are usually in a parallel relationship. In this project framework, from top to bottom, the root-level plan is used for the overall planning of the entire life cycle of the target project, including the determination of key phases and milestones, to summarize the main progress nodes and overall framework of the target project; the second-level plan is used to decompose the target project into multiple sub-plans, that is, to decompose the complex target project into smaller and manageable parts, which is convenient for subsequent supplementation, change, and management. According to the granularity requirements of project management, it can be further subdivided on the basis of the second level to generate a third-level sub-plan, such as a plan with a smaller granularity. In the embodiments of the present application, the number of levels in the project framework is not limited.

[0137] A template association module 1502, configured to start from the root-level plan, and layer by layer in response to a template association instruction for the current-level plan, insert tasks set under each project management element in the plan template under the corresponding project management element in the current-level plan according to the mapping relationship between the project management elements in the current-level plan and the project management elements in the plan template at the corresponding level, to obtain the structure tree of the current-level plan.

[0138] Optionally, Figure 15 the method shown may further include: a template definition module, configured to compile plan templates for different levels in response to a compilation instruction for plan templates of different levels, wherein in the plan template of any level, at least one project phase corresponding to the any level is provided, at least one task and at least one milestone are respectively provided under the at least one project phase, and at least one task may be set under the milestone, or no task is set under the milestone. In any of the plan templates, the task includes a task identifier and task content, and the task content may include the processes and steps for achieving the project objectives.

[0139] Specifically, the template definition module may be configured to: define the classification of the plan template; define the project management elements and the tasks under the project management elements in the plan templates of each level, and clarify the sequence and hierarchical relationship between different project management elements; define the task content in the plan templates of each level.

[0140] Specifically, the template association module 1502 may be configured to: in response to a template association instruction for the current-level plan, select a target plan template to be associated with the current-level plan from the plan template library; map the project management elements in the current-level plan to the project management elements in the target plan template; insert the tasks set under each project management element in the project plan template under the corresponding project management element in the current-level plan according to the mapping relationship between the project management elements in the current-level plan and the project management elements in the target plan template, to obtain the structure tree of the current-level plan.

[0141] Optionally, the template association module 1502 may further be configured to: if there is a parent-child relationship between tasks in the target plan template, mount the parent-child relationship of the tasks to the current-level plan; if there are tasks under the milestone of the target plan template and there is the same milestone in the current-level plan, mount the tasks under the milestone of the target plan template under the milestone of the current-level plan.

[0142] A plan generation module 1503, configured to arrange the structure trees of the plans of each level in the at least two levels according to the hierarchical relationship, to obtain the project plan of the target project.

[0143] Figure 15 The project plan management device 1500 provided by the illustrated embodiment can also execute Figure 1 the method, and implement Figure 1 the functions of the illustrated embodiment, and achieve the same technical effects. The embodiments of the present application will not be elaborated one by one here.

[0144] Optionally, in a software implementation, the project plan management device 1500 may include: an adjustment module, configured to, when the current state of the project plan is in configuration, in response to an instruction to assign a first user to the project plan, assign the project plan to the first user for task adjustment, where the task adjustment includes at least one of task trimming, supplementation, and modification.

[0145] Optionally, in a software implementation, the project plan management device 1500 may include: an audit module, configured to send the project plan to an audit platform for auditing; a first status update module, configured to update the current state of the project plan to pending audit; a second status update module, configured to, in response to the current state of the project plan being updated to audit passed, update the current state of the project plan to effective.

[0146] Optionally, in a software implementation, the project plan management device 1500 may include: an audit module, configured to send the project plan to an audit platform for auditing; a first status update module, configured to update the current state of the project plan to pending audit; a re-audit module, configured to, in response to the current state of the project plan being updated to audit passed, submit the project plan to a re-auditor for re-audit; a third status update module, configured to update the current state of the project plan to pending re-audit; a second status update module, configured to, in response to the current state of the project plan being updated to re-audit passed, update the current state of the project plan to effective.

[0147] Optionally, as Figure 16 illustrated, in a software implementation, the project plan management device 1500 may include: a first response module 1504 and a second response module 1505.

[0148] The first response module 1504 is configured to, in response to a change instruction for a target level plan in the at least two levels of plans, update the current states of the target level plan and the subordinate plans of the target level plan to configuration.

[0149] A second response module 1505, configured to, in response to a template association instruction for the target hierarchical plan, delete tasks mounted under the target hierarchical plan, and according to a mapping relationship between project management elements in the target hierarchical plan and project management elements in a corresponding plan template, re-insert tasks set under each project management element in the corresponding plan template under the corresponding project management element in the target hierarchical plan, to obtain a structure tree of the target hierarchical plan.

[0150] Figure 16 The project plan management device 1500 provided in the foregoing embodiment can further execute Figure 9 the method, and implement Figure 1 the functions of the foregoing embodiment, and achieve the same technical effects. The embodiments of the present application will not be elaborated herein one by one.

[0151] Optionally, as Figure 17 shown, in a software implementation manner, the project plan management device 1500 may include: a determination module 1506 and a third response module 1507.

[0152] The determination module 1506 is configured to determine a superior plan for which a plan needs to be added or deleted.

[0153] The third response module 1507 is configured to, in response to a plan addition instruction for the superior plan, insert a new subordinate plan under the superior plan, and / or, in response to a plan deletion instruction for the superior plan, delete a selected subordinate plan under the superior plan.

[0154] Figure 17 The project plan management device 1500 provided in the foregoing embodiment can further execute Figure 11 the method, and implement Figure 1 the functions of the foregoing embodiment, and achieve the same technical effects. The embodiments of the present application will not be elaborated herein one by one.

[0155] In summary, the foregoing are only the preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0156] The systems, devices, modules or units illustrated in the foregoing embodiments may be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0157] A computer-readable medium includes permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0158] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising the element.

[0159] Each embodiment in this application is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the description of the method embodiment.

Claims

1. A project planning management method, characterized in that: The method comprises: At least two levels of plans are set for the target project, wherein each plan is provided with a project management element, a root level plan of the at least two levels is used for the overall planning of the target project, and other level plans are used to decompose the target project into at least one level of sub-plans; Starting from the root-level plan, responding to the template association instructions for the current-level plan layer by layer, according to the mapping relationship between the project management elements in the current-level plan and the project management elements in the plan template of the corresponding level, inserting the tasks set under each project management element in the plan template under the corresponding project management element in the current-level plan, to obtain a structure tree of the current-level plan; The structure tree of the plans of each level in the at least two levels is arranged according to the hierarchical relationship to obtain the project plan of the target project.

2. The method according to claim 1, characterized in that Before responding to the template association instruction for the current level plan layer by layer starting from the root level plan, the method further includes: In response to instructions for preparing plan templates for different levels, plan templates for different levels are prepared, wherein in the plan template of any level, at least one project phase corresponding to the any level is provided, and at least one task and at least one milestone are provided under the at least one project phase, and at least one task is provided under a milestone, or no task is provided under a milestone.

3. The method according to claim 1, characterized in that The method further comprises: After inserting the tasks set under each project management element in the plan template corresponding to the current level plan into the corresponding project management element in the current level plan, the template association status of the current level plan is updated from unassociated to associated.

4. The method according to claim 1, characterized in that: The method further comprises: In response to a change instruction for a target-level plan among the at least two-level plans, updating the current status of the target-level plan and subordinate plans of the target-level plan to being configured; In response to the template association instruction for the target level plan, the tasks attached to the target level plan are deleted, and according to the mapping relationship between the project management elements in the target level plan and the project management elements in the corresponding plan template, the tasks set under each project management element in the corresponding plan template are reinserted into the corresponding project management elements in the target level plan to obtain a structure tree of the target level plan.

5. The method according to claim 1, characterized in that The method further comprises: Identify parent plans that require additions or deletions; In response to a plan adding instruction for the upper-level plan, a new lower-level plan is inserted under the upper-level plan, and / or, in response to a plan deleting instruction for the upper-level plan, a lower-level plan selected under the upper-level plan is deleted.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: When the current state of the project plan is in configuration, in response to an instruction to assign the first user to the project plan, the project plan is assigned to the first user for task adjustment, wherein the task adjustment includes at least one of cutting, supplementing and modifying the task.

7. The method according to claim 6, characterized in that The method further comprises: Send the project plan to the review platform for review; Update the current status of the project plan to pending review; In response to the current status of the project plan being updated to approved, the current status of the project plan is updated to effective.

8. An electronic device comprising: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 7. 9 . A computer-readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 7.

10. A computer program product comprising instructions, when a computer runs the instructions of the computer program product, the computer performs the method according to any one of claims 1 to 7.

Images