Progress management device, progress management method, and progress management program

Abstract

A progress management device (100) that manages the progress of a system development based on the progress corresponding to each task input by a person in charge of each task in the system development includes a delay risk calculation unit (140). The delay risk calculation unit (140) determines whether or not there is a risk of delay in the ongoing task based on the number of times a target person in charge of an ongoing task, which is a task in the system development and is an ongoing task, has input progress corresponding to the ongoing task.

Description

[Technical field]

[0001] The present disclosure relates to a progress management device, a progress management method, and a progress management program. [Background technology]

[0002] There are techniques for managing the progress of work in projects such as system development. Patent Document 1 discloses a work management device that manages work by personnel in charge of carrying out tasks related to a project. The work management device determines whether there is a delayed task, which is a delay in the progress of the assigned tasks, based on the personnel-related information, and if there is a delayed task, notifies the task personnel that a delay has occurred. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-091213 A Summary of the Invention [Problem to be solved by the invention]

[0004] In projects such as system development, each person in charge must manage the progress of the tasks for which he or she is responsible, and must frequently share the progress with other people. Here, each person in charge shares information by disclosing the plan (implementation period, etc.) and implementation status (progress rate, etc.) for the tasks for which he or she is responsible. Each person in charge must estimate the possibility of delays in each task and the scale of the delay based on the progress of the tasks that affect him or her, and must respond to the estimated delays promptly. Here, when the frequency of updating the progress corresponding to the ongoing task is relatively low, it is considered that the ongoing task has a risk of delay. However, the technology disclosed in Patent Document 1 has a problem that when the frequency of updating the progress corresponding to the ongoing task is relatively low, the ongoing task has a risk of delay not being detected. The present disclosure aims to detect a risk of delay in an ongoing task when the frequency of updates to the progress of an ongoing task is relatively low in a technology for managing the progress of system development. [Means for solving the problem]

[0005] The progress management device according to the present disclosure comprises: 1. A progress management device for managing a progress of a system development based on progress corresponding to each task input by a person in charge of each task in the system development, comprising: a delay risk calculation unit that determines whether or not there is a risk of delay in the ongoing task based on the number of times a target person in charge of the ongoing task, which is a task in the system development and is an ongoing task, inputs progress corresponding to the ongoing task. Equipped with. Effect of the Invention

[0006] According to the present disclosure, the delay risk calculation unit determines whether or not there is a risk of delay in an ongoing task based on the number of times a target person inputs progress corresponding to the ongoing task. Therefore, according to the present disclosure, in a technology for managing the progress of system development, it is possible to detect a delay risk in an ongoing task when the frequency with which progress corresponding to the ongoing task is updated is relatively low. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 shows an example of the configuration of a progress management system 90 according to a first embodiment. [Diagram 2] FIG. 2 is a diagram for explaining the operation of a progress management system 90 according to the first embodiment. [Diagram 3] 1 is a diagram showing an example of the configuration of each device included in a progress management system 90 according to a first embodiment. [Figure 4] 4 is a flowchart showing the operation of a progress input flow according to the first embodiment. [Diagram 5] 11 is a flowchart showing an input result calculation flow for an ongoing task according to the first embodiment. [Figure 6] FIG. 4 is a diagram for explaining an input result calculation flow according to the first embodiment. [Figure 7] FIG. 13 is a diagram showing an example of a hardware configuration of a progress management device 100 according to a modification of the first embodiment. [Figure 8] 13 is a flowchart showing an input result calculation flow for a completed task according to the second embodiment. [Figure 9] 13 is a flowchart showing an input result calculation flow for an ongoing task according to the second embodiment. [Figure 10] FIG. 11 is a diagram for explaining an input result calculation flow according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] In the description of the embodiments and the drawings, the same elements and corresponding elements are given the same reference numerals. Descriptions of elements given the same reference numerals are omitted or simplified as appropriate. Arrows in the drawings primarily indicate data flow or processing flow. In addition, "part" may be read as "circuit," "step," "procedure," "processing," or "circuitry" as appropriate.

