pm-workshop 030 kompr

8/4/2019 PM-Workshop 030 Kompr

1/55

Project Management

Basics


2/55

2

Project management

Goals of this workshop

Short introduction intoproject management

Getting familiar with somebasic tasks of a projectmanager

Concentration on project

planning


3/55

3

Project management

Agenda

9:00 Introduction of participants (Experience, expectations)

9:30 Presentation: Project Management Basics

11:45 Questions & Discussion12:00 Lunch break (1h)

13:00 Team-work exercises 1+2

14:30 Coffee break (15 min)

14:45 Team-work exercises 3+416:15 Feedback

16:30 End of Workshop


4/55

4

Content

Definition of Project Management

Tasks of a project manager

Project planning

Project management


5/55

5



6/55

6


What is aProject?

Limited regarding...Limited regarding...

-- TaskTask

-- TimeTime-- BudgetBudget

-- ResourcesResources

-- PlannedPlanned-- PerformedPerformed

-- ControlledControlled

-- NewNew

-- Clear goalClear goal

-- UniqueUnique

-- SpecificSpecific

organisationorganisation


7/557


What is a Project?

DIN 69 901:

Ein Projekt ist ein Vorhaben, das im Wesentlichen durch

Einmaligkeit der Bedingungen in ihrer Gesamtheit

gekennzeichnet ist, zum Beispiel:

Zielvorgabe

Zeitliche, finanzielle, personelle und andere Begrenzungen

Abgrenzung gegenber anderen Vorhaben

Projektspezifische Organisation


8/558


What is Project Management?

DIN 69 901:

Projektmanagement ist die Gesamtheit von

Fhrungsaufgaben, -organisation, -techniken

und -mitteln fr die Abwicklung eines Projekts.


9/559

Project

ManagerSkills

Project

ManagerSkills

Soft skillsSoft skills

Domain

knowledge

Domain

knowledge

MethodsMethods

Analyse

Avoid

Reduce

Mitigate

Plan

Accept

Risk



10/55


11/5511


Integration

Requirements

Time Costs

Quality

TeamCommunication

Risks

Tools


Processes

Material Problems


12/5512


Time Costs

Magic triangle

Scope


13/55


14/55

14


Project ManagerProject Manager

Build teamBuild team

Analyse Risks

Define Project

Goals

Analyse

Stakeholders

Analyse

Stakeholders

CreateProject Plan

Estimate

Project Costs

Estimate

Project Costs

Organise

Kick-Off Meeting /

Start Workshop

Organise

Kick-Off Meeting /

Start Workshop

Tasks during the project start phase


15/55

15


ProcessProcess

Goal hierarchy

ResultResult

ScopeScope TimeTime CostsCosts QualityQualityStakeholder

satisfaction

Stakeholder

satisfaction

SOP: March 1, 2010SOP: March 1, 2010 Target costs: 200Target costs: 200

Main goal


16/55

16


Goals shall be SMART:

Specific(unambiguous)Measurable

Achievable

Relevant(challenging)

Timely(assigned date)


17/55

17


Risk

management Risk

Analyse

Avoid

Shift

Reduce(Probability)

Mitigate(Impact)

Contingency

Plan

Accept
http://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.htmlhttp://www.yunphoto.net/de/photobase/hr/hr654.html


18/55

18


Managing the riskof a

ski race accident:

Analyse

Avoid Shift

Reduce (prob.)

Mitigate (imp.)

Conting. plan

Accept

Snow and slope conditions

=> Do not participate, if too dangerous=> Effect insurance, let s.o. else participate

=> Optimize training and equipment

=> Wear protective clothing

=> Organise ambulance, write last will

=> Participate, if risk is tolerable andprize is profitable


19/55

19


Probability

Impact

Risk=10

5 100

0

5

10

Risk=50

Risk = Impact x Probability

Iso-Risk


20/55

20

Content



Project planning

Project lifecycle Process definition

Development strategy

Work-breakdown structure

Staffing plan

Project schedule

Project management


21/55

21

Project planning

Phase Plan

TimeStrategyFeasibility

study

Concept,

Plan

Develop-

mentProduction Support


22/55

22

Requirements

Design

Implementation

Verification

Maintenance

Project planning

Waterfall Model


23/55

23

ValidationVerification

Build

Development

Planning

Analysis

