JP2004094827A - Software development progress management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problems on a conventional software development progress management system that work and progress are seized to some extent but it is impossible to identify detailed progress and difficult to set meticulous loads for every person responsible. <P>SOLUTION: Detailed schedule creating means 3 creates a detailed schedule for each work for which a schedule is created by master schedule creating means 1 and which has working items sectioned into one-to-several day work units. When the work is completed, work product registering means 6 registers a work product created by the work, and a work completion determining part 5 determines the completion of the work in accordance with the registration of the work product and a progress calculating part 8 calculates the progress of the working items from the total number of works and the number of completed works. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a software development progress management method for quantitatively and mechanically managing the development progress of software with an objective index based on detailed execution confirmation of a work item and a work product.
[0002]
[Prior art]
Conventionally, software development progress management can only be performed by reporting the completion rate of very coarse-grained work items or by confirming whether or not a work in a certain form has been completed. Did not.
In the report of the percentage of completion for coarse-grained work items, the percentage of completion of the work depends on the subjectivity of the reporter, and the way of understanding the percentage differs depending on the individual, and it is not possible to simply compare the percentage of completion with progress. In the middle of the period, I could not grasp the substance of the progress. In addition, since the specific work content and work process during the work period cannot be checked, only a check as to whether or not a certain set of work items has been completed has been made.
Similarly, there is a problem in that confirmation of a completed product to a certain extent can only confirm whether or not the work has been completed, and cannot confirm the specific work content and work process.
That is, in the conventional software development progress management method, only the confirmation of 0 (absence) or 1 (completion) is performed in a large unit, so that appropriate progress management cannot be performed. In addition, there is a problem that it is difficult to determine countermeasures because it is difficult to grasp the problems when the progress is delayed.
For this reason, for example, in "Software development progress management apparatus" of Patent Document 1, an apparatus for solving the problem of the progress report on coarse-grained work items is described. According to this, a work process for each work item and a work load value for each work process are set, and whether or not work has been completed for each work process is calculated, thereby calculating an actual progress rate based on the load value. ing.
[0003]
[Patent Document 1]
JP-A-4-141730 (pages 3 to 5, FIGS. 2 to 4)
[0004]
[Problems to be solved by the invention]
However, in the above-described conventional apparatus, since there is a load for each work process, some work and progress can be grasped, but detailed progress cannot be confirmed. For example, if there is a process with a load of 0.1 and a process with a load of 0.5, if it takes one week for the process with a load of 0.1 and 5 weeks for the process with a load of 0.5, Although the progress of the process is reported one week later, the progress of the process with a load of 0.5 may only be grasped after five weeks, and the progress during the five weeks will not be visible at all. In addition, a load value must be set for each work process, and if the load value is incorrectly set, an appropriate result cannot be obtained. In addition, the load should be different depending on the skill of the person in charge, and it is difficult to newly develop or set a detailed load according to the person in charge. Further, in the conventional apparatus, the completion of the work process is determined only by the completion report, and it cannot be objectively confirmed that the work is completed.
[0005]
SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and describes the work content, work process, and progress from 0 (none) to 1 (complete) of a certain work related to software development. The purpose is to obtain a software development progress management method that can be confirmed.
[0006]
[Means for Solving the Problems]
In the software development progress management method according to the present invention, a master schedule creating means for creating a schedule of work items required for software development, and a schedule for each work in which the work items are subdivided into units of one to several days. Detailed schedule creating means to be created, work product registration means for registering a work product created by the work when the work is completed, and completion of the work determined by registering the work product by the work product registration means And a progress calculation unit that calculates the degree of progress of the work item from the total number of works in which the work item is subdivided and the number of completed works whose completion is determined by the work completion determination unit. .
[0007]
Also, a person setting means for setting a person in charge for each work item, a work time registration means for registering the actual work time of the work, and a work based on the actual work time of the work registered by the work time registration means. A work time calculation unit that calculates the total actual work time of the item is provided. The detailed schedule creation means creates a work schedule for each person in charge, and the work time registration means registers the actual work time of the work. It is performed every time.
[0008]
Further, a storage unit is provided for storing the degree of progress of the work item calculated by the progress calculation unit and the total actual work time of the work item calculated by the work time calculation unit. The past data corresponding to the total actual work time of the item is stored, and the past data stored in the storage unit is compared with the progress of the work item and the total actual work time of the work item.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
Embodiment 1 FIG.
FIG. 1 is a diagram showing a schematic configuration of a software development progress management system according to a first embodiment of the present invention.
In FIG. 1, reference numeral 1 denotes a master schedule creating unit for creating a master schedule, 2 denotes a master schedule storage unit that stores the master schedule created by the master schedule creating unit 1, 3 denotes a detailed schedule creating unit that creates a detailed schedule, 4 Is a detailed schedule storage unit for storing the detailed schedule created by the detailed schedule creating means 3. Reference numeral 5 denotes a work completion determining unit that determines that the work is completed when the work product (evidence) is registered, 6 denotes a work product registration unit that registers the work product (evidence), and 7 denotes a work product registration unit. A work product storage unit that stores the work products registered by 6 and a progress calculation unit 8 that calculates the progress from the sum of the total number of works and the number of completed works registered in the detailed schedule, and registers the progress in the master schedule. .
[0010]
FIG. 2 is a diagram showing a specific example of the software development progress management method according to the first embodiment of the present invention, showing an example of a master schedule and a detailed schedule.
In FIG. 2, reference numeral 19 denotes a master schedule, and reference numeral 20 denotes work items (tasks) constituting the master schedule 19. The work schedule 20 is created by the work items 20. 22 is a work schedule of each work item 20, 23 is progress of the work item, 24 is a work item output (output), 25 is a detailed schedule created for each work item, and 26 is a worker in charge of work item A. , 27 are subdivided works of work item A (work), 28 is the work schedule of work 27, 29 is the actual work time of each work 27, 30 is the work product (evidence) of work 27, and 31 is work 27 Is completed, and indicates completion. 32 is the total number of works of the work 27, 33 is the total number of completed works which is the number of completed 31s, 34 is the total actual work time, 35 is the product a of the work a, and 36 is the work a.
The deliverable 24 is, for example, a set of specifications such as a system requirement specification and a system system design document, and the work product 30 includes, for example, each work for creating the system requirement specification. The results that occur for each case (list of survey targets, survey results, analysis results of survey results, requirements arrangement, preconditions / restrictions, solutions, systemization range study results, etc.) These are the results of review minutes, correction record list, etc.
[0011]
Next, the operation will be described.
The master schedule creation means 1 creates work items (hereinafter, tasks) 20 required for software development and respective work schedules 22 and records them in the master schedule storage unit 2.
Next, the detailed schedule creating means 3 creates a detailed schedule 25 for each task 20 according to the master schedule 19 and records it in the detailed schedule storage unit 4. First, a work (hereinafter referred to as a work) 27 necessary for realizing the task 20 and each work schedule 28 are created in units of one to several days. For example, in the detailed schedule 25, the work schedule is set to a maximum of seven days. When each work 27 is completed, the work product (hereinafter referred to as evidence) 30 is registered in the work product storage unit 7 by the work product registration means 6.
When the evidence 30 is registered, the work completion determination unit 5 determines that the work 27 has been completed. For example, when the product a35 is registered as the evidence 30 for the work a36, the work completion determination unit 5 determines that the work a36 is completed, and registers the completion 31.
[0012]
This will be described using the specific deliverables 24 and work products 30 described above. For the work item (task) “system requirements analysis”, the deliverable “system requirements specification” is planned. I do. As the detailed schedule for the analysis of the system requirements of the task, “examination of the investigation target”, “implementation of the investigation”, “analysis of the investigation result”, etc. of each work (work) are planned, and the “investigation” of the work product 30 is performed. Plan target list, survey results, analysis results of survey results, etc.
The work completion determination unit 5 determines that the “finding out of the investigation target” of the work is completed by registering the “list of investigation target”. The “system requirement specification” of the product 24 is completed by a set of the work products 30.
Next, the progress calculation unit 8 calculates the progress 23 (the total number of completed works 33 / the total number of works 32) from the total number of works 32 registered in the detailed schedule 25 and the total 33 of completed works according to the formula of “total number of completed works 33 / total number of works 32”. Calculate the progress) and register it in the master schedule.
[0013]
As described above, according to the first embodiment, for software development progress management, a detailed schedule in which work items (tasks) are broken down from one day to several days of work (work) is created, and a completion report is made for each work. Do. The progress is confirmed based on a value obtained by calculating the number of completed works / the number of planned works for each task. As a result, the work content and man-hours up to the completion of the work item can be grasped in units of one to several days, and appropriate progress management can be performed.
Also, in order to confirm the completion of the work, the work product (evidence) generated for each work is recorded. By making the work items finer, it is possible to grasp the problem with the delay in progress, and it becomes easier to take measures for the problem.
Note that the software development progress management system of the present invention is constituted by a kind of information processing device such as a computer.
[0014]
According to the first embodiment, as described above, the details of the work, the process of the work, and whether or not the work has been completed can be confirmed at a granularity of one to several days, and the completion of the work can be determined based on the registered evidence. It is possible to grasp objectively, and it is possible to control the work in detail and to appropriately allocate resources.
[0015]
Embodiment 2 FIG.
FIG. 3 is a diagram showing a schematic configuration of a software development progress management system according to a second embodiment of the present invention.
In FIG. 3, reference numerals 1 to 8 are the same as those in FIG. Reference numeral 9 denotes a product registration unit for registering a product, and reference numeral 10 denotes a product storage unit that stores the product registered by the product registration unit 9. 11 is a person setting means for setting a person in charge for each work item, 12 is a person list storage part in which persons are registered in advance, 13 is person registration means for registering persons in the person list storage part 12, 14 is a work item list storage unit in which work items that can be tasks 20 are registered, 15 is a work item registration unit that registers work items in the work item list storage unit 14, and 16 is a work time that registers the actual work time of the work 27 The registration unit 17 is a work time calculation unit that calculates the total work time 34 for each task.
[0016]
Next, the operation will be described with reference to FIG. 3 and FIG.
In the second embodiment, in addition to the first embodiment, a worker 26 is set for each task 20. The person in charge is registered in the person in charge list storage unit 12 by using the person in charge registering unit 13 in advance, and a worker 26 is set for each task 20 when the master schedule is created. A work schedule 28 is created for each work 27 of the set task 20 for each worker 26, and the evidence 30 is registered for each work 27.
Further, the task 20 is selected and set. Using the work item registration unit 15, items that can become the task 20 are registered in the work item list storage unit 14 in advance. A task 20 is selected by selecting from the work item list storage unit 14 when the master schedule is created.
In addition, a product (hereinafter, output) 24 is registered for each task 20. The output 24 is registered in the product storage unit 10 using the product registration means 9.
The actual work time 29 of the work 27 is registered for each person in charge using the work time registration means 16. The work time calculation unit 17 calculates the actual work time total 34 for each task 20 and registers it in the master schedule.
As described above, according to the second embodiment, for software development progress management, a detailed schedule in which a work item (task) is broken down from one day of a worker in charge to a work (work) in units of several days is created, and a work schedule is created. The actual work time and work completion are reported for each time. As a result, the work content, the person in charge of the work, and the man-hour until the completion of the work item can be grasped in units of one to several days, and appropriate progress management can be performed.
[0017]
According to the second embodiment, since the work, which is the smallest unit indicating the progress, can be planned according to the worker, the work is between the report generated by the load setting accompanying the work and the actual progress. The difference due to the skill of the worker can be eliminated.
Further, by registering the work time, the work time can be managed, and the load status of the worker can be checked.
[0018]
Embodiment 3 FIG.
FIG. 4 is a flowchart showing a flow of software development progress management according to the third embodiment of the present invention.
Hereinafter, FIG. 4 will be described.
First, the flow of schedule creation will be described below.
The project leader 37 creates a master schedule 40 and records it in the storage unit 39. At the time of the master schedule creation 40, a past schedule can be called from the storage unit 39 and used as a reference. The worker 38 creates a detailed schedule 41 based on the master schedule recorded in the storage unit 39. At this time, a consistency check 47 with the master schedule is performed.
[0019]
Next, the flow of the performance report / confirmation of the progress will be described below.
The worker 38 makes a performance report 43 based on the detailed schedule recorded in the storage unit 39 and records it in the storage unit 39. At the same time, a work product (evidence) is registered 44 and recorded in the storage unit 39. Next, the presence or absence of a work product (evidence) is confirmed in the storage unit 39, a work completion determination 45 is performed, and whether or not the work is completed is recorded in the storage unit 39. Further, a progress / work time calculation 46 is performed from the information in the storage unit 39, compared with past data 48, and the result is recorded in the storage unit 39.
The project leader 37 confirms the progress 42 from the information in the storage unit 39 and determines whether or not a countermeasure is necessary based on the result of comparison with the past data 48. The master schedule change 50 is performed.
[0020]
According to the third embodiment, the project leader can determine the necessity of a countermeasure by comparing with the past data.
[0021]
Embodiment 4 FIG.
FIG. 5 is a diagram showing the difference between the conventional and the software development progress management method of the present invention, and shows a conventional management method and a new management method. Here, the new management method shows only the large process A of the conventional management method.
In FIG. 5, 52 is the progress reported two months later, 53 is the progress reported two months later 52, 54 is the deliverable A, 57 is the work completed, 58 is the work Ab, and 59 is the work Ac.
With the conventional management method, it is known whether the progress at 52 months later is “on-time” or “delayed”, but from the progress 53 reported two months later at 52, the adequacy of the progress, However, the completion schedule is not clear. For example, if "60%" is reported, it is known that 60% of the plan for the entire process has been completed in 60 days, but it is unknown what the problem is. Nor can you determine if 40% will end in 40 days.
[0022]
However, with the new management method, the progress at 52 months after two months has completed 57 tasks out of a total of 8 tasks 57, indicating that the progress is 66%. In addition, it can be understood that the cause of the delay is a planning mistake of the work A-b 58 and the work A-c 59 (the work should be divided into two works and three works, respectively, or assigned to an inappropriate person). Regarding the work A-f, the report is 100, but the report is incomplete because no evidence has been registered. At this point, it can be seen that the completion schedule of the remaining three items is “21 days later” if there is no planning error.
[0023]
According to the fourth embodiment, the project leader can clarify not only the progress of the plan but also the problems of the plan and make a judgment.
[0024]
【The invention's effect】
Since the present invention is configured as described above, it has the following effects.
Master schedule creation means for creating a schedule of work items required for software development, detailed schedule creation means for creating a schedule for each work in which the work items are subdivided into one to several days, and the work is completed A work product registration means for registering a work product created by the work, a work completion determination unit for determining the completion of the work by registering the work product by the work product registration means, and A progress calculation unit that calculates the degree of progress of a work item from the total number of completed works and the number of completed works for which completion has been determined by the work completion determination unit is provided. Process, the completion of work can be confirmed, and the completion of work can be grasped objectively by registered work products. That.
[0025]
Also, a person setting means for setting a person in charge for each work item, a work time registration means for registering the actual work time of the work, and a work based on the actual work time of the work registered by the work time registration means. A work time calculation unit that calculates the total actual work time of the item is provided. The detailed schedule creation means creates a work schedule for each person in charge, and the work time registration means registers the actual work time of the work. Since the work is performed for each worker, the work can be planned according to the worker, and the work time can be managed for each worker.
[0026]
Further, a storage unit is provided for storing the degree of progress of the work item calculated by the progress calculation unit and the total actual work time of the work item calculated by the work time calculation unit. The past data corresponding to the total actual work time of the item is stored, and the past data stored in the storage unit is compared with the progress data of the work item and the total actual work time of the work item. Thus, the necessity of the countermeasure can be determined.
[Brief description of the drawings]
FIG. 1 is a diagram showing a schematic configuration of a software development progress management system according to a first embodiment of the present invention.
FIG. 2 is a diagram showing a specific example of a software development progress management method according to the first embodiment of the present invention.
FIG. 3 is a diagram showing a schematic configuration of a software development progress management system according to a second embodiment of the present invention;
FIG. 4 is a flowchart showing a flow of software development progress management according to a third embodiment of the present invention.
FIG. 5 is a diagram showing the difference between the conventional method and the software development progress management method of the present invention.
[Explanation of symbols]
1 master schedule creation means, 2 master schedule storage unit,
3 Detailed schedule creation means, 4 Detailed schedule storage unit,
5 work completion determination unit, 6 work product registration means, 7 work product storage unit,
8 progress calculation section, 9 product registration means, 10 product storage section,
12 person in charge list storage unit, 13 person in charge registration means, 14 work item list storage unit,
15 work item registration means, 16 work time registration means, 17 work time calculation unit,
19 master schedule, 20 work items (tasks),
22 work schedule, 23 progress, 24 deliverables (output),
25 detailed schedule, 26 worker, 27 work (work),
28 work schedule, 29 actual work time,
30 work products (evidence), 31 completed, 32 total number of works,
33 total number of completed work, 34 total actual work time, 35 product a,
36 work a, 37 project leader, 38 worker,
39 data storage unit, 40 master schedule creation,
41 Detailed schedule creation, 42 Progress confirmation, 43 Results report,
44 Work product (evidence) registration, 45 Work completion judgment,
46 Progress / work time calculation, 47 Consistency check, 48 Comparison with past data,
49 Considering countermeasures, 50 Changing master schedule,
52 Two months later, 53 Reported progress, 54 Deliverable A,
57 work completed, 58 work Ab, 59 work Ac.

Claims (3)

Master schedule creation means for creating a schedule of work items required for software development, detailed schedule creation means for creating a schedule for each work in which the above work items are subdivided into work of one to several days, and the above work has been completed. When the work product registration means for registering the work product created by the work, the work completion determining unit for determining the completion of the work by registering the work product by the work product registration means, A software development progress management method, comprising: a progress calculation unit that calculates the degree of progress of the work item from the total number of subdivided works and the number of completed works for which completion has been determined by the work completion determination unit. Person in charge setting means for setting a person in charge for each work item, work time registration means for registering the actual work time of the work, and the work based on the actual work time of the work registered by the work time registration means A work time calculation unit for calculating the actual work time of the item; the detailed schedule creating means creates a work schedule for each person in charge; 2. The software development progress management system according to claim 1, wherein registration is performed for each person in charge. A storage unit for storing the progress of the work item calculated by the progress calculation unit and the total actual work time of the work item calculated by the work time calculation unit; And past data corresponding to the total actual work time of the work item is stored, and the past data stored in the storage unit is compared with the progress of the work item and the total actual work time of the work item. 3. The software development progress management system according to claim 2, wherein:

Images