JP2006126898A - Project management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for managing progress of a project for objectively proposing proper measures for making up delay for occurrence of operation delay to a project manager. <P>SOLUTION: The occurrence of operation delay is decided from the progress status of each of sub-divided operations according to predetermined conditions, and when the delay is occurred, the information of the statuses or skills of current development personnel, the statuses or skills of preliminary development personnel or the progress circumstances, difficulty and budgets of a whole project or each of the sub-divided operations is integrally determined, and measures for properly making up the delay is proposed to a project manager or the like. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a system for managing the progress of a project, and more particularly to a project management system for grasping the progress of work and avoiding the occurrence or deterioration of delay.

  As a conventional system for managing the progress of a project, a system for performing progress management by quantifying the skill of each person, the importance of each work, the added value of work, and the like is known. For example, Patent Document 1 discloses a technique that increases the estimation accuracy of a work schedule of a project by paying attention to a product created in the course of the project and obtaining the creation man-hour for each product. As the contents of the deliverables are finalized as the development progresses, the man-hours necessary to create the deliverables are sequentially reviewed based on the confirmed contents, and the results are reflected in the project plan, and the project work schedule It is said that the estimation accuracy for can be further improved. In addition, the mechanism for constantly grasping the progress status of each process enables the progress status of related work to be quickly and accurately grasped. For example, it is possible to grasp at a glance whether there is a test waiting and the degree of the waiting time before entering the test process. As a result, it is easy to take work delay countermeasures and perform work progress considering cooperation with the next process. In addition, when planning a project, for tasks that are likely to change the person in charge later, work is assigned on a group basis, and for tasks that are unlikely to change the person in charge, on a worker basis. By assigning the work, it is possible to flexibly cope with a change in the situation such as a change in estimation of man-hours and a delay in work. As a result, it is said that accurate process management is possible based on a highly accurate project plan.

  Patent Document 2 displays the planned development value and actual value so that they can be compared and contrasted by inputting the planned development value before starting the project and then entering the actual value according to the actual development progress. Thus, a technique for grasping the progress is disclosed. As a result, the person in charge can detect that an abnormality has occurred in the progress of the work related to his / her work, and can take a countermeasure immediately. In addition, when one person is in charge of multiple tasks, it is possible to determine which task should be focused on by grasping the progress of each task and each related task. It is supposed to be possible.