System maintenanceSystem enhancement

System development

System concept

Project planning

Spiral Model


24/55

24

Customer requirements

System requirements

Software requirements

Software design

Delivered device

Integrated device

Integrated software

Software module

Software Construction

System validation

Review

Review

System verification

Software verification

Software module ver.

Review

System

Requirements

Analysis

Software

RequirementsAnalysis

Software

DesignSoftware

Integration

SystemIntegration

System

Delivery

Project planning

V-Model


25/55

25

Project planning


26/55

26

V-cycle, iterative

Basic requirementsBasic requirements DeliveryDelivery

New requir. & bugsNew requir. & bugs DeliveryDelivery

Project planning

Time

B-Sample

C-Sample


27/55

27

Phase synchronisation

Mechanical samples A B C D

Electronic samples

Software samples

A2 B2 C D

1.0 2.0 3.0 4.00.20.1 1.21.1 2.1 2.2 3.1 3.2

A1 B1

SOP

Project planning


28/55

28

Project planning

A-SamplePresentation & validation of basic functions

Finalisation of customer specs

B-Sample

Verification & Validation(e.g. Test rides, EMC tests)

C-SampleEnsure readiness for series production

PPAP (Production Part Approval Process)

Time

Mock-up

or RapidPrototype

RealHardware

HW built with

serial production

tools


29/55

29

Project lifecycle(regardingactivities)

Singular Iterative Continuous

t

Project start Project end

Project planning


30/55

30

Project end

Start of new

projects

Unplanned effort, bugs

Project lifecycle(regarding staffing)

Project start

Time

Manpower

Late bug-fix / change

Temporary

demand from

other projects

End of old projects

Project planning


31/55

31

Process definition

Requirements

ManagerTester

Software

Integrator

FunctionDeveloper

SoftwareDeveloper

Project planning


32/55

32

Process definition

Project planning

Study Plan Execute Finish

Feasibility Concept Design Development Production

Review Review Review

Activities


33/55

33

Project planning

54

321

0

Optimizing5Predictable4Established3Managed2Performed1Incomplete0

SPICE

SoftwareProcess

Improvement

Capability

dEtermination

CMMICapabilityMaturity

Model

Integration

543

21

Optimizing5Quantatively Managed4

Defined3Managed2

Initial1

Customer

Minimum

for suppliers

Automotive Spice: http://www.automotivespice.com/web/download.html,

CMMI: http://www.sei.cmu.edu/cmmi/


34/55

34

Project planning

HIS: Hersteller-Initiative Software SPICE

P j t l i


35/55

35

Project planning

Process Area

23

3

1

2

1

2

Capability Level: 0 = Incomplete 3 = Established

1 = Performed 4 = Predictable

2 = Managed 5 = Optimizing

2

Capabilitylevel

SPICE

ENG.1 Requirements elicitationENG.2 System requirements analysis

ENG.3 System architectural design

ENG.4 Software requirements analysis

ENG.5 Software design

ENG.6 Software construction

ENG.7 Software integration

ENG.8 Software Testing

SUP.8 Configuration management

SUP.1 Quality assurance

MAN.3 Project Management

Project planning


36/55

36

Project planning

Project Plan

Scope

of work

Main

requirements

Stakeholders,interfaces

Process

definitions

Developmentstrategy

...

Project planning


37/55

37

All product componentsInternal ExternalExternal

External

(Off the shelf)

External

(new)

Internal

Internal

(new)

Internal

(reused)

Project planning

Development Strategy

External

(Off the shelf)

External

(new)

Internal

(new)

Internal

(reused)

Internal

(new), Site A

Internal

(new), Site B

Project planning


38/55

38

Work-breakdown

Structure (WBS)

Deutsch:

Projektstrukturplan (PSP)

Project planning

Hierarchicalstructure Contains allwork-packages

Structurede.g. by

Phases(Concept, development, production, )

Competencies

(E.g. responsible departments)

Product components(Body, engine, ...)

Activities

Can be created

Top-down Bottom-up

Project planning


39/55

39

Project planning

Projekt X

Work-breakdown Structure(Example)

Phases

Competencies

Activities

Concept Definition Development

Product

components

Engine

Transmission

Body

Chassis

Front axle

Rear axle

Project

management

Quality

assurance

Hardware

Engineering

Software

Engineering

Systems

Engineering

