project management - delivered at purdue - september 6 - 2001

Project Planning and Management for ISD Projects ©2001 CADDI, Inc. P-1031 9/6/01

Project Planning and Managementfor ISD Projects

presentation to

Purdue’s Educational Technology ProgramSeminar Series

September 6, 2001

Project Planning and Project Planning and ManagementManagementfor ISD Projectsfor ISD Projects

presentation to

Purdue’s Educational Technology ProgramSeminar Series

September 6, 2001

Guy W. WallaceGuy W. Wallacepartnerpartner

CADDI, Inc.CADDI, Inc.

Guy W. Wallace is now accessible viawww.eppic.biz


From the Project Files of Guy W. Wallace…From the Project Files of Guy W. Wallace…


Session Introduction

Performance ContextPerformance ContextAs professional ISDers, you will occasionally have to plan and manage ISD projects

Session ObjectivesSession ObjectivesTo provide you with an overview of my approach to ISD projectplanning and management

AgendaAgendaOpen and speaker backgroundPlanning frameworkPlanning concepts and modelsPlan structure and formatProject teams and rolesProject management philosophiesProject management practicesQ&A and close


Speaker Background

Guy W. WallaceGuy W. Wallace

In the T&D profession since 1979

A T&D consultant to government and industry since 1982 after twoindustry jobs (Wickes Lumber andMotorola)

Clients in the last four years include- AT&T, Bandag, BankAmerica, Eli Lilly, General

Motors, GTE, H&R Block, NOVA Chemicals, Siemens, and Verizon

Involved in more than 250 ISD projects since 1979, many of which I’ve had to plan (and price!)

Guy’s professional biography can be accessed at

www.CADDI.com/GWW.htm

Guy’s professional biography can be accessed at

www.CADDI.com/GWW.htm


Details…details…details…details…details…details…details

Plan at the most detailed level possible

Think of/anticipate everythingeverything

Leave “wiggle room” between “key scheduled events”

Both God and the devil are in the detailsBothBoth God and the devil are in the detailsGod and the devil are in the detailsNote:


ISD Project Planning Framework

Use a “process model” for your planning framework

ADDIE . . . The Traditional ISD ModelADDIE . . . The Traditional ISD Model

CADDICADDI’’s MCDs MCD

= Project Steering Team gate review meetings

©1999 CADDI, Inc.

MCD Phase 4

Development/Acquisition

MCD Phase 6

Revision & Release

MCD Phase 1Project

Planning & Kick-off

MCD Phase 2

Analysis

MCD Phase 3

Design

MCD Phase 5

Pilot Test

©1999 CADDI, Inc.

MCD Phase 4


MCD Phase 4


MCD Phase 6

Revision & Release

MCD Phase 6

Revision & Release

MCD Phase 1Project

Planning & Kick-off

MCD Phase 1Project

Planning & Kick-off

MCD Phase 1Project

Planning & Kick-off

MCD Phase 2

Analysis

MCD Phase 2

Analysis

MCD Phase 2

Analysis

MCD Phase 3

Design

MCD Phase 3

Design

MCD Phase 3

Design

MCD Phase 5

Pilot Test

MCD Phase 5

Pilot Test

MCD Phase 5

Pilot Test

D

Development

D

Design Evaluation

EA

Analysis

I

Implementation

D

Development

D

Development

D

Design

D

Design

D

Design Evaluation

E

Evaluation

EA

Analysis

A

Analysis

I

Implementation

I

Implementation


ISD Project Planning Concepts and ModelsA “basic activity building block” for project planning

Four-part “activity block”: 1. Coordinate 2. Prep 3. Do it 4. Document it

Four-part “activity block”: 1. Coordinate 2. Prep 3. Do it 4. Document it

Preparation

Coordinate Logistics

Post-documentation

Conduct Activity/ Meeting

11

22

33

44


ISD Project Planning Concepts and Models (continued)

Build a chain of the “building blocks” for each phase of your

effort

Build a chain of the “building blocks” for each phase of your

effort

Conduct Interviews

Conduct Observations

Conduct Analysis Meeting

Conduct Project Steering Team Gate Review

ExampleExample

Prep

Do it Doc.

Prep Prep Prep Prep

Do it Do it Do it Do itDoc. Doc. Doc. Doc.

Coor.

Coor. Coor. Coor. Coor.


ISD Project Plan Structure and Format

Project Plan Structure

1. Purpose and goals

2. Background and rationale

3. Scope

4. Approach and methods

5. Project phases andmilestones

6. Outputs and deliverables

7. Roles and responsibilities

8. Project tasks, roles, and schedule

Project Plan SProject Plan Structuretructure

1. Purpose and goals

2. Background and rationale

3. Scope

4. Approach and methods

5. Project phases andmilestones

6. Outputs and deliverables

7. Roles and responsibilities

8. Project tasks, roles, and schedule

KEY: CADDI, Inc.GW = Guy WallacePH = Pete HybertPS = Production Support

TMC CorporationPM = Project managerPT = Project TeamPP = Pilot Participants

Project Plan Task Chart Project Plan Task Chart FFormatormatEstimated Days Required

CADDI, Inc. TMC CorporationSchedule

Project TasksGW PH PS PM PT PP Other

(each)Start End

1. Identify, contact, and recruit three to five “Project Team” members for the Working Committee to provide input, critique, and support to the Analysis, Design, Development, and Pilot Testing effort

– – – 2.0 – – –

2. Coordinate logistics for Task 4•Room arrangements•Equipment arrangements• Invitations and information to attendees•Meal/refreshments•Final confirmation of invited attendees’

intentions to attend

0.25 – – 1.0 – – –

3. Prepare to conduct Task 4•Meeting process design•Presentation preparation•“Straw” models/starter prototypes for use

in Task 4

1.0 2.0 2.0 – – – –

4. Conduct meeting 0.5 0.5 – 0.5 0.5 – – 9/28 9/28


ISD Project Teams and Roles

Project champion and Project Steering Team (PST)

Analysis Team(s) and Analysis Review Team(s)

Design Team(s) and Design Review Team(s)

Development Team(s)

Pilot-Test Team(s)

ISD TeamFor details about the responsibilities of each role and team, please see the CADDI article “lean-ISDSM

White Paper” on the CADDI Web site

For details about the For details about the responsibilitiesresponsibilities of each role of each role and team, please see the CADDI articleand team, please see the CADDI article ““leanlean--ISDISDSMSM

White PaperWhite Paper”” on the CADDI Web siteon the CADDI Web site

ProjectProjectSteering Steering

TeamTeamAnalysisAnalysis

TeamTeamDesignDesignTeamTeam Development

DevelopmentTeamTeam PilotPilot--Test Test

TeamTeamProject Project

ISD TeamISD TeamProjectProjectSteering Steering

TeamTeam

ProjectProjectSteering Steering



TeamTeamDesignDesignTeamTeam

DesignDesignTeamTeam Development

DevelopmentTeamTeamDevelopment

DevelopmentTeamTeam PilotPilot--Test Test

TeamTeamPilotPilot--Test Test

TeamTeamProject Project

ISD TeamISD TeamProject Project ISD TeamISD Team

Clarify responsibilities of


ISD Project Management PhilosophiesFind the rightright project champion

Work off a detailed, socialized Project Plan

Find and sell the toughest skeptic(s) and include them on the Project Steering Team

Allow nono surprises for your customers/stakeholders

Allow your customer to make all of the businessbusinessdecisions;decisions; T&D should make the ISD decisionsISD decisions

Take allall “bullets” and nono “credits”

Only work on projects with significant ROI


ISD Project Management Practices

Preview and presell the plan to the Project Steering Team

Make the customer responsible for project success; they should- Establish the value/ROI for the project- Sanction/hold/kill the project (as appropriate)- Handpick all project participants- Review all interim documents throughout the project

Use “gate reviews”

Maintain constant communication with the Project Steering Teamchairperson (or the individual charged with project management on the customer-side)

Own the “process,” not the “content”


Session Summary and Close

Plan in detail and detail the plan

Use a “framework” and a “building block”concept/model

Have a plan structure and format

Partner/collaborate with the customer for planning, resourcing, and reviewing project activities and outputs

Communicate, and then communicate more

Own the process, not the content- There are more “business decisions” in an ISD project

than “instructional design decisions”


Additional CADDI Readings/References

On the CADDI Web site“lean-ISD via the PACTSM Processes”

“lean-ISD White Paper”

“The Detailed Project Plan”

Other resourceslean-ISD (book)


About CADDI

CADDI, Inc., the Curriculum Architecture Design & Development Institute, Inc., is dedicated to performance-based training & development (T&D) and other performance improvement interventions and methods

Curriculum Architecture

Design & Development Institute, Inc.

CADDI

Curriculum Architecture

Design & Development Institute, Inc.

CADDI

“Gopher” more at CADDI.com


About CADDI (continued)

CADDI’s key models

©1999 CADDI, Inc.

PACT Analysis

CADCurriculum

ArchitectureDesignSM

MCDModular

Curriculum DevelopmentSM

IADInstructional

ActivityDevelopmentSM

PACT Project Planning and Management

©1999 CADDI, Inc.

PACT Analysis

PACT Analysis

CADCurriculum


CADCurriculum


MCDModular


MCDModular


IADInstructional


IADInstructional


PACT Project Planning and ManagementPACT Project Planning and Management

PP erformance-based

AA ccelerated

CC ustomer-/Stakeholder-driven

TT raining & Development

PP erformance-based

AA ccelerated

CC ustomer-/Stakeholder-driven

TT raining & Development

PACT Processes for T&DPACT Processes for T&D T&D T&D SystemsSystems ViewViewSMSM Targeting EPPITargeting EPPISMSM

Targeting Steps

Derive the Enablers and Determine Gaps and Target Improvement Efforts

Map the Processes, Model the Performance, and Target Step 3 Efforts

Map the Enterprise and its Systems/ Processes and Target Step 2 Efforts

STEP

1

STEP

2

STEP

3

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

1

2

3

4

1Role1

Process Map View Performance Model ViewArea of Performance:

KeyOutputs

KeyTasks

Roles/Responsibili ties1 2 3 4 5

TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Area of Performance:

KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

>=

Human Asset RequirementsHuman Asset Requirements

Environmental Asset Requirements










Process Map

Performance Model

Process Map

Performance Model

Process Map

Performance Model

Process Map

Performance Model

Performance Model

>=

Targeting Steps

Derive the Enablers and Determine Gaps and Target Improvement Efforts

Map the Processes, Model the Performance, and Target Step 3 Efforts

Map the Enterprise and its Systems/ Processes and Target Step 2 Efforts

STEP

1

STEP

2

STEP

3

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

C

S

L

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

>=

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

1

2

3

4

1Role1


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:


KeyOutputs

KeyTasks


TypicalPerf. Gaps

Prob. GapCause

dEdKdI

Role:

Role2

Role3

Role4

Role5

>=












Process Map

Performance Model

Process Map

Performance Model

Process Map

Performance Model

Process Map

Performance Model

Performance Model

>=



















Process Map

Performance Model

Process Map

Performance Model

Performance Model

Process Map

Performance Model

Process Map

Performance Model

Performance Model

Performance Model

Performance Model

>=

SM



project management - delivered at purdue - september 6 - 2001

Business