JP2004265351A - Project management system and its method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To quickly detect the influence of a program for changing the schedule of a business item to a project and to share the influence among a plurality of teams engaged in the project before an agreement. <P>SOLUTION: The project management system is provided with a plurality of team schedule management devices 1 each of which is prepared in each team and manages the schedule of a project part in which a target team is engaged and a shared schedule storage device 2 for storing the schedule of the project part in which a plurality of teams are cooperated. Each team schedule management device 1 informs an operator of the schedule cooperated with the schedules of other teams out of the schedules of project parts managed by its own device in relation with the schedules of other teams which are stored in a shared schedule storage device 2. The schedules of the project parts in which the plurality of teams are cooperated are stored in the shared schedule storage device 2 independently of other parts of the project. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a project management technique for managing a schedule of a project performed by a plurality of teams in cooperation.
[0002]
[Prior art]
Conventionally, various schedule management systems have been used. For example, Patent Literature 1 discloses a system audit support system that performs consistent progress management in a system design development process, and enables a balanced and high-quality system design while reviewing a system development plan for each process. Is disclosed.
[0003]
By the way, many of the conventional schedule management systems are classified into either an independent type which independently manages files representing schedules, or a database type which collectively manages files representing schedules in a database and collectively manages the files. be able to. In the stand-alone type, management of each file representing a schedule plan is entrusted to an OS (Operating System), and reading and writing of the file are performed through the OS. On the other hand, in the database type, the schedule management system centrally manages the files representing the schedule plans by accumulating them in the same data database. Here, the schedule is defined in the form of a set of business items (a set of business name and due date) indicating what or when. Each work item is associated with another work item (such as a process context or irrelevance).
[0004]
[Patent Document 1]
JP-A-7-114467
[0005]
[Problems to be solved by the invention]
By the way, when managing the schedule of a project that is performed by a plurality of teams in cooperation with the conventional schedule management system, a file representing the schedule of the project part in which the own team is involved for each team in both the independent type and the database type. And a delivery date of results between the teams (for example, a delivery date of the part a between the team A that manufactures the part a and a team B that sets up the product b from the part a) by a technique called an inter-file link. It is common to link files so that they are automatically matched. For this reason, when the schedule of a project is managed by the conventional schedule management system, the following problem occurs.
[0006]
(1) The schedule change schedule cannot be reflected in the system until agreement is reached between the teams.
[0007]
The entire project schedule is planned based on agreement between the teams. In the inter-file link, when one team changes the schedule, the schedule of the other linked team is automatically changed. For this reason, the schedule change schedule cannot be reflected on the system until agreement is obtained again from another team.
[0008]
(2) The processing load on the system is large.
[0009]
Even in the case of a project that is performed by a plurality of teams in cooperation, it is common that the scheduling of each team includes a plurality of work items. And not all the work items performed by the own team affect the schedules of other teams. In other words, of the work items included in the schedule, some work items need to be linked to work items of other teams, and some work items do not need to be linked. However, since conventional schedule management systems do not distinguish between them, when a schedule change is reflected from one file to another using file links, irrelevant work items are checked and the processing load on the system increases. Would.
[0010]
The present invention has been made in view of the above circumstances, and it is an object of the present invention to quickly detect the effect of a schedule change of a work item on a project and to evaluate the effect before agreement between multiple teams involved in the project. Is to be able to share it.
[0011]
[Means for Solving the Problems]
In order to solve the above problems, a project management system according to the present invention is provided for each team, and a plurality of team schedule management devices for managing the schedule of a project portion in which a target team is involved, and the plurality of team schedule management devices are accessible. And a shared schedule holding device for holding a schedule of a project part in which a plurality of teams cooperate. Each of the plurality of team schedule management devices operates a schedule associated with the schedule of the other team among the schedules of the project portion managed by the own device in association with the schedule of the other team held by the shared schedule holding device. Notify others.
[0012]
Specifically, for example, the team schedule management device includes a unique item storage unit that stores information on unique items that do not affect the schedule of the work items of other teams among the work items constituting the project part in which the target team is involved. And a shared item storage unit that stores information on shared items that affect the schedule of the work items of the other team among the work items constituting the project part in which the target team is involved, and are stored in the shared item storage unit. A shared item registration unit for registering information on the shared item in the shared schedule holding device; and a schedule of the shared item and information on a shared item of another team which affects the schedule of the shared item according to the information on the shared item stored in the shared item storage unit. A shared item search means for searching for information from the shared schedule holding device; and a shared item search for information on shared items stored in the shared item storage means. Stage has a item display means for displaying in association with the information of the shared item other teams that affect the schedule of the shared items detected.
[0013]
According to the present invention, the schedule of a project portion in which a plurality of teams cooperate is held by the shared schedule holding device independently of other portions of the project. Therefore, the effect of the schedule change of the work item on the project may be detected by checking the information held in the shared schedule holding device. Therefore, the effect of the schedule change of the work item on the project can be quickly detected.
[0014]
Further, the team schedule management device associates the information of the shared item stored in the own device with the information of the shared item of another team that affects the schedule of the shared item held in the shared schedule holding device. , The influence of the shared items of the other team on the shared items stored in the own device can be notified to the operator without changing the information of the shared items stored in the own device. Therefore, the influence can be shared before agreement between a plurality of teams involved in the project.
[0015]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described.
[0016]
FIG. 1 is a schematic diagram of a project schedule management system to which an embodiment of the present invention is applied. As shown in the drawing, the project management system according to the present embodiment includes a plurality of team schedule management apparatuses 1 provided for each team, and a shared schedule configured to be accessible by the plurality of team schedule management apparatuses 1 via the network 3. And a holding device 2.
[0017]
The team schedule management device 1 manages a schedule of a project part in which a target team is involved. FIG. 2 is a schematic configuration diagram of the team schedule management device 1. As illustrated, the team schedule management device 1 includes a GUI (Graphical User Interface) unit 11, a network IF unit 12, a storage unit 13, and a calculation unit 14.
[0018]
The GUI unit 11 inputs and outputs data stored in the storage unit 2, receives instructions from a user, and displays information to the user, using an input device such as a keyboard and a mouse and a display device such as a CRT and an LCD. .
[0019]
The network IF unit 12 communicates with the shared schedule holding device 2 via the network 3.
[0020]
The storage unit 13 stores a team schedule file 11 representing a schedule of a project part in which the target team is involved. The team schedule file 11 includes a unique item management table 111 for managing information on unique items that are business items that do not affect the schedule of the work items of other teams, among the work items constituting the project part in which the target team is involved, It has a shared item management table 112 for managing information on shared items, which are the work items that affect the schedule of the work items of other teams, among the work items constituting the project part in which the target team is involved. Here, the information on the unique item and the shared item includes, for each item, the identification information (item ID) of the business item, the name, the schedule (date or period), and the identification information (project ID) of the project part in which the target team is involved. ) Is included.
[0021]
Generally, in project management, work items are represented using tasks and milestones. A task is used to represent a task item whose operation has a duration such as a part manufacturing process (a band representing a period or time). Milestones are used to represent work items whose work has no duration, such as delivery of parts (points representing days and times). The shared item is basically expressed as a milestone because it is the date of delivery of the results between the teams.
[0022]
The calculation unit 14 includes a team schedule file update unit 141, a project shared item management table update unit 142, an influence item detection unit 143, and a schedule plan creation unit 144.
[0023]
The team schedule file updating unit 141 updates the team schedule file 131 in the storage unit 13 according to the operator's instruction received via the GUI unit 11.
[0024]
The project shared item management table updating unit 142 accesses the shared schedule holding device 2 via the network IF unit 12 according to the operator's instruction received via the GUI unit 11, and is stored in the shared schedule holding device 2. The project sharing management table 231 described later is updated.
[0025]
The affected item detection unit 143 accesses the shared schedule holding device 2 via the network IF unit 12 and is registered in the shared item management table 112 from a project shared management table 231 (described later) held in the shared schedule holding device 2. Obtain information on the shared items of the own team and / or information on the shared items of the other team that affect the schedule of the shared items of the own team.
[0026]
The schedule planning table creating unit 144 creates image data of a schedule planning table (Gantt chart) of a project part in which the own team is involved based on the team schedule file 131, and displays the image data on the monitor via the GUI unit 11. At this time, the shared items of the own team included in the schedule table are displayed in association with the shared items detected by the affected item detection unit 143.
[0027]
Returning to FIG. 1, the description will be continued. The shared schedule holding device 2 manages a schedule of a project part in which a plurality of teams cooperate. FIG. 3 is a schematic configuration diagram of the sharing schedule management device 2. As illustrated, the sharing schedule management device 2 includes a network IF unit 22, a storage unit 23, and a calculation unit 24.
[0028]
The network IF unit 2 communicates with the team schedule management device 1 via the network 3.
[0029]
The storage unit 23 stores a schedule plan of a project part in which a plurality of teams cooperate, that is, a project shared item management table 231 for managing information on shared items of each team. The project sharing item management table 231 has a schedule management table 232 and a link management table 233.
[0030]
In the schedule management table 232, information on shared items is registered for each team. FIG. 4 is a diagram illustrating a data configuration example of the schedule management table 232. As shown in the figure, the schedule management table 232 includes a team-specific schedule management table 2321 provided for each team performing the project. The team-specific schedule management table 2321 is provided with a project ID 2322 which is identification information of a project portion in which the target team is involved. A record 2328 registered in the team schedule management table 2321 includes a field 2323 for registering a management number, which is identification information of the record, and an item ID, which is identification information of a shared item targeted by the record. A field 2324 for registration, a field 2325 for registering the name of a shared item targeted by this record, a field 2326 for registering a schedule (due date) targeted by this record, and an agreement flag are registered. And a field 2327 for performing the operation. Here, the agreement flag indicates that the date registered in the field 2326 is between the team performing the shared item targeted by this record and another team performing the shared item that affects the date of the shared item. This is a flag indicating whether an agreement has been obtained. If no agreement has been obtained, the due date registered in field 2326 will be treated as the desired due date submitted by either team.
[0031]
In the link management table 233, link information for associating the shared items registered in the schedule management table 232 is registered. FIG. 5 is a diagram illustrating a data configuration example of the link management table 233. As shown in the figure, the record 2335 registered in the link management table 233 includes a project ID of a shared item as a link source, fields 2331 and 2332 for registering the item ID, a project ID of a shared item as a link destination, Fields 2333 and 2334 for registering item IDs are provided. Here, the project ID and the item ID are the same as those registered in the schedule management table 232. Further, the shared items that are associated with each other by the link information are such that one schedule affects the other schedule, such as delivery of results between teams. Although there is no particular rule as to which of the shared items associated with each other should be the link source and the link destination, in the present embodiment, the item located in the first stage in the project is set as the link source.
[0032]
Returning to FIG. 3, the description will be continued. The calculation unit 24 includes a project shared item management table update unit 241. The project sharing item management table updating unit 241 updates the contents of the project sharing item management table 231 stored in the storage unit 23 in accordance with the instruction of the team schedule management device 1 accessed via the network IF unit 22, The information is read from the project shared item management table 231 and transmitted to the team schedule management device 1. The project ID and item ID of the shared item managed in the project shared item management table 231 are generated when the project shared item management table update unit 241 newly registers the shared item in the project shared item management table 231. May be transmitted to the team schedule management device 1 that has transmitted the information of the shared item. Then, the team schedule management device 1 registers the project ID and the item ID received from the shared schedule holding device 2 in its own shared item management table 132 while including the information on the shared item.
[0033]
The team schedule management device 1 and the shared schedule holding device 2 having the above-described configurations include, for example, a CPU 901, a memory 902, an external storage device 903 such as an HDD, a CD-ROM, a DVD-ROM, and an IC card as shown in FIG. A reading device 904 that reads data from a storage medium such as a keyboard, an input device 906 such as a mouse, an output device 907 such as a monitor or a printer, a communication device 908 for connecting to the network 3, and each of these devices. In a general computer system including a bus 909 to be connected, this can be realized by the CPU 901 executing a program loaded on the memory 902. This program is downloaded from a storage medium via the reading device 904 or from the network 3 via the communication device 908 to the external storage device 903, and then loaded onto the memory 902 and executed by the CPU 901. You may. Alternatively, the program may be directly loaded on the memory 902 without going through the external storage device 903, and may be executed by the CPU 901. In this case, a memory 902 and an external storage device 903 are used for the storage units 13 and 23. The communication devices 908 correspond to the network IF units 12 and 22.
[0034]
Next, the operation of the team schedule management device 1 will be described.
[0035]
First, the effect detection processing of the team schedule management device 1 will be described. Here, the impact detection processing means that when the team schedule of the project part in which the team is involved is changed and the team schedule file 131 of the team schedule management device 1 is updated, this update is performed for the project part in which the other team is involved. This is a process for detecting the effect on the image. As described above, the update of the team schedule file 131 is performed according to the operator's instruction received by the team schedule file update unit 141 via the GUI unit 11.
[0036]
FIG. 7 is a diagram for explaining the operation of the influence detection processing of the team schedule management device 1. This flow is performed, for example, by the influence item detection unit 143 receiving an influence detection request from the operator via the GUI unit 11.
[0037]
First, the affected item detection unit 143 extracts one piece of shared item information from the shared item management table 132 registered in the team schedule file 131 of the storage unit 13 (S1001). Hereinafter, the extracted shared items will be referred to as attention items.
[0038]
Next, the affected item detection unit 143 accesses the shared schedule management device 2 via the network IF unit 12, and from the schedule management table 232 of the storage unit 23 via the project shared item management table update unit 241, detects the item of interest. The team-specific schedule management table 2321 having the project ID included in the information is specified. Then, from the specified team-based schedule management table 2321, a record of a shared item (referred to as an agreement item) having an agreement flag that matches the item ID included in the information of the attention item and indicates that agreement has been made 2328 is specified. Then, the affected item detecting unit 143 obtains the information of the record 2328 of the agreed item via the project shared item management table updating unit 241 (S1002).
[0039]
Next, the affected item detection unit 143 compares the schedule included in the information of the attention item with the schedule included in the agreement item record 2328 (S1003).
[0040]
If the two match (Yes in S1003), it is determined that the schedule of the attention item has not been changed, and the information of the attention item is passed to the schedule planning table creation unit 144 to instruct the display of only the attention item. In response to this, the schedule plan creating unit 144 arranges a mark indicating the schedule of the item of interest in, for example, a template (template) of the schedule plan prepared in advance (S1006). Then, the process proceeds to S1007. As described above, the schedule of the shared item is a point having no duration (a point representing a day or a time), and thus the attention item is represented by a milestone.
[0041]
On the other hand, if the two do not match (No in S1003), it is determined that the schedule of the attention item has been changed, and the shared items of other teams affected by this schedule change are extracted. Specifically, the project ID and the item ID set associated with the project ID and the item ID set of the agreement item are specified from the link management table 233 of the storage unit 23 via the project sharing item management table updating unit 241. I do. Next, the team-specific schedule management table 2321 having the project ID included in the specified set is specified from the schedule management table 232. Then, from the specified team-by-team schedule management table 2321, a shared item of another team that matches the item ID included in the specified set and has a flag indicating that the set has been agreed (the other team's shared item and the Record 2328). Then, the affected item detection unit 143 acquires the information of the record 2328 of the other team agreement item via the project shared item management table updating unit 241 (S1004).
[0042]
Next, the affected item detection unit 143 passes the information of the attention item and the other team agreement item to the schedule plan creation unit 144, and instructs the schedule plan table creation unit 144 to display both items. In response to this, the schedule plan maker 144 arranges marks indicating schedules of the attention item and the other team consensus items in the template of the schedule plan table so that the relationship between the two items can be identified (S1005). Then, the process proceeds to S1007. In order to identify whether the schedule of the item of interest (the schedule after the plan change) is delayed or ahead of the schedule of the other team's agreement item (the schedule agreed between the teams), Should be color-coded.
[0043]
Now, in S1007, the affected item detection unit 143 determines whether or not all the information of the shared item has been extracted from the shared item management table 132. If not, the process returns to S1001. If extracted, it instructs the schedule planning table creation unit 144 to display the unique items. In response to this, the schedule plan creating unit 144 reads information of each unique item from the unique item management table 133 registered in the team schedule file 131 of the storage unit 13. Then, a mark (task or milestone) indicating the schedule of each unique item is arranged in the template of the schedule table (S1008). As described above, the schedule plan for the project portion in which the own team is involved is created in a form in which the influence of the schedule change on other teams can be recognized. This schedule table is displayed on the monitor via the GUI unit 11 and presented to the operator.
[0044]
Next, the shared schedule update process of the team schedule management device 1 will be described. Here, the shared schedule update process is a process of updating the registered contents of the schedule management table 232 held by the shared schedule management device 2.
[0045]
FIG. 8 is a diagram for explaining the operation of the shared schedule update process of the team schedule management device 1. This flow is performed, for example, when the project sharing item management table updating unit 142 receives a request for updating the project sharing item from the operator via the GUI unit 11.
[0046]
First, the project shared item management table update unit 142 accesses the shared schedule management device 2 via the network IF unit 12, and performs an operation from the schedule management table 232 of the storage unit 23 via the project shared item management table update unit 241. The team-specific schedule management table 2321 having the project ID specified by the user or the project ID registered in advance is specified, and each record 2328 of the team-specific schedule management table 2321 is obtained. Then, the obtained information of each record 2328 is displayed on the monitor via the GUI unit 11 (S2001), and waits for the designation of the record to be updated and the update content received from the operator (S2002).
[0047]
When the user specifies a record in which a flag indicating agreement is registered in the field 2327 and requests update content “request registration”, the project shared item management table updating unit 142 sets a unique management number in the field 2323. Is added to the specified team schedule management table 2321, and the contents of the fields 2324 and 2325 of the specified record are copied to the fields 2324 and 2325 of the record 2328. In addition, a flag indicating non-agreement is registered in field 2327. Then, the desired schedule received from the user via the GUI unit 11 is registered in the field 2326 (S2003).
[0048]
Further, the project shared item management table updating unit 142 uses the link management table 233 when the user specifies a record in which a flag indicating agreement is registered in the field 2327 and requests update content “re-agreed”. The project ID and the item ID of the project ID and the item ID associated with the set of the item ID registered in the field 2324 of the specified record 2327 and the project ID of the specified team-based schedule management table 2321 (referred to as a first table) Identify the set. Next, a team-specific schedule management table 2321 (referred to as a second table) having a project ID included in the specified set is specified from the schedule management table 232. Then, from the second table, a record 2328 of a shared item (referred to as “other team unconsented item”) having a flag that matches the item ID included in the specified set and indicates a non-consensus, A record 2328 of a shared item (referred to as another team agreed item) having a flag that matches the item ID and that indicates agreement is specified (S2004).
[0049]
Next, the project shared item management table updating unit 142 stores the schedule registered in the field 2326 of the record designated by the user, which is registered in the first table, in the field 2326 of the record of the unconsented item of the other team. The schedule is changed to the registered schedule (S2005). Then, the record of the other team consensus item is deleted from the second table, and the flag registered in the field 2327 of the record of the other team disagreement item is changed from “unconfirmed” to “accepted” (S2006).
[0050]
Next, the effect confirmation processing of the team schedule management device 1 will be described. Here, the impact detection processing means that another team requests a change in the schedule of a project part in which the other team is involved, and updates the team-specific schedule management table 2321 of the other team held in the shared schedule holding device 2. If so, this is a process to confirm the effect of the change on the scheduling of the project part in which the own team is involved.
[0051]
FIG. 9 is a diagram for explaining the operation of the effect confirmation processing of the team schedule management device 1. This flow is performed, for example, when the influence item detection unit 143 receives an influence confirmation request from the operator via the GUI unit 11.
[0052]
First, the affected item detection unit 143 extracts one piece of shared item information from the shared item management table 132 registered in the team schedule file 131 of the storage unit 13 (S3001). Hereinafter, the extracted shared items will be referred to as attention items.
[0053]
Next, the affected item detection unit 143 accesses the shared schedule management device 2 via the network IF unit 12, and from the link management table 232 of the storage unit 23 via the project shared item management table updating unit 241, detects the target item. The project ID and the item ID extract the link information record 2335 registered as the link source or the link destination. Then, based on the extracted record 2335, the project ID and the link ID of the shared item of the other team associated with the attention item are specified (S3002).
[0054]
Then, the affected item detection unit 143 specifies the team-specific schedule management table 2321 having the project ID specified in S3002 from the schedule management table 232 of the storage unit 23 of the shared schedule management device 2. Then, from the specified team-based schedule management table 2321, a record 2328 of a shared item (referred to as an unconsented other team item) that matches the item ID specified in S3002 and has a flag indicating unconsensus is searched. (S3003).
[0055]
When the record 2328 of the other team unconsented item cannot be detected (No in S3004), the affected item detecting unit 143 determines that there is no request to change the schedule of the shared item that affects the schedule of the focused item, and The information of the item of interest is passed to the plan table creation unit 144, and an instruction to display only the item of interest is given. In response to this, the schedule plan creator 144 arranges a mark indicating the schedule of the item of interest in, for example, a template (template) of the schedule plan table prepared in advance (S3006). Then, the process proceeds to S3007. As described above, the schedule of the shared item is a point having no duration (a point representing a day or a time), and thus the attention item is represented by a milestone.
[0056]
On the other hand, when the record 2328 of the unteamed item of the other team is detected (Yes in S3004), the affected item detecting unit 143 determines that there is a request to change the schedule of the shared item that affects the schedule of the focused item, The information of the attention item and the items of the other team that have not been agreed to is passed to the schedule planning table creation unit 144, and the display of both items is instructed. In response to this, the schedule plan maker 144 arranges marks indicating schedules of the attention item and the other team unconsensus items in the template of the schedule table so that the relationship between the two items can be identified (S3005). . Then, the process proceeds to S3007. Whether the schedule of the item of interest (schedule after the plan change) is delayed or ahead of schedule of the unconsented item of the other team (unconfirmed schedule newly requested by the other team) It is advisable to color-code the two so that they can be distinguished.
[0057]
By the way, in S3007, the affected item detection unit 143 determines whether or not all the information of the shared item has been extracted from the shared item management table 132. If not, the process returns to S3001. If extracted, it instructs the schedule planning table creation unit 144 to display the unique items. In response to this, the schedule plan creating unit 144 reads information of each unique item from the unique item management table 133 registered in the team schedule file 131 of the storage unit 13. Then, a mark (task or milestone) indicating the schedule of each unique item is arranged in the template of the schedule table (S3008). As described above, the schedule plan of the project portion in which the own team is involved is created in a form in which the influence of the own team due to the schedule change of the other team can be recognized. This schedule table is displayed on the monitor via the GUI unit 11 and presented to the operator.
[0058]
Next, an operation of the project schedule management system according to the present embodiment will be described on the assumption that two teams A and B perform a project in cooperation.
[0059]
FIG. 10 shows a schedule table of the entire project which has been agreed between the teams A and B. In FIG. 10, the upper part of the dashed line is the work item of the project part in which the team A is involved, and the lower part of the dashed line is the work item of the project part in which the team B is involved. The business item indicated by a band (rectangle) mark is a task, and the business item indicated by a dot (diamond) mark is a milestone. The project schedule shown in FIG. 10 is as follows. That is, team A creates a purchase order (task TA1) and submits it to team B on March 14 (milestone MA1). Team B receives the purchase order from Team A on March 14 (milestone MB1) and creates part X (task TB1). Then, the created part X is submitted to the team A on April 20 (milestone MB2). On the other hand, team A creates part Y (task TA2) and completes part Y on April 20 (milestone MA3). Also, on April 20, the part X is received from the team B (milestone MA2). Then, a product is set up using the parts X and Y (task TA3), and the product is completed on June 20 (milestone MA4).
[0060]
In FIG. 10, of the work items of team A, two work items whose change in schedule affects the schedule plan of team B are two milestones MA1 and MA2. Other work items do not affect team B's scheduling unless the schedules for these two work items are changed. Therefore, in the shared item management table 132 of the team schedule management device 1 of the team A, information of the two work items of the milestones MA1 and MA2 is registered as information of the shared item. Information on other business items (tasks TA1 to TA3, milestones MA3, MA4) is registered in the unique item management table 133 as information on unique items.
[0061]
Similarly, in FIG. 10, of the work items of the team B, the work items whose schedule change affects the schedule plan of the team A are two milestones MB1 and MB2. Task TB1 does not affect team A's scheduling unless the schedules for these two work items are changed. Therefore, in the shared item management table 132 of the team schedule management device 1 of the team B, information of the two business items of the milestones MB1 and MB2 is registered as information of the shared item. Information on the task TB1 is registered in the unique item management table 133 as information on unique items.
[0062]
FIG. 11 shows the team-by-team schedule management tables 2321 of the teams A and B registered in the schedule management table 232 of the shared schedule management device 2 when the schedule plan table of the entire project is as shown in FIG. As shown in the figure, information on the milestone MA1 (item ID: MA1, work name: purchase order submission, schedule: 3/14, agreement flag: A record of “contracted” and a record of information of the milestone MA2 (item ID: MA2, business name: part X received, schedule: 4/20, agreement flag: agreed) are registered. The team B schedule management table 2321 (project ID: B) has information on the milestone MB1 (item ID: MB1, business name: purchase order received, schedule: 3/14, agreement flag: agreed). And the record of the information of the milestone MB2 (item ID: MB2, business name: part X submission, schedule: 4/20, agreement flag: agreed) are registered.
[0063]
FIG. 12 shows the link management table 233 of the shared schedule management device 2 when the schedule plan table of the entire project is shown in FIG. Here, the same project ID and item ID as those shown in FIG. 11 are used. As shown in FIG. 12, the milestone MA1 of team A is associated (linked) with the milestone MB1 of team B, and the milestone MB2 of team B is associated (linked) with milestone MA2 of team A.
[0064]
Now, in the above situation, there is a request that the entire project is to be completed sooner. In order to respond to this request, Team A has advanced the schedule of each work item of the project part in which he or she is involved by one week, It is assumed that the team schedule file 131 of the own team schedule management device 1 has been updated. FIG. 13 shows a schedule table of a project part in which the team A is involved, which has been changed after this update. The schedule of the milestones MA1 to MA4 is moved forward by one week with respect to FIG. Team A inputs an impact detection request to its team schedule management device 1 in order to detect the effect of this schedule change on the schedule planning of the project part in which team B is involved. In response to this, the team schedule management device 1 executes the impact detection process shown in FIG. 7, and reflects the effect of the schedule change on the schedule plan of the project part in which the team B is involved, and reflects the schedule of the project part in which the team A is involved. Create a planning board.
[0065]
FIG. 14 shows the schedule of the project part involving team A, reflecting the effect of the schedule change on the schedule planning of the project part involving team B, which is displayed on the team schedule management device 1 of team A by the impact detection processing. It is a figure showing the example of a display of a table. This figure shows that the schedule change for the milestones MA1 and MA2 of the work items of the project portion involving the team A affects the schedule of the project portion involving the team B. In this example, with respect to the milestones MA1 and MA2, the post-change (unconfirmed) schedule registered in the team schedule file 131 and the pre-change (registered in the project shared item management table 231 of the shared schedule management device 2) For example, it is displayed in a color-coded manner so that the date and time can be identified. At this time, colors may be color-coded so that it is possible to identify whether the changed schedule is ahead of the agreed schedule or delayed. In FIG. 14, reference numeral 401 is a description of each of the milestones MA1 and MA2 that affect the scheduling of the project portion in which the team B is involved. This description includes the description of the team B associated with each of the milestones MA1 and MA2. The description of the work item (milestone MB1, MB2) is also included. From the displayed contents, the team A can grasp the influence of the change in the schedule plan of the project part in which the own team is involved on the schedule plan of the team B, and can determine whether or not a re-meeting with the team B is necessary. Can be helpful.
[0066]
By the way, the team A confirms that the milestones MA1 and MA2 affect the scheduling of the team B with respect to the scheduling after the rescheduling of the project part in which the team A is involved. An update request for a project shared item is input, and the team schedule management device 1 executes a shared schedule update process shown in FIG. Then, the designation of the milestones MA1 and MA2 and the update content “request registration” are input, and further, the schedule after the change of the milestones MA1 and MA2 is entered, and the team schedule management device 1 executes S2003 in FIG. In the project sharing item management table 231 of the sharing schedule management device 2, an unconfirmed record including the changed schedule is registered for each of the milestones MA1 and MA2.
[0067]
FIG. 15 shows a case where the team A has changed from the schedule plan shown in FIG. 10 to the schedule shown in FIG. 13 and the team registered in the schedule management table 232 of the shared schedule management device 2 in a state where the team A has not re-agreed with the team B. A team-by-team schedule management table 2321 is shown. As shown in the drawing, the agreed schedule records (milestone MA1: management number “001”, milestone MA2) for each of the milestones MA1 and MA2 are stored in the team-based schedule management table 2321 (project ID: A) of team A. : Management number "002") and an unconfirmed record (milestone MA1: management number "003", milestone MA2: management number "004") are registered.
[0068]
As described above, the team A stores the schedule after the schedule change of the project part in which the team A is involved in the team-by-team schedule management table 2321 of the team A registered in the schedule management table 232 of the shared schedule management device 2. If so, inform Team B of the request to change the schedule. As the communication method, besides the manager of the team A contacting the manager of the team B using a telephone or the like, for example, the shared schedule management apparatus 2 sets a flag indicating that the agreement has not been made in the schedule management table 232 in the field 2327. Is added, and if such a record is added, using the link management table 233, the item ID of this record and the team-by-team schedule management table in which this record is registered An item ID and a project ID set associated with the set of 2321 project IDs are detected, and a message is automatically transmitted to a mail address or the like registered in advance in association with the project ID included in the detected set. Such a method can be considered.
[0069]
Now, when Team B receives notification that Team A's rescheduling needs to be changed, Team B will determine its impact on the scheduling of the project portion in which Team B will be working. An influence confirmation request is input to the schedule management device 1. In response to this, the team schedule management device 1 executes the impact confirmation process shown in FIG. 9, and reflects the effect of the change in the schedule of the project part in which the team A is involved. Create
[0070]
FIG. 16 shows a schedule table of a project part in which team B is involved, in which the effect of the change in the schedule of the project part in which team A is involved is displayed on the team schedule management device 1 of team B by the impact confirmation processing. It is a figure showing an example of a display. This figure shows that the milestones MB1 and MB2 of the work items of the project portion involving the team B are affected by the scheduling of the project portion involving the team A. In this example, for the milestones MB1 and MB2, the agreed schedule registered in the team schedule file 131 and the milestones MB1 and MB2 registered in the project shared item management table 231 of the shared schedule management device 2 respectively. For example, it is displayed in a color-coded manner so that it is possible to identify the schedule of the work items (milestones MA1 and MA2) of the team A associated with the unconfirmed schedule. At this time, colors may be color-coded so that it is possible to identify whether the unscheduled schedule is ahead of the agreed schedule or delayed. In FIG. 16, reference numeral 402 is a description of each of the milestones MB1 and MB2 affected by the scheduling of the project part in which the team A is involved, and the description includes a description of the team associated with each of the milestones MB1 and MB2. A description of the work item A (milestone MA1, MA2) is also included. From the displayed contents, the team B can grasp the influence of the change in the schedule plan of the project part in which the team A is involved on the schedule plan of the own team, and can determine whether or not a re-meeting with the team A is necessary. Can be helpful.
[0071]
Team B confirms that milestones MB1 and MB2 will be affected by the change in team A's schedule with respect to the scheduling of the project part in which team B is involved. Make adjustments to the scheduling. If the team A re-agreed on the change of the schedule, the team schedule file 131 of the own team schedule management device 1 is updated in accordance with the re-agreed schedule, and the project is added to the team schedule management device 1. An update request for a shared item is input, and the team schedule management device 1 executes the shared schedule update process shown in FIG. Then, the designation of the milestones MB1 and MB2 and the update content “re-agreement” are input, and the team schedule management device 1 executes S2004 to S2006 in FIG. As a result, for each record of milestones MB1 and MB2 registered in the project sharing item management table 231 of the sharing schedule management device 2, the date of the unconfirmed record of each of the milestones MA1 and MA2 whose schedule is associated therewith is obtained. Update to match the schedule. In addition, for each of the milestones MA1 and MA2 registered in the project sharing item management table 231 of the sharing schedule management device 2, the agreed records are deleted, and the unaccounted records are changed to agreed (field 2327). Change the flag from unagreed to agreed).
[0072]
By the above processing, the schedule of the project that is performed by the teams A and B in cooperation with each other is changed according to the request from the team A.
[0073]
Hereinabove, one embodiment of the present invention has been described.
[0074]
In the present embodiment, the schedule of the project portion in which a plurality of teams cooperate is held by the shared schedule holding device 2 independently of the other portions of the project. Therefore, the effect of the schedule change of the work item on the project can be detected by checking the information held in the shared schedule holding device 2. Therefore, the team schedule management device 1 can quickly detect the effect of the schedule change of the work item on the project.
[0075]
Further, the team schedule management device 1 associates the information of the shared item stored in the device itself with the information of the shared item of the other team that affects the schedule of the shared item held in the shared schedule holding device 2. To display. Therefore, it is possible to notify the operator of the influence of the shared items of the other team on the shared items stored in the own device without changing the information of the shared items stored in the own device. Therefore, the effect of the schedule of work item rescheduling on the project can be shared among the teams involved in the project before agreement.
[0076]
It should be noted that the present invention is not limited to the above embodiment, and various modifications are possible within the scope of the gist. For example, in the above embodiment, the schedule sharing holding device 2 may have at least one of the project sharing item management table updating unit 142 and the impact item detecting unit 143 of the team schedule managing device 1. .
[0077]
【The invention's effect】
As described above, according to the present invention, it is possible to quickly detect the effect of a schedule change of a work item on a project and to share the effect before agreement between a plurality of teams involved in the project. .
[Brief description of the drawings]
FIG. 1 is a schematic diagram of a project schedule management system to which an embodiment of the present invention is applied.
FIG. 2 is a schematic configuration diagram of a team schedule management device 1.
FIG. 3 is a schematic configuration diagram of a shared schedule management device 2.
FIG. 4 is a diagram showing a data configuration example of a schedule management table 232;
FIG. 5 is a diagram showing a data configuration example of a link management table 233.
FIG. 6 is a diagram illustrating an example of a hardware configuration of a team schedule management device 1 and a shared schedule holding device 2.
FIG. 7 is a diagram illustrating an operation of an influence detection process of the team schedule management device 1.
FIG. 8 is a diagram illustrating an operation of a shared schedule update process of the team schedule management device 1.
FIG. 9 is a diagram for explaining the operation of the influence confirmation processing of the team schedule management device 1.
FIG. 10 is a diagram showing a schedule table for the entire project which has been agreed between teams A and B.
11 is a diagram showing a team-specific schedule management table 2321 for each of teams A and B registered in the schedule management table 232 of the shared schedule management device 2 when the schedule plan table of the entire project is that of FIG. It is.
FIG. 12 is a diagram showing a link management table 233 of the shared schedule management device 2 when the schedule plan table of the entire project is shown in FIG.
FIG. 13 is a diagram showing a schedule plan after a change of a project part in which team A is involved.
FIG. 14 is a view showing the effect of the schedule change on the schedule of the project part involving team B, which is displayed on the team schedule management device 1 of team A by the impact detection processing, and reflects the effect of the schedule change on the project part involving team A; It is a figure showing the example of a display of a schedule table.
FIG. 15 shows a case where team A has changed the schedule from FIG. 10 to the schedule shown in FIG. 13 and is registered in the schedule management table 232 of the shared schedule management device 2 in a state in which the team A has not agreed with team B again. It is a figure which shows the team-by-team schedule management table 2321 of the team A performed.
FIG. 16 shows the schedule of the project part in which team B is involved, reflecting the effect of the change in the schedule of the project part in which team A is involved, which is displayed on the team schedule management device 1 of team B by the impact confirmation processing. It is a figure showing the example of a display of a schedule.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Team schedule management device, 2 ... Shared schedule holding device, 3 ... Network, 11 ... GUI unit, 12 ... Network IF unit, 13 ... Storage unit, 14 ... Operation unit, 22 ... Network IF unit, 23 ... Storage unit, 24 ... Calculation unit, 131 ... Team schedule file, 132 ... Shared item management table, 133 ... Unique item management table, 141 ... A team schedule file update unit, 142 ... a project shared item management table update unit, 143 ... an impact item detection unit, 144 ... a schedule plan creation unit, 231, ... a project shared item management table, 232 ...・ Schedule management table, 233 ・ ・ ・ Link management table, 241 ・ ・ ・ Project shared item management table update unit

Claims (6)

A project management system that manages the schedule of projects performed by multiple teams in cooperation,
A plurality of team schedule management devices that are provided for each team and manage the schedule of the project portion in which the target team is involved, and a shared schedule holding device that holds the schedule of the project portion in which the multiple teams cooperate,
Each of the plurality of team schedule management devices includes:
A unique item storage unit that stores information on unique items that do not affect the schedule of work items of other teams, among work items constituting a project part in which the target team is involved;
A shared item storage unit that stores information on shared items that affect the schedule of work items of other teams among work items constituting a project part in which the target team is involved;
Shared item registration means for registering information on shared items stored in the shared item storage means in the shared schedule holding device,
A shared item search unit that searches the shared schedule holding device for information on the shared item of the other team that affects the schedule of the shared item according to the information of the shared item stored in the shared item storage unit;
Item display means for displaying the information of the shared item stored in the shared item storage means in association with the schedule of the shared item detected by the shared item search means and the information of the shared item of the other team that affects the item. A project management system characterized by having. The project management system according to claim 1, wherein
The information of the shared item has at least one schedule information to which a flag indicating whether or not an agreement has been made with another team having the shared item that affects the schedule of the shared item is given,
The shared item display means can identify whether or not the schedule indicated by the schedule information has been agreed, based on a flag attached to the schedule information included in the information on the shared item to be displayed. A project management system characterized by displaying. The project management system according to claim 2,
The shared item display means, when the information of the shared item to be displayed includes schedule information to which an agreed flag has been added and schedule information to which an unconsented flag has been added, an unconfirmed flag is added. A project management system for displaying a schedule indicated by said schedule information so that it can be identified whether the schedule is advanced or delayed from the schedule indicated by the schedule information to which the agreed flag has been added. The project management system according to any one of claims 1 to 3,
The item display means includes:
A project management system, wherein information on the unique items stored in the unique item storage means is displayed together with information on the shared items stored in the shared item storage means. In a project management system that manages the schedule of a project that is performed by multiple teams in cooperation, the schedule of the project part in which the own team is used, connected to a shared schedule holding device that holds the schedule of the project part in which multiple teams cooperate Is a team schedule management device that manages
A unique item storage unit that stores information on unique items that do not affect the schedule of work items of other teams, among work items constituting a project part in which the target team is involved;
A shared item storage unit that stores information on shared items that affect the schedule of work items of other teams among work items constituting a project part in which the target team is involved;
Shared item registration means for registering information on shared items stored in the shared item storage means in the shared schedule holding device,
A shared item search unit that searches the shared schedule holding device for information on the shared item of the other team that affects the schedule of the shared item according to the information of the shared item stored in the shared item storage unit;
Shared item display means for displaying the information of the shared item stored in the shared item storage means in association with the information on the shared item of the other team that affects the schedule of the shared item detected by the shared item search means, A team schedule management device comprising: Multiple teams cooperate using multiple team schedule management devices that are provided for each team and manage the schedule of the project part in which the target team is involved, and a shared schedule holding device that holds the schedule of the project part where the multiple teams cooperate A project management method that manages the schedule of projects to be performed,
Each of the plurality of team schedule management devices includes information on a unique item that does not affect the schedule of the work item of the other team among the work items constituting the project portion in which the target team is involved, and a task constituting the project portion in which the target team is involved. Of the items, the schedule of the work items of the other team and the information of the shared items that affect are stored in their own storage devices,
Each of the plurality of team schedule management devices includes:
Registering the information of the shared item stored in the storage device in the shared schedule holding device;
According to the information on the shared items stored in the storage device, searching the shared schedule holding device for information on the shared items of other teams that affect the schedule of the shared items,
Displaying the information on the shared item stored in the storage device in association with the information on the detected shared item of the other team that affects the schedule of the detected shared item. .

Images