CN117114594A - Project change management method and system - Google Patents

Project change management method and system Download PDF

Info

Publication number
CN117114594A
CN117114594A CN202310826004.4A CN202310826004A CN117114594A CN 117114594 A CN117114594 A CN 117114594A CN 202310826004 A CN202310826004 A CN 202310826004A CN 117114594 A CN117114594 A CN 117114594A
Authority
CN
China
Prior art keywords
project
change
proposal
item
approver
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310826004.4A
Other languages
Chinese (zh)
Inventor
李栋梁
蒋文超
吴键
刘晓雨
闫俊伊
李楚楚
王功齐
周桐
孙仲毅
朱烨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huaneng Shandong Power Generation Co Ltd
Huaneng Information Technology Co Ltd
Shandong Rizhao Power Generation Co Ltd
Original Assignee
Huaneng Shandong Power Generation Co Ltd
Huaneng Information Technology Co Ltd
Shandong Rizhao Power Generation Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huaneng Shandong Power Generation Co Ltd, Huaneng Information Technology Co Ltd, Shandong Rizhao Power Generation Co Ltd filed Critical Huaneng Shandong Power Generation Co Ltd
Priority to CN202310826004.4A priority Critical patent/CN117114594A/en
Publication of CN117114594A publication Critical patent/CN117114594A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00—Machine learning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Marketing (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Artificial Intelligence (AREA)
  • Computing Systems (AREA)
  • Educational Administration (AREA)
  • Mathematical Physics (AREA)
  • Computer Hardware Design (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application relates to the technical field of enterprise management, and discloses a project change management method and system, wherein the project change management method comprises the following steps: carrying out change prediction on the project to be managed to obtain a prediction result; determining a project change category based on the project actual demand; providing a project change proposal writing direction based on the determined change project category so as to change the applicant writing the project change proposal; acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and a prediction result, and selecting a prediction result with the maximum relevance as a comparison group; transmitting the project change proposal and the comparison group to a project approver so that the project approver can make approval results on the project change proposal; and processing the project change based on the project approver approval result. The project change is predicted, approved and saved, so that the project change content can be rapidly and efficiently checked, the influence of the change is analyzed, the project decision is assisted, and the project management efficiency is improved.

Description

Project change management method and system
Technical Field
The application relates to the technical field of enterprise management, in particular to a project change management method and system.
Background
Item rules clearly define item scope. However, as work proceeds, changes may need to be made to the project scope, i.e., project changes are made. In the process of testing software items, particularly in the Internet field, the problem of demand change exists in the process of testing software items, whether the process of testing software items is earlier or later, and once the software item testing demands are changed and modified, the corresponding item testing demands in the process of testing are correspondingly changed. Since the current requirement change of most companies only needs to be notified orally or in mails, no record after internal review and related requirement change is made, so that some requirements of the products to be subsequently delivered are increased, and some are not increased. This results in incomplete information from the test and difficult maintenance of the subsequent product.
In actual software projects, project alterations are often unavoidable. Therefore, on the one hand, the project manager needs to accurately predict the influence of the change when the project change occurs, in order to take measures against the change. On the other hand, on the level of the project, the project manager needs to predict the impact of project changes on the whole project early in the project to determine the time and cost required for the project development process.
A common approach to cope with demand changes at present is expert estimation. When the request for changing the demand is submitted, the expert estimates the possible influence of the change of the demand according to the knowledge of the expert about the project and the past experience. But this method is highly subjective. On the one hand, the degree of knowledge of the project by the expert and the richness of the personal experience affect the accuracy of the estimation, so that the estimation results given by different experts may be quite different even if facing the same situation. On the other hand, as the scale of software increases and the complexity of software increases, even experienced professionals may not be able to take into account all aspects affected by project changes, and so the conclusions drawn may be highly misleading.
Disclosure of Invention
The application provides a project change management method and system, which are used for predicting, approving and storing project changes, and can be used for rapidly and efficiently checking project change contents, analyzing change influences, assisting project decision and improving project management efficiency.
In order to achieve the above object, the present application provides the following solutions: the application provides a project change management method, which comprises the following steps: step S1, carrying out change prediction on items to be managed to obtain a prediction result; step S2, determining a project change category based on the project actual demand; step S3, providing a project change proposal writing direction based on the determined change project category so as to change the project change proposal written by the applicant; step S4, acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and the predicted result, and selecting the predicted result with the highest relevance as a comparison group; step S5, the project change proposal and the comparison group are sent to a project approver so that the project approver can make approval results on the project change proposal;
and S6, processing the project change based on the project approver approval result.
In one embodiment, in step S1, performing change prediction on an item to be managed to obtain a prediction result, including: determining the type of the item to be managed, and determining the catalog of the item to be managed based on the type of the item to be managed; acquiring historical sample data based on item types and item catalogs, wherein the historical sample data is the item change history of similar items, and extracting features of the historical sample data; establishing a project change prediction model based on project characteristic data; and acquiring characteristic data of the project to be managed, inputting the characteristic data of the project to be managed into a project change prediction model, and outputting a prediction result.
In one embodiment, the project characteristic data includes a change term of the sub-project, a number of change terms, a cause of a change term change order, a project progress at the time of change of the change term, and a degree of change of the change term.
In one embodiment, building a project change prediction model based on project characteristic data includes: establishing an initial prediction model according to the project characteristic data; dividing the project characteristic data into training data and verification data according to preset conditions; training the initial predictive model based on the training data; and testing the trained initial prediction model based on the verification data, and outputting the project change prediction model conforming to a preset index.
In one embodiment, after the project change proposal and the comparison group are sent to the project approver, the project approver is prompted to read, and if the project approver does not read the project change proposal and the comparison group within a preset time, reminding service is carried out on the project approver; the reminding service comprises a voice reminding, a short message reminding, a mailbox reminding and a telephone reminding.
In one embodiment, the predicted feedback time of the approval result is displayed in real time after the project change proposal and the comparison group are sent to the project approver.
In one embodiment, the project change proposal writing direction includes a catalog to which the project change belongs, a project change content, a project change reason, a project progress, a project workload, and a project influence scope.
In one embodiment, the project change category includes a change in project implementation scope, a change in technical content, and a change in implementation content; the approval result comprises an approval project change suggestion, an agreement project change suggestion proposal modification and a rejection project change suggestion.
In one embodiment, the project change proposal, the comparison set and the approval result are transmitted in encrypted form.
In order to achieve the above object, the present application provides a project change management system, which is characterized in that the project change management system is disposed on an enterprise server, and each department personnel in the enterprise accesses the project change management system through a local area network;
the project change management system includes: the applicant module is used for logging in the applicant and downloading the project change proposal template from the applicant module for writing, and uploading the written project change proposal to the applicant module; the approver module is used for logging in by the approver and analyzing and processing the project change proposal based on the project change proposal and the comparison group between the approvers to make an approval result; the information processing module is used for carrying out change prediction on the project to be managed and obtaining a prediction result; the method comprises the steps of determining a project change category based on the actual requirements of the project; acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and a prediction result, and selecting a prediction result with the maximum relevance as a comparison group; and the database is used for storing project change proposal, prediction results and historical sample data.
The application has the technical effects that: automatically predicting possible project change results, carrying out relevance analysis on the project change proposal and the prediction results, and selecting the prediction result with the highest relevance as a comparison group; the project change proposal and the comparison group are sent to a project approver so that the project approver can make approval results on the project change proposal. The problems of instability and inaccuracy caused by the traditional subjective estimation method are solved to the maximum extent through the prediction result, and good decision support is provided for project approvers.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions of the prior art, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a project change management method provided by an embodiment of the present application;
fig. 2 is a schematic diagram of an item change management system according to an embodiment of the present application.
Detailed Description
The following describes in further detail the embodiments of the present application with reference to the drawings and examples. The following examples are illustrative of the application and are not intended to limit the scope of the application.
In the description of the present application, it should be understood that the terms "center," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate orientations or positional relationships based on the orientation or positional relationships shown in the drawings, merely to facilitate describing the present application and simplify the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and thus should not be construed as limiting the present application.
The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.
In the description of the present application, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be either fixedly connected, detachably connected, or integrally connected, for example; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present application will be understood in specific cases by those of ordinary skill in the art.
With the continuous expansion of modern company scale and continuous extension of office sites, the project management systems used in the present companies are not satisfactory. The impediment to scattered management and reuse of corporate resources results in a failure of smooth execution and efficient management of corporate business and technology accumulation. The project management system of the company is urgently required to be upgraded and improved, and the internal management capacity and management level of the project of the company are improved.
As shown in fig. 1, this embodiment discloses a project change management method, which includes: step S1, carrying out change prediction on items to be managed to obtain a prediction result; step S2, determining a project change category based on the project actual demand; step S3, providing a project change proposal writing direction based on the determined change project category so as to change the project change proposal written by the applicant; step S4, acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and the predicted result, and selecting the predicted result with the highest relevance as a comparison group; step S5, the project change proposal and the comparison group are sent to a project approver so that the project approver can make approval results on the project change proposal; and S6, processing the project change based on the project approver approval result.
It can be appreciated that in the above embodiment, by predicting the project change in advance, it is convenient for the project approver to make an approval result for the project change proposal. Project change is predicted, approved and stored, project change content can be rapidly and efficiently checked, change influence is analyzed, project decision is assisted, and project management efficiency is improved. The predicted results include project change category, project characteristic data, approval results, and the like.
In step S3, the change applicant proposes a change content and records the change content into the project change proposal; in step S5, after receiving the project change suggestion, the project approver a organizes related personnel to analyze and initially review the change content, evaluates the influence of the change content on the project progress, the project cost, the project quality and the like, and proposes a processing suggestion according to the influence; project approver B proposes a change treatment scheme according to the treatment proposal, and organizes technical groups to carry out technical influence evaluation so as to form a change application form and submit project approver C; the project approver C approves and confirms the change application form according to the processing proposal, the change processing proposal and the influence evaluation condition; and the project approver D feeds back the approval result to the change applicant according to the approval result.
In one embodiment, in step S1, performing change prediction on an item to be managed to obtain a prediction result, including: determining the type of the item to be managed, and determining the catalog of the item to be managed based on the type of the item to be managed; acquiring historical sample data based on item types and item catalogs, wherein the historical sample data is the item change history of similar items, and extracting features of the historical sample data; establishing a project change prediction model based on project characteristic data; and acquiring characteristic data of the project to be managed, inputting the characteristic data of the project to be managed into a project change prediction model, and outputting a prediction result.
It can be understood that in the above embodiment, the project to be managed is changed and predicted by the project change prediction model, so as to obtain the prediction result, and improve the accuracy of the prediction result.
In one embodiment, the project characteristic data includes a change term of the sub-project, a number of change terms, a cause of a change term change order, a project progress at the time of change of the change term, and a degree of change of the change term.
It may be understood that in the above embodiment, the project change prediction model is established based on the project feature data, where the project feature data is an influence factor that affects the prediction result, and the influence factor refers to an influence factor that affects the prediction result, and the change item of the sub project, the number of change items, the number of times of change items, the reason of the change item change order, the project progress when the change item is changed, and the change degree of the change item are all influence factors that affect the prediction result.
It should be noted that other factors that may affect the prediction result may be item feature data, and the item feature data in the embodiment is only a specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that may be easily contemplated by those skilled in the art within the scope of the present application should be covered by the scope of the present application.
In one embodiment, building a project change prediction model based on project characteristic data includes: establishing an initial prediction model according to the project characteristic data; dividing the project characteristic data into training data and verification data according to preset conditions; training the initial predictive model based on the training data; and testing the trained initial prediction model based on the verification data, and outputting the project change prediction model conforming to a preset index.
It can be understood that in the above embodiment, the preset condition may be 60% of the project characteristic data of the training data, 40% of the project characteristic data of the verification data, and the preset condition is determined according to the actual requirement.
Specifically, an initial prediction model can be established according to the project characteristic data; dividing the project characteristic data into training data and verification data according to preset conditions; training the initial predictive model with 60% project characteristic data; and testing the trained initial prediction model by using the residual 40% project characteristic data, and outputting the project change prediction model conforming to a preset index. The preset index is the index number of the predicted result meeting the predicted requirement, and the predicted requirement can be that the accuracy of the predicted result is 90% or more.
In one embodiment, after the project change proposal and the comparison group are sent to the project approver, the project approver is prompted to read, and if the project approver does not read the project change proposal and the comparison group within a preset time, reminding service is carried out on the project approver; the reminding service comprises a voice reminding, a short message reminding, a mailbox reminding and a telephone reminding.
It can be appreciated that in the above embodiment, the approver is enabled to approve as soon as possible through the reminding service, so as to improve the project change management efficiency.
In one embodiment, the predicted feedback time of the approval result is displayed in real time after the project change proposal and the comparison group are sent to the project approver.
It can be understood that in the above embodiment, by displaying the predicted feedback time of the approval result in real time, the approver can approve as soon as possible, so that the approver is prevented from forgetting to approve, and the project change management efficiency is improved.
In one embodiment, the project change proposal writing direction includes a catalog to which the project change belongs, a project change content, a project change reason, a project progress, a project workload, and a project influence scope.
It will be appreciated that in the above embodiments, in order to avoid significant impact on the item, aspects such as the catalog to which the item change belongs, the content of the item change, the reason for the item change, the progress of the item, the workload of the item, and the scope of impact of the item are described in the change application form.
In one embodiment, the project change category includes a change in project implementation scope, a change in technical content, and a change in implementation content; the approval result comprises an approval project change suggestion, an agreement project change suggestion proposal modification and a rejection project change suggestion.
It should be understood that in the above embodiment, the project change category includes a change of a project implementation scope, a change of a technical content, and a change of an implementation content, and project change proposal templates corresponding to different project change categories are different.
In one embodiment, the project change proposal, the comparison set and the approval result are transmitted in encrypted form.
It can be understood that in the above embodiment, the encrypted transmission avoids information leakage.
As shown in fig. 2, this embodiment further provides a project change management system, which is characterized in that the project change management system is disposed on an enterprise server, and each department personnel in the enterprise accesses the project change management system through a local area network;
the project change management system includes: the applicant module is used for logging in the applicant and downloading the project change proposal template from the applicant module for writing, and uploading the written project change proposal to the applicant module; the approver module is used for logging in by the approver and analyzing and processing the project change proposal based on the project change proposal and the comparison group between the approvers to make an approval result; the information processing module is used for carrying out change prediction on the project to be managed and obtaining a prediction result; the method comprises the steps of determining a project change category based on the actual requirements of the project; acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and a prediction result, and selecting a prediction result with the maximum relevance as a comparison group; and the database is used for storing project change proposal, prediction results and historical sample data.
It may be understood that in the above embodiment, the applicant module, the approver module, the information processing module, and the database are interconnected, so that personnel in each department of the enterprise access the project change management system through the local area network to implement project change management.
It should be understood that, although the steps in the flowcharts of the embodiments of the present application are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in various embodiments may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor do the order in which the sub-steps or stages are performed need to be sequential, but may be performed in rotation or alternating with at least a portion of the sub-steps or stages of other steps or steps.
Those of ordinary skill in the art will appreciate that: the above is only a preferred embodiment of the present application, and the present application is not limited thereto, but it is to be understood that the present application is described in detail with reference to the foregoing embodiments, and modifications and equivalents of some of the technical features described in the foregoing embodiments may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (10)

1. A method for managing a change in a project, comprising:
step S1, carrying out change prediction on items to be managed to obtain a prediction result;
step S2, determining a project change category based on the project actual demand;
step S3, providing a project change proposal writing direction based on the determined change project category so as to change the project change proposal written by the applicant;
step S4, acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and the predicted result, and selecting the predicted result with the highest relevance as a comparison group;
step S5, the project change proposal and the comparison group are sent to a project approver so that the project approver can make approval results on the project change proposal;
and S6, processing the project change based on the project approver approval result.
2. The method according to claim 1, wherein in step S1, the project to be managed is subjected to change prediction to obtain a prediction result, comprising:
determining the type of the item to be managed, and determining the catalog of the item to be managed based on the type of the item to be managed;
acquiring historical sample data based on item types and item catalogs, wherein the historical sample data is the item change history of similar items, and extracting features of the historical sample data;
establishing a project change prediction model based on project characteristic data;
and acquiring characteristic data of the project to be managed, inputting the characteristic data of the project to be managed into a project change prediction model, and outputting a prediction result.
3. The method according to claim 2, wherein the item feature data includes a change item of the sub item, the number of change items, the cause of change item change order, the item progress at the time of change of the change item, and the degree of change of the change item.
4. The method of claim 2, wherein creating a project change prediction model based on project characteristic data comprises:
establishing an initial prediction model according to the project characteristic data;
dividing the project characteristic data into training data and verification data according to preset conditions;
training the initial predictive model based on the training data;
and testing the trained initial prediction model based on the verification data, and outputting the project change prediction model conforming to a preset index.
5. The method according to claim 1, wherein after the project change proposal and the comparison group are sent to the project approver, the project approver is prompted to read, and if the project approver does not read the project change proposal and the comparison group within a preset time, a reminding service is performed to the project approver; the reminding service comprises a voice reminding, a short message reminding, a mailbox reminding and a telephone reminding.
6. The method of claim 1, wherein the predicted feedback time of the approval result is displayed in real time after the project change proposal and the comparison group are transmitted to the project approver.
7. The method of claim 1, wherein the project change proposal composition direction includes a catalog to which the project change belongs, a project change content, a project change reason, a project progress, a project workload, and a project influence range.
8. The item change management method according to claim 1, wherein the item change category includes a change in an item execution range, a change in technical content, and a change in execution content; the approval result comprises an approval project change suggestion, an agreement project change suggestion proposal modification and a rejection project change suggestion.
9. The method of claim 1, wherein the project change proposal, the comparison set, and the approval result are transmitted encrypted at the time of transmission.
10. The project change management system is characterized by being arranged on an enterprise server, and staff in each department in the enterprise access to the project change management system through a local area network;
the project change management system includes:
the applicant module is used for logging in the applicant and downloading the project change proposal template from the applicant module for writing, and uploading the written project change proposal to the applicant module;
the approver module is used for logging in by the approver and analyzing and processing the project change proposal based on the project change proposal and the comparison group between the approvers to make an approval result;
the information processing module is used for carrying out change prediction on the project to be managed and obtaining a prediction result; the method comprises the steps of determining a project change category based on the actual requirements of the project; acquiring a project change proposal provided by a change applicant, carrying out relevance analysis on the project change proposal and a prediction result, and selecting a prediction result with the maximum relevance as a comparison group;
and the database is used for storing project change proposal, prediction results and historical sample data.
CN202310826004.4A 2023-07-06 2023-07-06 Project change management method and system Pending CN117114594A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310826004.4A CN117114594A (en) 2023-07-06 2023-07-06 Project change management method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310826004.4A CN117114594A (en) 2023-07-06 2023-07-06 Project change management method and system

Publications (1)

Publication Number Publication Date
CN117114594A true CN117114594A (en) 2023-11-24

Family

ID=88800947

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310826004.4A Pending CN117114594A (en) 2023-07-06 2023-07-06 Project change management method and system

Country Status (1)

Country Link
CN (1) CN117114594A (en)

Similar Documents

Publication Publication Date Title
Shah Ali Cost decision making in building maintenance practice in Malaysia
US8027903B2 (en) Technology portfolio health assessment system and method
US20060004596A1 (en) Business process outsourcing
US20030069659A1 (en) Product development management system, product development management method, product reliability decision system and product reliability decision method
US20150081396A1 (en) System and method for optimizing business performance with automated social discovery
Exner et al. Proactive maintenance as success factor for use-oriented Product-Service Systems
JP2008542860A (en) System and method for risk assessment and presentation
US11699113B1 (en) Systems and methods for digital analysis, test, and improvement of customer experience
JP2002236736A (en) Method, device and system for supporting group management of building or the like and computer program storage medium
US20030055697A1 (en) Systems and methods to facilitate migration of a process via a process migration template
CN111768207A (en) Cognitive purchasing
KR102489119B1 (en) Smart FMEA system and process management system and method using thereof
Gu et al. Mission reliability-oriented integrated scheduling optimization model by combining production planning and maintenance activities
KR101944062B1 (en) Platform and method for automatically configuring ipo teams
CN116993116B (en) Distribution method and equipment for outsourcing human resources
JP2019175273A (en) Quality evaluation method and quality evaluation
US20040215618A1 (en) Automated quality compliance system
Pratiwi et al. Analysis of capability level in dealing with IT business transformation competition using cobit framework 5 (case study at Airasia Indonesia)
CN117114594A (en) Project change management method and system
US20120209644A1 (en) Computer-implemented system and method for facilitating creation of business plans and reports
US20070156480A1 (en) Commitment-process project-management methods and systems
US7684993B2 (en) Value diagnostic tool
JP2020004161A (en) Examination support apparatus, examination support method, and service providing method
KR100428070B1 (en) System and method for checking operation state of information system and media for storing program source thereof
Kurilenko et al. Virtual Employee Implementation Using Temporal Case-based Reasoning

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination