JP6102477B2 - Schedule management program, schedule management method, and schedule management apparatus - Google Patents

Description

  The present invention relates to a schedule management program, a schedule management method, and a schedule management apparatus.

  In recent outsourcing services, etc., business negotiations have become smaller and shorter, and there are cases where one person is in charge of multiple projects in parallel. A project consists of a plurality of processes, and personnel of the organization are assigned to each project, and each work is carried out according to a plan.

  If a plurality of projects are advanced in parallel, the progress management and task management of the project become complicated, and there is a risk of delay in delivery and quality deterioration (or excessive quality). Therefore, there is a tool for scheduling a schedule for each process in order for each person in charge to proceed the work on each project as scheduled (see Patent Documents 1 to 3).

Japanese Patent Laid-Open No. 7-21264 JP 62-26510 A JP-A-4-69136

  However, in the conventional project management tool, since all tasks are expressed in parallel, it is difficult to determine the work execution order. For example, inexperienced personnel or when a plurality of projects are running in parallel and schedule management is complicated, there is a possibility that an appropriate decision cannot be made and work delays and man-hours increase.

  In one aspect, the present invention aims to realize appropriate schedule management.

The schedule management program according to one aspect calculates a remaining work man-hour until the delivery date of the task by using an average lead time and a shortest lead time obtained from past results corresponding to one or a plurality of projects having at least one task. The schedule of the project is created using the shortest lead time, and the earliest start date and the latest start date of the task in the created schedule and information on other related tasks executed earlier or later are used. , Determining a priority according to the execution order of the tasks, and causing the computer to execute a process of detecting the task that is delayed based on the determined tasks in the priority order and the remaining man-hours.

  Appropriate schedule management can be realized.

It is a figure which shows the system configuration example of a schedule management system. It is a figure which shows an example of the hardware constitutions of a schedule management apparatus. It is a flowchart which shows an example of the project starting process of a schedule management apparatus. It is a flowchart which shows an example of the execution condition management process of a schedule management apparatus. It is a flowchart which shows an example of the delay notification corresponding | compatible process of a schedule management apparatus. It is a flowchart which shows an example of the list display process of a schedule management apparatus. It is a figure which shows an example of a task table. It is a figure which shows an example of a task execution order display. It is a figure (the 1) which shows the example of reallocation based on a buffer digestion rate. It is FIG. (2) which shows the example of reallocation based on a buffer digestion rate. FIG. 10 illustrates an example of task state transition (part 1); FIG. 10 is a second diagram illustrating an example of task state transition;

  Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

<Schedule management system: System configuration example>
FIG. 1 is a diagram illustrating a system configuration example of a schedule management system. A schedule management system 10 illustrated in FIG. 1 includes a schedule management device 11 as an example of an information processing device, and one or a plurality of administrator terminals 12-1 to 12-n (hereinafter referred to as “manager terminal 12” as necessary). And one or a plurality of person-in-charge terminals 13 (hereinafter collectively referred to as “person-in-charge terminals 13” as necessary). The schedule management device 11, the administrator terminal 12, and the person-in-charge terminal 13 are connected in a state in which data can be transmitted and received through a communication network 14 typified by the Internet, a local area network (LAN), and the like.

  The schedule management device 11 sets a work process (task), sets a work day, assigns a person in charge, etc. for a project based on a project startup instruction or the like from the manager terminal 12 used by a project manager or the like. . The schedule management device 11 manages the schedule of each person in charge.

  For example, the schedule management apparatus 11 calculates an average lead time and a shortest lead time based on the past performance of a project having at least one task, and calculates a possible buffer (remaining man-hours until delivery date) from the difference. The lead time is, for example, the time from the start of a task to the completion (delivery) of the task, but is not limited to this.

  The schedule management device 11 creates a schedule using the shortest lead time for each task. The schedule management device 11 determines the work start priority based on the earliest start date and the latest start date of each task in the project with respect to the buffer for each project. For example, ToDoList (task execution order display list, Order- To-Do List).

  Furthermore, the schedule management apparatus 11 recalculates the earliest start date and the latest start date every day in accordance with the progress of the task, and reflects it in ToDoList to detect a task that cannot be processed.

  As described above, the schedule management device 11 determines the priority of task execution based on past results, and presents the task execution order for each person in charge across projects, thereby preventing delays in delivery.

  The schedule management apparatus 11 is, for example, a personal computer (PC) or a server, but is not limited to this.

  The manager terminal 12 is a terminal used by a project manager such as a project manager as described above. The administrator terminal 12 accesses the schedule management apparatus 11 via the communication network 14 and performs work processes (tasks), schedules, work personnel assignments, and the like for executing the target project. Note that when the same information is to be changed from a plurality of administrator terminals 12, exclusive control may be performed.

  The person-in-charge terminal 13 is a terminal used by a person in charge who executes a task in each project described above. The person-in-charge terminal 13 can access the schedule management apparatus 11 via the communication network 14 to check its own progress and readjust the schedule.

  Note that the administrator terminal 12 and the person-in-charge terminal 13 are, for example, PCs, but are not limited thereto, and may be communication terminals such as a tablet terminal or a smartphone.