[0009] Embodiment 1 Hereinafter, the present embodiment will be described in detail with reference to the drawings.

[0010] ***Configuration Description*** Fig. 1 shows an example of the configuration of a progress management system 90 according to this embodiment. As shown in Fig. 1, the progress management system 90 includes a progress management device 100 and a plurality of user terminals 200. The progress management device 100 and each user terminal 200 are communicatively connected via a network. The progress management device 100 and the user terminals 200 may be configured integrally as appropriate.

[0011] As a specific example, the progress management system 90 is a system that has a function of allocating necessary resources (workers, computing resources, etc.) to each test in the testing process of system development, and manages and shares the influence of delays, etc. based on the relationship between each test. Here, the system being developed is a system that includes software. Each of the multiple persons in charge inputs and manages information (such as implementation period and progress) of the task for which he or she is in charge in the progress management system 90. A task specifically refers to each test item in a test process. In the progress management system 90, each person in charge can check the implementation status of other tasks that may affect the start of the task for which he / she is responsible before the start of the test for that person. Also, each person in charge can check the impact that the implementation status of the task for which he / she is responsible has on the tasks of other people during the test for that person.

[0012] The progress management device 100 detects the risk of delay for each task based on the input record (frequency) of progress corresponding to each task. The delay risk for a certain task is the risk that the certain task will be delayed. If there is a risk of delay for a certain task, there is a possibility that the certain task will not be completed as planned. The progress management device 100 manages the progress of the system development based on the progress corresponding to each task input by the person in charge of each task in the system development.

[0013] The user terminal 200 is a terminal for each person in charge to input progress corresponding to each task for which the person in charge is in charge and to confirm the progress corresponding to each task. The user terminal 200 is, as a specific example, a PC (Personal Computer) or a tablet terminal.

[0014] 2 is a diagram for explaining a specific example of the operation of the progress management system 90. This example will be explained below. In the progress management system 90, in order to smoothly advance the testing process, each person in charge inputs information related to the test and shares the results of comparing the input information. First, each person in charge inputs information about the test for which he / she is in charge into each user terminal 200. The test information is, for example, information indicating the implementation schedule, progress, and delay or risk of delay. Each user terminal 200 transmits the input information to the progress management device 100. Next, the progress management device 100 receives information from each user terminal 200, analyzes the received information, and transmits information indicating the analysis result to each user terminal 200. Next, each user terminal 200 receives information from the progress management device 100 and displays the received information on the screen of each user terminal 200. In this example, each user terminal 200 displays the relationships between the tasks using a directed graph. At this time, each user terminal 200 displays that there is a risk of delay in task T1 and that a delay has occurred in task T4. Next, based on the information displayed on each user terminal 200, each person in charge considers the need to modify the plan in response to the delay and the risk of delay.

[0015] FIG. 3 shows an example of the configuration of each device included in the progress management system 90. As shown in FIG. 3, the progress management device 100 includes, as functional components, an input unit 110, a data accumulation unit 120, an input record analysis unit 130, and a delay risk calculation unit 140. The user terminal 200 includes an input unit 210 and a display unit 220 .

[0016] The input section 110 includes a plan input section 111 and a progress input section 112 . The plan input unit 111 receives information indicating a plan for executing each task. The progress input unit 112 receives information indicating the progress corresponding to each task.

[0017] The data accumulation unit 120 appropriately stores the information received by each of the plan input unit 111 and the progress input unit 112 in the storage 13. In addition, the data accumulation unit 120 stores data indicating the input results of the progress corresponding to each task in an input results database (DB) 121. As a specific example, the input record DB 121 holds the number of times progress corresponding to each task is input as data related to the implementation status of each task. The input record DB 121 may hold information indicating a period in which there is no input operation of progress corresponding to each task analyzed by the data accumulation unit 120 as information related to the implementation status of the task. As a specific example, the data held in the input record DB 121 is used for calculating a delay risk, etc. As a specific example, the input record DB 121 is realized by the storage 13.

