Chapters 4 and 5 Concepts Flashcards
1
Q
Project Integration Management
A
includes the processes and activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups
2
Q
Project Integration Management includes making choices about:1
A
- resource allocation
3
Q
Project Integration Management includes making choices about: 2
A
- balancing competing demands
4
Q
Project Integration Management includes making choices about: 3
A
- examining any alternative approaches
5
Q
Project Integration Management includes making choices about: 4
A
- tailoring the processes to meet the project objectives
6
Q
Project Integration Management includes making choices about: 5
A
- managing the interdependencies among the Project Management Knowledge Areas
7
Q
Project Integration Mangement Processes (7) 1
A
1) Develop Project Charter
8
Q
Project Integration Mangement Processes (7) 2
A
2) Develop Project Management Plan
9
Q
Project Integration Mangement Processes (7) 3
A
3) Direct and Manage Project Work
10
Q
Project Integration Mangement Processes (7) 4
A
4) Manage Project Knowledge
11
Q
Project Integration Mangement Processes (7) 5
A
5) Monitor and Control Project Work
12
Q
Project Integration Mangement Processes (7) 6
A
6) Perform Integrated Change Control
13
Q
Project Integration Mangement Processes (7) 7
A
7) Close project or phase
14
Q
The accountability of Project Integration Management cannot….1
A
be delegated or transferred
15
Q
The accountability of Project Integration Management cannot….2
A
- a knowledge area that CAN NOT be managed by other specialists
16
Q
Trends and emerging practices in project integration management (5) 1
A
- use of automated tools
17
Q
Trends and emerging practices in project integration management (5) 2
A
- use of visual management tools
18
Q
Trends and emerging practices in project integration management (5) 3
A
- project knowledge management
19
Q
Trends and emerging practices in project integration management (5) 4
A
- expanding the PM’s responsibilities
20
Q
Trends and emerging practices in project integration management (5) 5
A
- hybrid methodologies
21
Q
Develop Project Charter Process
A
developing a document that formally authorizes the existence of a project and provides the PM with the authority to apply organizational resources to project activities
22
Q
Develop Project Charter Process key Benefit
A
- key benefit is it provides a direct link between the project and the strategic objectives or the organization, creates a formal record of the project, and shows the organizational commitment to the project
23
Q
Develop Project Charter - Inputs (4) 1
A
- business documents
24
Q
Develop Project Charter - Inputs (4) 2
A
- agreements
25
Develop Project Charter - Inputs (4) 3
- EEFs
26
Develop Project Charter - Inputs (4) 4
- OPAs
27
Develop Project Charter - Tools and Techniques (4) 1
- expert judgment
28
Develop Project Charter - Tools and Techniques (4) 2
- data gathering
29
Develop Project Charter - Tools and Techniques (4) 3
- interpersonal and team skills
30
Develop Project Charter - Tools and Techniques (4) 4
- meetings
31
Develop Project Charter - Otuputs (2) 1
- project charter
32
Develop Project Charter - Otuputs (2) 2
- assumption log
33
the project charter...
establishes a partnership between the performing and requesting organizations
34
The approved project charter...
formally initiates the project
35
The project charter provides the PM with...
the authority to plan, execute, and control the project
36
Business case (2) 1
describes the necessary information from a business standpoint to determine wheat the expected outcomes of the project justify the required investment
37
Business case (2) 2
- most commonly used to create the project charter
38
Agreements (2) 1
used to define initial intentions for a project
39
Agreements (2) 2
- take place in the form of contracts, memorandums of understanding (MOUs), service level agreements (SLAs), letters of agreement, letters of intent, verbal agreements, email, or other written agreements
40
A contract is typically used when...
a project is being performed for an external customer
41
Expert judgement
judgement provided based on expertise in an application area, knowledge are, discipline, industry, etc., as appropriate for the activity being performed
42
brainstorming
used to identify a list of ideas in a short period of time; conducted in a group environment and led by a facilitator
43
Consists of 2 parts (2) 1
idea generation
44
Consists of 2 parts (2) 2
analysis
45
Focus groups
bring together stakeholders and subject matter experts to learn about the perceived project risk, success criteria, and other topics in a more controversial way than a one-on-one interview
46
Interviews
used to obtain information on high-level requirements, assumptions or constraints, approval criteria, and other information from stakeholders by talking directly to them
47
Facilitation
the ability to effectively guide a group event to a successful decision, solution, or conclusion
48
At a high level...
the project charter ensures a common understanding by the stakeholders of the key deliverables, milestones, and the roles and responsibilities of everyone involved in the project
49
Develop Project Management Plan Process
defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan
50
Develop Project Management Plan Process key benefit
- key benefit is the production of a comprehensive document that defines the basis of all project work and how the work will be performed
51
Develop Project Management Plan - Inputs (4) 1
- project charter
52
Develop Project Management Plan - Inputs (4) 2
- outputs from other processes
53
Develop Project Management Plan - Inputs (4) 3
- EEFs
54
Develop Project Management Plan - Inputs (4) 4
- OPAs
55
Develop Project Management Plan - Tools and Techniques (4) 1
- expert judgement
56
Develop Project Management Plan - Tools and Techniques (4) 2
- data gathering (brainstorming, checklists, focus groups, interviews)
57
Develop Project Management Plan - Tools and Techniques (4) 3
- interpersonal and team skills (conflict management, facilitation, meeting management)
58
Develop Project Management Plan - Tools and Techniques (4) 4
- meetings
59
Develop Project Management Plan - Outputs (1)
- project management plan
60
The project management plan defines...
how the project is executed, monitored, controlled, and closed
61
Once the Project Management Plan is baselined, it may only be changed through...
the Perform Integrated Change Control process
62
The project kick-off getting is usually associated with...
the end of planning and the start of executing
63
Project Management Plan (definition)
document that describes how the project will be executed, monitored, controlled, and closed. It integrates and consolidates all of the subsidiary management plans and baselines, and other information necessary to manage the project
64
Subsidiary management plans included in Project Management Plan (10) 1
- scope management plan
65
Subsidiary management plans included in Project Management Plan (10) 2
- requirements management plan
66
Subsidiary management plans included in Project Management Plan (10) 3
- schedule management plan
67
Subsidiary management plans included in Project Management Plan (10) 4
- cost management plan
68
Subsidiary management plans included in Project Management Plan (10) 5
- quality management plan
69
Subsidiary management plans included in Project Management Plan (10) 6
- resource management plan
70
Subsidiary management plans included in Project Management Plan (10) 7
- communications management plan
71
Subsidiary management plans included in Project Management Plan (10) 8
- risk management plan
72
Subsidiary management plans included in Project Management Plan (10) 9
- procurement management plan
73
Subsidiary management plans included in Project Management Plan (10)10
- stakeholder engagement plan
74
Baselines included in Project Management Plan (3) 1
- scope baseline
75
Baselines included in Project Management Plan (3) 2
- schedule baseline
76
Baselines included in Project Management Plan (3) 3
- cost baseline
77
Additional components of Project Management Plan (6) 1
- change management plan
78
Additional components of Project Management Plan (6) 2
- configuration management plan
79
Additional components of Project Management Plan (6) 3
- performance measurement baseline
80
Additional components of Project Management Plan (6) 4
- project life cycle
81
Additional components of Project Management Plan (6) 5
- development approach
82
Additional components of Project Management Plan (6) 6
- management reviews
83
Direct and Manage Project Work Process
leading and performing the work defined in the Project Management Plan and implementing approved changes to achieve the project's objectives
84
Direct and Manage Project Work Process Key Benefit
- key benefit is that it provides overall management of the project work and deliverables, thus improving the probability of project success
85
Direct and Manage Project Work - Inputs (5) 1
- Project Management Plan (any component)
86
Direct and Manage Project Work - Inputs (5) 2
- project documents (change log, lessons learned register, milestone list, project communications, project schedule, requirements traceability matrix, risk register, risk report)
87
Direct and Manage Project Work - Inputs (5) 3
- approved change requests
88
Direct and Manage Project Work - Inputs (5) 4
- EEFs
89
Direct and Manage Project Work - Inputs (5) 5
- OPAs
90
Direct and Manage Project Work - Tools and Techniques (3) 1
- expert judgement
91
Direct and Manage Project Work - Tools and Techniques (3) 2
- project management information system
92
Direct and Manage Project Work - Tools and Techniques (3) 3
- meetings
93
Direct and Manage Project Work - Outputs (5) 1
- deliverables
94
Direct and Manage Project Work - Outputs (5) 2
- work performance data
95
Direct and Manage Project Work - Outputs (5) 3
- issue log
96
Direct and Manage Project Work - Outputs (5) 4
- change requests
97
Direct and Manage Project Work - Outputs (5) 5
- Project Management Plan updates (any component)
98
- Project Management Plan updates (any component)
- project documents updates (activity list, assumption log, lessons learned register, requirements documentation, risk register, stakeholder register)
99
Direct and Manage Project Work involves...
executing the planned project activities to complete project deliverables and accomplish established objectives
100
Risk Register vs Risk Report (2) 1
- risk register provides information on threats and opportunities that may impact project execution
101
Risk Register vs Risk Report (2) 2
- risk report provides information on sources of overall project risk along with summary information on identified individual project risks
102
An approved change request can be...
a corrective action, an preventative action, or a defect repair
103
Deliverable (definition)
any unique and verifiable product, result, or capability to performa. service that is required to be produced to complete a process, phase, or project
104
Work performance data (definition)
the raw observations and measurements identified during activities being performed to carry out the project
105
Change requests may include:
corrective action, preventative action, defect repair, updates
106
Manage Project Knowledge Process
using existing knowledge and creating new knowledge to achieve the project's objectives and contribute to organizational learning
107
Manage Project Knowledge Process- Key Benefit
- key benefits are that prior organizational knowledge is leveraged to produce or improve the project outcomes, and knowledge created by the project is available to support organizational operations and future projects or phases
108
Manage Project Knowledge - Inputs (5) 1
- Project Management Plan (all components)
109
Manage Project Knowledge - Inputs (5) 2
- project documents (lessons learned register, project team assignments, resource breakdown structure, stakeholder register)
110
Manage Project Knowledge - Inputs (5) 3
- deliverables
111
Manage Project Knowledge - Inputs (5) 4
- EEFs
112
Manage Project Knowledge - Inputs (5) 5
- OPAs
113
Manage Project Knowledge - Tools and Techniques (4) 1
- expert judgement
114
Manage Project Knowledge - Tools and Techniques (4) 2
- knowledge management
115
Manage Project Knowledge - Tools and Techniques (4) 3
- information management
116
Manage Project Knowledge - Tools and Techniques (4) 4
- interpersonal and team skills (active listening, facilitation, leadership, networking, political awareness)
117
Manage Project Knowledge - Outputs (3) 1
- lessons learned register
118
Manage Project Knowledge - Outputs (3) 2
- Project Management Plan updates (any component)
119
Manage Project Knowledge - Outputs (3) 3
- OPA updates
120
Explicit knowledge
knowledge that can be readily codified using words, pictures, and numbers
121
Tacit knowledge
knowledge that is personal and difficult to express, such as beliefs, insights, experiences, and "know-how"
122
Knowledge management is about...
making sure the skills, experience, and expertise of the project team and other stakeholders are used before, during, and after the project
123
The most important part of knowledge management is...
creating an atmosphere of trust so that people are motivated to share their knowledge
124
In practice, knowledge is shared using...
a mixture of knowledge management tools and techniques (interactions between people) and information management tools and techniques (in which people codify part of their explicit knowledge by documenting it so it can be shared)
125
Formal, rigid communication requirements are good for...
sharing information
126
Informal communication is more effective for...
creating new knowledge and integrating knowledge across diverse stakeholder groups
127
Knowledge management tools and techniques connect people so that they...
can work together to create new knowledge, share tacit knowledge, and integrate the knowledge of diverse team members
128
Information management tools and techniques are used to...
create and connect people to information
129
The lessons learned register is...
created as an output of this process early in the project
130
Monitor and Control Project Work Process
tracking, reviewing, and reporting the overall progress to meet the performance objectives defined in the Project Management Plan
131
Moniteor and Control Work Process Benefits
- key benefits are that it allows stakeholders to understand the current state of the project, to recognize the actions taken to address any performance issues, and to have visibility into the future project status with cost and schedule forecasts
132
Monitor and Control Project Work - Inputs (6) 1
- Project Management Plan (any component)
133
Monitor and Control Project Work - Inputs (6) 2
- Project documents (assumption log, basis of estimates, cost forecasts, issue log, lessons learned register, milestone list, quality reports, risk register, risk report, schedule forecasts)
134
Monitor and Control Project Work - Inputs (6) 3
- work performance information
135
Monitor and Control Project Work - Inputs (6) 4
- agreements
136
Monitor and Control Project Work - Inputs (6) 5
- EEFs
137
Monitor and Control Project Work - Inputs (6) 6
- OPAs
138
Monitor and Control Project Work - Tools and Techniques (4) 1
- expert judgement
139
Monitor and Control Project Work - Tools and Techniques (4) 2
- data analysis (alternatives analysis, cost-benefit analysis, earned value analysis, root cause analysis, trend analysis)
140
Monitor and Control Project Work - Tools and Techniques (4) 3
- decision making (voting)
141
Monitor and Control Project Work - Tools and Techniques (4) 4
- meetings
142
Monitor and Control Project Work - Outputs (4) 1
- work performance reports
143
Monitor and Control Project Work - Outputs (4) 2
- change requests
144
Monitor and Control Project Work - Outputs (4) 3
- project management plan updates (any component)
145
Monitor and Control Project Work - Outputs (4) 4
- project documents updates (cost forecasts, issue log, lessons learned register, risks register, schedule forecasts)
146
Monitoring includes...
Collecting, measuring, and assessing measurements and trends to effect process improvements
147
Control includes...
determining corrective or preventative actions or replanning and following up on action plans to determine whether the actions taken resolved the performance issue
148
To become work performance information...
the work performance data is compared with the project management plan components, project documents, and other project variables
149
Alternatives analysis
used to select the corrective actions or a combination of corrective and preventative actions when a deviation occurs
150
Trend analysis
used to forecast future performance based on past results
151
Trend Analysis 2
- looks ahead in the project for expected slippages and warns the PM ahead of time that there may be problems later in the schedule if the established trend persists
152
Variance analysis
reviews the differences (or variance) between planned and actual performance
153
Work performance reports
The physical or electronic representation of work performance information compiled in project documents, intended to generate decisions, actions, or awareness
154
Perform Integrated Change Control Process (3) 1
reviewing all change requests; approving changes and managing changes to deliverables, project documents, and the project management plan; and communicating the decisions
155
Perform Integrated Change Control Process (3) 2
- reviews all requests for changes to project documents, deliverables, or the project management plan and determines the resolution of the change requests
156
Perform Integrated Change Control Process (3) 3
- key benefit is that it allows or documented changes within the project to be considered in an integrated manner while addressing overall project risk, which often arises from changes made without consideration of the overall project objective or plans
157
Perform Integrated Change Control - Inputs (6) 1
-Project Management Plan (change management plan, configuration management plan, scope baseline, schedule baseline, cost baseline)
158
Perform Integrated Change Control - Inputs (6) 2
- project documents (basis of estimates, change log, requirements traceability matrix, risk report)
159
Perform Integrated Change Control - Inputs (6) 3
- work performance reports
160
Perform Integrated Change Control - Inputs (6) 4
- change requests
161
Perform Integrated Change Control - Inputs (6) 5
- EEFs
162
Perform Integrated Change Control - Inputs (6) 6
- OPAs
163
Perform Integrated Change Control - Tools and Techniques (5) 1
- expert judgement
164
Perform Integrated Change Control - Tools and Techniques (5) 2
- change control tools
165
Perform Integrated Change Control - Tools and Techniques (5) 3
- data analysis (alternatives analysis, cost-benefit analysis)
166
Perform Integrated Change Control - Tools and Techniques (5) 4
- decision making (voting, autocratic decision making, multi-criteria decision analysis)
167
Perform Integrated Change Control - Tools and Techniques (5) 5
- meetings
168
Perform Integrated Change Control - Outputs (3) 1
- approved change requests
169
Perform Integrated Change Control - Outputs (3) 2
- project management plan updates (any component)
170
Perform Integrated Change Control - Outputs (3) 3
- project documents updates (change log)
171
Changes may be requested by...
any stakeholder involved with the project and may occur at any time throughout the project life cycle
172
Although changes may be initiated verbally...
they should be recorded in written form and entered into the change management and/or configuration management system
173
configuration management plan
Describes the configurable items of the project and identifies the items that will be recorded and updated so that the product of the project remains consistent and operable
174
Configuration control is focused on...while change control is focused on...
the specification of both the deliverables and the processes,
175
autocratic decision making
one individual takes responsibility for making the decision for the group
176
Close Project or Phase Process
finalizing all activities for the project, phase, or contract
177
Close Project or Phase Process Key Benefit
- key benefits re the project or phase information is archived, the planned work is completed, and organizational team resources are released to pursue new endeavors
178
Close Project or Phase - Inputs (8) 1
- Project charter
179
Close Project or Phase - Inputs (8) 2
- project management plan
180
Close Project or Phase - Inputs (8) 3
- project documents
181
Close Project or Phase - Inputs (8) 4
- accepted deliverables
182
Close Project or Phase - Inputs (8) 5
- business documents
183
Close Project or Phase - Inputs (8) 6
- agreements
184
Close Project or Phase - Inputs (8) 7
- procurement documentation
185
Close Project or Phase - Inputs (8) 8
- OPAs
186
Close Project or Phase - Tools and Techniques (3) 1
- expert judgement
187
Close Project or Phase - Tools and Techniques (3) 2
- data analysis
188
Close Project or Phase - Tools and Techniques (3) 3
- meetings
189
Close Project or Phase - Outputs (4) 1
- project documents updates
190
Close Project or Phase - Outputs (4) 2
- final product, service, or result transition
191
Close Project or Phase - Outputs (4) 3
- final report
192
Close Project or Phase - Outputs (4) 4
- OPA updates
193
Benefits management plan
outlines the target benefits of the project
194
Final report (definition)
provides a summary of the project performance
195
Chp 4: Project Integration Management processes (7) 1
1. Develop Project Charter
196
Chp 4: Project Integration Management processes (7) 2
2. Develop Project Management Plan
197
Chp 4: Project Integration Management processes (7) 3
3. Direct and Manage Project Work
198
Chp 4: Project Integration Management processes (7) 4
4. Manage project knowledge
199
Chp 4: Project Integration Management processes (7) 5
5. monitor and control project work
200
Chp 4: Project Integration Management processes (7) 6
6. perform integrated change control
201
Chp 4: Project Integration Management processes (7) 7
7. close project or phase
202
4.1: develop project charter - inputs (4) 1
- business case
203
4.1: develop project charter - inputs (4) 2
- agreements
204
4.1: develop project charter - inputs (4) 3
- EEFs
205
4.1: develop project charter - inputs (4) 4
- OPAs
206
4.1: develop project charter - tools and techniques (10) 1
- data gathering
207
4.1: develop project charter - tools and techniques (10) 2
- expert judgment
208
4.1: develop project charter - tools and techniques (10) 3
- brainstorming
209
4.1: develop project charter - tools and techniques (10) 4
- focus groups
210
4.1: develop project charter - tools and techniques (10) 5
- interviews
211
4.1: develop project charter - tools and techniques (10) 6
- interpersonal and team skills
212
4.1: develop project charter - tools and techniques (10) 7
- conflict mgt
213
4.1: develop project charter - tools and techniques (10) 8
- facilitation
214
4.1: develop project charter - tools and techniques (10) 9
- meetings mgt
215
4.1: develop project charter - tools and techniques (10) 10
- meetings
216
4.1: develop project charter - outputs (2) 1
- project charter
217
4.1: develop project charter - outputs (2) 2
- assumption log
218
4.2: develop project management plan - inputs (4) 1
- project charter
219
4.2: develop project management plan - inputs (4) 2
- outputs from other processes
220
4.2: develop project management plan - inputs (4) 3
- EEFs
221
4.2: develop project management plan - inputs (4) 4
- OPAs
222
4.2: develop project management plan - tools and techniques (11) 1
- expert judgement
223
4.2: develop project management plan - tools and techniques (11) 2
- data gathering
224
4.2: develop project management plan - tools and techniques (11) 3
- brainstorming
225
4.2: develop project management plan - tools and techniques (11) 4
- checklists
226
4.2: develop project management plan - tools and techniques (11) 5
- focus groups
227
4.2: develop project management plan - tools and techniques (11) 6
- interviews
228
4.2: develop project management plan - tools and techniques (11) 7
- interpersonal and team skills
229
4.2: develop project management plan - tools and techniques (11) 8
- conflict management
230
4.2: develop project management plan - tools and techniques (11) 9
- facilitation
231
4.2: develop project management plan - tools and techniques (11) 10
-meeting management
232
4.2: develop project management plan - tools and techniques (11) 11
- meetings
233
4.2: develop project management plan - outputs (1)
- project management plan
234
4.3: direct and manage project work - inputs (13) 1
- project management plan (any component)
235
4.3: direct and manage project work - inputs (13) 2
- project documents
236
4.3: direct and manage project work - inputs (13) 3
- change log
237
4.3: direct and manage project work - inputs (13) 4
- lessons learned register
238
4.3: direct and manage project work - inputs (13) 5
- milestone list
239
4.3: direct and manage project work - inputs (13) 6
- project communications
240
4.3: direct and manage project work - inputs (13) 7
- project schedule
241
4.3: direct and manage project work - inputs (13) 8
- requirements traceability matrix
242
4.3: direct and manage project work - inputs (13) 9
- risk register
243
4.3: direct and manage project work - inputs (13) 10
- risk report
244
4.3: direct and manage project work - inputs (13) 11
- approved change requests
245
4.3: direct and manage project work - inputs (13) 12
- EEFs
246
4.3: direct and manage project work - inputs (13) 13
- OPAs
247
4.3: direct and manage project work - tools and techniques (3) 1
- expert judgement
248
4.3: direct and manage project work - tools and techniques (3) 2
- project management information system
249
4.3: direct and manage project work - tools and techniques (3) 3
- meetings
250
4.3: direct and manage project work - outputs (13) 1
- deliverables
251
4.3: direct and manage project work - outputs (13) 2
- work performance data
252
4.3: direct and manage project work - outputs (13) 3
- issue log
253
4.3: direct and manage project work - outputs (13) 4
- change requests
254
4.3: direct and manage project work - outputs (13) 5
- project management updates (any component)
255
4.3: direct and manage project work - outputs (13) 6
- project documents updates
256
4.3: direct and manage project work - outputs (13) 7
- activity list
257
4.3: direct and manage project work - outputs (13) 8
- assumption log
258
4.3: direct and manage project work - outputs (13) 9
- lessons learned register
259
4.3: direct and manage project work - outputs (13) 10
- requirements documentation
260
4.3: direct and manage project work - outputs (13) 11
- risk register
261
4.3: direct and manage project work - outputs (13) 12
- stakeholder register
262
4.3: direct and manage project work - outputs (13) 13
- OPA updates
263
4.4: manage project knowledge - inputs (9) 1
- project management plan (all components)
264
4.4: manage project knowledge - inputs (9) 2
- project documents
265
4.4: manage project knowledge - inputs (9) 3
- lessons learned register
266
4.4: manage project knowledge - inputs (9) 4
- project team assignments
267
4.4: manage project knowledge - inputs (9) 5
- resource breakdown structure
268
4.4: manage project knowledge - inputs (9) 6
- stakeholder register
269
4.4: manage project knowledge - inputs (9) 7
- deliverables
270
4.4: manage project knowledge - inputs (9) 8
- EEFs
271
4.4: manage project knowledge - inputs (9) 9
- OPAs
272
4.4: manage project knowledge - tools and techniques (9) 1
- expert judgement
273
4.4: manage project knowledge - tools and techniques (9) 2
- knowledge management
274
4.4: manage project knowledge - tools and techniques (9) 3
- information management
275
4.4: manage project knowledge - tools and techniques (9) 4
- interpersonal and team skills
276
4.4: manage project knowledge - tools and techniques (9) 5
- active listening
277
4.4: manage project knowledge - tools and techniques (9) 6
- facilitation
278
4.4: manage project knowledge - tools and techniques (9) 8
- leadership
279
4.4: manage project knowledge - tools and techniques (9) 8
- networking
280
4.4: manage project knowledge - tools and techniques (9) 9
- political awareness
281
4.4: manage project knowledge - outputs (3) 1
- lessons learned register
282
4.4: manage project knowledge - outputs (3) 2
- project management plan updates (any component)
283
4.4: manage project knowledge - outputs (3) 3
- OPAs
284
4.5: monitor and control project work - inputs (16) 1
- project management plan (any component)
285
4.5: monitor and control project work - inputs (16) 2
- project documents
286
4.5: monitor and control project work - inputs (16) 3
- assumption log
287
4.5: monitor and control project work - inputs (16) 4
- basis of estimates
288
4.5: monitor and control project work - inputs (16) 5
- cost forecasts
289
4.5: monitor and control project work - inputs (16) 6
- issue log
290
4.5: monitor and control project work - inputs (16) 7
- lessons learned register
291
4.5: monitor and control project work - inputs (16) 8
- milestone list
292
4.5: monitor and control project work - inputs (16) 9
- quality reports
293
4.5: monitor and control project work - inputs (16) 10
- risk register
294
4.5: monitor and control project work - inputs (16) 11
- risk report
295
4.5: monitor and control project work - inputs (16) 12
- schedule forecasts
296
4.5: monitor and control project work - inputs (16) 13
- work performance information
297
4.5: monitor and control project work - inputs (16) 14
- agreements
298
4.5: monitor and control project work - inputs (16) 15
- EEFs
299
4.5: monitor and control project work - inputs (16) 16
- OPAs
300
4.5: monitor and control project work - tools and techniques (11) 1
- expert judgement
301
4.5: monitor and control project work - tools and techniques (11) 2
- data analysis
302
4.5: monitor and control project work - tools and techniques (11) 3
- alternatives analysis
303
4.5: monitor and control project work - tools and techniques (11) 4
- cost-benefit analysis
304
4.5: monitor and control project work - tools and techniques (11) 5
- earned value analysis
305
4.5: monitor and control project work - tools and techniques (11) 6
- root cause analysis
306
4.5: monitor and control project work - tools and techniques (11) 7
- trend analysis
307
4.5: monitor and control project work - tools and techniques (11) 8
- variance analysis
308
4.5: monitor and control project work - tools and techniques (11) 9
- decision making
309
4.5: monitor and control project work - tools and techniques (11) 10
- voting
310
4.5: monitor and control project work - tools and techniques (11) 11
- meetings
311
4.5: monitor and control project work - outputs (9) 1
- work performance outputs
312
4.5: monitor and control project work - outputs (9) 2
- change requests
313
4.5: monitor and control project work - outputs (9) 3
- project management plan updates (any component)
314
4.5: monitor and control project work - outputs (9) 4
- project documents updates
315
4.5: monitor and control project work - outputs (9) 5
- cost forecasts
316
4.5: monitor and control project work - outputs (9) 6
- issue log
317
4.5: monitor and control project work - outputs (9) 7
- lessons learned register
318
4.5: monitor and control project work - outputs (9) 8
- risk register
319
4.5: monitor and control project work - outputs (9) 9
- schedule forecasts
320
4.6: perform integrated change control - inputs (15) 1
- project management plan
321
4.6: perform integrated change control - inputs (15) 2
- change management plan
322
4.6: perform integrated change control - inputs (15) 3
- configuration management plan
323
4.6: perform integrated change control - inputs (15) 4
- scope baseline
324
4.6: perform integrated change control - inputs (15) 5
- schedule baseline
325
4.6: perform integrated change control - inputs (15) 6
- cost baseline
326
4.6: perform integrated change control - inputs (15) 7
- project documents
327
4.6: perform integrated change control - inputs (15) 8
- basis of estimates
328
4.6: perform integrated change control - inputs (15) 9
- change log
329
4.6: perform integrated change control - inputs (15) 10
- requirements traceability matrix
330
4.6: perform integrated change control - inputs (15) 11
- risk report
331
4.6: perform integrated change control - inputs (15) 12
- work performance reports
332
4.6: perform integrated change control - inputs (15) 13
- change requests
333
4.6: perform integrated change control - inputs (15) 14
- EEFs
334
4.6: perform integrated change control - inputs (15) 15
- OPAs
335
4.6: perform integrated change control - tools and techniques (10) 1
- expert judgment
336
4.6: perform integrated change control - tools and techniques (10) 2
- change control tools
337
4.6: perform integrated change control - tools and techniques (10) 3
- data analysis
338
4.6: perform integrated change control - tools and techniques (10) 4
- alternatives analysis
339
4.6: perform integrated change control - tools and techniques (10) 5
- cost-benefit analysis
340
4.6: perform integrated change control - tools and techniques (10) 6
- decision making
341
4.6: perform integrated change control - tools and techniques (10) 7
- voting
342
4.6: perform integrated change control - tools and techniques (10) 8
- autocratic decision making
343
4.6: perform integrated change control - tools and techniques (10) 9
- multicriteria decision analysis
344
4.6: perform integrated change control - tools and techniques (10) 10
meetings
345
4.6: perform integrated change control - outputs (4) 1
- approved change requests
346
4.6: perform integrated change control - outputs (4) 2
- project management plan updates (any component)
347
4.6: perform integrated change control - outputs (4) 3
- project documents updates
348
4.6: perform integrated change control - outputs (4) 4
- change log
349
4.7: close project or phase - inputs (22) 1
- project charter
350
4.7: close project or phase - inputs (22) 2
- project management plan (all components)
351
4.7: close project or phase - inputs (22) 3
- project documents
352
4.7: close project or phase - inputs (22) 4
- assumption log
353
4.7: close project or phase - inputs (22) 5
- basis of estimates
354
4.7: close project or phase - inputs (22) 6
- change log
355
4.7: close project or phase - inputs (22) 7
- issue log
356
4.7: close project or phase - inputs (22) 8
- lessons learned register
357
4.7: close project or phase - inputs (22) 9
- milestone list
358
4.7: close project or phase - inputs (22) 10
- project communications
359
4.7: close project or phase - inputs (22) 11
- quality control measurements
360
4.7: close project or phase - inputs (22) 12
- quality reports
361
4.7: close project or phase - inputs (22) 13
- requirements documentation
362
4.7: close project or phase - inputs (22) 14
- risk register
363
4.7: close project or phase - inputs (22) 15
- risk report
364
4.7: close project or phase - inputs (22) 16
- accepted deliverables
365
4.7: close project or phase - inputs (22) 17
- business documents
366
4.7: close project or phase - inputs (22) 18
- business case
367
4.7: close project or phase - inputs (22) 19
- benefits management plan
368
4.7: close project or phase - inputs (22) 20
- agreements
369
4.7: close project or phase - inputs (22) 21
- procurement documentation
370
4.7: close project or phase - inputs (22) 22
- OPAs
371
4.7: close project or phase - tools and techniques (7) 1
- expert analysis
372
4.7: close project or phase - tools and techniques (7) 2
- data analysis
373
4.7: close project or phase - tools and techniques (7) 3
- document analysis
374
4.7: close project or phase - tools and techniques (7) 4
- regression analysis
375
4.7: close project or phase - tools and techniques (7) 5
- trend analysis
376
4.7: close project or phase - tools and techniques (7) 6
- variance analysis
377
4.7: close project or phase - tools and techniques (7) 7
- meetings
378
4.7: close project or phase - outputs (6) 1
- project documents updates
379
4.7: close project or phase - outputs (6) 2
- lessons learned register
380
4.7: close project or phase - outputs (6) 3
- final product, service, or result transition
381
4.7: close project or phase - outputs (6) 4
- final report
382
4.7: close project or phase - outputs (6) 5
- OPA updates
383
4.7: close project or phase - outputs (6) 6
Project Scope Management
384
4.7: close project or phase - outputs (6) 1
includes the processes required to ensure the project includes all the work required, and only the work required, to complete the project successfully
385
Project Scope Management Processes (6) 1
1. Plan Scope Management
386
Project Scope Management Processes (6) 2
2. Collect Requirements
387
Project Scope Management Processes (6) 3
3. Define Scope
388
Project Scope Management Processes (6) 4
4. Create WBS
389
Project Scope Management Processes (6) 5
5. Validate Scope
390
Project Scope Management Processes (6) 6
6. Control Scope
391
Product scope
The features and functions that characterize a product, service, or result
392
Project scope
The work performed to deliver a product, service, or result with the specified features and function
393
Predictive/waterfall life cycle
The project deliverables are defined at the beginning of the project and any changes to the scope are progressively managed
394
Adaptive/agile life cycle
Deliverables are developed over multiple iterations where a detailed scope is defined and approved for each iteration when it begins
395
For projects with adaptive life cycles...
three processes (collect requirements, define scope, and create WBS) are repeated for each iteration
396
In a predictive project...
these processes are performed toward the beginning of the project and updated as necessary, using the integrated change control process
397
The project manager is responsible for...
ensuring that requirements-related work is accounted for in the project management plan and that requirements-related activities are performed on time and within budget and deliver value
398
Agile methods deliberately spend less time trying to...
define and agree on scope in the early stage of the project and spend more time establishing the process for its ongoing discovery and refinement
399
In agile approaches, the requirements constitute...
the backlog
400
Plan Scope Management Process
creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled
401
Plan Scope Management - Inputs (5) 1
1. project charter
402
Plan Scope Management - Inputs (5) 2
2. project management plan (quality management plan, project life cycle description, development approach)
403
Plan Scope Management - Inputs (5) 3
3. EEFs
404
Plan Scope Management - Inputs (5) 4
4. OPAs
405
Plan Scope Management - Inputs (5) 5
Plan Scope Management - Tools and Techniques (3)
406
Plan Scope Management - Tools and Techniques (3) 1
1. expert judgement
407
Plan Scope Management - Tools and Techniques (3) 2
2. data analysis (Alternatives analysis)
408
Plan Scope Management - Tools and Techniques (3) 3
3. meetings
409
Plan Scope Management - Outputs (2) 1
1. scope management plan
410
Plan Scope Management - Outputs (2) 2
2. requirements management plan
411
Scope management plan
A component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and verified
412
Project life cycle description
determines the series of phases that a project passes through from its inception to the end of the project
413
Development approach
defines whether waterfall, iterative, adaptive, agile, or a hybrid development approach will be used
414
Scope management plan
a component of the project management plan that describes how the scope will be defined, developed, monitored, controlled, and validated
415
Requirements management plan
A component of the project management plan that describes how project and product requirements will be analyzed, documented, and managed
416
Collect Requirements Process
The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives
417
- key benefit is that it provides the basis for defining the product scope and project scope
Collect Requirements - Inputs (7)
418
Collect Requirements - Inputs (7) 1
1. project charter
419
Collect Requirements - Inputs (7) 2
2. project management plan (scope management plan, requirements management plan, stakeholder engagement plan)
420
Collect Requirements - Inputs (7) 3
3. project documents (Assumption log, lessons learned register, stakeholder register)
421
Collect Requirements - Inputs (7) 4
4. business documents (business case)
422
Collect Requirements - Inputs (7) 5
5. agreements
423
Collect Requirements - Inputs (7) 6
6. EEFs
424
Collect Requirements - Inputs (7) 7
7. OPAs
425
Collect Requirements - Tools and Techniques (8) 1
1. expert judgement
426
Collect Requirements - Tools and Techniques (8) 2
2. data gathering (brainstorming, interviews, focus groups, questionnaires and surveys, benchmarking)
427
Collect Requirements - Tools and Techniques (8) 3
3. data analysis (document analysis)
428
Collect Requirements - Tools and Techniques (8) 4
4. decision making (voting, autocratic decision making, multi-criteria decision analysis)
429
Collect Requirements - Tools and Techniques (8) 5
5. data representation (Affinity diagrams, mind mapping)
430
Collect Requirements - Tools and Techniques (8) 6
6. interpersonal and team skills (nominal group technique, observation/conversation, facilitation)
431
Collect Requirements - Tools and Techniques (8) 7
7. context diagram
432
Collect Requirements - Tools and Techniques (8) 8
8. prototypes
433
Collect Requirements - Outputs (2) 1
1. Requirements documentation
434
Collect Requirements - Outputs (2) 2
2. Requirements traceability matrix
435
The project's success is directly influenced by...
active stakeholder involvement in the discovery and decomposition of needs into project and product requirements and by the care taken in determining, documenting, and managing the requirements of the product, service, or result of the project
436
Requirements become the foundation of...
the WBS
437
the WBS
Focus groups
438
Focus groups
Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result
439
Voting techniques
1. unanimity
440
1. unanimity
2. majority
441
2. majority
3. plurality (The largest block in a group decides, even if a majority is not achieved. This method is generally used when the number of options nominated is more than 2)
442
Autocratic decision making
one individual takes responsibility for making the decision for the group
443
Affinity diagrams
allow large numbers of ideas to be classified into groups for review and analysis
444
Mind mapping
consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas
445
Nominal group technique
Enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization
446
- structured form of brainstorming
context diagram
447
context diagram
Visually depict the product scope by showing a business system (process, equipment, computer system, etc) and how people and other systems interact with it
448
Prototypes
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it
449
Storyboarding
a prototyping technique showing sequence or navigation through a series of images or illustrations
450
Requirements documentation
Describes how individual requirements meet the business need for the project
451
Requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them
452
Define Scope Process
process of developing a detailed description of the project and product
453
Define Scope - Inputs (5) 1
1. project charter
454
Define Scope - Inputs (5) 2
2. project management plan (scope management plan)
455
Define Scope - Inputs (5) 3
3. project documents (assumption log, requirements documentation, risk register)
456
Define Scope - Inputs (5) 4
4. EEFs
457
Define Scope - Inputs (5) 5
5. OPAs
458
Define Scope - Tools and Techniques (5) 1
1. Expert Judgement
459
Define Scope - Tools and Techniques (5) 2
2. Data Analysis (Alternatives Analysis)
460
Define Scope - Tools and Techniques (5) 3
3. Decision Making (Multicriteria Decision Analysis)
461
Define Scope - Tools and Techniques (5) 4
4. Interpersonal & Team Skills (Facilitation)
462
Define Scope - Tools and Techniques (5) 5
5. Product Analysis
463
Define Scope - Outputs (2) 1
1. project scope statement
464
Define Scope - Outputs (2) 2
2. project documents updates (Assumption log, requirements documentation, requirements traceability matrix, stakeholder register)
465
During project planning, the project scope is...
defined and described with greater specificity as more information about the project is known
466
Product analysis
can be used to define products and services; includes asking questions about a product or service and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be delivered
467
Project scope statement
The description of the project scope, major deliverables, and exclusions; includes product scope description, deliverables, acceptance criteria, and project exclusions
468
Project Charter vs Project scope statement
the project charter contains high-level information, while the project scope statement contains a detailed description of scope components
469
Create WBS Process
The process of subdividing project deliverables and project work into smaller, more manageable components
470
Create WBS - Inputs (4) 1
1. project management plan (Scope management plan)
471
Create WBS - Inputs (4) 2
2. project documents (project scope statement, requirements documentation)
472
Create WBS - Inputs (4) 3
3. EEFs
473
Create WBS - Inputs (4) 4
4. OPAs
474
Create WBS - Tools and Techniques (2) 1
1. Expert Judgement
475
Create WBS - Tools and Techniques (2) 2
2. Decomposition
476
Create WBS - Outputs (2) 1
1. scope baseline
477
Create WBS - Outputs (2) 2
2. project documents updates (assumption log, requirements documentation)
478
The WBS is a...
hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables
479
Work package
The lowest level in a WBS with a unique identifier; can be used to group the activity where work is scheduled and estimated, monitored, and controlled
480
Decomposition
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts
481
Rolling wave planning
waiting until the deliverable or the subcomponent is agreed on, so the details of the WBS can be developed
482
Scope baseline
The approved version of a scope statement, WBS, and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison
483
planning package
A work breakdown structure component below the control account with known work content but without detailed schedule activities
484
WBS dictionary
A document that provides detailed deliverable, activity, and scheduling information about each component in the WBS
485
Validate Scope Process
The process of formalizing acceptance of the completed project deliverables
486
Validate Scope - Inputs (4) 1
1. project management plan (Scope management plan, requirements management plan, scope baseline)
487
Validate Scope - Inputs (4) 2
2. project documents (lessons learned register, quality reports, requirements documentation, requirements traceability matrix)
488
Validate Scope - Inputs (4) 3
3. verified deliverables
489
Validate Scope - Inputs (4) 4
4. work performance data
490
Validate Scope - Tools and Techniques (2) 1
1. inspection
491
Validate Scope - Tools and Techniques (2) 2
2. decision making (Voting)
492
Validate Scope - Outputs (4) 1
1. accepted deliverables
493
Validate Scope - Outputs (4) 2
2. work performance information
494
Validate Scope - Outputs (4) 3
3. change requests
495
Validate Scope - Outputs (4) 4
4. projects document updates (lessons learned register, requirements documentation, requirements traceability matrix)
496
Validate scope vs control quality processes
validate scope is primarily concerned with acceptance of the deliverables, while control quality is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables
497
Verified deliverables
project deliverables that are completed and checked for correctness through Control Quality Process
498
Deliverables that meet the acceptance criteria are...
formally signed off and approved by the customer or sponsor
499
Work performance information
includes information about project progress, such as why deliverables have been accepted and which have not been accepted and the reasons why
500
Control Scope Process
Monitoring the status of the project and product scope and managing changes to the scope baseline
