JP2728450B2 - Project management diagnostic system - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to a project management diagnosis system for diagnosing the feasibility of a development plan of a project such as software development of an electronic computer and the deviation of an actual result from the plan for each process. It is.

[Conventional technology]

Promoting and completing projects on time and within budget is an important issue in project management. If the initial plan is found to be inadequate after project development,
Not only will the budget be exceeded, but it will also have a great impact on many aspects, such as overloading personnel, reducing trust in delivery destinations, and deteriorating quality due to moral degradation of projects. JP-A-62-
Japanese Patent Publication No. 152065 discloses a simulation device that can grasp the progress and results of a project in advance in an initial planning stage. This system stores the individual productivity of development personnel and the workload of each task, sets schedule information for assignment tasks for each personnel, performs simulations, and monitors the progress and results of the project in advance. Can be grasped. The reliability of the input data for individual productivity used in simulations using the individual productivity of the development staff of this equipment (the basis for calculating the data) belongs to the project staff or the manager, and generally the input It is difficult to objectively prove the accuracy of the data to a third party. Therefore, in order to identify problems at an early stage, it is desirable to have a method that allows a third party of the project to quantitatively and objectively evaluate the development plan of the project. Japanese Patent Application Laid-Open No. 63-12066 also discloses a project progress diagnosis.

[Problems to be solved by the invention]

In the above prior art, not only the assignment of personnel and work, but no consideration is given to a standard scale by which a third party can quantitatively and objectively evaluate the project development plan.
There was a problem that project management was more objective and could not be implemented by a third party.

It is an object of the present invention to provide a project management diagnostic system for performing quantitative and objective feasibility analysis of a project development plan.

Another object of the present invention is not only to examine the development plan, but also to examine whether the implementation has been carried out as planned, and to review the plans after that point according to the implementation status, and to add the results and the revised plan to realize the plan again. An object of the present invention is to provide a project management diagnostic system for performing gender analysis.

[Means for solving the problem]

In order to achieve the above objectives, the project management elements are classified into a plurality of items that are difficult to be subjective, a project development plan is set for each item, and the feasibility of the project is determined individually or in combination with each item. (= Diagnosis). further,
Each item is provided with a reference table in which an evaluation reference scale is set, and is compared with a plan / actual table so that a third party can make an objective diagnosis.

In addition to the diagnosis of the development plan, in order to diagnose whether or not the implementation is being carried out as planned, it is possible to set a diagnosis time for each process break, and to conduct a diagnosis based on the actual results and the review plan in each process. It is made possible.

[Action]

According to the present invention, by providing an evaluation criterion serving as a reference scale for diagnosis, a third party (upper manager or manager) can also make a diagnosis, and the parties and the third party have a common understanding of the project. In the event of a problem, the recommendation to the supervisor of the party concerned is easily recognized, and a business diagnosis such as a change in the project plan is promptly made, thereby preventing damage to customers as a result. be able to.

In addition, by performing a diagnosis at each process break,
Problems can be found in a timely manner and delays in process progress can be minimized.

〔Example〕

FIG. 1 is a diagram for explaining the overall process of project diagnosis in an embodiment of the present invention, FIG. 2 is an example of a system configuration of the present invention, FIG. 3 is an example of a personnel composition planning table for each job, and FIG. Example of personnel composition plan / actual table, FIG. 5 is an example of personnel composition reference table by job, FIG. 6 is an example of schedule table, FIG. 7 is an example of development scale table, FIG. 8 is an example of quality table, 9 is an example of a production efficiency table, FIG. 10 is an example of a setting table containing coefficients for setting diagnostic data, FIG. 11 is an example of an evaluation table for storing diagnostic evaluation points,
FIG. 12 shows an example of a control table for judging a diagnosis step, and FIG. 13 shows an example of a process explanatory diagram of a staff input piled-up diagnosis item section.