[0018] The input record analysis unit 130 includes a progress analysis unit 131 and an input frequency analysis unit 132 . The progress analysis unit 131 refers to the plan and progress corresponding to each task, and analyzes the difference between the plan and progress corresponding to each task. The input frequency analysis unit 132 analyzes the frequency with which progress information corresponding to each task is input. The input frequency analysis unit 132 may analyze a period during which no input operation for the progress information corresponding to each task is performed.

[0019] The delay risk calculation unit 140 judges whether or not there is a risk of delay in the ongoing task based on the number of times that the target person in charge of the ongoing task has input progress corresponding to the ongoing task. The ongoing task is a task in system development that is not completed and is in progress. As a specific example, the delay risk calculation unit 140 calculates the delay risk of each task based on the analysis results of the progress analysis unit 131 and the input frequency analysis unit 132, and transmits data indicating the calculated delay risk to each user terminal 200. The delay risk calculation unit 140 may determine that there is a risk of delay in the ongoing task when the ratio of the cumulative number of days that the target person in charge has input progress corresponding to the ongoing task to the cumulative number of days that the target person in charge has performed the ongoing task is equal to or less than a delay reference ratio. The delay reference ratio may be determined in any manner. The delay risk calculation unit 140 may detect the delay risk from the total number of times progress is input, the pace at which progress is input, the ratio of the period during which progress is input to the period during which progress is not input, or the like. The delay risk calculation unit 140 may determine that there is a delay risk when there has been no progress input operation for a certain period of time.

[0020] The input unit 210 receives input of progress corresponding to each task from the person in charge. The display unit 220 displays the data received from the progress management device 100 .

[0021] 3, the progress management device 100 is a computer including hardware such as a processor 11, a memory 12, a storage 13, and a communication interface 14. These hardware components are appropriately connected via signal lines. The progress management device 100 may be composed of multiple computers.

[0022] The processor 11 is an integrated circuit (IC) that performs arithmetic processing and controls the hardware of the computer. Specific examples of the processor 11 include a central processing unit (CPU), a digital signal processor (DSP), and a graphics processing unit (GPU). The progress management device 100 may include a plurality of processors that replace the processor 11. The plurality of processors share the role of the processor 11.

[0023] The memory 12 is typically a volatile storage device, and a specific example is a random access memory (RAM). The memory 12 is also called a primary storage device or a main memory. Data stored in the memory 12 is saved in the storage 13 as necessary.

[0024] The storage 13 is typically a non-volatile storage device, and specific examples thereof include a read only memory (ROM), a hard disk drive (HDD), or a flash memory. Data stored in the storage 13 is loaded into the memory 12 as necessary. The memory 12 and the storage 13 may be integrated.

[0025] The communication interface 14 is a receiver and a transmitter, and is, for example, a communication chip or a network interface card (NIC).

[0026] The storage 13 stores a progress management program. The progress management program is a program that causes a computer to realize the functions of each unit included in the progress management device 100. The progress management program is loaded into the memory 12 and executed by the processor 11. The functions of each unit included in the progress management device 100 are realized by software.

[0027] Data used when executing the progress management program and data obtained by executing the progress management program are appropriately stored in a storage device. Each part of the progress management device 100 appropriately uses a storage device. As a specific example, the storage device is composed of at least one of the memory 12, the storage 13, a register in the processor 11, and a cache memory in the processor 11. Note that the terms "data" and "information" may have the same meaning. The storage device may be independent of the computer. The functions of the memory 12 and the storage 13 may be realized by other storage devices.

[0028] The progress management program may be recorded in a computer-readable non-volatile recording medium. Specific examples of the non-volatile recording medium include an optical disk and a flash memory. The progress management program may be provided as a program product. The hardware configuration of the user terminal 200 may be similar to the hardware configuration of the progress management device 100 .

[0029] ***Explanation of Operation*** The operation procedure of the progress management device 100 corresponds to a progress management method. Also, the program that realizes the operation of the progress management device 100 corresponds to a progress management program.