JP-A-8-202773. JP-A-7-114466.

  The technology disclosed in Patent Document 1 focuses on the product created in the course of the project and estimates the work schedule of the project by sequentially reviewing the man-hours of the product based on the contents of the confirmed product. It is intended to improve accuracy, and it is said that a mechanism for grasping the progress status of each process can cope with work delay countermeasures and synchronize with other linked work. However, as specific work delay measures, prior measures such as preventing delays by instructing project managers to give priority work are the main measures. If a delay actually occurs, a warning is issued. However, there is no guideline on what kind of measures should be taken in order to recover the work that has been delayed.

  The technique disclosed in Patent Document 2 detects that an abnormality has occurred in the progress of work at an early stage and takes measures against it. It is not clear what to do. Conventionally, when project managers take measures such as reassigning personnel as countermeasures for work delays, project managers depend on uncertain factors such as manager's "experience" and "intuition". There was no way to ensure that he was objectively taking appropriate measures.

  The present invention has been made in view of such circumstances, and is a system for managing the progress of a project. When a work delay occurs, the project manager is objectively requested for delay recovery. It is intended to provide a system that can propose appropriate measures.

  As a result of earnest research in view of the above-mentioned problem, the present inventor determines the occurrence of delay according to a predetermined condition from the progress status of each subdivided work, and if a delay occurs, Measures for appropriate delay recovery by comprehensively judging information such as status and skills, status and skills of spare development personnel, the entire project and the progress status of each subdivided work, difficulty level, budget, etc. I came up with the idea of building a system that was proposed to project managers. In this system, the status, skills, performance, etc. of the development personnel, as well as the progress of the project and work, the difficulty level, the budget, etc. are expressed as objective indicators (numerical values, etc.) and stored in the database. It is possible to objectively determine what measures are appropriate for delay recovery.

  The present invention provides a development personnel information database that holds information relating to the development ability and schedule of development personnel, a project information database that holds information relating to the development scale, development schedule, and progress of a project to be developed, and the project information database. Referring to the project information database for delay determination means for determining the occurrence of delay in project development based on the development scale, development schedule and progress of the project, To calculate the amount of work required to make up the delay from the development scale, development schedule and progress of the project, and to make up for the delay from the development ability and schedule of the development personnel by referring to the development personnel information database A project management system including a measure determining means for determining a measure suitable for processing a required amount of work, and a measure suggesting means for presenting the determined measure to a user. It is an object of the present invention to provide a project management system characterized by including at least one of instructing development staff to overtime, adding spare development personnel, and instructing priority work.

  In the project management system of the present invention, the development personnel information database further holds information relating to the cost of development personnel, and the project information database further retains information relating to a project budget, and the measure determination means Calculates the cost increase due to overtime instructions or the addition of spare development personnel and is suitable for delayed recovery on the condition that the project budget is not exceeded due to the increase in costs. It is characterized in that it is determined as a countermeasure.

  In the project management system of the present invention, the project information database further holds information indicating a relationship between the operations included in the project development, and the countermeasure determination means The work causing the delay is determined based on the information indicating the relationship, and the delay is performed by preferentially performing the work based on the development schedule and progress of the project and the development ability of the development personnel. When it is predicted that the amount of work necessary for recovery can be processed, it is determined that it is a suitable measure to instruct the work as a priority work.

  In the project management system of the present invention, the project information database further holds information on a development scale, a development schedule, and a progress status for each module creation work included in the development of the project, and the delay determination unit includes: The occurrence of delay is determined for each module creation work, and the measure determination means refers to the project information database for the module creation work in which the delay has occurred, and determines the development scale, development schedule, and progress of the module creation work. Calculate the amount of work necessary to make up for the delay, and refer to the development personnel information database, suitable for processing the amount of work necessary to make up for the delay from the development personnel's development ability and schedule It is characterized by determining the countermeasures.

  In the project management system of the present invention, the project information database further holds information on the complexity of each module, and the measure determining means is for making up for the delay in module creation work in which a delay has occurred. In calculating the required work amount, the calculation is performed in consideration of the complexity of the module.

  The project management system according to the present invention further includes means for determining the complexity of the module according to a function point method.

  In the project management system of the present invention, the measure determination means calculates the work amount necessary for the delay recovery in consideration of the degree of understanding of the work of the development personnel.

  In the project management system of the present invention, the development personnel information held in the development personnel information database includes development language, development efficiency, skill level according to a predetermined standard, bug rate, bug countermeasure man-hour ratio, etc. It is characterized by being. In addition, the information on the schedule of the development personnel held in the development personnel information database includes the work currently in charge, the planned development start date and planned development end date of the work, the progress status of the work, etc. It is characterized by that.

  In the project management system of the present invention, when the countermeasure determining means determines that there is no countermeasure suitable for processing the amount of work necessary to make up for the delay for the project in which the delay has occurred, The countermeasure suggesting means presents a predetermined warning to the user.

  The present invention also provides, as a program for realizing the above-described project management system on a computer, a development personnel information database that holds information on development capabilities and schedules of development personnel, and the development scale and development of a project to be developed. A program for managing project development with reference to a project information database that holds information on schedule and progress, and based on the development scale, development schedule, and progress of the project with reference to the project information database The delay determination step for determining the occurrence of delay in project development, and the project in which the delay has occurred, with reference to the project information database, the development scale, development schedule, and progress of the project The delay recovery work amount calculation step for calculating the amount of work necessary for recovering the delay, and the development personnel information database, with reference to the development personnel information database, are necessary for recovering the delay from the development capability and schedule of the development personnel. A countermeasure determining step for determining a countermeasure suitable for processing the amount of work, and a countermeasure proposing step for presenting the determined countermeasure to the user, wherein the countermeasure is directed to the development staff of the project And providing a program characterized by including at least one of adding spare development personnel and instructing priority work.

  As described above, according to the project management system of the present invention, when work delay occurs, it is possible to propose an appropriate countermeasure objectively for delay recovery to the project manager. . This improves project management efficiency.

  The best mode for carrying out the project management system of the present invention will be described below in detail with reference to the accompanying drawings. 1 to 20 are diagrams illustrating embodiments of the present invention. In these drawings, the same reference numerals denote the same components, and the basic configuration and operation are the same. To do.

