JP2013120579A - Work result management method, work result management program and management server related to software development - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately obtain actual work time for every work of each person in charge in a project, and to provide a work result management method, a work result management program, and a management server.SOLUTION: A project manager registers a correspondence relation of work, work results, and applications used therefor that are determined for every project, and related information among the work, to a management server. A worker registers daily progress result information to the management server. An operation history monitoring program of a terminal that is resident in a worker's terminal transmits daily terminal operation history information to the management server. The management server identifies work from the terminal operation history information of the worker using the progress result information and the related information among the work, totals terminal operation time, and thereby obtains work time for every work of each person in charge in an arbitrary period.

Description

  The present invention relates to a technique for managing the results of work hours for each work of each person in charge when performing project management such as software development.

  When performing project management, there is a need to accurately grasp the work time for each person in charge. The purpose of this is to appropriately manage the progress of work and the cost, and to improve the accuracy of future work amount estimation. As a method of measuring work time, there is a method in which the person in charge enters the work time into the system and totals it based on the entered value, but the work time input value is based on the memory of the person in charge, so it is accurate time It is difficult to grasp.

  Therefore, as a system that can manage work results regardless of the memory of the person in charge, a method of totaling work time by automatically measuring the access time to the file operated on the worker's terminal has been proposed. ing. For example, Patent Documents 1, 2 and the like.

JP 2010-39620 A JP 2009-123038 A

  However, the conventional system described above has the following problems.

  Since it is the access time to the file that is the basis of the work time on the PC, it is necessary to associate the work with the file. However, depending on the project work, there is a work that uses the application but does not involve updating the file as a product. For example, in the test process, when there are work of checklist creation and test execution, checklist creation is a product as a checklist, but test execution itself is not accompanied by a product as a file. In such a case, it is necessary to count the application startup time as work time, but there are multiple tasks that do not involve file update as described above. Since the work cannot be specified, it is difficult to grasp the work time from the start time of the application.

  Further, when performing a certain work, the work may be performed with reference to a file created in the previous process of the current work. For example, in the detailed design process, the design document of the basic design which is the previous process is referred to. Since the previous process file referenced at this time is referred to in order to accomplish the current work, it is desirable that the access time to the previous process file is counted as the current work time. However, in the case of the above-described conventional system, since the access time to the file in the previous process is associated with the work in the previous process, it is counted as the work time in the previous process, not the current work. Therefore, it is not possible to accurately grasp the work time.

  The present invention has been made in view of such circumstances, and provides a work performance management method, a work performance management program, and a management server for more accurately grasping the work time performance for each work of each person in charge in a project. This is the issue.

  One means for solving the above problem will be described. The present invention is a work performance management method for managing work performance results for each work of each person in charge in a management server connected to a manager terminal and a plurality of worker terminals via a network. The management server registers work item registration means for registering work items, applications, and deliverables in association with each other, related work registration means for registering work and work related to the work, and a schedule for the work items. Means, a means for identifying applications and files used in the personal terminal, a means for collecting the access time, and a work person registering the progress status when the person in charge performs the work. And means for counting the work time spent on the work items. The management server specifies the work corresponding to the access time of the application and the file using the progress and the related work when the work time is totaled from the access time of the application and the file in the client terminal, The work performance time for an arbitrary period is calculated by counting the time.

  ADVANTAGE OF THE INVENTION According to this invention, in software development, the precision at the time of totaling the result of the working time for every operation | work which divided the process is improved. In addition, it saves the trouble of recording the time spent by the operator and inputting it to the system.