[0030] 4 is a flowchart showing an example of a progress input flow, which will be described with reference to FIG.

[0031] (Step S101) Each person in charge inputs the progress corresponding to the task for which he / she is in charge into the user terminal 200. At this time, each person in charge may input the progress rate of each task, or may select the completed test item from a list showing the test items corresponding to each task. The input unit 210 transmits the input information indicating the progress to the progress management device 100.

[0032] (Step S102) The data accumulation unit 120 measures the number of times the progress corresponding to each task has been input based on the input record of the progress corresponding to each task, and stores data indicating the measured number of times of input in the input record DB 121 for each task.

[0033] Fig. 5 is a flowchart showing an example of an input record calculation flow for an ongoing task. The input record calculation flow will be described with reference to Fig. 5. Hereinafter, an ongoing task is each task corresponding to data stored in the input record DB 121, and each task that is in progress.

[0034] (Step S111) The input frequency analysis unit 132 calculates the progress input result as a ratio obtained by dividing the number of days on which progress input corresponding to the ongoing task was made by the number of working days.

[0035] (Step S112) If the progress input result calculated in step S111 is greater than the certain ratio, the progress management device 100 ends the processing of this flowchart. Otherwise, the progress management device 100 proceeds to step S113.

[0036] (Step S113) The delay risk calculation unit 140 adds information indicating a delay risk to the information indicating the ongoing task, and transmits to the user terminal 200 the information indicating the ongoing task to which the information indicating the delay risk has been added.

[0037] FIG. 6 shows a specific example of the input result calculation flow. The delay risk calculation unit 140 determines that there is a delay risk for an ongoing task when the input frequency of the progress rate corresponding to the ongoing task does not meet a certain standard. Here, the percentage of the number of days on which the progress rate is input corresponds to the input frequency, and the certain standard is 70%. Also, it is assumed that the person in charge of the ongoing task inputs the progress rate corresponding to the ongoing task once a day. Note that if the person in charge inputs the progress rate multiple times on a certain day, the number of times the progress rate was input on that certain day may be regarded as one. In this example, it is currently the 12th day since the start of the ongoing task, and the progress rate corresponding to the ongoing task has been input for a total of 7 days out of a total of 11 past work days. Therefore, the ratio of input days is about 64%, which does not meet a certain standard. Therefore, the delay risk calculation unit 140 determines that there is a delay risk in the ongoing task. Here, if the input of the progress corresponding to the ongoing task does not meet a certain standard, it is considered that there is a possibility that a problem that will cause a delay in the ongoing task has occurred. 6, the number of times the progress rate has been input is 7. The delay risk calculation unit 140 may determine the presence or absence of a delay risk based only on the number of times the progress rate has been input, ie, 7.

[0038] ***Explanation of the Effects of the First Embodiment*** According to this embodiment, when progress corresponding to a task for which a certain person is in charge is not input, the delay risk of the task is detected based on the frequency of input of progress corresponding to the task. Therefore, according to this embodiment, each person in charge can grasp the delay risk of the task for which he / she is in charge even if other people in charge input progress infrequently.

[0039] ***Other configurations*** <Variation 1> FIG. 7 shows an example of the hardware configuration of the progress management device 100 according to this modified example. The progress management device 100 includes a processing circuit 18 in place of the processor 11 , the processor 11 and memory 12 , the processor 11 and storage 13 , or the processor 11 , memory 12 , and storage 13 . The processing circuitry 18 is hardware that realizes at least a portion of each unit of the progress management device 100. The processing circuitry 18 may be dedicated hardware, or may be a processor that executes programs stored in the memory 12 .

[0040] When processing circuitry 18 is dedicated hardware, processing circuitry 18 may be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof. The progress management device 100 may include a plurality of processing circuits that replace the processing circuit 18. The plurality of processing circuits share the role of the processing circuit 18.

[0041] In the progress management device 100, some of the functions may be realized by dedicated hardware, and the remaining functions may be realized by software or firmware.