Configuration of Project Management System FIG. 1 is a functional block diagram schematically showing the overall configuration of the project management system of this embodiment. In FIG. 1, the project management system includes a user terminal 101 of an employee who is a project manager or a development worker, an employee basic information DB 102 including basic information such as an employee's name and affiliation, and information on the skill level of each employee. Employee skill information DB 103 including, employee schedule information DB 104 including information on the period of work currently in progress, current work status, and attendance status for each employee, project name, person in charge, work content, budget, progress The project DB 105 including information related to the employee, the employee basic information DB 102, the employee skill information DB 103, the employee information registration unit 110 for registering predetermined information in the employee schedule information DB 104, and employees who meet predetermined conditions from various databases 102 to 105 Employee search unit 111 that searches for A delay countermeasure processing unit 112 that proposes personnel to be invested to make up for delays in work, a progress processing unit 113 that obtains the progress of development work from the project DB 105 and presents it to the user, and a module that records development results A development result registration unit 114 that registers in the project DB 105 in units or projects, a project registration unit 115 that registers information about the project and information about modules created in the project in the project DB 105, and a module complexity that determines module complexity And a thickness determination processing unit 116.

  FIG. 2 is a diagram illustrating a data configuration of the employee basic information table included in the employee basic information DB 102. The basic employee information table includes an employee number for identifying an employee, a name, an e-mail address as a contact information, a department to which the employee belongs, wage (hourly wage), and the like.

FIG. 3 is a diagram illustrating a data configuration of an employee skill information table included in the employee skill information DB 103. The employee skill information table includes a skill level and an average development ability per unit time for each employee. Skill level is an objective index that has been digitized shows the development skills of employees, here ITSS that the Ministry of Economy, Trade and Industry was established is: the skill level of the 7 stage due to the (S kill S tandards for IT professional IT Skill Standards) Adopted. In addition, objective indicators of the average development ability of employees per hour include development language, development efficiency, bug countermeasure man-hour ratio (ratio of man-hours for bug countermeasures out of all man-hours required for development), bug rate ( The average number of bugs that occur during 1000 steps) is adopted.

  FIG. 4 is a diagram illustrating a data configuration of an employee schedule information table included in the employee schedule information DB 104. The employee schedule information table includes the contents of work that each employee is currently engaged in, and information such as the schedule and work status. Note that the current work status may include only statuses such as during work, completed, and not started. As shown in FIG. 4, when the progress status is displayed as a percentage, the calculation is performed using progress rate data in a module creation progress status table, which will be described later.

FIG. 5 is a diagram illustrating a data configuration of a project management table included in the project DB 105. The project management table includes basic information about the project such as project name, development language, development scale, man-hours, budget, and employee number of the person in charge for each project. Although not shown in the figure, the project management table includes information on the order relationship between each work process in the project development work. This information may include, for example, PERT (P rogram E valuation and R eview T echnique) is information based on such.

  FIG. 6 is a diagram illustrating a data configuration of a module information table included in the project DB 105. The module information table includes information about modules created in each project. In particular, the present project management system is characterized in that the module information table includes “complexity” indicating numerically the difficulty level of each module creation. Similarly to the above-described project management table, it includes information on the order relationship between the respective work steps in the module creation work.

  FIG. 7 is a diagram illustrating a data configuration of a module creation progress status table included in the project DB 105. The project progress table includes the planned development schedule and actual development progress for each module. Further, a delay flag indicating that a work delay has occurred and information on the cause of the delay are included. For example, a delay flag can be turned on for a module whose development has not yet been completed even though the planned development end date has passed.

  FIG. 8 is a diagram illustrating a data configuration of a delay cause table included in the project DB 105. The delay cause table includes the cause of work delay occurrence and the countermeasure time. The countermeasure time preferably includes the estimated value and the actual value. In this case, for the actual value of the countermeasure time, the time taken after the countermeasure is actually taken is input, and when there are a plurality of inputs, the average value may be held.

  The data configurations of the tables shown in FIGS. 2 to 8 are merely examples, and those obtained by normalization and configuration changes as necessary may be used.

