Exam #2 Flashcards

1
Q

Project Schedule importance

A

key technical aspect of project management serves as the main integration point for planning efforts and includes most project plans

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

Project Schedule steps

A

is a tool that
1)merges all of the work to be performed(WBS)
2) their estimated duration/effort
3) their task relationships(Activity on node)
4)assigned resources,
5) risks response
to a calendar

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

Final Project schedule should be

A

complete (all WBS), accepted(by stakeholders) , realistic (time expectations, formal (documented)

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

time decomposition

A

breaking down project deliverables into smaller and more manageable activities

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

analogous estimating

A

top down estimating; history

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

parametric estimating

A

multiplying work to be done by a known productivity rate

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

contingency reserves

A

used for known unknowns by project manager

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

management reserves

A

used for unknown unknown by management sh

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

shorten schedule

A

crashing:add resources to critical path activities only
fast tackling: perfrom critical path activities in parallel
process improvements: gaining over productivity
overtime: get extra time

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

critical path

A

The earliest path through the project, given
the current task relationships and estimated
durations

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

mandatory dependencies

A

hard dependencies or logic

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

discretionary dependencies

A

permed way of doing things

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

external dependencies

A

project depended on external environment factors(weather, permits)

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

straight line depreciation

A

Ann. Dep. = (Purchase Price – Salvage Value) / Usable Life

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

Developing initial budget

A

use bottom up approach and excel

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

estimating the budget phases

A

initial phase: ROM (-50,+50)
planning phase: definitive estimate (-5,+10)

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

Estimating costs

A

analogous estimating: top-down estimating using history
parametric estimating: multiply the quantity of work to be performed by a productivity rate

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

Finalizing budget

A

once the project schedule nears completion and actual resources have been identified

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

project control

A

processes that enure that project objectives are met by monitoring and measuring progress regularly to identify variances from plan so that corrective action can be taken if necessary

20
Q

Principles of project control

A

PDA (prevention, detection, action)

21
Q

Management fundamentals for project control

A

pay attention early (15% completion rule almost no project recovers from a variance at the 15% completion point

22
Q

Powerful technique for porject control

A

milestone and checkpoints

23
Q

Performance reporting

A

answer 3 big questions:
Where do we stand
what variances exist and how are we solving them
has the forecast changed

24
Q

variances responses

A

take corrective action, ignore small problems, cancel the project if necessary, reset baselines,

25
Q

Project recoveries

A

review planning principles, reset baseline, frequent status check, aggressive issue resolution, ensure clarity, increase visibility and accountability

26
Q

project change

A

a change in any of the critical success factors (scope, schedule, costs, quality, and project acceptance criteria)

27
Q

fundamental for managing project change

A

plan for changes, set up a change control system, educate stakeholders, use the system built, over-communicate, minimize scope changes, be watchdog

28
Q

Project change control system key principles

A

scope changes are documented, evaluated, and approved before, stakeholders are involved with changes and communicated and documented, correct management level supports change requests, impact of change is assessed, roles and responsibilities are clearly defined,

29
Q

project change control system key components

A

change request form, change request log, unique identification number to track, made a control board (stakeholders)

30
Q

Managing project deliverables

A

configuration management, the process by which work products are controlled

31
Q

Managing Project issue

A

proactive project management; the earlier an issue is identified the greater the chance of resolving the issue before it impacts any of the project’s critical success factors

32
Q

The objective of project issue management

A

to identify, record, track, resolve, and communicate all issues that may impact the project

33
Q

principles of project issue management

A

administrative process principles and project manager mindset principle

34
Q

administrative process principles

A

document the issues, track until closure, align with project needs, cost-effective approach

35
Q

project manager mindset principle

A

ringmaster: a focal point for tackling issues
smiling bulldog: persistence with a warm style
swivel head: on the constant lookout for potential trouble
goaltender: let no issues go unnoticed or unresolved
disciplined

36
Q

key features of issue management system

A

a clear process with escalation procedures, issue log, issue data point, issue log admin

37
Q

Best practices for dealing with project issues

A

assign a unique id to the issue, make one person responsible, take ownership, try to solve the issue at the lowest level, and find root cause of issue, review issues frequently

38
Q

Manging project risks

A

is the ultimate proactive project management ; to identify and prepare for any potential threats to the projects critical success factors before they occur

39
Q

risk matrix

A

id #, risk description, probability, impact, importance( prob*impact), category, owner
add scale 1-10 at bottom

40
Q

rik response options

A

avoidance, acceptance, monitoring and prepare, mitigate, transference(insurance policy)

41
Q

powerful risk control strategies

A

tackle high risks first, communicate with stakeholders, detect planning defects

42
Q

project quality

A

conformance to requirements and fitness of use, project satisfies customer needs and completes what was asked of

43
Q

principles of managing project quality

A

identify targets(needs), plan for quality right size it set expectations, stay customer focused, assume nothing, up to PM to assure quality

44
Q

Tools for project quality

A

checklists, templates, reviews, completion criteria, audits, standards, quality management plans,

45
Q

Leading a project

A

communication skills, technical skills, leadership skills, business management skills, project management fundamentals

46
Q

Keys to better project leadership

A

about the people(customers), visualize the goal and how to get there, earn trust, take ownership, be resilient, facilitate progress, be a teacher, compensate for weakness, have self-control