JP2004110102A - Project management method and process definition device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform highly accurate project management by automatically defining detail work items, and reducing the management costs of a project manager, and reducing mistake such as the inconsistency or leakage of the definition of a WBS since the detail works to be actually performed by each project are made various according to the configurations of targets (components) to be developed by the project. <P>SOLUTION: This device is provided with a component configuration managing part 102 for managing the configuration information of targets (components) to be developed by using the configurations of the targets to be developed of each project as input information, a common WBS managing part 104 for managing the definitions of the commonized WBS and a rule for detailing each item, a WBS detailing device 107 for automatically detailing the WBS from the information managed by the two managing parts, and a WBS managing part 108 for managing the detailed WBS. A project manager automatically defines the detail work items specific to the project. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a method for managing work information of a project and a process definition device in project management.
[0002]
[Prior art]
As an example related to the conventional project management, there is, for example, "Information Management Apparatus and Recording Medium" described in JP-A-2000-215038. This is because the project manager defines the work process to be performed in the project, and associates the work process definition, work progress, deliverables, etc. with the project management by centrally managing the project. This is a system that improves the efficiency of the system.
[0003]
With this device, if a basic process definition is described first, project information can be sequentially generated in a correct order by a plurality of processing means in accordance with the contents of the process definition. Therefore, there is an advantage that no contradiction occurs between project information.
However, in such a system, attempts are generally made to improve the development efficiency by standardizing the work process to be defined by the project manager as an organization, and it is not particularly novel.
[0004]
Another proposal is, for example, a “product development process management system and method, and a recording medium on which the method is recorded” described in JP-A-2001-42915. This is intended to make it possible for a project manager to smoothly carry out the project by providing a means for adding or modifying work in the development process at a necessary stage while the project is in progress.
[0005]
According to this system, since the data of the existing system is only referred to from the outside, the product or product to be developed can be developed without modifying the business support system built and used in the general product development environment. , It is possible to hold the relationship between the attribute data of the parts.
[0006]
[Problems to be solved by the invention]
When the standardized work process is followed, more detailed work to be actually performed in each project varies depending on the configuration of an object (component) to be developed in the project. Therefore, with regard to such detailed work, the project manager needs to add or modify necessary work sequentially. As a result, the project manager needs a management cost for correcting the work process while the project is in progress. It is desirable to reduce this management cost.
[0007]
An object of the present invention is to solve such a problem, to enable a project-specific detailed work item to be automatically defined, reduce the management cost of a project manager, and to contradict or omit the definition of a work process. It is an object of the present invention to provide a project management method and a process definition device capable of realizing highly accurate project management by eliminating mistakes by a project manager.
[0008]
[Means for Solving the Problems]
According to the project management method of the present invention, configuration information to be developed for each project is input to a component configuration management unit, and also to a common WBS (Work Breakdown Structure) management unit. In addition to managing the configuration information of the components, the common WBS management unit defines a work process that can be commonly used, manages a WBS detailing level representing a pattern for detailing each item of the work process, and manages the WBS. The refinement device and the WBS management unit are characterized in that they receive information managed by the two management units, refine the WBS, and manage the WBS.
[0009]
In addition, the process definition device of the present invention uses a component configuration management unit that manages configuration information of a development target (component) using a configuration of a development target of each project as input information, and a work process (WBS) that can be commonly used. And a common WBS management unit that manages a WBS refinement level that represents a pattern that refines each of those items, and a WBS refinement that automatically refines the WBS from information managed by these two management units It is characterized by comprising a device and a WBS management unit for managing the detailed WBS.
[0010]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(1st Embodiment)
FIG. 1 is a system configuration diagram of a process definition device according to the first embodiment of the present invention.
The process definition device 101 includes a component configuration management unit 102 (detailed in FIG. 3) that manages component configuration information 103 specific to each project, and a common WBS management unit that manages common WBS information 105 and WBS detail level information 106. 4 (detailed in FIG. 4), a WBS detailing device 107 (detailed in FIG. 6), and a WBS management unit 108 (detailed in FIG. 5) for managing the refined WBS information 109. . The WBS refinement device 107 refines the WBS using the component configuration information 103, the common WBS information 105, and the WBS refinement level information 106 as input information, and stores the result in the refined WBS information 109.
[0011]
FIG. 2 is a diagram showing an example of WBS refinement realized in the system shown in FIG.
In the component configuration management unit 102, a component (A) 201, a component (B) 202, a component (C) 203, and a component (D) 204 are defined as components to be developed, and the component (D) 204 is a component (B). ) 202 and the component (C) 203 define a dependency 205 between the component (B) 202 and the component (C) 203 that depends on the component (A) 201. The above is the first work definition and the second work, the dependency relationship, is determined.
[0012]
Next, in the common WBS management unit 104, the common part of the WBS is defined, and the internal specification design 207 is coded as the external specification design 206, the coding 208 is coded as the internal specification design 207, and the module test 209 is coded as the internal specification design 207. In the integrated test 210, a dependency 211 is defined which depends on the external specification design 206 and the coding 208. The internal specification design 207 is 2 and the integrated test 210 is 0. A refinement level 212 has been defined. The WBS refinement device 107 refines the WBS from these pieces of information, and stores the result in the WBS management unit 108. The above is the definition of the dependency of the second work and the detailed WBS (work process).
[0013]
The WBS management unit 108 has the same definition as the work 206, 207, 208, 209, 210, etc. defined by the common WBS management unit 104 as a result of WBS refinement, and is further refined by the WBS refinement unit 107. Operations 213, 214, and 215 are defined. In the dependency 211 defined by the common WBS management unit 104, the dependencies 216, 217, 218, and 219 are also defined by the WBS management unit 108 according to the WBS detail level 212 by the WBS detail unit 107. Note that these dependency relationships 216, 217, 218, and 219 have different types of lines in the figure, but this is to clarify the distinction between the lines, and represent exactly the same type of information as the dependencies. ing.
[0014]
FIGS. 3A and 3B are diagrams illustrating a method of managing the component configuration information 103 in the component configuration management unit 102. FIG.
The information that the component (A) 201, the component (B) 202, the component (C) 203, and the component (D) 204 have the dependency 205 as shown in the drawing is the component name 301 in the component configuration information 103. It is managed by a table having two columns of the relationship 302. For example, since there is no value in the column of the dependency relationship 302 whose component name 301 is A, the component (A) 201 does not have another component on which it depends. In addition, since the column of the dependency 302 with the component name 301 of D has two values of B and C, the component (D) 204 depends on two components, the component (B) 202 and the component (C) 203. It becomes.
[0015]
FIGS. 4A and 4B are diagrams illustrating a method of managing the common WBS information 105 and the WBS detail level information 106 in the common WBS management unit 104.
The common WBS management unit 104 manages the common WBS information 105 in two tables, a work definition 401 and a dependency definition 404. The work definition 401 is a table having two columns, a work name 402 and a parent work 403. For example, since the work name 402 is the parent work 403 of the coding, the work of the coding 208 has the parent work of the manufacture 409, and the parent work 403 of the work name 402 has no value. The work has no parent work.
[0016]
The dependency relationship definition 404 is a table having two columns of a work name 405 and a dependency 406. For example, the work name 405 depends on the internal specification design and coding of the module test dependency 406, so that the module test 209 depends on the internal specification design 207 and coding 208. The WBS detail level information 106 is managed in a table having two columns of a work name 407 and a WBS detail level 408. For example, since the work name 407 has a WBS detail level 408 of the external specification design of 0, the WBS detail level 212 of the open specification design 206 is 0.
[0017]
FIGS. 5A and 5B are diagrams illustrating a method of managing the refined WBS information 109 in the WBS management unit 108 that manages the WBS refined by the WBS refinement device 107.
The WBS management unit 108 manages the detailed WBS information 109 in two tables, a work definition 501 and a dependency definition 502. The work definition 501 is a table having the same structure as the work definition 401 of the common WBS information 105, and also manages the detailed definitions of the works 213, 214, and 215. The dependency definition 502 is also a table having the same structure as the dependency definition 404 of the common WBS information 105, and also manages the definitions of the dependency 216, 217, 218, and 219 of the detailed operations 213, 214, and 215. .
[0018]
FIG. 6 is a flowchart showing the flow of the entire processing executed by WBS detailing apparatus 107.
The WBS detailing device 107 copies the work defined in the work definition 401 of the common WBS information 105 to the work definition 501 of the detailed WBS information 109 (Step 601). Next, regarding the work in which the WBS detail level 212 is defined as one or more in the WBS detail level information 106, the work of the detailed WBS information 109 is regarded as the detailed work corresponding to the component defined in the component configuration information 103. A definition is added to the definition 501 (step 602). The work is acquired sequentially from the work definition 401 of the common WBS information 105 (step 603).
[0019]
It is checked whether the parent work 403 of the acquired work is defined (step 604). If it is not defined, the work is the parent work, and the work definition 401 includes the next work that has not been executed yet. It is confirmed whether or not to perform the operation (step 610), and if there is a next operation, the processing is executed again from the processing of step 603. If there is no next work that has not performed the process, the WBS detailing device ends the process. If the parent work is defined in the check in step 604, the WBS detail level 212 of the work is acquired from the WBS detail level information 106 (step 605). The processing differs depending on the acquired WBS detailing level (step 606). When the processing is 0 (step 607), 1 (step 608), and 2 (step 609), the above-described steps are performed. The processing after 610 is executed.
[0020]
The flow of processing (steps 607, 608, 609) at each WBS detail level will be described in order using a flowchart.
FIG. 7 is a flowchart showing details of the processing of step 607 in the flowchart of FIG. 6 when the WBS detail level 212 is 0.
First, it is checked whether or not a dependency definition exists from the dependency definition 404 of the common WBS information 105 for the work to be processed (step 701). If there is no dependency definition, the process of the level 0 detailing process is terminated. On the other hand, if there is a dependency, the WBS refinement level 202 is obtained from the WBS refinement level information 106 for all of the dependent works (step 702), and the following processing is executed according to the value.
[0021]
If the value of the obtained WBS detail level is 1 or more, the dependent work is also refined corresponding to the component, and thus the dependency relationship between all the refined work and the currently processed work Is newly defined in the dependency definition 502 of the detailed WBS information 109 (step 703). If the value of the obtained WBS detail level is not 1 or more, the dependency defined in the dependency definition 404 of the common WBS information 105 is copied to the dependency definition 502 of the detail WBS information 109 (step 704), and the level is determined. The processing of the detailing processing part of 0 is ended.
[0022]
FIG. 8 is a flowchart showing details of the processing of step 608 in the flowchart of FIG. 6 when the WBS detail level 212 is 1.
First, it is checked whether a dependency definition exists from the dependency definition 404 of the common WBS information 105 for the work to be processed (step 801). If the dependency definition does not exist, the processing of the level 1 detailing processing section is terminated. If there is a dependency, the WBS refinement level 202 is obtained from the WBS refinement level information 106 for all of the dependent operations (step 802), and the following processing is executed according to the value.
[0023]
If the value of the acquired WBS detail level is 1 or more, the dependent work is also refined corresponding to the component, so the refined work from those refined work and the work currently being processed The dependency is newly defined in the dependency definition 502 of the detailed WBS information 109 (step 803). If the acquired value of the WBS detail level is not 1 or more, a record is added to the dependency definition 502 of the detailed WBS information 109 for all the detailed work and the dependent work (804). Then, the processing of the detailing processing part of level 0 ends.
[0024]
FIG. 9 is a flowchart showing details of the processing of step 609 in the flowchart of FIG. 6 when the WBS detail level 212 is 2.
First, the same dependency as the dependency defined in the component configuration information 103 is newly defined in the dependency definition 502 of the detailed WBS information 109 for the detailed work (step 901). Next, for the work to be processed, it is checked whether or not a dependency definition exists from the dependency definition 404 of the common WBS information 105 (step 902). If there is no dependency definition, the process of the level 0 detailing process is terminated.
[0025]
If there is a dependency, the WBS detail level 202 is obtained from the WBS detail level information 106 for all of the dependent tasks (step 903), and the following processing is executed according to the value. If the value of the acquired WBS detail level is 1 or more, the dependent work is also refined corresponding to the component, so the refined work from those refined work and the work currently being processed The dependency is newly defined in the dependency definition 502 of the detailed WBS information 109 (step 904). If the acquired value of the WBS detail level is not 1 or more, a dependency relationship is newly defined in the dependency definition 502 of the detailed WBS information 109 with respect to all the work refined from the current processing target work and the dependent work. Then (step 905), the processing of the level 0 detailing processing section ends.
[0026]
(Second embodiment)
Next, a method of reflecting the change by the WBS detailing apparatus 107 when the configuration of the component to be developed is changed during the progress of the project will be described. That is, the second embodiment is an example where the configuration of components is changed during the progress of a project.
FIG. 10 illustrates the second embodiment of the present invention, and illustrates a method of managing the component configuration information 103 when the configuration of a component to be developed is changed.
Here, as an example, the component E1001 is newly added, the component B202 depends on the component E1001, and the component E1001 depends on the component A201. Along with this change, a record is added to the component configuration information 103. That is, here, the dependency A for the component name E and the dependency E for the component name B are added as component configuration information.
[0027]
FIG. 11 is a diagram illustrating a management method of the refined WBS information 109 after the WBS refinement process when the configuration of the component to be developed is changed.
Operations 1101, 1102, and 1103 corresponding to the newly added component E1001 are added, and dependencies 216, 217, 218, and 219 with other operations are defined. Note that FIG. 11 shows only the dependencies related to the component E1001.
[0028]
FIG. 12 is a flowchart showing the flow of processing of the WBS detailing apparatus 107 when the configuration of a component to be developed is changed.
First, updated information is obtained from the component configuration information 103 (step 1201). If the deleted component or its dependency exists, all records related to the deletion target are deleted from the work definition 501 and the dependency definition 506 of the detailed WBS information 109 (step 1202).
[0029]
Next, when the added component or its dependency exists, the work in which the WBS detail level 212 is defined as one or more in the WBS detail level information 106 is regarded as a detailed work corresponding to the added component. Then, the definition is added to the work definition 501 of the detailed WBS information 109 (step 1203). Next, the work definition 401 related to the updated component is sequentially acquired (step 1204), and the WBS detail level 212 of the work is acquired from the WBS detail level information 106 of the common WBS management unit 104 (step 1205). .
[0030]
Thereafter, as in the case of newly executing the WBS detailing process, the process differs depending on the acquired WBS detailing level (step 1206), 0 (step 607), 1 (step 608), 2 Each process of (Step 609) is executed for the updated detailed work. When the process is completed for all the work definitions 401 related to the updated component (step 1207), the update process of the detailed WBS information 109 by the WBS detail device 107 ends.
[0031]
【The invention's effect】
As described above, according to the present invention, project management is performed by using a common WBS for each project and automatically generating detailed work unique to each project from component configuration information of a development target. This reduces human management costs and eliminates human errors such as inconsistencies and omissions in definition in detailed work, and as a result, high-quality project management can be easily realized.
[Brief description of the drawings]
FIG. 1 is an overall configuration diagram of a process definition device according to a first embodiment of the present invention.
FIG. 2 is a diagram showing an outline of detailing a work process of a process definition device based on sample data in FIG. 1;
FIG. 3 is a diagram illustrating a data format of component configuration information managed by a component configuration management unit.
FIG. 4 is a diagram illustrating a data format of common WBS information and WBS detail level information managed by a common WBS management unit.
FIG. 5 is a diagram illustrating a data format of detailed WBS information managed by a WBS management unit;
FIG. 6 is a flowchart showing the whole WBS detailing process.
FIG. 7 is a flowchart of a detailing processing portion when the WBS detailing level is 0;
FIG. 8 is a flowchart of a detailing process portion when the WBS detail level is 1.
FIG. 9 is a flowchart of a detailing process portion when the WBS detailing level is 2.
FIG. 10 is a diagram illustrating a data format of component configuration information when component configuration information is changed according to the second embodiment of this invention.
FIG. 11 is a diagram showing a data format of the refined WBS information after the WBS refinement processing in a case where component configuration information is changed in FIG.
FIG. 12 is a flowchart showing the whole WBS detailing process when the component configuration information is changed.
[Explanation of symbols]
101: process definition device 102: component configuration management unit 103: component configuration information 104: common WBS management unit 105: common WBS information 106: WBS detail level information 107: WBS detail device 108: WBS management unit 109: detail WBS Information 201, 202, 203, 204, 1001: Components 205, 211, 216, 217, 218, 219: Dependencies 206, 207, 208, 209, 210, 213, 214, 215, 1101, 1102, 1103: WBS Work to be composed 212: WBS detail level 301: Component name columns 302 and 406: Dependency columns 401 and 501: Work definition 402, 405, 407, 503, 505: Work name columns 403 and 504: Parent work Columns 404, 502, 506: Dependency Definition 408: WBS refinement level of the column 1001: Added component

