1 Lect Proj Mgt Mar 2011

7/31/2019 1 Lect Proj Mgt Mar 2011

1/54

Project Managementfor BME Project Design (1BPD)

Mar 2011


2/54

Introduction

Outline of LecturesProject DefinitionProject Statement

ExamplesDeveloping Objectives

ExamplesProject Specification

MethodsAssessmentExampleFormat 1:Project ObjectivesApplied Example

WBS

Block DiagramFormat 2: WBSResourcesExample

Summary

2 of 54

Concept of ProjectManagement

Standard formatfor projectmanagement in ECE

Aim to increase chance forsuccessand quality

Useful (forfuture work)


3/54

Introduction





WBS


Summary

3 of 54

What is a project & Why we need tomange it?

specific objectives

defined start and end dates

a unique set of interrelated activities

a limit to funds and other resources

sufficient complexity to require control

A project must be managed so that it

SUCCEEDS!


4/54

Introduction





WBS


Summary

4 of 54

Defining project requirements(Part 1: Proj Def.)

project statement, objectives, specifications, workbreakdown, resource requirements

Planning Project Activities & Ensuring

successful project implementation

(Part 2: Proj Planning & Implementation)

Assign responsibility, Sequence deliverables, Scheduledeliverables.

monitor project, modify project, closeout and evaluate


5/54

Part 1: Project Definition

Definition Phase:

State the Purpose of the Project

Develop Objectives

Develop Work Breakdown Structure(WBS)

Identify:Resource Requirements

sub-Projects (Parts & Whole Analysis)

Phases of Project Definition

Begin with the end in mind.The Seven Habits of Highly Effective People by Stephen Covey


6/54

Introduction





WBSBlock DiagramFormat 2: WBSResourcesExample

Summary

6 of 54

To define the purposeand scopeofthe project, ask:

What needs to be done?

Why are we doing this?

When do we need to be finished?

How much will/can this cost? Write a short statement consisting of

i. Action

ii. End Result

iii. Time

iv. Cost (optional, if it is oblivious)


7/54

Introduction






Summary

7 of 54

Sample Statements:

Design and implement a home patientmonitoring system by Monday 13June 2011* for Final Review on 25July 2011.

Design and install a Sleep WalkingAlert and Alarm by 18 July 2011 for$9,000.

Design and implement a UserInterface for identifying CorneaAbnormity for the general user.

*Consult NPs Academic Calendar


8/54

Introduction






Summary

8 of 54

Developing Project ObjectivesTo define the benefitsand measures of successfor a project, ask:

At the end of project, what value will we have?

What benefits do we want?

What are the constraints that restricts us?

What requirements must be met?

How will we know when we satisfy each objective?(specification)

Write a list of short statements

Specific benefits and primary objectives of the project

Specifications of the project

Statement + objectives + specifications

Your Charter, Mission, Goal.


9/54

Introduction






Summary

9 of 54

Example: Intelligent Postal Box

Primary Objectives:

To enable a user to send letters orparcels by auto-payment withoutaffixing stamps.

To incorporate a variety of paymentmethods for the convenience of theusers of the post box.

To provide a user friendly interface forthe benefit of the general user of thepostal box.


10/54

IntroductionOutline of LecturesProject DefinitionProject Statement





Summary

10 of 54

Specifications/Features

Define in more details what the system candoin order to achieve the primary objectivesstated.

Specify the constraints or limitationsof the

project.Refine primary objectives based on

specifications.

If not sure about what theproject can do?

Consider aboutGenerating Possibilities


11/54






Summary

11 of 54

How to generate possibilities?

Brainstormwith your partner & list downallpossibilities that you can think of.

Categorizethe possibilities to make sure wehave different kinds of possibilities.

Brainstorm againto addnew possibilities,new categories.

List down any unusual/originalpossibilities.

Apply creative thinking methods. e.g.

Parts & Whole; Mind Mapping;


12/54






Summary

12 of 54

Assessing Possibilities

What information would you needin order to decide which of thepossibilities are best for theproject?

What are the criteria used todecide?

Rank the possibilities based onchosen criteria.


13/54






Summary

13 of 54


Generating Possibilities: accept coins, cash card accepts foreign currency key pad, LCD

weigh letters frank: put a stamp or mark on letters

after postage had been paid accepts different size

indicate when box is full ..


14/54






Summary

14 of 54


User

Interface

Payment

Method

Security Reliability Others

LCD,

Keypad,

Proximity

Detector,Wakeup

circuit,

Voice,

Touch

Screen

Coin,

Cash Card,

Credit Card,

Giro,Foreign

Currency,

Alarm,

Lighted at

night,

Camera,

Under Hot

Sun,

Rain-proof,

weatherresistant,

Vandal-

proof

Sale of

envelopes,

Frank

(PrintingLabels)


15/54






Summary

15 of 54

Format 1: Project ObjectivesProject Title:

_________________________________Project Statement:

________________________________________

________________________________________

Primary Objectives:________________________________________

________________________________________

________________________________________

Detail Specifications:________________________________________

________________________________________

Preliminary user manual (if applicable):


16/54






Summary

16 of 54

Applied Example: Intelligent Postal BoxProject Statement: Design and implement an intelligent

postal box for the general user by Tuesday 21st June2011.

Primary Objectives:1. To enable a user to send letters or parcels by auto-

payment without affixing stamps.2. To incorporate a variety of payment methods for the

convenience of the users of the post box.3. To provide a user friendly interface for the benefit of

the general user of the post box.

Specifications:1. Operate between 10C to 50C2. Load cell for weighing of letters or light parcels up to 500g3. Sleep Mode, 10 minutes after the last user.4. Wake up within 0.3 seconds and be ready within 3 seconds at

the presence of a user within a distance of 70 cm from thescreen.

5. Auto stamping, label printing & dispensing.6. Coin, cash-card for payment7. Touch screen input8. LCD Screen visual display9. Box Full indication...

Preliminary User Manual (if applicable)


17/54






Summary

17 of 54

Chart or Outline showing how majordeliverables relate to sub-deliverables

Lowest level deliverable/accomplishment iscalled a terminal element(modules)

Terminal elements combines to create allhigher level deliverables

Each terminal element should have aspecific quality or performance standard

Work Breakdown Structure


18/54





WBSBlock Diagram

Format 2: WBSResourcesExample

Summary

18 of 54

Develop Work Breakdown Structure Toestablish specific outputs and

accomplishments to be completed,ask:What do we want to accomplish in this project?What are the major outputs of this project? What are the component parts of ?

List themajor deliverables Separate each deliverables intosub-deliverables

Develop a chart oroutline

Divide and

Conquer


19/54





WBSBlock Diagram


Summary

19 of 54

System Block Diagram

Elements of a Block Diagram

uP system

WeighingMechanism

& load cell

Coin

machine

SizeDetection

Franking

Mechanism

CapacityDetection

LCD

KeypadUserInter-face

User

ProximityDetector


20/54





WBSBlock Diagram


Summary

20 of 54

Format 2: WBS

1._____________________________________ ______________ ______

1.1 ___________________________________ _____________ ______

______________________________________ ______________ ______

2._____________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

______________________________________ ______________ ______

duration/

equipment/materials/others

Knowledge/skill/facilities

WBS Outline:Resource Requirement:

Example: Intelligent Postal Box WBS


21/54




Methods

AssessmentExampleFormat 1:Project ObjectivesApplied Example

WBSBlock Diagram


Summary

21 of 54

Example: Intelligent Postal Box WBS

(deliverables and sub-deliverables)

Hardware Design and Fabrication

A1. Load Cell Interface to uPA1.1 Schematic of signal conditioning circuitsA1.2 List of componentsA1.3 prototype using breadboardA1.4 Test Plan for load cell

A2. Stamping/Printing Mechanism ..A4. PCB Design

A4.1 Schematic EntryA4.2 PCB Outline and special requirement

A4.3 Component footprints and mechanical dimensions finalizedA4.4 Component layout and RoutingA4.5 Plotting .

Software Design & ImplementationB1. Software for driving load cell, flow-chart,B2. Software for stamping mechanism controlB2. User Interface (using VB)Packaging

.Use formating that allows you to do an outline. Define multiplecolumns to conform to Format 2.


22/54




Methods


WBSBlock Diagram


Summary

22 of 54

Resource Requirements

To avoid future resource problemsand help assign responsibility

Consider each WBS terminal element,ask What knowledge and skills* are needed?

What facilities* will we need?

What equipment* is required?

What supplies/materials* should we have?

Identify the type, amount and cost if

applicable


23/54

IntroductionOutline of Lectures

Project DefinitionProject Statement



Methods


WBSBlock Diagram


Summary

23 of 54

Resources

knowledge/skill is lacking: learn through research, reading,

experimenting, learn from others (friends,technicians, lecturers, ).

Procure necessaryfacilities,equipment, materials early. These arethe causes for latter delays.

Try alternatives. Very often there areother possibilities.

THINK!

resources

Put First Things FirstThe Seven Habits of Highly Effective People by Stephen Covey


24/54





Methods


WBSBlock Diagram


Summary

24 of 54

Example : WBS


25/54





Methods


WBSBlock Diagram


Summary

25 of 54

Project Definition State the Project Develop Objectives

Develop Work Breakdown Structure

Identify Resource Requirements

Important: The clearer is your project definition, the better

is the chance of success!

Begin with the end in mind.

Try your best. Revise as you move on.

Brief Schedule


26/54

Format 1:Project

Statement &Objectives

Format 2: WBS& ResourceRequirement

Format 3: RAMFormat 4:PrecedenceList & Duration

Format 5: Bar

Chart(schedule)

Draft Proposal

26 of 54

e Sc edu e

14/3/11

15/3/11

16/3/11

17/3/11

18/3/11

21/3/11

22/3/11

23/3/11

24/3/11

25/3/11

28/3/11

29/3/11

30/3/11

31/3/11

1/4/11

4/4/11

5/4/11

6/4/11

7/4/11

8/4/11

11/4/11

12/4/11

13/4/11

14/4/11

15/4/11

18/4/11

19/4/11

20/4/11

21/4/11

22/4/11

9AMProjectProgressReview

(ShowandTell'Style')

Semes

ter1

Starts

VPP wk no

date

Log

boo

kInspec

tion

By

Supev

isor

9AMPro

jec

tSk

ills

Lec

ture

&W/S

1

9AM

Pro

jec

tMan

agemen

tLec

ture

1

9AM

Pro

jec

tManagemen

tLec

ture

2&3

AMPSRP&PMBrainAwar

enessWeek(SciCtr)

652 3 4

G.

Fri

day

22/4/11

P.

Ho

liday

9AM

Pro

jec

tPlan

ing

Revie

w(Con

ference

Style)


27/54

Part 2Project Planning & Implementation

Planning PhaseAssign Responsibility

Responsibility Assignment Matrix

Sequence Deliverables

Schedule Deliverables

Gantt ChartProtect the Plan

Implementation Phase

Monitor Project

Milestones

Modify Project

Closeout and Evaluation

Project Success Factors

Summary


28/54

Planning

PhaseAssignResponsibility

ResponsibilityAssignmentMatrix

SequenceDeliverables

ScheduleDeliverables

Gantt Chart

Protect thePlan

Summary28 of 55

To organize the work and avoid

future problems

Assign responsibility

Sequence deliverables

Schedule deliverables


29/54

Planning





Gantt Chart

Protect thePlan

Summary29 of 55

To ensure clear ownership for all work

Consider the resource requirement list.Ask: Who has the resources(=

knowledge/information/) for this terminalelement(= deliverable/accomplishment) ?

List who will contribute to each terminal

element and what they willdo.

Show primary responsibilityfor each

terminal element.

Responsibility Assignment Matrix


30/54

Planning





Gantt Chart

Protect thePlan

Summary30 of 55

Responsibility Assignment Matrix(RAM)

To make responsibilities clear and

visible

Create the matrix. WBS terminal elements down the left side Names of person across the top

List work requirement in each cell.

Mark primaryresponsibility with a P.

Only one Pfor each terminal element

Other member(s) can/may providesupport. Mark with a S


31/54

Planning





Gantt Chart

Protect thePlan

Summary31 of 55

Format 3: RAM

1._____________________________________________________ _______ _________1.1__________________________________________________ _______ _____________________________________________________________ _______ _______2._____________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _______

______________________________________________________ _______ _____________________________________________________________ _______ _______

col:derivedfrom WBS

Names

Mark P forprimary responsibilities.Mark S for providing support.Include abrief descriptionof thework.


32/54

PlanningPhase

AssignResponsibility




Gantt Chart

Protect thePlan

Summary32 of 55

Example: Intelligent Postal Boxxx yy

Hardware Design

C1. Chassis/packaging design Pcomplete diagrams

C2. PCB Design

C2.1 Schematic Diagram

C2.2 PCB Layout and Component Outline toidentify special space requirement S P

C2.3 Create Component footprints andmatch to assembly techniques P

C2.4 Functional Layoutand Assembly Plan P

C2.5 PCB Routing P

Put First


33/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary33 of 55

Sequence Deliverables

To help schedule work efficiently ConsiderWBSterminal elements.

Estimate calendardurationfor each

activity. Mark out interruptions e.g.

holidays,

Listprecedencefor each of them.

Develop a project precedence list.

things First

e.g. to do a PCB Layout you have to obtain first the actual

components. That is the best way to finding out about theirreal dimensions or footprint on the PCB. Before that you

need a circuit diagram .


34/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary34 of 55

Format 4: Precedence List

WBS Precedence Duration (days)

1._____________________________________ _____ ______1.1__________________________________ _____ __________________________________________ _____ ____2._____________________________________ _____ ____

______________________________________ _____ __________________________________________ _____ __________________________________________ _____ __________________________________________ _____ __________________________________________ _____ __________________________________________ _____ __________________________________________ _____ ____


35/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary35 of 55

Example: Intelligent Post Box

Precedence dur

Hardware Design

C1. Chassis/packaging design ? 4C2. PCB Design

C2.1 Schematic Entry ? 4

C2.2 Draft PCB Assembly Outline andidentify special space requirement after C1, B1 1

C2.3 Obtain Component footprints and

finalized dimensions ? 3

C2.4 Component layout after C2.2, C2.3 2

C2.5 PCB Routing after C2.4 5

Draw from past experience with related modules:MI or Workshop ( Electronic Practical Skills 1 & 2,Project Design Practice 1 & 2)


36/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary36 of 55

To provide the basis for projectmonitoring

List start and finish dates for eachterminal element.

Identify start and finish dates for each

terminal element. Review precedence to ensure no

terminal element starts too soon orfinishes too late.

Use a Gantt Chart (bar chart).


37/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary37 of 55

A Gantt chart is a graphical representation ofthe project schedule. It is:

to help make scheduling (visible) easier;

to help monitor the passing oftime.

List WBS terminal elements down the left.Draw atimeline across the top.

Draw a bar between the start and finish datesfor each terminal element.


38/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary38 of 55

Format 5: Bar Chart

Shade horizontal row to indicate start and stop dates for eachterminal element. Leave an empty row for bar to mark actual

time taken.2 day == 1 week applies during the semester (?).You may include Project Review Dates in the schedule.

WBS (only Terminal

Elements)14/3/11

15/3/11

16/3/11

17/3/11

18/3/11

21/3/11

22/3/11

23/3/11

24/3/11

25/3/11

28/3/11

29/3/11

30/3/11

31/3/11

1/4/11

4/4/11

5/4/11

6/4/11

7/4/11

8/4/11

11/4/11

12/4/11

13/4/11

14/4/11

15/4/11

18/4/11

19/4/11

20/4/11

21/4/11

22/4/11

652 3 4

G.

Fri

day

22/4/11P

.Ho

liday

9

AM

Pro

jec

tPlan

ing

Rev

iew

(Con

ference

Style)

9AMProjectProgressReview(ShowandTell'Style')

Semes

ter

1Starts

Bill of Material & Purchase

Requsition

Layout Component

Position on PCB

Customize Component's

footprints

Layout PCB

Temp Tranducer's T vs

Vout Charateristics

VPP wk no

date

Strain Gauge's Vout vs F

Charateristics

Log

boo

kInspec

tion

By

Supev

isor

9AMProjectSkillsLecture&W/S

1

9AM

Pro

jec

tManag

emen

tLec

ture

1

9AM

Pro

jec

tManagem

en

tLec

ture

2&3

AMPSRP&PMBrainAwarene

ssWeek(SciCtr)

Design Circuit


39/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary39 of 55

To help ensure that we meet orexceed the project objectives

Spot areas of the plan where we areconcerned.

Potential Problems: What if we cantget that component?

Potential opportunities: Can we buy a

unit off the shelf rather build our own?


40/54

PlanningPhase





Gantt Chart

Protect thePlan

Summary40 of 55

Project Planning Assign Responsibility

Sequence Deliverables Schedule Deliverables Protect the Plan