Operation of Project Management System FIG. 9 is a flowchart showing an overall processing flow when performing development work using the project management system of the present embodiment. In FIG. 9, first, the project manager or the person in charge of development registers, with the project registration unit 115, information related to the development project and modules created in the project in the project management table and module information table of the project DB 105 (step 901). Further, the person in charge of development and the development schedule are registered in the module creation progress table for each module (step 902). Further, when registering a module, the module complexity determination processing unit 116 determines the complexity of each module and registers the result in the module information table (step 903).

  Here, a method for determining the complexity of the module will be described. In the project management system of the present embodiment, the module complexity determination processing unit 116 determines the module complexity by the function point method. First, data constituting a module is classified into five data types of internal logical file, external interface file, external input, external output, and external inquiry, and the number of each is counted in advance. For external input, external output, and external inquiry, weighting is performed based on the number of external reference files and the number of items (number of data elements). For internal logical files and external interface files, the number is based on the number of record types and the number of items. Perform weighting. The weighting is quantified for each data type (weighting coefficient). An example of weighting is shown in FIG. For each of the five types of data constituting the module, the total value obtained by multiplying the number of the data and the weighting coefficient is defined as a coarse function point. On the other hand, a correction coefficient is obtained based on the system characteristics of the module. FIG. 11 shows an example of system characteristic items that are the basis for calculating the correction coefficient. A function point is obtained by multiplying the coarse function point by the correction coefficient. This function point is output to the project registration unit 115 as the complexity of the module. An example of calculating the complexity of the module by the method described above is shown in FIG.

  Subsequently, when the development work is started, the project manager or the person in charge of development registers the result of the product of the development work in the module creation progress status table of the project DB 105 by the development result registration unit 114 (step 904). . The data input as the development performance is a numerical value such as a man-hour and a progress rate, for example. Further, the development record registration unit 114 predicts the development end date of the module based on the input record data, and writes it in the module creation progress status table.

  In order to predict the development end date of the module from the input development results data, the future development will take into account the degree of understanding of the developer's work (hereinafter abbreviated as “degree of understanding” for simplicity). Predict the progress of work. Usually, when an inexperienced work is performed, it takes time to understand the experience and get used to it (the degree of understanding increases). However, the degree of comprehension gradually increases with experience and familiarity, and the amount of deliverables increases and the working time decreases. FIG. 13 and FIG. 14 are graphs showing the transition of the degree of understanding of such general developer work.

In FIG. 13, the product creation amount at the completion of the work is V _F (which can be expressed by development scale [KS]), γ is a constant (a constant determined from past results), and time is t (currently). The growth curve V _t is expressed by the following equation.

  In FIG. 14, a growth rate curve depicting a growth rate that is a measure of the growth rate related to understanding of work is expressed by the following equation obtained by differentiating equation (1) with respect to time t.

According to Equation (2), the value of V _t + V _Δt = V _{t + Δt} that serves as an index for predicting the amount of future product creation is the product creation amount V _t at an arbitrary time _t, and the work It can be seen that the product creation amount V _F at completion and the difference V _F −V _t between the product creation amounts V _{t at} an arbitrary time t are inversely proportional to the work completion V _F.

  When the module creation progress status table in the project DB 105 is updated by inputting the development result data, the progress status processing unit 113 compares the planned development end date, the expected development end date, and the progress rate for the updated module. The progress is determined (step 905). Here, if the development work has not been completed even though the current development end date has passed, or if the expected development end date is later than the planned end date, etc. Then, the delay flag of the module is turned on. Alternatively, whether the work is delayed or not can be determined from the remaining days (the number of days from the current time to the planned end date of development) and the progress rate. The progress status processing unit 113 displays the progress status determination result on the user terminal 101 (step 906).

  An example of displaying the progress of the module creation work in a graph is shown in FIG. In this graph, the production amount creation amount is taken along the vertical axis, and the time is taken along the horizontal axis. By looking at this graph, the project manager or development staff can visually grasp how much the planned value and the actual value differ for each module or for the entire project. Moreover, future predicted values can also be visually confirmed. The progress display format is not limited to the graph display, but may be displayed in a table format.

  Further, the progress status processing unit 113 determines whether a work delay has occurred from the development schedule of the entire project (907). It is assumed that the determination condition for the occurrence of delay is set in advance by the project manager or the person in charge of development. For example, determination conditions can be set on a screen as shown in FIG. If it is determined in step 907 that a delay has occurred, the delay countermeasure processing unit 112 performs a predetermined delay countermeasure process (step 908).

  Thereafter, the processing from step 904 to step 908 is repeated until the creation of all the deliverables is completed (step 909).