<Example of Functional Configuration of Schedule Management Device 10>
Next, a functional configuration example of the above-described schedule management apparatus 10 will be described with reference to FIG. The schedule management device 10 shown in FIG. 1 includes an authentication unit 20, a project management unit 21, a schedule creation unit 22, a person-in-charge assignment unit 23, an execution status management unit 24, a delay notification unit 25, and a screen generation unit. 26, storage means 27, communication means 28, and control means 29.

  In the schedule management apparatus 10, the project management means 21, the schedule creation means 22, and the person-in-charge assignment means 23 are functions for a project manager. The execution status management means 24 and the delay notification means 25 are functions for persons in charge.

  The authentication unit 20 authenticates a user who has accessed from the administrator terminal 12, the person-in-charge terminal 13, or the like, and identifies the administrator or the person in charge. For example, the authentication unit 20 refers to the authentication information stored in the storage unit 27 or the like in advance based on the authentication information such as the user ID or password input by the user via the administrator terminal 12 or the person-in-charge terminal 13 or the like. If there is information corresponding to the authentication information stored in advance, it is specified as an administrator or a person in charge set for the user, but the authentication method is not limited to this.

  If the authentication is successful, the authentication unit 20 permits access to the schedule management apparatus 10 as a corresponding administrator or person in charge. Further, when the authentication unit 20 fails in the authentication (for example, when the input authentication information is not in the pre-stored authentication information), the authentication unit 20 notifies that fact, for example, causes the authentication information to be input again. , Such as denying access.

  The project management means 21 manages one or more projects across. The project management means 21 manages the current status of one or a plurality of projects for which the manager is in charge based on, for example, the authentication information of the manager logged in from the manager terminal 12. Further, the project management means 21 manages the progress of work of each person in charge assigned to each project.

  Further, the project management means 21 determines a template for setting a project based on a project launch instruction or the like from the manager terminal 12. The project management means 21 performs project pattern selection (standard lead time, shortest lead time), project name, project start date and end date, project overview, project member registration, and the like for each project.

  Project member registration means assigning a person in charge for each task. For example, “task A-1 is in charge X”, “task A-2 is in charge Y”, and the like are set. It is not a thing. The project information set by the administrator terminal 12 is stored in the storage unit 27.

  For example, the project management means 21 calculates a buffer using an average lead time and a shortest lead time obtained from past results of one or more projects having at least one task, and the calculated buffer is a schedule creation means 22. Output to. The buffer is the remaining man-hours until the delivery date for each task, and can be obtained, for example, by the difference between the average lead time and the shortest lead time, but is not limited to this. Further, the above-mentioned past results are stored in advance in the storage means 27, for example.

  Further, the project management means 21 can perform work breakdown structure (WBS) management. WBS is one of the methods used when planning in project management, and is a configuration in which the entire project is divided into fine work. In WBS, first, the project deliverables are broken down into the smallest possible units. At this time, the whole is divided into large units, and then each part is divided into smaller units and structured hierarchically. After subdividing the deliverables, consider at least one work (task) necessary to configure each part and place them in the lowest layer. In addition, the WBS creates a work package having a series of work pieces constituting individual parts. The project management means 21 can manage one or a plurality of projects in parallel.

  The schedule creation unit 22 creates a master schedule for one or a plurality of projects set by the project management unit 21 when the project is launched. The master schedule is, for example, a list of all necessary work from the start to the completion of a project and the order of them. Each project member creates a WBS based on the master schedule described above and performs progress management.

  For example, the schedule creation unit 22 creates a master schedule of a project based on the shortest lead time based on the past performance of one or more projects having at least one task, for example.

  The schedule created by the schedule creation unit 22 is not limited to the master schedule described above, and rescheduling (reassignment) can be performed when a person in charge delays, for example.

  The person-in-charge assigning unit 23 assigns a person in charge to the scheduled schedule of each task based on the contents of the schedule and the person in charge stored in the storage unit 27 or the like in advance. The project management means 24 can create an organization chart for executing the project by assigning the person in charge by the person-in-charge assignment means 23.

  The execution status management means 24 manages the execution status of each work task for each project assigned to the person who has logged in from the person-in-charge terminal 13.

  For example, the execution status management means 24 executes at least one work among calculating the earliest start date and the latest start date, calculating the task priority, managing the work results, and the like. The execution status management unit 24 can create and display ToDoList and the like in order of task execution for each person in charge, but is not limited to this.

  For example, the execution status management unit 24 determines the priority of each task for each person in charge using the earliest start date and the latest start date of each task in each project obtained by the schedule creation unit 22. Further, the execution status management unit 24 detects a task that becomes a delay based on the tasks in the order of priority and the remaining work man-hours.

  Further, the execution status management unit 24 can change the content to be notified to the delay notification unit 25 according to the level (degree) of delay. For example, when the delay level is low, a delay notification is given only to the person in charge, and when the delay level is high, a delay notice is sent to the person in charge and the administrator. The level of the delay level can be determined by, for example, comparing with a threshold set in advance with reference to the number of days delayed, but is not limited thereto.

  When the delay notification means 25 determines that a delay has occurred by comparing the execution (progress) status of the person in charge with a preset condition, the delay notification means 25 alerts the person in charge and the administrator by the delay notification. (Warning) process. For example, the delay notification unit 25 may perform a buffer digestion rate management process for determining how much spare time (buffer) set in advance for the number of work days is consumed. The delay notification means 25 may perform an escalation process for notifying the manager terminal 12 such as a project manager to perform rescheduling or reassignment of the person in charge.

  When the person-in-charge terminal 13 accesses the delay notification means 25, if there is information to notify the person in charge corresponding to the user ID at the time of login authentication, the information may be notified. Further, when it becomes necessary to notify, the delay notification means 25 may transmit an e-mail notifying delay information to an e-mail address included in preset user information. The delay notification process is not limited to this.

  The screen generation unit 26 generates an image to be displayed on the administrator terminal 12 or the person-in-charge terminal 13, a screen layout, or the like. For example, the screen generation unit 26 generates a setting screen for displaying a template on the administrator terminal 12 when a project is launched, or generates a screen for displaying ToDoList. The screen generation means 26 generates a screen for displaying the execution status on the person-in-charge terminal 13. Furthermore, a screen for performing a person in charge at the time of delay or resetting the schedule may be generated, but the present invention is not limited to this.

  The storage unit 27 stores various types of information necessary in the present embodiment. For example, the storage unit 27 stores project management information, schedule creation information, person-in-charge assignment information, execution status, delay information, and the like. The information stored in the storage means 27 is not limited to the above-described information. For example, authentication information for authenticating a user, past work results for each person in charge, for each task, or for each project ( For example, work time (lead time), man-hours, etc. may be stored.

  The storage unit 27 reads and writes various stored information at a predetermined timing as necessary. In addition, the storage unit 27 may function as a database that is systematically configured so that such information can be searched and extracted using, for example, keywords. The storage means 27 is, for example, a hard disk or a memory.

  The communication unit 28 is a communication unit for transmitting and receiving various types of information to / from the administrator terminal 12, the person-in-charge terminal 13, and other external devices via the communication network 14. The communication means 28 can receive various information already stored in an external device or the like, and the result processed by the schedule management device 11 is sent to the administrator terminal 12 or the person in charge via the communication network 14 or the like. It can also be transmitted to the terminal 13 and other external devices.

  The control unit 29 controls the entire components of the schedule management device 11. Specifically, the control means 29 performs each control regarding schedule management, for example based on the instruction | indication from a user etc. Here, each control includes, for example, causing the project management unit 21 to manage one or a plurality of projects, causing the schedule creation unit 22 to create a schedule, and assigning a person in charge to the person-in-charge assignment unit 23. Further, each control includes execution status management means 24 for managing execution status, delay notification means 25 for delay notification, screen generation means 26 for generating a screen, etc., but is not limited thereto. .

  With the configuration of the present embodiment described above, appropriate schedule management can be realized.

<Hardware Configuration Example of Schedule Management Device 11>
FIG. 2 is a diagram illustrating an example of a hardware configuration of the schedule management apparatus. 1 includes an input device 31, an output device 32, a drive device 33, an auxiliary storage device 34, a main storage device 35, a central processing unit (CPU) 36 that performs various controls, and a network. And a connection device 37, which are connected to each other via a system bus B.

  The input device 31 includes a pointing device such as a keyboard and a mouse operated by a user, and a voice input device such as a microphone. The input device 31 activates a program execution instruction, various operation information, software, and the like from the user. The input of the information etc. is received.

  The output device 32 has a display for displaying various windows and data necessary for operating the computer main body for performing the processing in the present embodiment. Can be displayed.

  Here, the execution program installed in the computer main body in the present embodiment is provided by, for example, a universal recording bus 38 such as a Universal Serial Bus (USB) memory, a CD-ROM, or a DVD. The recording medium 38 on which the program is recorded can be set in the drive device 33, and an execution program included in the recording medium 38 is transmitted from the recording medium 38 via the drive device 33 on the basis of a control signal from the CPU 36. Installed on.

  The auxiliary storage device 34 is a storage unit such as a hard disk drive or a solid state drive (SSD). The auxiliary storage device 34 stores an execution program according to the present embodiment, a control program provided in the computer, and the like based on a control signal from the CPU 36, and performs input / output as necessary. The auxiliary storage device 34 can read and write necessary information from each stored information based on a control signal from the CPU 36.

  The main storage device 35 stores an execution program read from the auxiliary storage device 34 by the CPU 36. The main storage device 35 is a Read Only Memory (ROM), a Random Access Memory (RAM), or the like. The auxiliary storage device 34 and the main storage device 35 correspond to the storage means 27 described above, for example.

  The CPU 36 controls processing of the entire computer such as various operations and data input / output with each hardware component based on a control program such as an operating system and an execution program stored in the main storage device 35. Each process can be realized. Various information necessary during the execution of the program can be acquired from the auxiliary storage device 34, and the execution result and the like can also be stored.

  Specifically, the CPU 36 executes processing corresponding to the program on the main storage device 35 by executing the program installed in the auxiliary storage device 34 based on, for example, an instruction to execute the program obtained from the input device 31. Do.

  For example, by executing a schedule management program, the CPU 36 performs processes such as project management by the project management means 21, schedule creation by the schedule creation means 22, and assignment of persons in charge by the person-in-charge assignment means 23. Further, the CPU 36 performs processing such as execution status management by the execution status management unit 24, delay notification by the delay notification unit 25, and screen generation by the screen generation unit 26. In addition, the processing content in CPU36 is not limited to this. The contents executed by the CPU 36 are stored in the auxiliary storage device 34 as necessary.

  The network connection device 37 communicates with the administrator terminal 12 and the person-in-charge terminal 13 via the communication network 14. The network connection device 37 acquires an execution program, software, setting information, and the like from an external device or the like connected to the communication network by connecting to the communication network 14 or the like based on a control signal from the CPU 36. The network connection device 37 can provide an execution result obtained by executing the program or the execution program itself in the present embodiment to an external device or the like.

  With the hardware configuration described above, the schedule management process in the present embodiment can be executed. Further, by installing an execution program (schedule management program) capable of executing the above-described functions in a computer, the schedule management process in the present embodiment can be easily realized by a computer such as a general-purpose PC.

  Further, when the administrator terminal 12 and the person-in-charge terminal 13 are general-purpose PCs or the like, the same hardware configuration as that of the schedule management apparatus 11 described above can be applied.

<Example of processing of schedule management device 11>
Next, an example of processing of the schedule management apparatus 11 will be described using a flowchart. Note that schedule management can be broadly divided into project startup processing, delay notification handling processing, execution status management processing, and list display processing, so these processing will be described separately.

<Project launch process>
FIG. 3 is a flowchart illustrating an example of project startup processing of the schedule management apparatus. In the example of FIG. 3, the authentication unit 20 performs login authentication of a user (administrator, person in charge) who has accessed via the communication network 14 from the administrator terminal 12, the person-in-charge terminal 13, or the like (S01). In the process of S01, the authentication unit 20 determines that the authentication is successful when authentication is successful using authentication information input from the administrator terminal 12 or the person-in-charge terminal 13, and the user is an administrator. Subsequent processing is performed, and if authentication fails, the user inputs again or denies access.

  When the authentication is permitted, it is determined whether or not new registration (startup) of the project is performed (S02). When new registration is performed (YES in S02), a new project is registered (S03).

  Project registration involves selecting a project pattern from a plurality of project templates previously managed by the WBS or the like, and setting a standard lead time, a shortest lead time, and the like. The standard lead time is, for example, an average lead time based on the past performance of a project having at least one task. The shortest lead time is, for example, the shortest lead time based on the past performance of a project having at least one task.

  After the process of S03, the schedule creation means 22 creates a master schedule based on the shortest lead time set in the process of S03 (S04). For example, the schedule creation means 22 sets the project name, start date, end date, project overview, task assignment to the project, and the like.

  In the process of S04, the schedule creating means 22 obtains the average lead time and the shortest lead time based on the past performance of the project having at least one task as described above, and a possible buffer (remaining work until delivery date) from the difference. Calculate the man-hour). Moreover, the schedule creation means 22 creates a schedule using the shortest lead time for each task from the calculation result.

  After the process of S04, the person-in-charge assignment means 23 assigns a person in charge for each task to the master schedule of the project (S05). In the process of S05, the person-in-charge assigning means 23 can take charge of each task based on skill information, current work status, past work results, etc. included in the person-in-charge information stored in advance in the storage means 27 etc. Assign the right person. Note that one person in charge may be assigned to a plurality of tasks, or a plurality of persons in charge may be assigned to one task. When assigning a plurality of persons in charge, information on the leader among them is accumulated as person-in-charge information.

  In the above-described processing of S02, when new registration is not performed (NO in S02), or after the processing of S05, it is determined whether or not to display the current project execution status (S06). In the process of S06, an administrator (user) may select a project to be displayed, or a project newly created in the processes of S03 to S05 immediately before may be displayed. All projects may be displayed, but the present invention is not limited to this. When displaying the execution status (YES in S06), the screen generation means 26 generates execution information of the project selected by the user and displays the contents (S07).

  When the execution status is not displayed in S06 (NO in S06), or after the process of S07, the control unit 29 determines whether or not to end the process (S08), and does not end the process (S08). NO), the process returns to S02. In addition, when the process is terminated by an instruction from the user or the like (YES in S08), the control unit 29 ends the schedule management process.

