Introduction to Project Management Damian McCourt HELLO! I am - - PowerPoint PPT Presentation

introduction to project management
SMART_READER_LITE
LIVE PREVIEW

Introduction to Project Management Damian McCourt HELLO! I am - - PowerPoint PPT Presentation

Introduction to Project Management Damian McCourt HELLO! I am Damian McCourt Training full time since 2014 IT infrastructure project manager, BT & FBD You can find me at damian@dcmlearning.ie Today! When to use a project management


slide-1
SLIDE 1

Introduction to Project Management

Damian McCourt

slide-2
SLIDE 2

HELLO!

I am Damian McCourt Training full time since 2014 IT infrastructure project manager, BT & FBD You can find me at damian@dcmlearning.ie

slide-3
SLIDE 3

Today!

▰ When to use a project management approach ▰ Project management methodologies ▰ One fundamental project management tool ▰ Budget, schedule, change management

slide-4
SLIDE 4

Project Management

Defining a project / defining a project manager

slide-5
SLIDE 5

Project?

“A temporary endeavour undertaken to create a unique product, service or result. A project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources”

slide-6
SLIDE 6

Project?

slide-7
SLIDE 7

The Triple Constraints

slide-8
SLIDE 8
slide-9
SLIDE 9

Project Manager Qualities

slide-10
SLIDE 10

Failures

slide-11
SLIDE 11

Failures

slide-12
SLIDE 12

Failures

Deadlines missed Repeated work Budget overruns Reputational damage Quality issues Annoyed stakeholders Scope creep Loss of relevance

slide-13
SLIDE 13

Failures

slide-14
SLIDE 14

Top 4 reasons projects fail

▰ Poor or incomplete requirements ▰ Scope creep ▰ A lack of a structured project management methodology ▰ Lack of change control

slide-15
SLIDE 15

Expert Knowledge

▰ Industry awareness ▰ Subject matter expertise ▰ Political/organisational skills ▰ Attitude to documentation

slide-16
SLIDE 16

Project Management

Project Management Methodologies

slide-17
SLIDE 17

Waterfall and Agile

slide-18
SLIDE 18

Agile

Short, iterative cycles End-user closely involved Requirements unclear Collaborative work

Waterfall

Gated progress User Quality Assurance only Well-defined requirements Strictly managed work

Waterfall and Agile

slide-19
SLIDE 19

Agile

Gradually more refined Avoids assumptions Can go on forever ☹ Needs an experienced PM

Waterfall

Easier to budget and schedule Easier to manage Assumptions can kill a project Requirements may change

Waterfall and Agile

slide-20
SLIDE 20

Assumptions!

▰ NASA/ESA Mars Climate Orbiter ▰ US$ 193.1m ▰ Thrust specified in Pounds ▰ Programmed in Newtons

slide-21
SLIDE 21

Project Management

Some basic tools

slide-22
SLIDE 22

Business Case

slide-23
SLIDE 23

Project Charter

slide-24
SLIDE 24

Project Management Plan

Requirements management plan

Schedule management plan

Cost management plan

Quality management plan

Resource management plan

Risk management plan

Scope statement

slide-25
SLIDE 25

Project Management Plan

slide-26
SLIDE 26

Work Breakdown Structure

▰ Project Charter includes a Scope Statement ▰ Which includes a Main Deliverable: “A new sales office” “Customer relationship management software” “A wedding planning service”

slide-27
SLIDE 27

Work Breakdown Structure

slide-28
SLIDE 28

Work Breakdown Structure

slide-29
SLIDE 29

Work Breakdown Structure

▰ Sets out what is going to be delivered ▰ Allows you to start planning the ‘how’ and ‘when’… ▰ …blueprint for schedule and budget ▰ Clarity for stakeholders – ‘this is what you’re getting’ ▰ Forces stakeholders to focus on deliverables rather than activities

slide-30
SLIDE 30

Work Breakdown Structure

slide-31
SLIDE 31

WBS Activities

▰ Each work package consists of a list of activities ▰ Used to create the project schedule and budget ▰ Have an expected duration ▰ Consume budget and/or resources ▰ Are usually verb-noun format (build frame, test brakes)

slide-32
SLIDE 32

Budget Creation

slide-33
SLIDE 33

Change Management

▰ Scope creep: unmanaged changes to project scope ▰ Any change can be mapped to the WBS ▰ Change to an Activity, Work Package or Key Deliverable? ▰ Cost of the change can be accurately estimated ▰ Great way to highlight the triple constraints

slide-34
SLIDE 34

Project Management

Unique endeavour – time, cost, scope limited

Very easy to get wrong without a framework

Defined approaches tested in the real world

Every project document exists for a reason!

Work Breakdown Structure

Main deliverable – key deliverables – work packages – activities

Budget, schedule, change

slide-35
SLIDE 35

Project Management

slide-36
SLIDE 36