For example, the system configuration shown in FIG. 2 is used for implementing the present invention. 50 is a central processing unit (MPU), 51 is a keyboard, 52 is a display, 53 is a printer, 54 is a memory, and 55 is an external storage device such as a floppy disk.

FIG. 3 is an example of a duty-based personnel composition plan table. This table stores data set at the time of drafting a project plan. In this table, duties are divided into four categories: leaders, planners, programmers, and assistants, and the number of input staff and the input staff ratio by job are shown for each job. For example, a leader is a person who can organize a project team technically and administratively,
The planner is a person who can create functional specifications, the programmer is a person who can create structural design documents, can perform coding and test work, and the assistant is a person who can support test work. A person who can do it. The number of input staff is calculated by multiplying the development staff, which is an index indicating the ratio of the work amount of the development staff who can devote to this project for each process. In this embodiment, the processes are divided into, for example, a functional design process, a structural design process, a coding process, a test process, and an inspection process.

Creation of the personnel composition plan table for each job shown in FIG. 3 has a table of the degree of dedication of the job and the process (monthly) for every person who participates in the project for each individual, and calculates and totals based on this table and stores it in this plan table. To do.

FIG. 4 is an example of a personnel composition plan / results table by duty. The items in this table are the same as those in Fig. 3. At the start of the project, the same values as those in the plan table in Fig. 3 are stored. Indicates plan data. When the plan is changed depending on the diagnosis status, the plan data of the uncompleted process is corrected. As described above, the content of the data changes at each diagnosis time, but if it is desired to keep the data changed in a time series, this table can be left at each diagnosis time (process completion time). .

The plan / actual table in FIG. 4 also has a monthly work result table for each person similarly to the plan table in FIG. 3, which is calculated and stored in the plan / actual table in FIG.

FIG. 5 is an example of a personnel composition reference table by duty. The items in this table are the same as those in FIG. 3, and store the ratio of personnel by duty as a reference for evaluating the development system diagnosis items. According to Fig. 5, for example, as a standard of personnel efficiency in the function design process, leaders and assistants are 10
%, Planner and programmer are 40%, which is 100% in total.

FIG. 6 shows an example of the configuration of a schedule table, which includes a reference table, a plan table, and a plan / actual table. It is a schedule and a project development schedule, and stores a work start date and an end date for each process. In the reference table, the reference schedule, which is the basis for evaluation, and in the planning table,
The performance table stores the performance schedule.

FIG. 7 shows an example of the configuration of a development scale table, which includes a reference table, a plan table, and a plan / actual table. The development scale indicates the resources invested and the production volume of the project, and includes work man-hours, computer time used, the number of development steps, the number of document pages, and the like. Taking the man-hours in the plan / results table as an example, this is an estimated value at the beginning of development, but is a value obtained by adding the estimated value from the next step to the results up to this step after the progress of the process.

FIG. 8 shows a configuration example of the quality table, which includes a reference table, a plan table, and a plan / actual table. Items in the table include items generally referred to as substitute characteristics indicating quality, such as the number of inspection failures per development step and the number of test items per development step. It has the feature that it has items of potential quality characteristics inherited from previous products, such as the number of external accidents in six months.

FIG. 9 shows a configuration example of the production efficiency table, which includes a reference table, a plan table, and a plan / actual table. The table items include indices such as man-hour efficiency obtained by dividing the number of development steps by the number of man-hours. Fig. 10 is an example of a setting table. This example is a configuration example of a man-hour setting table for setting the number of man-hours. is there. For example, Here, it is calculated by the formula: k: by job. FIG. 10 shows the performance coefficient k for each job.

FIG. 11 is an example of the evaluation table. In this table, when the diagnosis of the diagnosis item i / diagnosis item j is completed, the diagnosis evaluation point is stored at the position of i · j. For example, there is a method that gives a score of 5 points or a method that gives a score of 10 points. At the time of diagnosis after completion of each process, the actual evaluation of scale, system, pile, period, etc. It is stored as an evaluation point such as a perfect score of 5 or 10 points.

FIG. 12 is a control table for determining a diagnosis step. Each process has a project progress judgment table.
When 100% is set in the process j, the process j is regarded as completed, and the control shifts to the diagnosis of the process j. As for the diagnosis status for each diagnosis item in the diagnosis process j, the diagnosis is completed, and the conditioner of “1” is set in the diagnosis item column i of the control table for the diagnosis item i whose evaluation point is stored in the evaluation point table. . “0” is set in advance for unfinished diagnostic items, and the current diagnostic process is controlled by this conditioner.

FIG. 1 is a basic processing flow chart of the present invention. Processing numbers 1 to 39 in the following description correspond to numbers 1 to 39 shown in FIG. In judgment 1, a diagnosis item i of a certain development project is selected from a menu screen of the display device. This i is
Depending on the diagnosis items set by classifying the elements of the software development management, the control is divided into the case of going to the processing block 13 and the case of going to the processing block 37.

Processing screens 3 to 12 are display screens for each diagnosis item. The processing screen 3 is a diagnosis screen of a development scale transition item for prompting a development scale for each process and diagnosing a development risk based on a deviation from an initial plan. Here, the development scale is the number of work steps, computer usage time, number of development steps (new addition, replacement, deletion, number of completed steps, etc.) and number of document pages (basic specifications, functional specifications, structural design, connection specifications) And maintenance manuals)
And so on.

The processing screen 4 is a diagnostic screen of a development system that focuses on qualitative personnel allocation, evaluates the personnel, classifies them into job-specific capability classes, and examines the balance of job-specific personnel ratios by process. Here, it is the project leader or manager who assesses the abilities of personnel, but the assessment is based on the work and proficiency evaluation definition common to all employees. In general, there is no need to use individual productivity, which is very difficult to measure in software development.

The processing screen 5 is a diagnosis screen of a staffing input item for evaluating a monthly staffing quantity and its shape, paying attention to staffing in terms of quantity.

The processing screen 6 is a diagnosis screen of a development term item for detecting an unreasonable schedule plan or a redundant schedule plan.

The processing screen 7 is a diagnosis screen for a development environment item. The development environment refers to problems in production technology and the degree of computer resources used. For example, problems in production technology include the maintenance level of development jigs and tools, the degree of specification change of related programs, the internal release time received from related programs, and the like.

The processing screen 8 is a diagnostic screen for quality items focusing on the quality of the product in each process. For example, the following four items are diagnosed when developing a development plan. Diagnosis of the ratio of experienced development mothers focusing on the level of understanding of the development matrix of personnel, diagnosis of the number of external accidents in the past six months, focusing on the stability of the development matrix, diagnosis based on the number of failed inspections of the previous product, and development matrix Are the four items of diagnosis focusing on the degree of document maintenance.

The processing screen 9 is a diagnosis screen for a risk factor item. Here, the risk factor item is an item for diagnosing a qualitative problem that cannot be expressed by other diagnosis items.

The processing screen 10 is a diagnostic screen for the production efficiency items of the project. Here, the production efficiency is not the individual one but the efficiency of the whole project.

Processing screen 11 focuses on the priority management measures of the project,
9 is a diagnosis screen of a management level item for preventing missing or omission of an indispensable management item. The number of management items defined here exceeds 180.

The processing screen 12 is a comprehensive evaluation item diagnosis screen in which the evaluation points of the diagnosis results of the processing screens 3 to 11 are totaled for each item. The evaluation points of each diagnostic item i and each diagnostic step j are stored in the evaluation table (FIG. 11) for each diagnostic item, and the data of the latest stored evaluation points can be input at the time of counting. This j is an identifier or a pointer indicating a diagnosis step.

The processing block 13 is a process for selecting a diagnosis step j in the diagnosis item i selected in the judgment 1. In this process, the current process is stored in the diagnosis process determination table (FIG. 12), and the most recently completed process is automatically selected. However, any process can be selected.

The diagnosis step is judged in the judgment 14, and if it is the plan setting step, the control is passed to the processing block 21;

Processing blocks 15 to 20 correspond to the diagnosis step j. The processing block 15 is a plan setting process for drafting a project development plan. The processing block 16 is a function design completion step in which the creation of the basic specification and the function specification has been completed. Processing block 17 is a process at the time of completing the structural design document in which the creation of the structural design document has been completed. Processing block 18 is a coding completion step in which PAD diagram creation, coding creation, and desk debugging have been completed. Processing block 19 is a module test completion step in which the work of each module obtained by dividing the program is completed. After this, the test process continues with a program test process focusing on the interlock test between the modules constituting the program, and a system test process focusing on the interlock test between the programs constituting the system.
Since the present invention aims at early extraction of problems by diagnosing a project development plan, diagnosis in the preceding process is more effective, and diagnosis after the program test process is basically omitted. However, as an optional function, a process not defined in this process can be selected at any time.

The processing block 20 is a completed process in which, after the completion of the test process, the product inspection work for ensuring the quality to be delivered to the customer is completed. There is no work related to the project after this step, and the reason for making a diagnosis in this step is to evaluate the project development results based on the diagnosis through all the steps and to use it as a guideline for drafting the next development plan.

The process block 21 reads the plan data of the item i and the process j when the process selected in the judgment 14 is the time when the plan is set. Table 1 shows the relationship between item i / process j and the table to be read.

The processing block 24 determines whether or not the process selected in the judgment 14 is other than when the plan is set, or when the processing block 21 is completed.
The plan / actual table of the process j is read.

The processing block 25 reads the setting table (FIG. 10) used for calculating the diagnostic data of the item i and the step j.

The processing block 26 is a process for processing the data of the plan table or the plan / actual table using the coefficients of the setting table of the item i and the process j to create diagnostic data.
A specific example will be described later.