<Execution status management processing>
FIG. 4 is a flowchart illustrating an example of execution status management processing of the schedule management device. In the example of FIG. 4, the authentication unit 20 performs login authentication of a user who has accessed via the communication network 14 from the administrator terminal 12, the person-in-charge terminal 13, or the like (S11). In addition, since the process of S11 performs the process similar to the process of S01 mentioned above, detailed description here is abbreviate | omitted.

  When the authentication is permitted, the execution status management means 24 displays the current execution status of the person in charge who has been authenticated (S12). The display content is generated by the screen generation means 26.

  Next, the execution status management means 24 determines whether or not to input the progress status for the task work assigned to itself (S13). When the progress status is input (YES in S13), the person in charge is in charge. The input of progress information from the person-in-charge terminal 13 to be used is accepted (S14). Further, the execution status management unit 24 updates the execution status with the input progress information (S15).

  Here, when the progress is not input in the process of S13 (NO in S13), or after the process of S15, the execution status management unit 24 determines whether there is a delayed task for the person in charge (step S13). S16).

  In the process of S16, the execution status management means 24 determines the work start priority based on, for example, the earliest start date and the latest start date of each task in the project for the buffer for each project, and creates ToDoList in order of priority. Furthermore, the execution status management means 24 recalculates the earliest start date and the latest start date at predetermined time intervals in accordance with the progress of the task, reflects them in ToDoList, and detects a task that becomes delayed (unprocessable). The predetermined time interval is, for example, every day, every week, every month, etc., but is not limited to this.

  The method for detecting the presence / absence of a delayed task is not limited to this. For example, the execution status management unit 24 may calculate a buffer digestion rate or the like and detect a delayed task based on the calculation result.

  In the process of S16, when there is a delayed task (YES in S16), the delay notification means 25 notifies the person in charge of the delay (S17). Further, in the process of S17, the delay notification means 25 can also notify the project manager of the delayed work task.

  Further, when there is no delayed task in the process of S16 (NO in S16), or after the process of S17, the control means 29 determines whether or not to end the process (S18) and does not end the process. (NO in S18), the process returns to S12. In addition, when the process is terminated by an instruction from the user or the like (YES in S18), the control unit 29 ends the schedule management process.

