JP2006195677A - Apparatus for managing project information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve accuracy of estimation of a project schedule, and to allow each person in charge to input the progress of tasks assigned. <P>SOLUTION: An apparatus for managing project information includes: a project task list creation means for creating a list of tasks to be accomplished in the project, a project progress summarization time point setting means for setting a plurality of time points for summarizing the progress of the project, a task progress input time point setting means for allowing the person in charge of the task to select a prescribed progress input time point from among the plurality of project progress summarization time points, a task progress input means for inputting the progress of the task at the task progress input time point, a project progress summarizable time point specifying means for specifying the summarizable time point of the project progress based on the progress of each task entered, and a project progress summarization means for summarizing the progress of the project at the summarizable time point of the project progress. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a project information management apparatus that inputs and summarizes tasks in a project for developing software or the like.

  In project management methodologies such as PMBOK, it is recommended to manage a list of all tasks (work and requirements) to be implemented in the project in a list with a hierarchical structure called WBS (work breakdown structure). ing.

  In general, the project progress at a certain point in time can be calculated as a result of summing up all the task progresses of the project at a certain point in time. At this time, in order to obtain a correct counting result, it is premised that the latest progress statuses of all tasks are inputted at the time of counting.

  However, in a real project, it is difficult for all task managers to complete the progress input properly on a fixed progress count date. Conventionally, a method of prompting input of task progress and measuring project progress by various methods has been devised. For example, in the “project progress management system” described in Patent Document 1, a method for requesting the latest task progress report from a person in charge has been devised.

  In addition, the “software progress management device” described in Patent Document 2 is based on the idea that it is difficult to input task progress on a fixed date. A method has been devised that can be collected and considered as task achievements.

JP 09-022429 A JP 2001-014157 A

However, in the above conventional technology example, each person in charge inputs the progress status of the task, and when it is counted as the progress of the entire project,
1) Although the degree of progress (for example,%) of each task at the time when each person in charge inputs each is input, it is not possible to determine when the degree of progress of the entire project is.

2) At the time of progress counting (for example, once every week, at a fixed time on a fixed day of the week), the progress of the entire project cannot be accurately calculated unless all the persons in charge have completed the input.
There was a problem.

  In the present invention, when inputting the progress for each task, by specifying explicitly to what point the progress is, 1) the finalization of the project at a certain point can be known, and 2) each person in charge Is given a time delay to input the progress of the task. 3) In particular, the person in charge who is late in inputting the progress can be notified.

  The purpose of the present invention is to improve the accuracy of the estimation of the project schedule by accumulating the finalization progress of the entire project at a certain point of time, and accumulating progress data at each point of time of aggregation, and each person in charge is in charge of himself / herself. It is to be able to reliably input the progress of the assigned task.

  In order to solve the above-mentioned problems, the project information management device of the present invention is capable of project task list creation means, project progress count time setting means, task progress input time setting means, task progress input means, and project progress count. Time point specifying means, project progress totaling means, task progress input confirming means, and task progress input delay notifying means are provided.

  The project progress totaling time setting means, task progress input time setting means, project progress totalable time specifying means, and project progress totaling means make it possible to know the finalization of the project at a certain time.

  Also, the task progress input time setting means and the task progress input means allow each person in charge to give time to input the task progress.

  Further, the task progress input confirming means and the task progress input delay notifying means can particularly notify a person in charge of the progress input being delayed.

  In the present invention, when inputting the progress for each task, by specifying explicitly to what point the progress is, 1) the finalization of the project at a certain point can be known, and 2) each person in charge 3) In particular, the person in charge of the progress input can be notified.

  According to the present invention, when the progress of the project is totalized in advance, and when the progress for each task is input, by specifying the time until which the degree of progress is specified, The finalization progress of the project can be calculated.

  Another effect is that even if all current task progresses are not entered, the project confirmation progress at a specific point in the past and the estimated project progress at the present time can be calculated. Allow time to enter task progress.

  Furthermore, when the progress of a project at a specific time is aggregated, by detecting which task's progress input is delayed, it becomes possible to notify a person in charge of the progress input being delayed.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

<Embodiment 1>
[System configuration]
A server computer (hereinafter referred to as a server) and each client computer (hereinafter referred to as a client) of a project information management system (hereinafter referred to as the system) according to Embodiment 1 of the present invention have the same hardware configuration, and FIG. FIG.

  In FIG. 1, 101 is a CPU, 102 is a main memory, 103 is a ROM, 104 is a display interface (I / F), 105 is a monitor, 106 is an input I / F, 107 is a keyboard, 108 is a mouse, 109 is a disk I / F, 110 is a hard disk drive (HDD), 111 is a floppy disk drive (FDD), 112 is a network I / F, 113 is a LAN, and 114 is a system bus.

  The server and each client are connected to the LAN 113 via the network I / F 112, and exchange necessary data with the present system operating on the server.