Work Delay Countermeasure Processing FIG. 17 is a flowchart showing details of the delay measure processing performed in step 908 of FIG. In FIG. 17, the delay countermeasure processing unit 112 first performs a calculation for estimating the amount of work necessary to recover the processing delay from the module creation progress status table of the project DB 105 (step 1701). The amount of work can be expressed in units of [person / time], for example, with the amount of work performed by one person in charge of development of standard ability per hour as a unit work amount. In the following steps, a measure for delay recovery is determined based on the required work amount, and is proposed to the project manager or development staff. It is assumed that a condition as a criterion for determining the delay recovery measure is set in advance by the project manager or the person in charge of development. For example, conditions can be set on a screen as shown in FIG. Note that the conditions related to overtime work of the development staff shall be changed from time to time by the project manager or the development staff themselves depending on the situation. For example, when the amount of work is reduced due to fatigue or interruption of other work occurs, it is necessary to reduce the overtime available time.

  In order to determine a countermeasure for delay recovery, the delay countermeasure processing unit 112 determines whether or not delay recovery is possible when the person in charge of development works overtime (step 1702). This determination can be made by comparing the amount of work required for delay recovery with a preset condition related to overtime of a developer. If it is determined that it is possible, a proposal is made to instruct the developer in charge of overtime (step 1703). This proposal is displayed on the user terminal 101.

  When it is determined that delay recovery is not possible depending on overtime, the delay countermeasure processing unit 112 determines whether there is a budget for adding personnel (step 1704). This determination can be made by comparing the amount of work required for delay recovery with a preset condition related to the development budget. If it is determined that it is possible, an instruction for searching for employees to be assigned to the delay recovery work is output to the employee search unit 111 together with the amount of work necessary for the delay recovery. The employee search unit 111 searches the employee basic information DB 102, the employee skill information DB 103, and the employee schedule information DB 104 for an employee who can accept the delay recovery work, and returns the result to the delay countermeasure processing unit 112 (step 1705). The delay countermeasure processing unit 112 makes a proposal to add those employees to the development personnel (step 1706). The search method in step 1705 will be described in detail later.

  FIG. 19 shows an example of a screen that displays a search result of employees who can undertake delayed recovery work. The project manager or the like can determine the employee who is entrusted with the delay recovery work by looking at the search result screen displayed on the user terminal 101. Since the work efficiency may vary depending on the skill level of the employee, it is preferable to estimate the work time of the employee engaged in the delayed recovery work based on the work time conversion table as shown in FIG. The coefficient shown in FIG. 20 is a value calculated by using past data held in the project DB 105 or the like. As the calculation method, the actual value of the work time of each developer is obtained for each type of work. There are methods such as calculating and calculating from the average and standard deviation.

  If there is no budget for adding personnel for the delay recovery work, the delay countermeasure processing unit 112 determines whether the delay recovery is possible according to the priority work instruction (step 1707). For example, when there is a work process that is a bottleneck, delayed recovery may be possible by temporarily assigning personnel of other work processes to the work process to promote the work. The delay countermeasure processing unit 112 can determine whether such a countermeasure is possible with reference to a project management table, a module information table, and the like in the project DB 105. When it is determined that the delay recovery is possible according to the priority work instruction, a screen showing the work process to be prioritized is displayed on the user terminal 101 (step 1708).

  When it is determined that the delay recovery cannot be performed by any of the above means, the delay countermeasure processing unit 112 displays a screen indicating a warning that the delay recovery cannot be performed on the user terminal 101 (step 1709).

  Here, in the above step 1705, a method for searching for an employee who can undertake delayed recovery work from the employee basic information DB 102, employee skill information DB 103, and employee schedule information DB 104 will be described with a specific example.