<Delay notification processing>
FIG. 5 is a flowchart illustrating an example of the delay notification handling process of the schedule management apparatus. In the example of FIG. 5, when the project management means 21 receives a delay notification for the managed project by escalation from the delay notification means 25 (S 21), the project management means 21 displays a delayed task list for the person in charge on the manager terminal 12. It is displayed (S22). Further, the project management means 21 displays the task list of the person in charge included in the delayed task list (S23). The delayed task list and the task list of the person in charge are generated by the screen generation means 26.

  Next, the project management means 21 determines whether or not to reassign the schedule and the person in charge (S24). When reassigning is performed (YES in S24), reassignment is performed (S25). Further, after the process of S25, the project management unit 21 displays the reassignment result on the administrator terminal 13 or the like by the screen generation process 26 (S26), and whether or not the reassignment is OK according to an instruction from the administrator or the like. Is determined (S27).

  If the result based on the instruction from the administrator or the like is not OK (if there is a rejection) (NO in S27), the project management unit 21 returns to the process of S25. If the reassignment is OK (YES in S27), the project management unit 21 updates the schedule (S28) and ends the process.

<List display processing>
FIG. 6 is a flowchart illustrating an example of the list display process of the schedule management apparatus. In the example of FIG. 6, the live situation management means 24 acquires the earliest start date and the latest start date of each task in the project when creating a list such as ToDoList (S31).

  Next, the actual situation management means 24 determines the work task priority from the earliest start date and the latest start date obtained in S31 (S32). Next, the screen generation unit 26 generates a screen to be displayed in the order of priority of the work tasks determined in the process of S32, and outputs the generated screen (S33).