[Operation procedure]
Programs and data of this system are stored in the HDD 110 or the FDD 111 on the server on which the system operates, and are taken into the main memory 102 via the disk I / F 109. When programs and data are stored in the ROM 103, they are read from the ROM 103 into the main memory 102. The CPU 101 accesses the main memory 102 and operates the program.

  The user inputs or instructs necessary information using the keyboard 107 or the mouse 108 of the client in accordance with an instruction on a screen of a Web browser or the like displayed on the client monitor 105. The input data is transmitted to the CPU 101 via the client input I / F 106 and transmitted to the server via the network I / F 112 and the LAN 113. The result processed by the server is transmitted to the client again via the network I / F 112 and the LAN 113, and displayed on the screen of the client monitor 105 such as a Web browser.

[Aggregation of project progress]
FIG. 2 is a flowchart showing the operation procedure of the present invention.

  First, a project leader (hereinafter referred to as a leader) creates a task list to be achieved in the project (S101: project task list creation means).

  FIG. 3 shows an example of a project task list.

  The task list is created with general-purpose spreadsheet software (hereinafter referred to as software) such as Microsoft Excel, general-purpose project management software such as Microsoft Project, or original software having functions equivalent to these, and stored in a database on the server. . The task list may be appropriately hierarchized for classification. In particular, when the task list is hierarchized, a terminal task without a child node is called a leaf task. For each leaf task, the leader assigns a task person (hereinafter, person in charge). Each task has a scheduled start date.

  The leader sets in advance a plurality of time points (project progress time points, or simply referred to as a total date) at which the project progress is to be totaled for each project (S102: project progress total time point setting means).

  For example, it is set on the 1st and 15th of every month, and set on every Monday.

  In the following, for the sake of simplicity, it is assumed that the project progress count time is set on the 1st and 15th of each month, and the progress of the task is entered as a percentage, and is currently assumed to be June 10, 2004. To do.

  Each person in charge must input the degree of task progress at the time when all the project progresses are totaled during the period from the start of the task to the completion of the task.

  For example, a task that has not yet reached the scheduled start date, such as tasks T11 and T12 in FIG. In addition, as with tasks T21 and T22, a task that has already been completed before the previous project progress count time (June 1) does not need to be input after that.

  Each person in charge, when inputting the progress of the task, selects one of a plurality of project progress aggregation time points to which task progress is to be input (referred to as task progress input time). (S103: task progress input time setting means).

  Next, each person in charge inputs the progress of the task at the task progress input time selected in S103 (S104: task progress input means).

  For example, when inputting the task progress at the time of the next project progress aggregation (June 15) of task T24 in FIG. 3, first, the link labeled “Information” in T24 in FIG. 3 is clicked. Then, the task property screen of FIG. 4 is displayed. Items that are grayed out here are items that cannot be edited by the person in charge of the task.

  At T24, the task progress up to the previous project progress count (June 1) has already been entered, so the task manager selects “2004/6/15 (next count date)” and then the progress is shown. Enter it. In the status column, the display may change automatically such as “Unstarted”, “Started”, “Completed” etc. in conjunction with the progress, and the task person in charge inputs it independently of the progress Also good.

  When you enter a confirmed value as the task progress until the next aggregation date (June 15), if you check the “Confirmed progress” check box at the same time, you can enter the progress that is still in progress. You can tell whether it is a value that is in the middle of the process, or a fixed value that does not change the task progress by the next aggregation date.

  The progress of a task can be entered as a percentage value or as an integer value from 0 to 5, for example. For example, when the software development task progress is entered as a percentage, it has not yet started (0%), started (20%), design completed (40%), implementation completed (60%), unit test completed (80%) It is necessary to determine progress guidelines according to the status such as completion (100%) for each project or organization.

  As another example, when inputting the task progress of task T23 in FIG. 3, first, the link labeled “Information” in T23 in FIG. 3 is clicked. Then, the task property screen of FIG. 5 is displayed. For this task, since the task progress at the time of the previous project progress aggregation (June 1) has not been entered, the person in charge of the task has selected “2004/6/1 (previous aggregation date)” in FIG. The progress at the time of the previous aggregation date must be entered, and the task progress at the time of the next project progress aggregation (June 15) must also be entered.

  In addition, the meaning of each button of the upper part of FIG.4 and FIG.5 is as follows.

  1) Apply: When this button is pressed in the editing state, data is saved.

  2) Edit (or EditEnd): When the task property screen is opened, it is in an edit-disabled state (display only). At this time, if the “Edit” button is pressed, each property is in an editable state, and the button display is changed to “EditEnd”. change. When the “EditEnd” button is pressed in the editable state, the editable state is restored.

  3) Close: Close the task property screen.

  In the project task list of FIG. 3, it is easy to understand if the progress input status of each task is displayed in different colors. For example, the task T23 is displayed in red because the confirmed progress input date (May 15) has passed the previous aggregation date. Since the progress input deadline (June 1) has passed, this is also displayed in red. Since T25 is a task that has already passed the previous aggregation date (June 1) but has not yet started, the status, scheduled start date, and confirmed progress input date are displayed in red. Tasks that are currently in progress (the scheduled start date has passed and have not been completed as of the previous aggregation date) are displayed in blue, and tasks that should be entered by the next aggregation date (June 15) It is. In FIG. 3, tasks that are currently in progress during this period and tasks completed during this period are further color-coded in green.

  Each time the project progress count comes, the system will schedule all the planned tasks for the project (for example, about two days after the project progress count) (scheduled tasks are planned to have some progress up to that point). That is, that is, a task that has passed the scheduled start date). Then, a time point at which the project progress can be tabulated is identified (S105: Project progress tabular time point identifying means).

  This specifying method is as follows.

  1) At each project progress calculation point, check whether the progress of all scheduled tasks up to that point has been entered.

  2) Find the task with the most delayed input of scheduled tasks, and determine the task progress input time as the project progress totalable time.

  In the example of FIG. 3, if there is no task progress input until the next project progress calculation time point (June 15), the project progress until May 15 of the scheduled task T23 with the latest progress input is confirmed. .

  However, since there is only one task whose progress input is delayed, the project progress cannot be calculated, so the project progress at the time of project progress aggregation (unestablished estimated value because there are unentered persons) It can be calculated by assuming that the delayed task has no change in progress.

  Then, the system totals the progress of the entire project at the specified project progress totaling possible time (S106: project progress totaling means).

