Issues Related to "Project Documents"
The Organizational Process Assets,[50] and Enterprise Environmental Factors,[51] are described clearly and sufficiently. According to the contents of Project Documents,[52] this component should also get a general description, or we can use the definition from the 1996 Edition, i.e. "Inputs and outputs are documents (e.g. a scope statement) or documentable items (e.g. activity dependencies)"[53] (or a similar definition from the 2000 Edition.[54] As the "Organizational Process Assets", "Enterprise Environmental Factors" and "Project Documents" have a broad meaning, they should be removed from processes. However, they should have identified and extracted a specific part of their meaning, in the form of input or output, to associate with the process input or output set. This can then tell us something more about a particular process.
"Project Document Updates", sometimes has vague contents, e.g. "may be updated include, but are not limited to" and refers to outputs that are not defined in the Fourth Edition. Such outputs cannot be used for process relationships. For example: "cost estimates";[55] "responsibility assignment matrix";[56] "quality audit reports", "training plans", "process documentation";[57] "quality standards";[58] "assumption log updates", "technical documentation updates";[59] and "requirements traceability documentation".[60]
5.3.3.4 Project Document Updates refers to "change requests" as a possible output in this process, which is not defined here.[61]
11.2.1.9 Project Documents, as defined here cannot be input into process 11.2. This input resides in the Planning Process Group, while its description mostly reminds us to collect information from the Executing Process Group and Monitoring and Controlling Process Group.[62]
There are cases, where the description of "Project Documents Updates" output can be identified and extracted to make a meaningful output/input relation. Outputs with potentially specific description are:
| |
5. 2.3.2 Project Document Updates that refers to defined inputs, as "Stakeholder register", "Requirements documentation", and "Requirements traceability matrix". For example "Stakeholder register" can be used to relate with input 10.2.1.1 Stakeholder register.[63] |
| |
6.2.3.2 Project Document Updates that refers to defined inputs such as "Activity lists", "Activity attributes", and "Risk register".[64] For example: |
| |
|
"Activity lists" can be used to relate with input 6.3.1.1 Activity lists. "Activity attributes" can be used to relate with input 6.3.1.2 Activity attributes. As we can see, this invisible relationship between processes 6.2 and 6.3 is accomplished with output 6.2.3.2 Project Document Updates. Such relationships should be part of the data flow diagrams. |
| |
|
"Risk register" can be used to relate with inputs 7.1.1.4 Risk register, 8.1.1.5 Risk register, and 12.1.1.4 Risk register. |
| | 6.3.3.3 Project Documents Updates that refers to defined inputs such as "Activity lists", "Activity attributes", and "Resource calendars".[65] For example: |
| |
|
"Activity lists" can be used to relate with input 6.4.1.1 Activity lists. |
| |
|
"Activity attributes" can be used to relate with input 6.4.1.2 Activity attributes. |
| |
|
"Resource calendars" can be used to relate with inputs 6.4.1.4 Resource calendars, 6.5.1.5 Resource calendars, and 7.2.1.5 Resource calendars. |
| |
6.5.3.4 Project Document Updates that refers to defined inputs "Activity resource requirements", "Activity attributes", "Calendar", and "Risk register".[66] For example: |
| |
|
"Activity resource requirements" can be used to relate with inputs 9.1.1.1 Activity resource requirements, and 12.1.1.6 Activity resource requirements. |
| |
|
"Calendar" can be used to relate with inputs 7.2.1.5 Resource calendars. |
| |
|
"Risk register" can be used to relate with inputs 7.1.1.4 Risk register, 8.1.1.5 Risk register, and 12.1.1.4 Risk register. |
| |
5.4.3.3 Project Document Updates that refers to "any documents that define the product or report status on product completion".[67] Therefore, this output can be used to relate with input 5.5.1.2 Work performance information.[68] |
| | 7.2.3.3 Project Document Updates that refers to defined inputs, "Risk register", and "Project schedule".[69] For example: |
| | | "Risk register" can be used to relate with input 12.1.1.4 Risk register. |
| | | "Project schedule" can be used to relate with inputs 6.6.1.2 Project schedule and 12.1.1.7 Project schedule. |
| | 10.2.3.2 Project Document Updates that refers to defined inputs, "Project schedule", "Stakeholder register", and "Stakeholder management strategy".[70] For example: |
| | | "Project schedule" can be used to relate with input 12.1.1.7 Project schedule. |
| | | "Stakeholder register" can be used to relate with input 10.4.1.1 Stakeholder register. |
| | | "Stakeholder management strategy" can be used to relate with input 10.4.1.2 Stakeholder management strategy. |
| | 6.4.3.2 Project Document Updates that refers to defined input, "Activity attributes".[71] This output can be used to relate with inputs 6.5.1.1 Activity lists and 6.5.1.2 Activity attributes. |
There are other outputs that can be used to relate with insufficiently defined inputs. For example:
| |
Output 9.1.3.1 Human Resource Plan, contains "Staffing management plan" that refers to input "Resource calendars".[72] This piece of output, "Resource calendars", can be used to relate with input 7.2.1.5 Resource Calendars. |
| |
Output 7.1.3.1 Activity Cost Estimates,[73] contains information that can be used to relate with input 7.2.1.6 Contracts.[74] |
| |
Output 7.1.3.2 Basis of Estimates,[75]
contains information that can be used to relate with input 7.2.1.6 Contracts.[76]
|
50. Ibid, p32
51. Ibid, p14
52. Ibid, p350
53. PMBOK® Guide, © 1996, p viii
54. PMBOK® Guide, © 2000, p32
55. PMBOK® Guide, © 2008, p179 & 188
56. Ibid, p201
57. Ibid, p205
58. Ibid, p214
59. Ibid, p307
60. Ibid, p335
61. Ibid, p122
62. Ibid, p285
63. Ibid, p116
64. Ibid, p141
65. Ibid, p145
66. Ibid, p159
67. Ibid, p125
68. Ibid, p127
69. Ibid, p179
70. Ibid, p258
71. Ibid, p151
72. Ibid, pp222-224
73. Ibid, p174
74. Ibid, p176
75. Ibid, p174
76. Ibid, p176
|
Recommended Further Development and Updating of the PMBOK® Guide - Fourth Edition
