Project schedule management method, device and equipment and readable storage medium
By creating a delivery progress table and updating the delivery progress table with agenda advance information, the problem of insufficient flexibility in compressing the project cycle is solved, and flexible control and efficiency improvement of the project cycle is achieved.
Patent Information
- Application Number
- CN202411023134.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-29
- Publication Date
- 2024-11-22
AI Technical Summary
Traditional project schedule management methods are not flexible enough when compressing project cycles, making it difficult to quickly respond to market changes and consumer demands.
By creating a delivery progress table, record the estimated completion time, delivery items and their responsible departments and submission status of each project stage, update the delivery progress table using schedule advance information and delivery advance information, flexibly adjust the estimated submission time of delivery items, and realize the project Flexible control of cycles.
It improves project execution efficiency and competitiveness, can quickly respond to market changes and consumer needs, and ensures that the project is carried out smoothly according to the new schedule.
Smart Images

Figure CN119005934A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of project management, and in particular to a project schedule management method, device, equipment and readable storage medium. Background Art
[0002] In today's competitive business environment, project schedule management is critical to the success of an enterprise. In order to respond more quickly to changing consumer demands and market trends, it is often necessary to move the estimated completion time of a project phase forward during project execution to shorten the project cycle. Traditional project schedule management methods usually rely on simple timeline planning and task allocation, which lacks flexibility when compressing project cycles. Summary of the invention
[0003] The present application provides a project schedule management method, device, equipment and readable storage medium, which can solve the technical problem that the project schedule management method in the prior art is insufficiently flexible when compressing the project cycle.
[0004] In a first aspect, an embodiment of the present application provides a project schedule management method, the project schedule management method comprising:
[0005] Create a delivery progress sheet, which is used to record the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department submitting the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase;
[0006] After obtaining the schedule advance information from the management department, check whether there is a first deliverable in the current project phase, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information;
[0007] If there is a first deliverable, the schedule advance information is sent to the responsible department of the first deliverable, the delivery advance information is obtained from the responsible department and the review process is executed. After the review is passed, the delivery progress table is updated according to the schedule advance information and the delivery advance information, otherwise the delivery progress table is updated according to the schedule advance information, where the delivery advance information is used to move the estimated submission time of the first deliverable forward.
[0008] Furthermore, in one embodiment, the delivery progress table is also used to record the achievement rate of deliverables in each project phase and the importance of each deliverable.
[0009] Furthermore, in one embodiment, after the step of creating the delivery progress table, the following steps are further included:
[0010] If the deliverable achievement rate of the current project phase is greater than or equal to the preset threshold, and all important deliverables of the current project phase are in the submitted state, a schedule advance suggestion is sent to the management department.
[0011] Furthermore, in one embodiment, the delivery progress table is also used to record the measures to be taken in case of overdue deliverables;
[0012] After the step of creating the delivery progress table, the method further includes:
[0013] Detect whether there is a second deliverable in the current project phase, wherein the second deliverable is in an undelivered state after the expected delivery time;
[0014] If the estimated delivery time of the second deliverable has not been updated based on the delivery delay information, a delay reminder is sent to the responsible department of the second deliverable, and the delivery delay information is obtained from the responsible department and a review process is performed, wherein the delivery delay information is used to move the estimated delivery time of the second deliverable backwards;
[0015] If the delivery delay information is approved, the delivery progress table will be updated according to the delivery delay information;
[0016] If the delivery delay information fails to pass the review, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0017] Furthermore, in one embodiment, after the step of updating the delivery progress table according to the delivery delay information if the delivery delay information is approved, the step further includes:
[0018] If the estimated delivery time of the second deliverable is updated based on the delivery delay information, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0019] Furthermore, in one embodiment, after the step of creating the delivery progress table, the following steps are further included:
[0020] Detect whether there is a second deliverable and a third deliverable in the current project phase, wherein the second deliverable is in an unsubmitted state after the expected submission time, and the third deliverable is in an unsubmitted state within a preset time before the expected submission time;
[0021] An overdue reminder is sent to the department responsible for the second deliverable, and an upcoming reminder is sent to the department responsible for the third deliverable.
[0022] Furthermore, in one embodiment, the step of creating a delivery progress table includes:
[0023] The estimated completion time of each project phase is sent to each professional department. The departmental delivery plan is obtained from each professional department and the review process is carried out. After the review is passed, a delivery progress sheet is created based on the estimated completion time of each project phase and each departmental delivery plan. The departmental delivery plan includes the deliverables that the professional department needs to submit at each project phase and their estimated submission time.
[0024] In a second aspect, an embodiment of the present application further provides a project schedule management device, the project schedule management device comprising:
[0025] A creation module is used to create a delivery progress sheet, where the delivery progress sheet is used to record the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department submitting the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase;
[0026] A first detection module is used to detect whether there is a first deliverable in the current project phase after obtaining the schedule advance information from the management department, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information;
[0027] The schedule compression module is used to send schedule advance information to the responsible department of the first deliverable if there is a first deliverable, obtain the delivery advance information from the responsible department and execute the review process. After the review is passed, the delivery progress table is updated according to the schedule advance information and the delivery advance information, otherwise the delivery progress table is updated according to the schedule advance information, wherein the delivery advance information is used to move the estimated submission time of the first deliverable forward.
[0028] In a third aspect, an embodiment of the present application further provides a project schedule management device, comprising a processor, a memory, and a project schedule management program stored in the memory and executable by the processor, wherein when the project schedule management program is executed by the processor, the steps of the above-mentioned project schedule management method are implemented.
[0029] In a fourth aspect, an embodiment of the present application further provides a readable storage medium, on which a project schedule management program is stored, wherein when the project schedule management program is executed by a processor, the steps of the above-mentioned project schedule management method are implemented.
[0030] In this application, the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable are recorded through the delivery progress table. When the management department requires the estimated completion time of the current project phase to be moved forward, it can quickly determine which deliverables need to be moved forward accordingly, so as to quickly update the delivery progress table. Through this application, flexible control can be performed when compressing the project cycle, thereby improving the execution efficiency and competitiveness of the project. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] Figure 1 This is a flowchart of a project schedule management method in one embodiment of the present application;
[0032] Figure 2 This is a functional module diagram of a project schedule management device in one embodiment of the present application;
[0033] Figure 3 This is a schematic diagram of the hardware structure of the project schedule management device involved in the embodiment of the present application. DETAILED DESCRIPTION
[0034] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0035] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.
[0036] In a first aspect, an embodiment of the present application provides a project schedule management method.
[0037] Figure 1 A flowchart of a project schedule management method in an embodiment of the present application is shown.
[0038] Reference Figure 1 In one embodiment, the project schedule management method includes the following steps:
[0039] S11. Create a delivery progress chart, where the delivery progress chart is used to record the estimated completion time of each project stage and the deliverables that need to be collected, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department that submits the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project stage.
[0040] In this embodiment, the delivery progress table can be used by all relevant departments to view the delivery plan and completion progress. The initial submission status of the deliverable is unsubmitted. After the responsible department submits the deliverable, it needs to execute the review process. The deliverable that passes the review will be changed to submitted status.
[0041] It should be noted that different deliverables may have dependencies. For deliverables with dependencies, the estimated delivery time of downstream deliverables needs to be determined based on the estimated delivery time of upstream deliverables. The estimated completion time of each project phase is confirmed by the management department, and the deliverables to be collected at each project phase, as well as the responsible department and estimated delivery time of each deliverable, are jointly confirmed by the management department and multiple professional departments.
[0042] For example, the project phases of a new car development project with a normal cycle include project start-up, project premise, project confirmation, solution confirmation, production start-up, product freeze, production condition confirmation, trial production, small batch, mass production, and market launch. The project phases of a new car development project with a short cycle include project start-up, project confirmation, solution confirmation, product freeze, production condition confirmation, mass production, and market launch.
[0043] The deliverables that the technical department needs to submit include: final version tool list of the sample book, data review list, supplier designated agreement, technical contract, design review, arrival acceptance form, quality assurance certificates for various engineering sections, installation, calibration, commissioning construction plan and corresponding acceptance forms, etc.
[0044] The deliverables that the logistics department needs to submit include: production condition confirmation operation plan planning and operation documents, warehouse layout plan review form, initial system parameter maintenance list, mass production parts warehouse layout plan, final system parameters, punching, welding, coating and other bus edge station plan layout confirmation, mass production parts online route planning confirmation, packaging style collection and review form, trial production packaging verification review form, mass production input container plan and acceptance report, key packaging parts boundary information list, special feature parts list, logistics plan planning list, shipping location confirmation list, pickup trial run qualified list, basic data confirmation completion checklist, mass production judgment meeting resolution materials, third-party logistics warehousing and transportation contract, in-stock storage plan report, transportation loading, fastening plan evaluation report, service center visit problem report, mass production capacity calculation report, mass production warehousing personnel list, storage location confirmation report, etc.
[0045] The deliverables that the materials department needs to submit include: formal order, small batch indicative order, small batch formal order, small batch management arrival schedule, mass production indicative order, production adjustment record, mass production first batch order, mass production first batch management arrival schedule, etc.
[0046] The deliverables that the purchasing production standard department needs to submit include: production standard kick-off meeting plan, supplier production standard plan, supplier mold list and inspection fixture list, equipment & tooling list, supplier capacity list, risk and difficulty topic discussion group parts process failure and effect analysis report, design stage debugging parts test list, production stage test list, automotive tooling sample approval report, parts submission guarantee signing report, etc.
[0047] The deliverables that the vehicle quality department needs to submit include: vehicle quality target list, quality assurance planning list for each stage, quality result report of implementation plan, minutes or list of shipment judgment meeting, inspection and regulation documents, special characteristics list, safety and protection documents, re-insurance torque documents, first edition of safety and protection simplified regulations, quality assurance list for vehicle evaluation stage, etc.
[0048] The deliverables that the R&D department needs to submit include: engineering inspection list, production parts approval procedure approval list, parts submission guarantee signature list, production stage test list, career plan, data freeze list, supplier capacity list, recurrence prevention problem list of key and difficult topic discussion group, capacity planning list, valve point confirmation list for each stage, etc.
[0049] The deliverables that the supplier's quality engineering department needs to submit include: T0 product confirmation list, T1 product confirmation list, parts special characteristics list, special characteristics achievement tracking form, inspection fixture acceptance form, inspection fixture sample review form, inspection fixture acceptance form, supplier capability review list, engineering supervision list, production parts approval procedure approval list, parts submission guarantee signature approval list, production stage test management list, recurrence prevention list, suitability determination list, etc.
[0050] S12. After obtaining the schedule advance information from the management department, check whether there is a first deliverable in the current project phase, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information.
[0051] In this embodiment, the management department refers to the delivery schedule and market demand, submits the schedule advance information, and requests that the estimated completion time of the current project stage be moved forward. Before updating the estimated completion time of the current project stage, it is necessary to detect whether there is an unsubmitted state in the current project stage, and the deliverables with the estimated submission time after the new estimated completion time corresponding to the schedule advance information are recorded as the first deliverable. Moving the estimated completion time forward will affect the estimated submission time of the first deliverable, and it is necessary to notify the responsible department of the first deliverable to assist in adjusting the estimated submission time.
[0052] S13. If there is a first deliverable, send the schedule advance information to the responsible department of the first deliverable, obtain the delivery advance information from the responsible department and execute the review process. After the review is passed, update the delivery progress table according to the schedule advance information and the delivery advance information, otherwise update the delivery progress table according to the schedule advance information, wherein the delivery advance information is used to move the estimated submission time of the first deliverable forward.
[0053] In this embodiment, after receiving the schedule advance information, the responsible department of the first deliverable submits the delivery advance information in combination with the actual situation, and moves the estimated delivery time of the first deliverable forward so that the new estimated delivery time is before the new estimated completion time. After the delivery advance information is reviewed and approved, the delivery progress table is updated according to the schedule advance information and the delivery advance information. If there is no first deliverable, the delivery progress table can be directly updated according to the schedule advance information.
[0054] It should be noted that step S13 describes the situation where the project cycle is successfully compressed according to the advance schedule information. During actual execution, it may happen that the responsible department of the first deliverable is unable to submit the advance delivery information that meets the requirements due to its own situation, resulting in the inability to update the delivery progress table.
[0055] Therefore, in this embodiment, the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable are recorded in the delivery progress table. When the management department requires the estimated completion time of the current project phase to be moved forward, it can be quickly determined which deliverables need to have their estimated submission time moved forward accordingly, thereby quickly updating the delivery progress table. Through this embodiment, flexible control can be performed when compressing the project cycle, thereby improving the execution efficiency and competitiveness of the project.
[0056] Furthermore, in one embodiment, the delivery progress table is also used to record the achievement rate of deliverables in each project phase and the importance of each deliverable.
[0057] In this embodiment, the management department can refer to the deliverable achievement rate and the importance of the deliverables in the current project stage to decide whether to move the estimated completion time of the current project stage forward, so as to make reasonable decisions. For example, when the deliverable achievement rate of the current project stage is low or the first deliverable includes important deliverables, it is very likely that the responsible department of the first deliverable cannot submit the required advance delivery information according to its own situation, resulting in the inability to update the delivery progress table.
[0058] Furthermore, in one embodiment, after the step of creating the delivery progress table, the following steps are further included:
[0059] If the deliverable achievement rate of the current project phase is greater than or equal to the preset threshold, and all important deliverables of the current project phase are in the submitted state, a schedule advance suggestion is sent to the management department.
[0060] In this embodiment, the schedule advance suggestion is automatically triggered according to the deliverable achievement rate and the submission status of important deliverables in the current project stage, so as to assist the management department in making decisions and improve the execution efficiency.
[0061] Furthermore, in one embodiment, the delivery progress table is also used to record the measures to be taken in case of overdue deliverables;
[0062] After the step of creating the delivery progress table, the method further includes:
[0063] Detect whether there is a second deliverable in the current project phase, wherein the second deliverable is in an undelivered state after the expected delivery time;
[0064] If the estimated delivery time of the second deliverable has not been updated based on the delivery delay information, a delay reminder is sent to the responsible department of the second deliverable, and the delivery delay information is obtained from the responsible department and a review process is performed, wherein the delivery delay information is used to move the estimated delivery time of the second deliverable backwards;
[0065] If the delivery delay information is approved, the delivery progress table will be updated according to the delivery delay information;
[0066] If the delivery delay information fails to pass the review, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0067] In this embodiment, the deliverable that has not been submitted within the time limit is called the second deliverable. If the second deliverable has not been extended, the responsible department can first try to apply for an extension. If the extension is approved, the estimated submission time of the second deliverable can be moved back, and overdue coping measures can be taken to strive to complete the submission before the new estimated submission time. If the extension is not approved, it means that the current overdue coping measures need to be updated. After the new overdue coping measures are approved, the delivery progress table is updated. Through this embodiment, the delivery progress table can record effective overdue coping measures for use in new projects.
[0068] Optionally, the extended response measures include temporary response measures and long-term response measures.
[0069] Furthermore, in one embodiment, after the step of updating the delivery progress table according to the delivery delay information if the delivery delay information is approved, the step further includes:
[0070] If the estimated delivery time of the second deliverable is updated based on the delivery delay information, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0071] In this embodiment, if the second deliverable is extended, it means that the current overdue countermeasures need to be updated, and the delivery progress table is updated after the new overdue countermeasures are approved. Through this embodiment, the delivery progress table can record effective overdue countermeasures for use in new projects.
[0072] Furthermore, in one embodiment, after the step of creating the delivery progress table, the following steps are further included:
[0073] Detect whether there is a second deliverable and a third deliverable in the current project phase, wherein the second deliverable is in an unsubmitted state after the expected submission time, and the third deliverable is in an unsubmitted state within a preset time before the expected submission time;
[0074] An overdue reminder is sent to the department responsible for the second deliverable, and an upcoming reminder is sent to the department responsible for the third deliverable.
[0075] In this embodiment, the deliverables that are not submitted on time are called the second deliverables, and the deliverables that are not submitted before the due date are called the third deliverables. Overdue reminders and near-due reminders are sent to the corresponding responsible departments respectively, without the need for dedicated personnel to follow up on the issues, thereby reducing manpower consumption.
[0076] Furthermore, in one embodiment, the step of creating a delivery progress table includes:
[0077] The estimated completion time of each project phase is sent to each professional department. The departmental delivery plan is obtained from each professional department and the review process is carried out. After the review is passed, a delivery progress sheet is created based on the estimated completion time of each project phase and each departmental delivery plan. The departmental delivery plan includes the deliverables that the professional department needs to submit at each project phase and their estimated submission time.
[0078] This embodiment facilitates the rapid establishment of a delivery progress table in the early stages.
[0079] In a second aspect, an embodiment of the present application also provides a project schedule management device.
[0080] Figure 2 A schematic diagram of the functional modules of a project schedule management device in an embodiment of the present application is shown.
[0081] Reference Figure 2 In one embodiment, the project schedule management device includes:
[0082] A creation module 10 is used to create a delivery progress table, wherein the delivery progress table is used to record the estimated completion time of each project phase and the deliverables that need to be collected, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department that submits the deliverable is recorded as the responsible department of the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase;
[0083] A first detection module 20 is used to detect whether there is a first deliverable in the current project phase after obtaining the schedule advance information from the management department, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information;
[0084] The schedule compression module 30 is used to send schedule advance information to the responsible department of the first deliverable if there is a first deliverable, obtain the delivery advance information from the responsible department and execute the review process, and after the review is passed, update the delivery progress table according to the schedule advance information and the delivery advance information, otherwise update the delivery progress table according to the schedule advance information, wherein the delivery advance information is used to move the estimated submission time of the first deliverable forward.
[0085] Furthermore, in one embodiment, the delivery progress table is also used to record the achievement rate of deliverables in each project phase and the importance of each deliverable.
[0086] Furthermore, in one embodiment, the project schedule management device further includes a suggestion module, which is used to:
[0087] If the deliverable achievement rate of the current project phase is greater than or equal to the preset threshold, and all important deliverables of the current project phase are in the submitted state, a schedule advance suggestion is sent to the management department.
[0088] Furthermore, in one embodiment, the delivery progress table is also used to record the measures to be taken in case of overdue deliverables;
[0089] The project schedule management device also includes an overdue tracking module for:
[0090] Detect whether there is a second deliverable in the current project phase, wherein the second deliverable is in an undelivered state after the expected delivery time;
[0091] If the estimated delivery time of the second deliverable has not been updated based on the delivery delay information, a delay reminder is sent to the responsible department of the second deliverable, and the delivery delay information is obtained from the responsible department and a review process is performed, wherein the delivery delay information is used to move the estimated delivery time of the second deliverable backwards;
[0092] If the delivery delay information is approved, the delivery progress table will be updated according to the delivery delay information;
[0093] If the delivery delay information fails to pass the review, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0094] Furthermore, in one embodiment, the overdue tracking module is also used to:
[0095] If the estimated delivery time of the second deliverable is updated based on the delivery delay information, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0096] Furthermore, in one embodiment, the project schedule management device further includes a reminder module, which is used to:
[0097] Detect whether there is a second deliverable and a third deliverable in the current project phase, wherein the second deliverable is in an unsubmitted state after the expected submission time, and the third deliverable is in an unsubmitted state within a preset time before the expected submission time;
[0098] An overdue reminder is sent to the department responsible for the second deliverable, and an upcoming reminder is sent to the department responsible for the third deliverable.
[0099] Furthermore, in one embodiment, the creation module 10 is used to:
[0100] The estimated completion time of each project phase is sent to each professional department. The departmental delivery plan is obtained from each professional department and the review process is carried out. After the review is passed, a delivery progress sheet is created based on the estimated completion time of each project phase and each departmental delivery plan. The departmental delivery plan includes the deliverables that the professional department needs to submit at each project phase and their estimated submission time.
[0101] Among them, the functional implementation of each module in the above-mentioned project schedule management device corresponds to each step in the above-mentioned project schedule management method embodiment, and its functions and implementation processes are no longer repeated here.
[0102] In a third aspect, an embodiment of the present application provides a project schedule management device, which may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.
[0103] Figure 3 A schematic diagram of the hardware structure of a project schedule management device involved in an embodiment of the present application is shown.
[0104] Reference Figure 3In an embodiment of the present application, the project schedule management device may include a processor, a memory, a communication interface, and a communication bus. The device of the present invention calls the project schedule management program stored in the memory through the processor and performs the following operations:
[0105] Create a delivery progress sheet, which is used to record the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department submitting the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase;
[0106] After obtaining the schedule advance information from the management department, check whether there is a first deliverable in the current project phase, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information;
[0107] If there is a first deliverable, the schedule advance information is sent to the responsible department of the first deliverable, the delivery advance information is obtained from the responsible department and the review process is executed. After the review is passed, the delivery progress table is updated according to the schedule advance information and the delivery advance information, otherwise the delivery progress table is updated according to the schedule advance information, where the delivery advance information is used to move the estimated submission time of the first deliverable forward.
[0108] The device of the present invention calls the project schedule management program stored in the memory through the processor, and the delivery progress table is also used to record the achievement rate of deliverables in each project stage and the importance of each deliverable.
[0109] The device of the present invention calls the project schedule management program stored in the memory through the processor, and also performs the following operations:
[0110] If the deliverable achievement rate of the current project phase is greater than or equal to the preset threshold, and all important deliverables of the current project phase are in the submitted state, a schedule advance suggestion is sent to the management department.
[0111] The device of the present invention calls the project schedule management program stored in the memory through the processor, and the delivery progress table is also used to record the overdue coping measures of the deliverables, and the following operations are performed:
[0112] Detect whether there is a second deliverable in the current project phase, wherein the second deliverable is in an undelivered state after the expected delivery time;
[0113] If the estimated delivery time of the second deliverable has not been updated based on the delivery delay information, a delay reminder is sent to the responsible department of the second deliverable, and the delivery delay information is obtained from the responsible department and a review process is performed, wherein the delivery delay information is used to move the estimated delivery time of the second deliverable backwards;
[0114] If the delivery delay information is approved, the delivery progress table will be updated according to the delivery delay information;
[0115] If the delivery delay information fails to pass the review, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0116] The device of the present invention calls the project schedule management program stored in the memory through the processor, and also performs the following operations:
[0117] If the estimated delivery time of the second deliverable is updated based on the delivery delay information, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
[0118] The device of the present invention calls the project schedule management program stored in the memory through the processor, and also performs the following operations:
[0119] Detect whether there is a second deliverable and a third deliverable in the current project phase, wherein the second deliverable is in an unsubmitted state after the expected submission time, and the third deliverable is in an unsubmitted state within a preset time before the expected submission time;
[0120] An overdue reminder is sent to the department responsible for the second deliverable, and an upcoming reminder is sent to the department responsible for the third deliverable.
[0121] The device of the present invention calls the project schedule management program stored in the memory through the processor, and specifically performs the following operations:
[0122] The estimated completion time of each project phase is sent to each professional department. The departmental delivery plan is obtained from each professional department and the review process is carried out. After the review is passed, a delivery progress sheet is created based on the estimated completion time of each project phase and each departmental delivery plan. The departmental delivery plan includes the deliverables that the professional department needs to submit at each project phase and their estimated submission time.
[0123] The communication bus can be of any type, and is used to interconnect the processor, memory, and communication interface. The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, which are used to interconnect the devices inside the project schedule management device, and an interface used to interconnect the project schedule management device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, an optical fiber interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.
[0124] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0125] The processor may be a general-purpose processor, which may call the project schedule management program stored in the memory and execute the project schedule management method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU).
[0126] Those skilled in the art will understand that Figure 3 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0127] In a fourth aspect, an embodiment of the present application also provides a readable storage medium.
[0128] The readable storage medium of the present application stores a project schedule management program, wherein when the project schedule management program is executed by a processor, the steps of the project schedule management method as described above are implemented.
[0129] Among them, the method implemented when the project schedule management program is executed can refer to the various embodiments of the project schedule management method of the present application, and will not be repeated here.
[0130] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.
[0131] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.
[0132] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.
[0133] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.
[0134] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.
[0135] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.
[0136] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A project schedule management method, characterized in that: The project schedule management method comprises: Create a delivery progress sheet, which is used to record the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department submitting the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase; After obtaining the schedule advance information from the management department, check whether there is a first deliverable in the current project phase, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information; If there is a first deliverable, the schedule advance information is sent to the responsible department of the first deliverable, the delivery advance information is obtained from the responsible department and the review process is executed. After the review is passed, the delivery progress table is updated according to the schedule advance information and the delivery advance information, otherwise the delivery progress table is updated according to the schedule advance information, where the delivery advance information is used to move the estimated submission time of the first deliverable forward.
2. The project schedule management method according to claim 1, characterized in that: The delivery progress sheet is also used to record the deliverable achievement rate of each project phase and the importance of each deliverable.
3. The project schedule management method according to claim 2, characterized in that: After the step of creating the delivery progress table, the method further includes: If the deliverable achievement rate of the current project phase is greater than or equal to the preset threshold, and all important deliverables of the current project phase are in the submitted state, a schedule advance suggestion is sent to the management department.
4. The project schedule management method according to claim 1, characterized in that: The delivery progress sheet is also used to record the measures to be taken when deliverables are overdue; After the step of creating the delivery progress table, the method further includes: Detect whether there is a second deliverable in the current project phase, wherein the second deliverable is in an undelivered state after the expected delivery time; If the estimated delivery time of the second deliverable has not been updated based on the delivery delay information, a delay reminder is sent to the responsible department of the second deliverable, and the delivery delay information is obtained from the responsible department and a review process is performed, wherein the delivery delay information is used to move the estimated delivery time of the second deliverable backwards; If the delivery delay information is approved, the delivery progress table will be updated according to the delivery delay information; If the delivery delay information fails to pass the review, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
5. The project schedule management method according to claim 4, characterized in that: After the step of updating the delivery progress table according to the delivery delay information if the delivery delay information is approved, the method further includes: If the estimated delivery time of the second deliverable is updated based on the delivery delay information, a reminder for updated measures will be sent to the responsible department of the second deliverable, and new overdue response measures will be obtained from the responsible department and the review process will be carried out. After the review is passed, the delivery progress table will be updated according to the new overdue response measures.
6. The project schedule management method according to any one of claims 1 to 5, characterized in that: After the step of creating the delivery progress table, the method further includes: Detect whether there is a second deliverable and a third deliverable in the current project phase, wherein the second deliverable is in an unsubmitted state after the expected submission time, and the third deliverable is in an unsubmitted state within a preset time before the expected submission time; An overdue reminder is sent to the department responsible for the second deliverable, and an upcoming reminder is sent to the department responsible for the third deliverable.
7. The project schedule management method according to any one of claims 1 to 5, characterized in that: The steps of creating a delivery progress table include: The estimated completion time of each project phase is sent to each professional department. The departmental delivery plan is obtained from each professional department and the review process is carried out. After the review is passed, a delivery progress sheet is created based on the estimated completion time of each project phase and each departmental delivery plan. The departmental delivery plan includes the deliverables that the professional department needs to submit at each project phase and their estimated submission time.
8. A project schedule management device, characterized in that: The project schedule management device comprises: A creation module is used to create a delivery progress sheet, where the delivery progress sheet is used to record the estimated completion time and deliverables to be collected for each project phase, as well as the responsible department, estimated submission time and submission status of each deliverable. The professional department submitting the deliverable is recorded as the responsible department for the deliverable, and the estimated submission time of the deliverable is before the estimated completion time of the corresponding project phase; A first detection module is used to detect whether there is a first deliverable in the current project phase after obtaining the schedule advance information from the management department, wherein the schedule advance information is used to move the estimated completion time of the current project phase forward, the first deliverable is in an unsubmitted state, and the estimated submission time is after the new estimated completion time corresponding to the schedule advance information; The schedule compression module is used to send schedule advance information to the responsible department of the first deliverable if there is a first deliverable, obtain the delivery advance information from the responsible department and execute the review process. After the review is passed, the delivery progress table is updated according to the schedule advance information and the delivery advance information, otherwise the delivery progress table is updated according to the schedule advance information, wherein the delivery advance information is used to move the estimated submission time of the first deliverable forward.
9. A project schedule management device, characterized in that: The project schedule management device includes a processor, a memory, and a project schedule management program stored in the memory and executable by the processor, wherein when the project schedule management program is executed by the processor, the steps of the project schedule management method according to any one of claims 1 to 7 are implemented.
10. A readable storage medium, characterized in that: The readable storage medium stores a project schedule management program, wherein when the project schedule management program is executed by a processor, the steps of the project schedule management method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Method, device and system for confirming project progress and computer-readable storage medium
CN108537462A
Delivery structured management method based on scheduled task progress
CN117745208A
Planning operation management support system, and planning operation management support program
CN1674025A
Method and device for planning input program of part to be processed
JP1992030954A
System and Method for Updating Real-Time Project Status Based on Deliverable Status
US20220004993A1