Define installation space

Define max. forces

Project planning


40/55

40

Work-breakdown

Structure

Project planning

Must be

Complete(Check each level!)

Unambigous

Detailled

One levelone structure criterion(e.g. phase)

Activities:Verb + Noun(e.g. Paint cover)

Each element: Unambigous identifier(alphanumerical)

Level of detail:

Manageable number of work-packages

Each work-package should be A self-contained task

Assignable to one person or group

Project planning


41/55

41

Work-breakdown

structure

Project planning

Project

P1

Project

P1

SubprojectP1.A

SubprojectP1.A

SubprojectP1.B

SubprojectP1.B

SubprojectP1.C

SubprojectP1.C

SubtaskP1.A.1

SubtaskP1.A.1

SubtaskP1.A.2

SubtaskP1.A.2

SubtaskP1.A.3

SubtaskP1.A.3

SubtaskP1.A.1.1

SubtaskP1.A.1.1

WorkpackageP1.A.1.1.1








WorkpackageP1.A.2.1

WorkpackageP1.A.2.1

WorkpackageP1.A.3.1

WorkpackageP1.A.3.1

WorkpackageP1.A.3.2

WorkpackageP1.A.3.2

Project planning


42/55

42

StaffingStaffing

Staffing plan

Project planning

AvailabilityAvailability

EffortEffort

WorkloadWorkload

BudgetBudgetTimeTime

SkillsSkills

Project planning


43/55

43

Project planning

Work packages

Milestones Sample deliveries

Quality gates

SOP

Clarify requirements

Create design

Perform implementation

Execute test

2 wks, John Doe

3 wks, Jane Saw

1 wk, Bob Tail

2 wks, N.N.Deliver 1. sample

EffortsEstimated, actual

Dependencies

Assignments

Sequence

Project Schedule

Project planning


44/55

44

j p g

How to save time

Reduce scope of work

Cancel tasks

Reject change requests

Reduce quality of work

Reduce effort

Buy Know-how and licences

Use Off-the-shelf components

Optimize resources

Add manpower Reassign tasks

(Limited) Overtime

Encrease productivity

Lift motivation

Teach project members

Recruite skilled people

Optimize schedule

Parallelize tasks

Partition tasks (e.g. for parallelization)

Change order of tasks

Prepare work before a critical period

Project management


45/55

45

Content Definition of Project Management


Project planning

Project lifecycle Process definition

Development strategy

Work-breakdown structure

Staffing plan

Project schedule

j g

Project management


46/55

46

j g

Questions? Comments? Criticism?


47/55

47

Exercises

Exercises


48/55

48

The story

Tomorrow morning (9 am), there will be an important prospection meeting at

a customer site.

Its the first contact between this company and Askon. Therefore it will be

essential to make a good first impression.

Goals:

Arrive on time

Make a good impression

Do not spend any money

(exept for fuel)

Exercises


49/55

49

Evaluation

Delay up to 5 min 0

10 min 1

20 min 2

30 min 3

> 30 min 4

Not shaved or bloody, dirty teeth, no breakfast, no business cards,

important political news unknown: Each1

No shower, missing or dirty dress part, no coffee: Each 2

Image loss > 3: Game over

Image loss

Image loss

Exercises


50/55

50

Phase Plan, WBS and Project Schedule

1.) Plan trip

1. Create a Phase Plan

2. Create a Work-breakdown Structure

3. Create a Project Schedule

4. Calculate your wake-up time

Exercises


51/55

51

Work packages Duration/min

Take a shower 10

Shave 5

Brush teeth 3

Choose a dress 5

Dress 5

Pack your briefcase 10

Make coffee 3

Prepare breakfast 5

Have breakfast & coffee 15

Read the newspaper 15 Plan the route 10

Drive car 80

Exercises


52/55

52

2.) Optimise your plan

How much time can you save?

Exercises


53/55

53

3.) Create a Risk Management Plan

1. Identify 10 risks

2. Evaluate & prioritize risks (Top 5)3. Plan counter measures

4. Re-evaluate the risks

Risk Management

Exercises


54/55

54

4.) Cope with occuring problems

1. Evaluate impact

2. Propose solutions3. Select solution

4. Implement solution

5. Re-plan your project

Problem Management

Project management


55/55

55

Thank you for your attendance!

pm-workshop 030 kompr

Documents