The employee search unit 111 determines whether or not to accept the delayed recovery operation based on whether or not each employee satisfies all the following requirements.
(A) Can you afford to support other work? (B) Are you satisfied with the necessary development language and skills? (C) Does the required cost fall within the budget? (D) The original work of the employee Ends within the scheduled period

  The requirements (a) and (d) are determined with reference to the employee schedule information table of the employee schedule information DB 104. For example, if the employee continues working within the working hours of the day (not including overtime) based on the scheduled work end date, development scale, progress rate, man-hours used, etc. of the delayed project or module If it can be predicted that the work will be completed by the day, it can be determined that this requirement is satisfied.

  The requirement (b) is determined with reference to the employee skill information table in the employee skill information DB 103. For example, it may be determined whether or not the development language, skill level, development efficiency, etc. of the employee are suitable for performing the development work of the project or module. In the determination, it is desirable to consider a coefficient as shown in FIG.

  The requirement (c) is determined by referring to the project management table in the project DB 105. For example, if you estimate the amount of delayed recovery work to be entrusted to the employee based on the scheduled work end date, development scale, progress rate, man-hours used, etc. of the delayed project or module, and multiply this by the employee's wage, The required cost for the employee is calculated.

  An employee who satisfies all the above requirements (a) to (d) is presented as an employee who can undertake delayed recovery work.

  The project management system of the present invention has been described above with specific embodiments, but the present invention is not limited to these. A person skilled in the art can make various changes and improvements to the configurations and functions of the invention according to the above-described embodiments or other embodiments without departing from the gist of the present invention.

  The project management system of the present invention can be realized on a computer equipped with storage means, input means, display means, etc., and information processing called project development management is performed using the above storage means, input means, display means, etc. Since it is concretely realized by using, it is an invention that can be utilized industrially.

It is a functional block diagram which shows roughly the whole structure of the project management system of this invention. It is a figure which shows the data structure of the employee basic information table which employee basic information DB shown in FIG. 1 has. It is a figure which shows the data structure of the employee skill information table which the employee skill information DB shown in FIG. 1 has. It is a figure which shows the data structure of the employee schedule information table which employee schedule information DB shown in FIG. 1 has. It is a figure which shows the data structure of the project management table which project DB shown in FIG. 1 has. It is a figure which shows the data structure of the module information table which project DB shown in FIG. 1 has. It is a figure which shows the data structure of the module creation progress situation table which project DB shown in FIG. 1 has. It is a figure which shows the data structure of the delay cause table which project DB shown in FIG. 1 has. It is a flowchart which shows the flow of the whole process at the time of performing development work using the project management system shown in FIG. It is a figure which shows the example of the weight according to data type used in the complexity determination process of a module. It is a figure which shows the example of the item of the system characteristic used as the foundation which calculates the correction coefficient used in the complexity determination process of a module. It is a figure which shows the example which calculates the complexity of a module using the criterion shown in FIG.10 and FIG.11. It is a graph which shows the transition of the understanding degree with respect to the work of a general developer with a growth curve. It is a graph which shows the transition of the understanding degree with respect to the work of a general developer with a growth rate curve. It is a figure which shows the example which displays the progress of module creation work in a graph. It is a figure which shows the example of a screen which sets the determination condition of generation | occurrence | production of a delay by the progress status process part of the project management system shown in FIG. 10 is a flowchart showing details of a delay countermeasure process performed in step 908 of FIG. 9. It is a figure which shows the example of a screen which sets the conditions used as the reference | standard which determines the delay recovery countermeasure by the delay countermeasure process part of the project management system shown in FIG. It is a figure which shows the example of a screen which displays the search result of the employee who can undertake delay recovery work by the delay countermeasure process part of the project management system shown in FIG. It is a figure which shows the conversion table of the skill level of a person in charge of development, and work time.

Explanation of symbols

101 User terminal 102 Basic employee information DB
103 Employee skill information DB
104 Employee schedule information DB
105 Project DB
110 Employee Information Registration Unit 111 Employee Search Unit 112 Delay Countermeasure Processing Unit 113 Progress Status Processing Unit 114 Development Result Registration Unit 115 Project Registration Unit 116 Module Complexity Determination Processing Unit