[0042] Processing circuitry 18 is illustratively implemented in hardware, software, firmware, or a combination thereof. The processor 11, memory 12, storage 13, and processing circuit 18 are collectively referred to as the “processing circuitry.” In other words, the functions of the functional components of the progress management device 100 are realized by the processing circuitry. The progress management device 100 according to other embodiments may also have a similar configuration to this modified example.

[0043] Embodiment 2 The following mainly describes the differences from the above-described embodiment with reference to the drawings.

[0044] ***Configuration Description*** The configuration of the progress management system 90 according to the present embodiment is similar to the configuration of the progress management system 90 according to the first embodiment. The input frequency analysis unit 132 according to this embodiment analyzes the input tendency of each person in charge based on the progress input record by each person in charge for the tasks completed by that person. Specific examples of the input tendency of the progress are the frequency of inputting the progress, the time period in which the progress is input, or the maximum value of the interval between two consecutive progress inputs. The delay risk calculation unit 140 according to this embodiment judges whether there is a risk of delay in an ongoing task based on a comparison between the progress input tendency of a target person in a task that the target person has previously completed in system development and the progress input tendency of the target person in an ongoing task. A specific example of the input tendency is input frequency. As a specific example, the delay risk calculation unit 140 judges that there is a delay risk in the ongoing task that each person is in charge of when the progress input tendency of each person in charge for the ongoing task is inferior to the progress input tendency of each person in charge by a certain level or more.

[0045] ***Explanation of Operation*** The progress input flow according to this embodiment is similar to the progress input flow according to embodiment 1. The differences from embodiment 1 will be described below.

[0046] (Step S102) The data accumulation unit 120 appropriately stores information used by the input frequency analysis unit 132, such as the number of inputs as well as the date and time when the progress was input, in the input record DB 121.

[0047] Fig. 8 is a flowchart showing an example of an input frequency calculation flow for a completed task. The input frequency calculation flow will be explained with reference to Fig. 8. A completed task is each task corresponding to data stored in the input record DB 121, and each task that has been completed.

[0048] (Step S201) The input frequency analysis unit 132 extracts the implementation period of the completed task. The implementation period is, for example, the number of working days.

[0049] (Step S202) The input frequency analysis unit 132 extracts the number of inputs of progress corresponding to the completed tasks during the implementation period.

[0050] (Step S203) The input frequency analysis unit 132 calculates a value obtained by dividing the number of progress inputs extracted in step S202 by a value corresponding to the implementation period as an index of the progress input frequency. Note that the index of the progress input frequency may be a value obtained by dividing a value corresponding to the implementation period by the number of progress inputs, or may be a value calculated in any other way based on the number of progress inputs and the value corresponding to the implementation period.

[0051] (Step S204) The input frequency analysis unit 132 stores the index calculated in step S203 as progress input frequency data corresponding to the person in charge who executed the completed task. Here, the progress input frequency data corresponding to a certain person indicates the progress input frequency for tasks that the certain person in charge has previously completed. As a specific example, the progress input frequency is the average value of the progress input frequencies for all or some of the tasks that the certain person in charge has previously completed.

[0052] 9 is a flowchart showing an example of an input frequency calculation flow for an ongoing task according to the present embodiment. The input frequency calculation flow will be described with reference to FIG.

[0053] (Step S211) The input frequency analysis unit 132 calculates a value by dividing the number of times the progress rate corresponding to the ongoing task is input by a value corresponding to the implementation period corresponding to the ongoing task. The implementation period corresponding to the ongoing task is, for example, the cumulative number of days for which the ongoing task is implemented.

[0054] (Step S212) If the value calculated in step S211 exceeds the progress rate input frequency indicated by the progress input frequency data corresponding to the person in charge of executing the ongoing task, the progress management device 100 ends the processing of this flowchart. Otherwise, the progress management device 100 proceeds to step S113.