For the sake of simplicity, assuming that the tasks of the project are all 10 tasks T11 to T12 and T21 to T28 displayed in FIG. The project progress is as shown in FIG. As already illustrated, since the progress input on June 1 of T23 and the progress input on June 15 of T23, T24, T25, and T28 have not been confirmed, the project progress is also on June 1 and June 15. For days, this is an uncertain estimate. In FIG. 6, a “?” Mark is described after the numerical value. The calculation is simply
Total progress (%) of each task / total number of tasks in the project ... (Formula 1)
May be calculated for each project progress aggregation time point.

[Notification of progress input delay]
In S105, the system has specified a time point at which the project progress can be totaled “after” the project progress time point, but “before” the project progress time point (for example, about one day before the project progress time point). Then, the process of S105 is performed, and a “scheduled” task for which the confirmed progress up to the next counting date (June 15 in the example) has not been input at this time is extracted (S107: task progress input confirming means).

  Then, the system notifies the person in charge of these tasks that the task progress has not been input (S108: task progress input delay notification means).

  Notification methods include sending an e-mail directly to the person in charge, displaying on a portal site where the person in charge usually logs in first, and so on.

<Other embodiments>
The order of the processing of S101 and the processing of S102 in FIG. That is, the project progress calculation time point may be determined for each project first, and then a project task list may be created.

It is a block diagram which shows the hardware constitutions of the project information management system which concerns on Embodiment 1 of this invention. It is a flowchart which shows the process sequence of the project information management system which concerns on Embodiment 1 of this invention. It is a figure which shows the example of the screen which displays a project task list. It is a figure which shows the example of the screen which displays and edits the task property of the task whose progress input is not delayed. It is a figure which shows the example of the screen which displays and edits the task property of the task which progress input is overdue. It is a figure which shows the example which calculated the project progress for every total time.

Explanation of symbols

101 CPU
102 Main memory 103 ROM
104 Display interface (I / F)
105 Monitor 106 Input interface (I / F)
107 Keyboard 108 Mouse 109 Disk interface (I / F)
110 HDD
111 FDD
112 Network interface (I / F)
113 LAN
114 System bus

Claims (3)

  Project task list creation means for creating a list of tasks to be achieved in the project, project progress count time setting means for setting a plurality of time points at which the project progress should be totaled, and a task person in charge from the plurality of project progress time points A task progress input time setting means for selecting a specific progress input time, a task progress input means for inputting a task progress at the task progress input time, and a project progress based on the input progress of each task. A project information management apparatus comprising: a project progress totaling time specifying unit for specifying a totalable time point; and a project progress totaling unit for totalizing a project progress at the project progress totaling time point.   Task progress input confirmation means for confirming whether or not the task progress at the time of specific project progress aggregation has been input, and task progress input delay notification means for notifying the task staff that task progress has not been entered. The project information management apparatus according to claim 1, further comprising:   2. The project information management apparatus according to claim 1, wherein the project progress totalable time specifying means determines a task progress input time of a task that is most delayed in task progress input as a project progress totalable time.

Images