Processing block 27 reads the reference table for item i and step j. The reference table is a table for each diagnosis item (fifth
(FIGS. 9 to 9), and numerically, the contents are stored as reference values for the diagnosis of each item.
For example, the personnel composition standard table for each job shown in FIG. 5 stores the allowable range satisfying the standard personnel comparison and the standard personnel comparison for each job and each process, and may be considered as a reference scale for evaluation.

In the judgment 28, the diagnostic data of the item i and the step j are compared with the reference table. If the reference table is not satisfied, the control is passed to the processing block 31.

The judgment 29 compares the diagnostic data of the item i / process j with the diagnostic data of the item i / process j-1. If there is a plan change from the time point j-1, the process goes to the processing block 33. Pass control. The actual value up to the j-th step and the plan value after the j-th step are included in the diagnostic data of the step j, and the actual value up to the j-th step and the planned value after the j-th step are included in the diagnostic data of the step j-1. Is a process for determining whether the work in the j-th process is proceeding as planned in the j-1 process by comparing the two.

Processing block 31 issues a warning message if the criteria are not met in decision 28, suggests future plan changes,
Pass control to decision 32.

Judgment 32 is based on the plan change proposal from the system received by the user of the system in processing block 31. Control is switched to processing block 30 if the plan after step j is to be changed, and to decision 29 if the plan is not changed. give.

The processing block 30 receives the control from the judgment 32, and the user of the present system corrects the data after the (j + 1) th step in the plan / actual table, and passes the control to the processing block 26.

The processing block 33 receives control from the decision 29, and determines the j-step and j-
The degree of change of the diagnostic data in one process is calculated and displayed, and control is passed to the processing block 34.

The processing block 34 stores the diagnosis result of the diagnosis item i and the diagnosis step j in the evaluation table (FIG. 11), and passes control to the processing block 35.

The processing block 35 sets the diagnosis execution flag of the item i and the item j.
Turn ON, and set 1 to the corresponding item in the diagnostic process judgment table (FIG. 12).

The judgment 36 is for judging whether or not to continue the diagnosis. When diagnosing the next diagnosis item, the control is passed to the judgment 1, and when ending the diagnosis, the control is passed to the processing block 37.

The processing block 37 reads all diagnostic items and diagnostic results of all diagnostic steps from the evaluation table (FIG. 11).

The processing block 38 sums up the evaluation points (= diagnosis results) of all diagnosis items for each diagnosis step j and calculates an average point.

The processing block 39 outputs the evaluation score for each diagnostic item i to the printer 53 for each diagnostic step j.

Next, with reference to FIG. 13, a specific example of processing when the staff input piled-up diagnosis item (i = 3) is selected in the project diagnosis processing explanatory diagram of FIG. 1 will be described. The processing flow in FIG. 13 corresponds to steps 14 to 35 in FIG.

First, the diagnosis process determination table (No. 12
FIG. 4), j is determined as the largest j in which 1 stands in item 3, and j + 1 is determined as a diagnostic step. If 1 stands in the items of j = 1, 2 and 3, j = 4 is selected. If 1 does not stand for each item of j, j = 1 is selected. In FIG. 12, i =
In the three-mountain diagnosis, j = 1 is selected when j = 1 is planned, and is 0 when the functional design of j = 2 is completed, so j = 2 is selected. If the process is a plan setting process (j = 1), the control is passed to a processing block 81, and if the process is the next process (j = 2 to 6), the control is passed to a processing block 84.

A processing block 81 reads the monthly and duty-based personnel input data from the plan data, and passes control to a processing block 83. This data is calculated by multiplying the development dedication planned for each individual by month and the planned input personnel volume for each month. Here, the monthly development dedication is the ratio of personnel engaged in the project with respect to the working hours of the entire month, and is the ratio of actual engagement in the project after subtracting the degree of impact of work with other projects. is there.

If the diagnosis step is not the process at the time of the plan setting in the judgment 80, the processing block 82 reads the actual personnel for each month and duty and the planned personnel input data for this month and thereafter from the plan / actual table, and passes control to the processing block 83. Processing block 83
Reads the setting table (FIG. 10) of the staff input piled-up diagnosis item, and passes control to the processing block 84. Processing block 84
Is calculated by multiplying the monthly and job-specific staff input data read from the plan table or the plan / actual table by the job-specific capacity factor defined in the setting table for each job, and averaging the monthly staff input. Calculate the data. The processing block 85 reads the monthly and duty-based personnel input data from the reference table, and passes control to a processing block 86. The staffing data is the monthly staffing that is calculated based on the development scale and taking into account productivity deviations due to project characteristics such as difficulty, etc. You can think of it as multiplied. The calculation formula is shown below.

Ykl = ax ₁ × bx ₂ × cx ₃ × S × dk × βlm × γn where Ykl: k program type / monthly reference personnel (because the number of personnel varies by month) a, b, c: project characteristics x ₂ Difficulty factor for each x ₃ S: Number of development steps (variable) dk: Reference personnel per number of development steps of k program types βlm: Development period characteristics of the first month of m personnel input pattern γn: 1 / Planned development period n (month) Processing block 86 recognizes the input curve of the input staff pile (the actual plus the planned value after the actual process) in the plan / actual table in the pattern, and evaluates the input staff pattern for evaluation set in advance. To match. Here, the evaluation personnel input pattern is ideal type, attenuation type (there is no personnel to be input when required), one-time input type (all development personnel are input from the basic specification creation process), and sequential input type (Patterns are gradually input as the process becomes later).

The processing block 88 compares the planned / actual input staff pile (diagnosis data) for each month with the monthly staff input pile for the reference table, and calculates the satisfaction rate of the diagnostic data for the reference table. The processing block 89 compares the actual input staff pile at the j-th process with the planned input staff pile at the j-1 process for each month, and calculates the satisfaction rate of the actual value with respect to the plan value set in the previous process.

The judgment 90 judges whether the satisfaction rate calculated in the processing block 88 satisfies the reference table, and calculates the evaluation point A.
Next, the evaluation point B is calculated based on the reference table of the matched pattern in the processing block 86. Further processing block 89
It is determined whether or not the satisfaction rate calculated in the step satisfies the reference table, and the evaluation point C is calculated. The weighted average of the evaluation points A, B, and C is set as an evaluation point. If the system user satisfies the evaluation points, control is passed to a processing block 94; otherwise, control is passed to a processing block 91.

Processing block 91 issues a warning if the criteria is not met at decision 90 and suggests a future plan change. In the judgment 92, the control is transferred to the processing block 93 if the planned input personnel pile in the plan / actual table is changed, and if not, the control is passed to the processing block 94. The processing block 93 modifies the planned input personnel accumulation data for each month and job and stores it in the plan / actual table according to the warning content of the processing block 91, and passes control to the processing block 84.

The processing block 94 calculates and displays the degree of change in the monthly and duty-based personnel piles of the diagnostic data at the j-th step relative to the j-th step, and passes control to a processing block 95. Processing block
Reference numeral 95 stores the diagnosis result of the diagnosis item 3 / diagnosis step j (the evaluation point) in an evaluation table (FIG. 11), and passes control to a processing block 96. The processing block 96 turns on the diagnosis execution flag of the diagnosis item 3 / diagnosis step j, and sets the diagnosis step determination table (12th
Set 1 to the corresponding item in (Fig.). Upon completion of this processing, the diagnosis of the staff input piled item ends.

〔The invention's effect〕

According to the present invention, a quantitative and objective diagnosis of a project development plan can be performed not only by a developer but also by a third party from various angles. In addition, not only the development plan can be diagnosed, but also the results and plans of intermediate processes can be diagnosed, so that problems can be discovered early and measures can be taken to prevent process delays.

[Brief description of the drawings]

FIG. 1 is a diagram showing a processing flow for explaining the whole project diagnosis of one embodiment of the present invention, FIG. 2 is a block diagram showing an example of the system configuration of FIG. 1, and FIG. Diagram, Fig. 4 is a diagram showing a staff composition plan / actual table by job, Fig. 5 is a diagram showing a staff composition reference table by job, Fig. 6 is a diagram showing a schedule table, and Fig. 7 is a development scale table , FIG. 8 shows a quality table, FIG. 9 shows a production efficiency table, FIG. 10 shows a setting table, FIG. 11 shows an evaluation table,
FIG. 12 is a diagram showing a diagnosis process determination table, and FIG.
It is a figure showing the processing flow of the staff input pile accumulation diagnosis item part of a figure. 50: Central processing unit (MPU), 51: Keyboard, 52 ...
Display, 53 printer, 54 memory, 55 external storage device

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Minoru Chikusa 3-10-22 Sakae, Naka-ku, Nagoya City, Aichi Prefecture Within Hitachi Chubu Software Co., Ltd. 81-chome Hitachi Software Engineering Co., Ltd. (56) References JP-A-63-12066 (JP, A) JP-A-1-257553 (JP, A) JP-A-1-161571 (JP, A) JP-A-1-82638 (JP, A) JP-A-1-180634 (JP, A) JP-A-61-194532 (JP, A) "Comprehensive software production management system CAPS" Hitachi Review, Vol. 62. No. 12 (December 1980) PP. 37−42

Claims (1)

(57) [Claims] A memory for storing data, an external storage device, an input device for inputting data, an output device for outputting data, and a central processing unit for controlling a storage device and an input / output device. In a system for diagnosing the process status at the time of the development planning and the intermediate process of the development project by using these, the stored man-hour setting table of various projects and one of the development plan table and the development result table are inputted. The central processing unit selects a table corresponding to the diagnostic items, creates diagnostic data of the development plan and actual results of the development project, and inputs the reference table stored in the data storage device to the diagnostic data and the diagnostic items. The corresponding reference table is compared, the evaluation result for each diagnosis item is stored in the evaluation table, and the diagnosis data and the evaluation table are updated. Project management diagnosis system, characterized in that stored in the storage device, and outputs to the output device.