1 is a diagram illustrating an example of the overall configuration of a computer network system 100 according to the present embodiment. It is a figure which shows the hardware structural example of the client terminal 103 which a person in charge uses. It is a figure which shows the hardware structural example of the client terminal 102 which an administrator uses. 2 is a diagram illustrating a hardware configuration example of a management server 101. FIG. It is a figure which shows the example of a data structure of the work information table 420 which the management server 101 comprises. It is a figure which shows the data structural example of the related work table 421 which the management server 101 comprises. It is a figure which shows the data structural example of the schedule table 422 which the management server 101 comprises. It is a figure which shows the data structural example of the progress performance table 423 which the management server 101 comprises. It is a figure which shows the example of a data structure of the operation performance table 424 which the management server 101 comprises. It is a figure which shows the example of a data structure of the operation history table 220 which the person in charge terminal 103 comprises. FIG. 6 is a sequence diagram illustrating an outline of processing for registering work plan information in the management server 101. FIG. 10 is a sequence diagram illustrating an overview of processing for registering progress information in the management server 101. FIG. 10 is a sequence diagram illustrating an outline of processing for registering operation history information of a person-in-charge terminal 103 in a management server 101. It is a sequence diagram which shows the outline | summary of the process which totals work results. It is a flowchart which shows the process of the operation history monitoring function 211 which the person in charge terminal 103 comprises. It is a flowchart which shows the process of the work performance totaling function 411 which the management server 101 comprises.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an example of the overall configuration of a work management system 100 that is a computer network system according to the present embodiment. The work management system 100 is configured by connecting a management server 101, an administrator terminal 102, and a plurality of person-in-charge terminals 103 to a network 104. The management server 101 holds correspondence information between work and deliverables, progress management information, and information on the daily operation time of the terminal transmitted from the person-in-charge terminal 103, and works according to a request from the administrator terminal 102 Aggregate time results. The person-in-charge terminal 103 is a terminal for the person-in-charge to perform the project work. The person-in-charge terminal 103 monitors the application operation status executed on the person-in-charge terminal 103 and transmits an operation history to the management server 101. The administrator terminal 102 is a terminal used by the project manager, registers the project definition and schedule definition in the management server 101 at the start of the project, acquires the daily work time results from the management server 101, and displays them on the screen. To do.

  FIG. 2 is a diagram illustrating a hardware configuration example of the client terminal 103 for the person in charge used by the person in charge. The person-in-charge terminal 103 can be realized by a general computer and includes a display unit 202, an input unit 203, a control unit 204 such as a CPU, a network interface unit 205, and a storage unit 201. The storage unit 201 stores a program having an operation history monitoring function 211 and an operation history transmission function 212, and an operation history table 220. Each unit is connected by a bus (BUS). The operation history monitoring function 211 is started as a resident program at the timing of login to the terminal, acquires the identification information of the person in charge from the login information, monitors the operation history of the person in charge terminal 103, and stores the application and file. History information such as access time is stored in the operation history table 220, and the operation history transmission function 212 has a function of transmitting the history information to the management server 101 at a timing such as logout from the terminal. The program may be stored in the storage unit 201 in advance, or stored in a portable storage medium that can be used by a computer, and read as necessary via a reader (not shown). Or may be downloaded from another computer connected to the network 104 as necessary and stored in the storage unit 201.

  FIG. 3 is a diagram illustrating a hardware configuration example of the administrator terminal 102 used by the administrator. The administrator terminal 102 includes a display unit 302, an input unit 303, a control unit 304, a network interface unit 305, and a storage unit 301. The storage unit 301 stores a program having a work performance inquiry function 311. Each unit is connected by a bus (BUS). In addition, the work performance inquiry function 311 acquires information about work time for each work in an arbitrary period from the management server 101 and displays it. The program may be stored in advance in the storage unit 301 or stored in a portable storage medium that can be used by a computer, and can be read as necessary via a reader (not shown). Or may be downloaded from another computer connected to the network 104 as necessary and stored in the storage unit 301.

  FIG. 4 is a diagram illustrating a hardware configuration example of the management server 101. The management server 101 includes a control unit 402, a network interface unit 403, and a storage unit 401. The storage unit 401 includes a work plan registration function 411, a progress information registration function 412, an operation record registration function 413, a program having a work record totaling function 414, a work information table 420, a related work table 421, and a schedule. A table 422, a progress record table 423, and an operation record table 424 are stored. Each unit is connected by a bus (BUS). The work plan registration function 411 is a function for the administrator to register information regarding work items at the start of the project, and has a function of updating the work information table 420, the related work table 421, and the schedule table 422. . The progress information registration function 412 is a function for the person in charge to register the progress of work at an arbitrary timing, and has a function of updating the progress record table 423. The operation record registration function 413 has a function of registering history information such as an application and file access time transmitted from the client terminal 103 in the operation record table 424. The work result totaling function 414 specifies work corresponding to the application and file registered in the operation result table 424 from the related work table 421 and the progress result table 423 according to the total period transmitted from the administrator terminal 102. The operation time for each identified operation is totaled, and the totaled result is transmitted to the administrator terminal 102. The program may be stored in the storage unit 401 in advance, or stored in a portable storage medium that can be used by a computer, and read as necessary via a reader (not shown). Or may be downloaded from another computer connected to the network 104 as necessary and stored in the storage unit 401. FIG. 5 is a diagram illustrating a data configuration example of the work information table 420 included in the management server 101. The work information table 420 is a table that holds a correspondence relationship between work, applications, and files, and is defined by the administrator as work plan information after the start of the project. As illustrated in FIG. 5, the work information table 420 stores work items 501, applications 502, and files 503 in association with each other. Here, the application 502 corresponding to the work item 501 is necessarily registered, but the file 503 is not registered in the case of a work item that does not handle a file as a product. The same application 502 can be associated with different work items 501, but the same file 503 cannot be associated with different work items 501.

  FIG. 6 is a diagram illustrating a data configuration example of the related work table 421 included in the management server 101. The related work table 421 is a table that holds a correspondence relationship between a work item and a work item that is a premise of the work item. The work item 601 and the work item that is a premise of the work item 601 are used as the related work item 602. Remember. These pieces of information are defined by the administrator as work plan information after the start of the project. A plurality of related work items 602 can be defined for the work item 601.

  FIG. 7 is a diagram illustrating a data configuration example of the schedule table 422 included in the management server 101. The schedule table 422 is a table that holds a project schedule, and after the start of the project, a person in charge and a start schedule and an end schedule for each work item are defined by the administrator as work plan information. As shown in FIG. 7, the schedule table 422 stores a work item 701, a person in charge 702, a scheduled start date 703, a scheduled end date 704, and a completion date 705 in association with each other. The completion date 705 is the date when the work is completed, and is registered by the person in charge. An operation for which the completion date 705 is not registered indicates that the operation has not been completed.

  FIG. 11 is a sequence diagram illustrating an outline of processing for registering work plan information in the management server 101, which is performed when a project is started. The administrator terminal 102 stores the correspondence between the work item, the application, and the file, the correspondence between the work item and the related work item, the work item, the person in charge, the scheduled start date, and the scheduled end date, which are input by the administrator. Work plan information including the correspondence is transmitted to the management server (step S1101). In the management server 101, the correspondence between the work item, the application, and the file acquired from the received work plan information is registered in the work information table 420 (step S1102), and the correspondence between the work item and the related work item is registered in the related work table. Registered in 421 (step S1103), and the correspondence between the work item, the person in charge, the scheduled start date, and the scheduled end date is registered in the schedule table 422 (step S1104).

  FIG. 8 is a diagram illustrating a data configuration example of the progress record table 423 provided in the management server 101. The progress result table 423 is a table that holds the progress status for each work item, and the daily progress status is registered by the person in charge. As illustrated in FIG. 8, the progress record table 423 stores a work item 801, an update date 802, and a progress rate 803 in association with each other. Here, the progress rate 803 indicates the degree of progress of each work, and the ratio of the implemented man-hour to the planned man-hour of each work is expressed as a percentage.

  FIG. 12 is a sequence diagram illustrating an outline of processing for registering work progress information in the management server 101 that is performed daily by a person in charge. The person-in-charge terminal 103 transmits, to the management server 101, progress information including the work item, the update date for the work item, and the progress rate input by the person in charge (step S1201). In the management server 101, the work item, the update date, and the progress rate acquired from the received progress information are registered in the progress record table 423 (step S1202), and there is a work item whose progress rate value is 100. The completion date 905 in the corresponding record of the schedule table 422 is updated to the update date acquired from the progress information (step S1203).

  FIG. 10 is a diagram illustrating a data configuration example of the operation history table 220 provided in the person-in-charge terminal 103. The operation history table 220 is a table that holds operation history information of applications and files in the person-in-charge terminal 103, and is registered as needed by the operation history monitoring function 211. As illustrated in FIG. 10, the operation history table 220 stores 1001, a person in charge 1001, a date 1002, an application 1003, a file 1004, a start time 1005, and an end time 1006 in association with each other.

  FIG. 15 is a flowchart showing processing of the operation history monitoring function 211 provided in the person-in-charge terminal 103. The operation history monitoring function 211 is activated when the person in charge logs into the person-in-charge terminal 103, and has a function of registering the operation history of the person-in-charge terminal 103 in the operation history table 220. First, the operation history monitoring function 211 acquires the person in charge and the date from the login information (step S1501), and monitors the active state of the window of the person in charge terminal (step S1502). Next, it is determined whether or not active window switching has occurred (step S1503), and the following processing is performed to update the operation history table 220 when switching has occurred. First, the operation history monitoring function 211 acquires the system time (step S1504), and determines whether there is a record in the operation history table 220 (step S1505) in order to set an end time for the application before switching. If there is a record, the data of the end time 1006 of the last line of the operation history table 220 is updated to the system time acquired in step S1504 (step S1506). Next, the operation history monitoring function 211 acquires the active application and file name (step S1507), and acquires the application 1003 and file 1004 of the next record in the last row of the operation history table 220 in step S1507. And the file name are set, the system time acquired in step S1504 is set to the start time 1005, the person and date acquired in step S1501 are set to the person in charge 1001 and date 1002, and the record is registered (step S1508). . Thereafter, the processing from step S1502 is repeatedly executed, and the operation history of the person-in-charge terminal 103 is continuously registered until the terminal logs out.

  FIG. 9 is a diagram illustrating a data configuration example of the operation result table 424 provided in the management server 101. The operation result table 424 is a table that stores application and file operation history information, and registers data transmitted from the person-in-charge terminal 103. As illustrated in FIG. 7, the operation result table 424 stores a person in charge 901, a date 902, an application 903, a file 904, and an operation time 905 in association with each other. Here, the operation time 905 holds a value that is totaled based on the information of the start time and the end time transmitted from the person-in-charge terminal 103. In addition, when registering an operation history of an application that does not involve file update, it is registered that there is no data in the file 904.

  FIG. 13 is a sequence diagram showing an outline of processing for registering operation history information of the person-in-charge terminal 103 in the management server 101, automatically transmitted from the person-in-charge terminal 103. In the person-in-charge terminal 103, the operation history transmission function 212 is automatically activated at the timing of logout or the like, and all records in the operation history table 220 are transmitted from the person-in-charge terminal 103 to the management server 101 (step S1301). In the management server 101, the operation record registration function 413 extracts a record in which the application 1003 matches the application 502 registered in the work information table 420 from all the records in the operation history table 220 received from the person-in-charge terminal 103 ( In step S1302, the operation time is calculated from the end time 1006 and the start time 1005 for all the extracted records (step S1303), and the person in charge 1001, the date 1002, the application 1003, and the file 1004 are calculated. The operation time is associated with each other and registered in the operation result table 424 (step S1304).

  FIG. 14 is a sequence diagram illustrating an outline of processing in which an administrator totals work results. The administrator terminal 102 transmits the total period including the total start date and the total end date input by the administrator to the management server 101 as a total condition (step S1401). In the management server 101, a record in which the date 902 is within the counting period is extracted from the operation result table 424, and work items corresponding to the application 903 and the file 904 of the extracted record are related to the work information table 420 and the progress result table 423. The work table 421 is specified, and the operation time 905 for each work item is totaled for each person in charge 901 (step S1402). The work item identification and work performance totaling processing in step S1402 is performed by the work performance totaling function 414 provided in the management server 101. Details of the processing will be described later with reference to FIG. Next, the results totaled in step S1402 are transmitted to the administrator terminal 102 (step S1403).

  FIG. 16 is a flowchart of the work performance totaling function 414 provided in the management server 101. The work performance totaling function 414 is executed when a work performance totaling request is received from the administrator terminal 102 in the totaling period including the totaling start date and the totaling end date. The work result totaling function 414 returns data in which the person in charge, the work item, and the work result total time are associated with each other as the total result. First, the work performance totaling function 414 reads from the operation result table 424 the totaling start date (2011/6/20 in this example) that the date 902 received from the administrator terminal 102 and the totaling end date (in this example). The record that is between 2011/6/20 is extracted (step S1601). The following processing is repeated for the number of records extracted in step S1601 (1 in this example) (step S1602). The work result totaling function 414 searches the work information table 420 based on the application 903 (A0003 in this example) and the file 904 (no value in this example) acquired from the extracted record, and the work item 501 is obtained from the corresponding record. (Step S1603, 4444 in this example). The work result totaling function 414 determines the number of search results (1 in this example) in step S1603 (step S1604), and if the search result is 0, the work information is determined not to be a project work. Then, the value is not added to the total result (step S1612), and the process proceeds to the next record (step S1613). If there are one or more search results, work identification processing is performed based on the work item acquired in step S1603. First, using the date 902 (2011/6/20 in the present example) of the extracted record as the aggregation target date, it is checked whether there is a progress record of the work item acquired in step S1603 on the aggregation target date. The tabulation function 414 searches the progress record table 423 for a record in which the update date 802 matches the tabulation target date, and extracts a task item in which the task item 801 in the search result record matches the task item acquired in step S1603 (step S1603). S1605, no corresponding record in this example). The work result totaling function 414 determines the number of extraction results (0 in this example) in step S1605 (step S1606). If the number of extraction results is one or more, the person in charge of the totaling result and the work item are displayed in steps. The operating time 905 acquired from the record extracted in step S1601 is added to the total work time of the data that matches the person in charge 901 acquired from the record extracted in S1601 and the work item acquired in step S1603 (step S1611), The process moves to the next record (step S1611). If the extraction result is 0, there is a possibility that the work based on the work item acquired in step S1603 may have been performed. Therefore, the work item acquired in step S1603 is related work item 602 from the related work table 421. Are searched for (step S1607, 5555 and 6666 in this example). The number of search results in step S1607 (2 in this example) is determined (step S1608). If the search result is 0, it is determined that the work item acquired in step S1603 is not a project work, and the total result (Step S1612), the process proceeds to the next record (step S1613). If the number of search results is one or more, the work item acquired in step S1607 is set as a candidate for the work item actually performed. In order to check whether or not there is a progress record of the aggregation target date with respect to the work item candidate, a record whose update date 802 matches the aggregation target date is searched from the progress record table 423, and the work item 801 of the search result record is retrieved. Extracts a work item that matches the work item acquired in step S1607 (step S1609, 6666 in this example). The number of extraction results (1 in this example) in step S1609 is determined (step S1610), and if the extraction result is 0, it is determined that the work item acquired in step S1607 is not a project work, and the total result (Step S1612), the process proceeds to the next record (step S1613). If the number of extraction results is one or more, the person in charge and the work item of the total result match the person in charge 901 acquired from the record extracted in step S1601 (ah in this example) and the work item acquired in S1607. The operation time 905 (2 in this example) acquired from the record extracted in step S1601 is added to the total work performance time (step S1611), and the process proceeds to the next record (step S1611). Through the above processing, a totaling result (in this example, the person in charge is ah, the work item is 6666, and the work actual total time is 2) is obtained.

  The embodiment of the present invention has been described above. According to the said Example, the track record of the working time for every work of each person in charge in a project can be grasped | ascertained correctly.

  The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the invention.

