project++

IPEMC

initiating

planning

executing

monitoring & controlling

Closing

Initiating

business case, project charter, identify stakeholders

planning

scope, schedule budget, risk management, communications, WBS (work breakdown schedule)

executing

complete the work, manage the team, communicate

monitoring and controlling

track progress, manage changes, risks, quality, scope, and cost

closing

final acceptance, lessons learned, archive documentation

acronym for ipemc

I plan on eating mexican cuisine

business case

why should the project happen

project charter

officially authorizes the project

statement of work (SOW)

what work will be performed

work breakdown structure (wbs)

breaks work into manageable pieces

risk register

tracks risks, probability, impact and responses

issue log

problems that are happening now

lessons learned

completed at the end for future projectss

Scope creep

uncontrolled additions

gold plating

team adds features nobody requested

prevent creep and gold plating with

change control

Change request process

1. identify change

2. document the request

3. analyze impact (cost, scope, schedule, risk)

4. review by change control board

5. approve or reject

6. update project documents

7. implement if approved

change Request Process1

identify change

change Request Process2

document the request

change Request Process3

analyze impact

change Request Process4

review by ccb

change Request Process5

approve or reject

change Request Process6

update project documents

change Request Process7

implement if approved

Risk responses negative

avoid

mitigate

transfer

accept

Risk responses positive

exploit

enhance

share

accept

gantt chart

timeline

network diagram

dependencies and critical path

raci matrix

responsible

accountable

consulted

informed

Leadership Styles Democratic

team input

Leadership Styles autocratic

leader decides

Leadership Styles laissez-faire

hands-off approach

Leadership Styles Servant leader

supports the team

Agile

iterative

customer feedback throughout

adapts to change

waterfall

sequential

requirements fixed

documentation heavy

quality assurance

prevents defects

quality control

finds defects