[0055] Fig. 10 is a diagram for explaining the input frequency calculation flow. In Fig. 10, the input tendency of the progress rate corresponding to the completed task is shown on the left side, and the input tendency of the progress rate corresponding to the in-progress task is shown on the right side. Based on these input tendencies, the input frequency analysis unit 132 judges whether the input frequency of the progress rate corresponding to the in-progress task is lower than the input frequency of the progress rate corresponding to the completed task by a certain amount or more. The delay risk calculation unit 140 judges whether there is a delay risk for the in-progress task according to the judgment result of the input frequency analysis unit 132. As a specific example, consider a case where person A is performing task T4 after completing tasks T1 to T3. That is, consider a case where tasks T1 to T3 are each completed tasks and task T4 is an ongoing task. In this case, as a specific example, if the number of progress inputs for tasks T1 to T3 is once a day, but the number of progress inputs for task T4 is once every two days, the input frequency analysis unit 132 determines that the progress input frequency corresponding to task T4 is lower than a certain level. As a result, the delay risk calculation unit 140 determines that there is a delay risk for task T4. Here, if the progress input frequency corresponding to the ongoing task is lower than the previous input frequency of the person in charge of the ongoing task, it is considered that there is a possibility that a fault that causes a delay has occurred in the ongoing task.

[0056] ***Explanation of the Effects of the Second Embodiment*** According to this embodiment, it is possible to determine whether or not there is a risk of delay in the ongoing task for which each person is in charge, based on the past progress input tendency of each person in charge.

[0057] ***Other embodiments*** The above-described embodiments may be freely combined, or any of the components in each embodiment may be modified, or any of the components in each embodiment may be omitted. Moreover, the embodiments are not limited to those shown in the first and second embodiments, and various modifications are possible as necessary. The procedures explained using the flowcharts and the like may be modified as appropriate. [Explanation of symbols]

[0058] 11 processor, 12 memory, 13 storage, 14 communication interface, 18 processing circuit, 90 progress management system, 100 progress management device, 110 input section, 111 plan input section, 112 progress input section, 120 data accumulation section, 121 input performance DB, 130 input performance analysis section, 131 progress analysis section, 132 input frequency analysis section, 140 delay risk calculation section, 200 user terminal, 210 input section, 220 display section.

Claims

1. 1. A progress management device for managing a progress of a system development based on progress corresponding to each task input by a person in charge of each task in the system development, comprising: a delay risk calculation unit that determines whether or not there is a risk of delay in the ongoing task based on the number of times a target person in charge of the ongoing task, which is a task in the system development and is an ongoing task, inputs progress corresponding to the ongoing task. A progress management device comprising:

2. 2. The progress management device according to claim 1, wherein the delay risk calculation unit determines that there is a risk of a delay in the ongoing task when a ratio of the cumulative number of days for which the target person has entered progress corresponding to the ongoing task to the cumulative number of days for which the target person has executed the ongoing task is equal to or less than a delay reference ratio.

3. 3. The progress management device according to claim 1, wherein the delay risk calculation unit determines whether there is a risk of a delay in the ongoing task based on a comparison between the progress input tendency of the target person in tasks that the target person has previously completed in the system development and the progress input tendency of the target person in the ongoing task.

4. The progress management device according to claim 3 , wherein the input tendency is an input frequency.

5. 1. A progress management method executed by a progress management device that is a computer that manages the progress of a system development based on progress corresponding to each task input by a person in charge of each task in the system development, comprising: A progress management method in which the progress management device determines whether there is a risk of delay in an ongoing task, based on the number of times a target person in charge of an ongoing task, which is a task in the system development and is currently in progress, inputs progress corresponding to the ongoing task.

6. A progress management program executed by a progress management device that is a computer that manages the progress of a system development based on the progress corresponding to each task input by a person in charge of each task in the system development, comprising: A delay risk calculation process for determining whether or not there is a risk of delay in the ongoing task based on the number of times a target person in charge of the ongoing task, which is a task in the system development and is an ongoing task, inputs progress corresponding to the ongoing task. A progress management program that causes the progress management device to execute the above.