DESCRIPTION OF SYMBOLS 101 ... Management server, 102 ... Manager terminal, 103 ... Person in charge terminal, 104 ... Network, 201, 301, 401 ... Storage part, 202, 302 ... Display part, 203 , 303... Input unit, 204, 304, 402... Control unit, 205, 305, 403.

Claims (3)

In the management server connected to the terminal for managers and the terminals for multiple workers via the network, a work performance management method for managing the performance of the work time for each work of each person in charge,
Register the work item, application, and file correspondence received from the manager terminal in the work information table,
Register the correspondence between the work item received from the manager terminal and the related work item in the related work table,
Register the correspondence between the work item, the person in charge, the scheduled start date and the scheduled end date received from the manager terminal in the schedule table,
Register the progress record information consisting of the work item received from the worker terminal, the update date, and the progress rate in the progress record table,
Based on the terminal operation history information received from the worker terminal, the person in charge, the date, the application, the file, and the operating time are registered in the operating result table,
Receiving a counting period including a counting start date and a counting end date from the manager terminal;
A work item corresponding to the application and file of the record whose update date of the operation result table is within the aggregation period is specified from the work information table, the related work table, and the progress result table,
By associating the identified work item and the operation time of the operation result table, and summing up for each work item, the total value of the work time for each work item for each person in charge is obtained,
To the manager terminal, to send the total result of the work time for each work item for each person in charge carried out during the total period,
A work performance management method characterized by that.   A work performance management program for causing a computer to execute the work performance management method according to claim 1. A management server that is connected to a manager terminal and a plurality of worker terminals via a network, and is a management server that manages the results of work hours for each person's work,
Means for registering the correspondence between work items, applications, and files received from the manager terminal in a work information table;
Means for registering the correspondence between the work item received from the manager terminal and the related work item in the related work table;
Means for registering the correspondence between the work item, the person in charge, the scheduled start date and the scheduled end date received from the manager terminal in the schedule table;
Means for registering the progress record information including the work item received from the worker terminal, the update date, and the progress rate in the progress record table;
Based on the terminal operation history information received from the worker terminal, means for registering the person in charge, the date, the application, the file, and the operation time in the operation result table;
Means for receiving a counting period including a counting start date and a counting end date from the manager terminal;
Means for identifying a work item corresponding to an application and file of a record whose update date of the operation result table is within the counting period from the work information table, the related work table, and the progress result table;
A means for associating the identified work item with the operation time of the operation result table and calculating the total value of the work time for each work item for each person in charge by totaling each work item;
Means for transmitting, to the manager terminal, a totaling result of work time for each work item for each person in charge carried out during the totaling period;
A management server characterized by that.

Images