PMP Group and Knowledge Areas Flashcards

1
Q

Project Charter

A
High level req
Risks
Milestones
Pre-approved finances
Key stakeholders`
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Project scope statement

A
  • description
  • acceptance criteria
  • deliverable
  • Project exclusion
  • constraints
  • assumptions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Scope baseline

A

Approved:

  • project scope statement
  • WBS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Other name for Requirements Mgmt Plan

A

Business Analysis Plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Difference between projects charter and scope statement

A
  • project charter - more about objectives and very high level
  • project scope statement - focus only on actual project outcome
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Output of Collect Requirements Proess

A

Requirements traceability Matrix

Requirements documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Requirements documentation

A

Requirements from different areas like:

  • Business req.
  • Stakeholders req.
  • Quality req.
  • and others
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Affinity diagrams

A

grouping of elements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Nominal group technique

A
  1. Silent brainstorming
  2. collecting ideas
  3. Discuss pros and cons of all ideas
  4. voting
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Task decomposition process (steps):

A
  1. identified deliverables
  2. Organize WBS
  3. Decompose
  4. add unique ID
  5. check if work packages are aligned with requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Precedence diagram method

A

metoda diagramu pierwszeństwa
Finish to start
itp

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Lead and Lag

A

Lead - how much next task can be advanced

Lag - how much next task will be delayed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Management by objectives

A

Setting objectives at the beg. of project/phase enforce commitment and engagement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Schedule model

A

Representation of the plan + all schedule artifacts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Brook’s law

A

More people at the end of project may delay it in overall

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Resource optimization - Leveling

A

Resources = constant; schedule -> may change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Resource optimization - Smoothing

A

Schedule = constant; Resources-> may change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Schedule compression

A
Crashing (more people)
Fast tracking (overlapping)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Project budget component

A
  1. Work package cost estimate = Activity cost Estimates + Activity contingency reserves
  2. Control Account = Contingency reserves + Work package cost estimate
  3. Project Budget = Management reserves + Cost Baseline (Control account)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Cost of quality

A

Cost of conformance: Preventive cost & appraisal cost

Cost of nonconformance: Internal/external failure costs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Vision

A

set of artefacts/mindsets/deliverables/aspects which should not change during the Project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Behavior Modeling

A

be an example for the others

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Salience Model

A
(Model istotnosci)
Divide stakeholders by:
Power
Urgency
Legitimacy
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Push/Pull methods

A

Push: To som specific group. Meails/letters/fax/voice msg
Pull: websites/ eleraning/ knowleadge bases/ bulletin boards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Hurdle (przeszkoda)
- Impediments - some situation which may slow down project - Obstacles - problems which can be solved - Blockers - Events that stops work/progress
26
Delphi technique
for complex issues -> estimate probability of some event
27
risk identification
- structured review of documents - gathering info by brainstorming, Checklist itp - assumptions & constrains analysis - SWOT analysis
28
Difference between Risk and issue
Risk - focused on the future/ positive or negative/ documented in risk register/ risk response Issue - focuesd on the present/ positive or negative/ documented in issue log / warkaround
29
Qualitative Risk Analysis
Set priority to risks | Must have
30
Quantitative Risk Analysis
Precise numbers related to risk probability nice to have - only for most important Use probabilistic distribution/simulations
31
Risk response - Thread
``` escalate avoid transfer mitigate accept ```
32
Risk response - Opportunity
``` escalate exploit share enhance accept ```
33
Contract types
firm fixed price - price & scope = const fixed price incentive fee - price ceiling + performance fixed price with economic price adjustment - price + inflation
34
cost-reimbursable contracts
(zwrot kosztow) cost plus fixed fee cost plus incentive fee (cost + performance) cost plus award fee (cost + 100x perf)
35
Procurement mgmt -> source selection methods
sole source - no competition but proposal is negotiated | Fixed price - price = const but scope may change
36
Bid documents - type of requests
- request for info - question aboutwhat seller need to estimate cost - request for quotation - what is the cost - request for proposal - very formal with rules and restrictions
37
Stakeholder Analysis
group stakeholders by similarities
38
Stakeholder engagement Assessment Matrix
Compare current engagement level with desired. categories: | Unaware/Resistant/Neutral/Supportive/Leading
39
Explicit and Tacit knowledge
tacit - know how, experience | explicit - knowledge codified and digitized in books, documents, reports
40
scope of Knowledge mgmt
All opportunities to share knowledge
41
scope of information mgmt
Ways to codify explicit knowledge
42
case and effect diagram
Ishikawa diagram | fishbone diagram
43
design for X
optimize X where X is a project aspect
44
Agile estimating
rolling-wave planning methods -> task level on a just-in-time basis
45
Quality assurance
actions needed to create product with required quality
46
5 phillars of compliance
1. Compliance Documentation: draft documents (dynamically will change) -> aligned with ISO 9000 -> because it is treated as a deliverable of the project. 2. Compliance Council: Group of people (with experts) which needs to tak part in compliance process 3. Compliance Risk: Not only during project but also those which extend scope 4. Compliance Audit: Body independent from management wich will verify all aspects of project if they fulfill compliance needs 5. Compliance Responsibilities: all activities and their corresponding compliance objectives shall be allocated as parts of the project’s tasks and processes. Project managers must extract themselves from the compliance responsibility and act only as coordinators of the resources and activities required to achieving the proposed objectives.
47
Tuckman ladder
forming/storming/norming/performing/adjourning
48
Conflict mgmt technique
* withdraw (avoid) -> lose-leave * smooth (accommodate) ustapic by zachowac harmonie -> yield-lose * compromise (reconcile) pogodzic -> moderate lose-moderate lose * force (direct) -> win-lose * collaborate (problem solve) -> integrative
49
Variance analysis
collect data of performance/estimations/... and use it as a base for retrospective discussions
50
Key Performance Indicator
need to satisfy SMART (specific, measurable, achievable, relevant, time-bounded)
51
Information Radiators
agile practice. Shared place where important info are shared
52
Velocity Chart
overview how much work has been delivered for each sprint
53
Value Stream Map
Mapa strumienia wartości to schemat przepływów informacji i materiałów w procesie. Dzięki tej technice można wykluczyć czynności zbędne w procesie
54
change control board
committee that consists of Subject Matter Experts who decide whether to implement proposed changes to a project
55
change control system - provides:
forms tracking methods processes approval levels
56
Validate scope -> flow
1. Verified deliverable (quality controle) + Work performance date (Develop and Manage project work) 2. Validation 3. Accepted deliverable + Work perf. info OR change req.
57
Project-Funding Requirements
How much (money) is needed by project in paritcular moment in time
58
Validate scope -> flow
1. Verified deliverable (quality control) + Work performance date (Develop and Manage project work) 2. Validation 3. Accepted deliverable + Work perf. info OR change req.
59
Project-Funding Requirements
How much (money) is needed by project in particular moment in time
60
claims administration
disputes between seller and buyer
61
Key activities in closing project phase
- customer approvals - procurements - storing info/knowledge - actions to move to next phase
62
Project overview statement
very short description of project to inform all stakeholders what is it about
63
XP Metaphore
require to crete nontechnical metaphore for some problem which help to understand and solve it
64
Product Box Exercise
imagine that you are designing box for your product. What will be on it to best represent your product?
65
McGregors theory X and Theory Y
lazy employs assigned to theory X require micromanagement, ambition employs assigned to theory Y and they require ownership of their work
66
Herzberg Motivation-hygiene theory
there are hygiene factors which are impacting satisfaction/dissatisfaction. Examples for diss...: salary/security/status/work environment & for satis: recognition/achievements
67
McClelland's Acquired needs theory
People are motivated by following needs: achivement/affiliation/power (osiagniecia/przynaleznosc/wladza)
68
Vrooms Expectancy theory
people are motivated thanks to reward they will get for their effort
69
Termination by extinction
The project may be stopped because it has been either successful, or unsuccessful
70
Termination by addition
This is where a project is made more or less an external, but full-fledged addition to the parent organization
71
Termination by integration
The output of the project becomes part-and-parcel of the operating systems of the parent or client, becoming embedded in day-to-day operations
72
Termination by starvation
financial, human, and material resources needed to execute the project are curtailed or withheld
73
Business case
``` list objectives critical success factors why project undertaken analysis of situation recommendations ```
74
Constrained optimization analysis
- Project Selection Method - mathematical model of calculating whether the project is financially viable or not - finding "best available" values of some objective function given a defined domain
75
Project Selection Methods
- Benefit Measurement Method (comparing one project with other competing projects) - Constrained Optimization Method (mathematical model of calculating whether the project is financially viable or not )