Claims (11)

Development personnel information database that holds information on development capabilities and schedules of development personnel;
A project information database that holds information on the development scale, development schedule, and progress of the project being developed;
A delay determination unit that refers to the project information database and determines the occurrence of delay in project development based on the development scale, development schedule, and progress of the project;
For the project where the delay occurred, refer to the project information database, calculate the amount of work required to recover the delay from the development scale, development schedule and progress of the project, and refer to the development personnel information database. A measure determination means for determining a measure suitable for processing the amount of work necessary to recover the delay from the development ability and schedule of the development personnel;
A project management system including countermeasure proposal means for presenting a determined countermeasure to a user;
The project management system characterized in that the countermeasure includes at least one of instructing development personnel of the project to overtime, adding a spare development personnel, and instructing priority work. The development personnel information database further holds information on the cost of development personnel,
The project information database further holds information regarding the budget of the project,
The measure determination means calculates the cost increase due to overtime instruction or addition of spare development personnel, and delays the overtime instruction or addition of spare development personnel on the condition that the project budget is not exceeded due to the cost increase. The project management system according to claim 1, wherein the project management system determines that the measure is suitable for recovery. The project information database further holds information indicating the relationship between each work included in the project development,
The measure determination means determines the work causing the delay based on the information indicating the relationship between each work included in the project development, the development schedule and progress of the project, and the development personnel development If it is predicted from the ability that the work amount necessary for the delay recovery can be processed by preferentially performing the work, it is determined that it is a suitable measure to instruct the work as a priority work. The project management system according to claim 1, wherein the system is a project management system. The project information database further holds information on the development scale, development schedule, and progress of each module creation work included in the project development,
The delay determination means determines the occurrence of delay for each module creation work,
The measure determination means refers to the project information database for the module creation work in which a delay has occurred, calculates the amount of work necessary to recover the delay from the development scale, development schedule and progress of the module, The measure suitable for processing the amount of work necessary to make up for the delay is determined from the development capability and schedule of the development personnel with reference to the development personnel information database. 4. The project management system according to any one of 3 above. The project information database further holds information on the complexity of each module,
The measure determining means, when calculating the amount of work necessary to make up for the delay in module creation work in which a delay has occurred, performs calculation taking into account the complexity of the module. 4. The project management system according to 4.   6. The project management system according to claim 5, further comprising means for determining module complexity according to a function point method.   7. The method according to claim 1, wherein the measure determination unit calculates the work amount necessary for the delay recovery in consideration of a degree of understanding of the work of the development personnel. The project management system described.   The development personnel information database holds information relating to the development capabilities of development personnel, and includes at least one of development language, development efficiency, skill level according to a predetermined standard, bug rate, and bug countermeasure man-hour ratio. The project management system according to any one of claims 1 to 7.   The information on the schedule of the development personnel held in the development personnel information database includes at least one of the current work, the planned development start date and the planned development end date, and the progress status of the work. The project management system according to any one of claims 1 to 8, wherein the system is a project management system.   If the countermeasure determining means determines that there is no countermeasure suitable for processing the amount of work required to recover the delay for the project in which the delay has occurred, the countermeasure proposing means The project management system according to claim 1, wherein a warning is presented to the user. Manage project development with reference to a development personnel information database that holds information on development capabilities and schedules of development personnel, and a project information database that holds information on the development scale, development schedule, and progress of the development target project A program that performs
A delay determination step for determining occurrence of delay in project development based on the development scale, development schedule and progress of the project with reference to the project information database;
A delay recovery work amount calculating step for calculating a work amount necessary for recovering the delay from the development scale, development schedule and progress of the project with reference to the project information database for the project in which the delay has occurred,
A measure determination step for determining a measure suitable for processing the amount of work necessary for recovering the delay from the development capability and schedule of the development personnel with reference to the development personnel information database;
A countermeasure proposal step for presenting the determined countermeasure to the user,
The program includes at least one of instructing development personnel of the project to overtime, adding spare development personnel, and instructing priority work.

Images