<Specific example>
Next, a specific example of schedule management in the present embodiment will be described with reference to the drawings. FIG. 7 is a diagram illustrating an example of a task table. In the example of FIG. 7, task transitions at the time of July 1, the time of July 3, the time of July 11, and the time of July 12 are shown.

  The items in the task table shown in FIG. 7 include, for example, “project name”, “task name”, “shortest LT (Lead Time)”, “progress”, “type”, “early start date (early)”, “ There are, but are not limited to, “late start date (late)”, “task completion date (MS)”, “remaining buffer”, “in charge”, and the like.

  In the example of FIG. 7, the task table for the persons in charge X and Y is shown. However, the present invention is not limited to this, and the tasks of other persons in charge may be stored in the storage means 27 or the like. .

  In the example of FIG. 7, “project name” is identification information for identifying a project. “Task name” is identification information for identifying a task name in a project. By inputting a part of the project name as the task name, it is possible to prevent the task name from being the same as the task name of another project even if only the task name is referred to, but this is not restrictive.

  “Shortest LT” is the shortest lead time obtained from the past record of the same project or the like. In the example of FIG. 7, it is set in units of days, but is not limited to this, and may be weekly or monthly. Progress is the progress status of the in-process task. “Progress” is set in units of days, but is not limited to this, and may be weekly or monthly.

  “Type” is identification information for identifying whether each task has not been started or is in progress (including completion). However, the type is not limited to this. For example, the type is not completed or is being worked (first half, A stepped type such as a middle stage or a second half may be set. The “earliest start date” and “latest start date” are the earliest start date and the latest start date of each task in the project with respect to the buffer for each project.

“Task completion date (MS)” is the completion date (delivery date) for each work task. The “remaining buffer” is the number of days of difference obtained by subtracting the earliest start date from the latest start date. Note that the remaining buffer shown in FIG. 7 is set in units of days, but is not limited to this, and may be weekly or monthly.
“Person in charge” is information on a person in charge in charge of the task. In this embodiment, a plurality of tasks can be set for one task. In that case, only a representative (leader) may be set as a person in charge, or a plurality of people may be set. .

<Display task execution order>
FIG. 8 is a diagram illustrating an example of the task execution order display. In the example of FIG. 8, the task execution order display list (ToDoList) of the person in charge X on July 1, 2012, July 3, July 11, July 12, 2012 and July 11, 2012 The task execution order display list of the person in charge Y on July 12 is displayed.

  The items in the task execution order display list include, for example, “task name”, “shortest LT”, “related task”, “status”, “latest start date”, “project name”, etc., but are not limited thereto. It is not something. In addition, the detailed description here is abbreviate | omitted about the item similar to the task table mentioned above.

  In FIG. 8, “related task” is to set a context with other tasks. For example, in the task execution order display list on July 1 of the person in charge X, in the case of task A-1, the related tasks A-2 and A-4 indicate that they cannot be executed unless the task A-1 is completed. In the case of the task A-2, the related task A-1 must be executed before the task A-1, and the related task A-3 cannot be executed unless the task A-2 is completed. . Note that the content of the related task is not limited to this.

  The “status” indicates the progress status of the work task as a ratio of the work elapsed days and the shortest LT. For example, if one day has elapsed since the start of the shortest LT at task A-1 on the second day, the status is displayed as “working in half”. For tasks that have not been started, “Status” indicates the earliest start date.

  The list shown in FIG. 8 is displayed in the order of priority set for each work task. As a result, each person in charge can check the execution status of the person in charge, and can grasp the priority order at that time, including other projects, across the board, and can execute appropriate work.

  For example, in the list of July 1 of the person in charge X shown in FIG. 8, task A-6 cannot be executed until July 8 because it is a related task, and after task A-3 is completed on July 6, On July 7th there will be a one-day buffer. The task B-3 is a task that can be executed in the July 7 buffer because the shortest LT is one day and there is no related task. Accordingly, the task priority of the task B-3 is increased.

  In addition, in the July 3 list of the person in charge X, the buffer on July 7 is digested for two days, and the ranking is also moved down based on the status status of other tasks.

  Further, in FIG. 8, in the list of the person in charge X on July 11, A-5 is incomplete, so A-6 cannot be started, and there is a high possibility of delay. In this case, the execution status management means 24 detects it as a delayed task and gives a delay notification. Therefore, the person-in-charge is reassigned by the person-in-charge assigning means 23, and in the list of July 12 shown in FIG. 8, the person in charge A-6 is reassigned from X to Y in the Y list. The result is reflected.

<Example of reallocation based on buffer digestibility>
9 and 10 are diagrams (No. 1 and No. 2) showing an example of reallocation based on the buffer digestion rate. In the example of FIG. 9, standard LT and shortest LT for three projects (projects A, B, and C) are set.

  The project management unit 21 sets a buffer for each task included in the project based on the standard LT and the shortest LT shown in FIG. For example, the schedule creation means 22 acquires the average lead time and the shortest lead time based on the past performance of a project having at least one task. The past performance information is stored in the storage means 27, for example, but is not limited thereto. Further, the schedule creation means 22 calculates the difference between the acquired average lead time and the shortest lead time, and calculates a possible buffer (remaining man-hours until delivery date) from the calculated result.

  Further, the project management means 21 calculates a digestion rate (for example, what percentage is consumed with respect to the buffer) on the calculated buffer based on the daily progress, and reassigns tasks based on the calculation result. Etc. For example, the calculated digestion rate is compared with a preset threshold value, and when the buffer is digested more than the threshold value, task reallocation is performed, but the present invention is not limited to this.

  Here, in the project A in FIG. 10, if the earliest start date on July 13 and July 14 exceeds the latest start date, the project management means 21 detects that there is a high possibility of delay in delivery time. To do. Further, the delay notification means 25 issues a delay alert to the manager terminal 12 such as the project manager of the project A and performs escalation processing.

  As a result, the project manager instructs the manager terminal 12 to reassign tasks and persons in charge, and the task A-6 is changed from the person in charge X to the person in charge Y as shown in FIG. .

<Example of task state transition>
11 and 12 are diagrams (part 1 and part 2) illustrating an example of task state transition. The example of FIG. 11 shows an image diagram of task state transitions in the person in charge X, and the example of FIG. 12 shows an image diagram of task state transitions in the person in charge Y.

  In the example of FIGS. 11 and 12, the shortest LT and the earliest start date (early), the latest start date (late), and the priority (order) are set for each task for each task. In FIG. 11 and FIG. 12, “(1)” indicates a task in progress, and “complete” indicates completion of the task.

  In FIG. 11, the person in charge X cannot start A-6 at the stage of July 10 because the preceding task A-5 is not completed. In addition, since the person in charge X has started B-2, it becomes the buffer 0 (earlyest = latest) of the project A. Therefore, the execution status management unit 24 determines that there is a possibility of delay. Therefore, the delay notification means 25 performs a delay alert notification.

  Further, in FIG. 11, the person in charge X has the earliest start date exceeding the latest start date at the stage of July 12. Therefore, the execution status management unit 24 determines that there is a high possibility of delivery delay. Therefore, the delay notification means 25 issues a delay alert to the project manager management terminal 12 and further prompts the project manager to reassign.

  For example, the execution status management unit 24 can select whether to perform only the delay alert or notify the project manager according to the level (degree) of the delay, and can notify the delay notification unit 25 of the selection.

  The project manager uses the manager terminal 12 to reassign task A-6 from the person in charge X to the person in charge Y as shown in FIG.

  In FIG. 12, the person in charge Y becomes the buffer 0 (earliest = latest) of the project C at the stage of July 14th. Therefore, the execution status management unit 24 determines that there is a possibility of delay. The delay notification means 25 notifies the person in charge Y of a delay alert (warning) including information on a task that has been determined to be possibly delayed.

  The contents shown in FIGS. 7 to 12 described above are generated by, for example, the screen generation unit 26 and can be displayed on the screen of the administrator terminal 12 or the person-in-charge terminal 13.

  As described above, in the present embodiment, appropriate schedule management can be realized. For example, in the present embodiment, by presenting the execution order (priority order) of tasks of a plurality of projects to the project person in charge, appropriate schedule management can be realized, and delivery delays can be prevented. Further, in this embodiment, even an inexperienced person in charge can reliably perform tasks in the optimal order equivalent to that of a veteran. Moreover, in this embodiment, the man-hour for reviewing a daily schedule can be reduced.

  Each embodiment has been described in detail above. However, the present invention is not limited to the specific embodiment, and various modifications and changes other than the above-described modification are possible within the scope described in the claims. .

In addition, the following additional remarks are disclosed regarding the above Example.
(Appendix 1)
Using the average lead time and the shortest lead time obtained from the past results corresponding to one or more projects having at least one task to calculate the remaining work man-hours until the delivery date of the task;
Create a schedule for the project using the shortest lead time,
The priority of the task is determined using the earliest start date and the latest start date of the task in the created schedule,
A schedule management program for causing a computer to execute a process of detecting the task that is delayed based on the determined task in the priority order and the remaining man-hours.
(Appendix 2)
The schedule management program according to appendix 1, wherein a delay notification is sent to a person in charge of the task when the task that becomes the delay is detected.
(Appendix 3)
The schedule management program according to appendix 2, wherein the content of the delay notification is changed according to the delay level.
(Appendix 4)
4. The schedule management program according to any one of appendices 1 to 3, wherein a screen for displaying the tasks in the priority order for the project in correspondence with a person in charge is generated.
(Appendix 5)
The schedule management program according to any one of appendices 1 to 4, wherein the task is reassigned when the task that becomes the delay is detected.
(Appendix 6)
The schedule management device
Using the average lead time and the shortest lead time obtained from the past results corresponding to one or more projects having at least one task to calculate the remaining work man-hours until the delivery date of the task;
Create a schedule for the project using the shortest lead time,
The priority of the task is determined using the earliest start date and the latest start date of the task in the created schedule,
A schedule management method comprising: detecting the task that is delayed based on the determined task in the priority order and the remaining work man-hours.
(Appendix 7)
A project management means for calculating a remaining work man-hour until the delivery date of the task by using an average lead time and a shortest lead time obtained from past results of one or a plurality of projects having at least one task;
A schedule creation means for creating a schedule of the project using the shortest lead time;
Using the earliest start date and the latest start date of the task in the project obtained by the schedule creation means, the priority of the task is determined, the task in the determined priority order, and the remaining work man-hours And an execution status management means for detecting the task that is delayed based on the schedule management device.

10 Schedule Management System 11 Schedule Management Device (Information Processing Device)
DESCRIPTION OF SYMBOLS 12 Manager terminal 13 Person in charge terminal 14 Communication network 20 Authentication means 21 Project management means 22 Schedule preparation means 23 Person in charge allocation means 24 Execution status management means 25 Delay notification means 26 Screen generation means 27 Storage means 28 Communication means 30 Control means 31 Input device 32 Output device 33 Drive device 34 Auxiliary storage device 35 Main storage device 36 CPU
37 Network connection device 38 Recording medium

Claims (6)

Using the average lead time and the shortest lead time obtained from the past results corresponding to one or more projects having at least one task to calculate the remaining work man-hours until the delivery date of the task;
Create a schedule for the project using the shortest lead time,
Using the earliest start date and the latest start date of the task in the created schedule and information on other related tasks executed earlier or later, the priority according to the execution order of the tasks is determined,
A schedule management program for causing a computer to execute a process of detecting the task that is delayed based on the determined task in the priority order and the remaining man-hours.   The schedule management program according to claim 1, wherein when the task that becomes the delay is detected, a delay notification is made to a person in charge of the task.   3. The schedule management program according to claim 1, wherein a screen for displaying the tasks in the priority order for the project in correspondence with a person in charge is generated.   The schedule management program according to any one of claims 1 to 3, wherein the task is reassigned when the task that becomes the delay is detected. The schedule management device
Using the average lead time and the shortest lead time obtained from the past results corresponding to one or more projects having at least one task to calculate the remaining work man-hours until the delivery date of the task;
Create a schedule for the project using the shortest lead time,
Using the earliest start date and the latest start date of the task in the created schedule and information on other related tasks executed earlier or later, the priority according to the execution order of the tasks is determined,
A schedule management method comprising: detecting the task that is delayed based on the determined task in the priority order and the remaining work man-hours. A project management means for calculating a remaining work man-hour until the delivery date of the task by using an average lead time and a shortest lead time obtained from past results of one or a plurality of projects having at least one task;
A schedule creation means for creating a schedule of the project using the shortest lead time;
Using the earliest start date and the latest start date of the task in the project obtained by the schedule creation means, and information on other related tasks to be executed earlier or later, the priority according to the execution order of the tasks is determined. And an execution status management unit that detects the task that is delayed based on the determined task in the priority order and the remaining work man-hours.

Images