Claims (5)

Input the configuration information to be developed for each project to the component configuration management section and also to the common work process management section,
The component configuration management unit manages configuration information of a component to be developed,
The common work process management unit defines work processes that can be used in common, and manages a detail level of a work process that represents a pattern that details each item of the work process,
The work process detailing device receives the information managed by the above two management units, details the work process,
A project management method, wherein a work process management unit manages work processes detailed by the work process detailing device. A component configuration management unit that manages the configuration information of the development target using the configuration of the development target of each project as input information;
A common work process management unit that manages a definition of a work process that can be used in common, and a work process detailing level that represents a pattern for detailing each item of the work process;
A work process detailing device for automatically detailing work processes from information managed by these two management units;
A process definition device comprising: a work process management unit that manages a work process refined by the work process refinement device. The detailed work of each of the work items is defined by reflecting the dependency relation for each work item defined by the work process shared by the common work process management unit and the dependency relationship between the components managed by the component configuration management unit. 3. The process definition device according to claim 2, wherein a dependency is automatically defined between the work items of the process. The method according to claim 2, wherein a work process detailing level managed by the common work process management unit is set so that a method of defining a dependency of each work can be selected for each work item to be refined. Process definition device. During the progress of the project, if the configuration of the component to be developed is changed, obtain updated information, and if there is a deleted component or its dependency, the work definition of the detailed work process information, Delete all records related to the deletion target from the dependency definition,
For the work for which the work process refinement level is defined in the work process refinement level information, add a definition corresponding to the work definition of the refined work process information as a detailed work corresponding to the added component, and then 2. The project according to claim 1, wherein a work definition related to the updated component is obtained in order, and a work process detail level of the work is obtained from work process detail level information of the common work process management unit. Management method.

Images