Comments: If the plan is sufficiently thorough, you have set

the stage for success!

Try your best. Revise as you move on.

(Experience)


41/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and

EvaluationProject SuccessFactors

Summary

41 of 54

The final phase of a project when

deliverables are produced to meet theproject objectives.

To deliver value to the project

Start to implement

Monitor project as time passes.

Modify project

Closeout and evaluate


42/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

42 of 54

To ensure work begins on time with clear

performance standards

Review project statement and objectives.

Set ground rules for working together.

Review initial project assignments.

Confirm performance expectations.


43/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

43 of 54

To keep the project on track

These aspects can be monitored:

Progress against Objectives Progress against Milestones (markers) Resource Use and Cost Human Performance

Set deliverables and performances

expectations in advance.

Scheduled reviews to monitor progress.


44/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

44 of 54

Milestones are events which mark the

completion of part of a project.

To show where progress can bechecked

Review the WBS, sequence and

schedule.

Add milestones to mark: Completion of a major deliverable Start or finish a sub-project OR important

terminal elements

Schedule reviews around milestones.

To respond to problems,


45/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

45 of 54

p p ,

opportunities or even changes in

objectives

Review and clarify threats and

opportunities.

Locate the earliest point in processwhen each concern has impact.

Use the Definition and Planning

phase steps as required to revise theplan.


46/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

46 of 54

To ensure all objectives were met and

share lessons learned

Review success against objectives.

Review lessons learned.

Document a project summary.


47/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

47 of 54

Some success factors:

Project team commitment andcapabilities

Effectiveness of planning and control

Minimizing start-up difficulties

Team work

Clear criteria for success

P j t I l t ti


48/54

ImplementationPhase

Monitor Project

Milestones

Modify Project

Closeout and


Summary

48 of 54

Project Implementation Start to Implement

Monitor project Modify project Closeout and evaluate

Comment: Changes are unavoidable. Do it only when it

is necessary, otherwise not implementingimportant changes will be a cause to failure.

A di F t f


49/54

Appendix: Format for

Planning ReviewFormat 1: Project Statement & ObjectivesFormat 2: WBS and Resource

Requirement

Format 3: RAM

Format 4: Precedence List & Duration

Format 5: Bar Chart (schedule)

Results & Draft Proposal (Deadline)

Project Statement:


50/54

Format 1:ProjectStatement &

Objectives


Format 3: RAM

Format 4:PrecedenceList & Duration

Format 5: BarChart(schedule)

Draft Proposal

50 of 54

Project Statement:________________________________________________________________________________

Primary Objectives:

________________________________________________________________________________________________________________________________________________________________________________________________________

Detail Specifications:

________________________________________________________________________________

Preliminary user manual (if applicable):


51/54


Objectives


Format 3: RAM



Draft Proposal

51 of 54

1._____________________________________ ______________ ______1.1 ___________________________________ ______________ ____________________________________________ ______________ ______2._____________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ____________________________________________ ______________ ______

duration/equipment/

materials/others

Knowledge/skill/facilities

WBS Outline:Resource Requirement:


52/54


Objectives


Format 3: RAM



Draft Proposal

52 of 54

1._____________________________________________________ _______ _________1.1__________________________________________________ _______ _____________________________________________________________ _______ _______2._____________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _____________________________________________________________ _______ _______

______________________________________________________ _______ _______

Names


53/54


Objectives


Format 3: RAM



Draft Proposal

53 of 54

WBS Precedence Duration (days)

1._____________________________________ _____ ____ __1.1__________________________________ _____ ____ ______________________________________ _____ ____ 2._____________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____ ______________________________________ _____ ____

Submit to supervisor, to be writteninside logbook by Day 15


54/54


Objectives


Format 3: RAM



Draft Proposal

54 of 54

g y y(Mon 28/3/11), all results and data for VPPmust be complied by Day 33 (Fri 15/4/11)

Project Title Background Information Objectives Specifications Visualization of What You will show on your Fina

Review. (Begin with the end in mind.) Design Alternatives Final Design Description & System Block

Diagram User Manual (Skeleton?)

WBS, RAM, Precedence List, Gantt Chart (mayuse software aid) OR Schedule

results, results, results

Most Complicated

The END

1 Lect Proj Mgt Mar 2011

Documents

Transcript of 1 Lect Proj Mgt Mar 2011