PROPOSAL DEVELOPMENT GUIDELINES - EPPIC

I' --:.'

- ..-- ._--;----;-'--T-- (-'-l---T--~i-~--f"--~r----,

-~;~tiffi~ij~~__Group ...'__.'.___'_.i __ !-. _1_ ~__' I_l__.__~__;_r~. __ L._ J.._! /

PROPOSAL DEVELOPMENT GUIDELINES

Geary A. Rummler

Twenty- Five Franklin Place Summit, New Jersey 07901 (201) 273- 3170

f,

'.TA!3LE I --Sur~MARY OF ROLE INTERESTS

f'V

I Expectations Evaluation Project Product Resources,Rol c rrolllProject Cri tc ri (1 Constraints Cons trai nts Ave-i l ab loI

Sponsor:

.iStudcnLs: -

III

Instructionalenvironillent:

~-0 ,

"

Job,Environment:

TAGLE II--SUMMARY OF STUDENT POPULATIONPas i ti ons to No. of StudentsIknefi L f roin Common Constraints onI 11':; t ru c t ion Initially Each Year I Des ired ~1astery Enter; ng Skills Def ici enci es Taking Instruction1-----';"'-:-~~.'--::::-",-- -- -:-::-:.-=:-::-.-:::':-:::=-::::"':::- ..~~-:-==-:::-:-::-::-- _ ... --. -.... .- -.-.~..... .._- - _.- ..- .

I

IIIIIII

.

!II

.. -...... _-,

I

II

III

F. Project Administration1. How many rev iew stages or client sign-offs?

,2. Who par t icipates in sign-offs? i

3. Hho has final say in sign-offs?4. What is sign-off turn around time?5. Does the final sign-off have any special requirements?\6. What form do submissions to client take? Formal or informal?

How many copies?7. How many reports? What form do reports take? How many

copies?8. Who will be client contact?9. Will test subjects be available 0hen needed?

10. Where will developmental and pilot tests be done?11. When will project start and end?12. How will product or project be evaluated?

G. Contract Terms1. Does contract require guarantee of perfor~ance?

a) Who makes up test?b) Who sets performance level?

2. Hhat are time constraints? To what extent can they slip?3. Ylhat money is available?4. Are partial payments possible?

6

4. Need for or feasibility of the project--value?5. Personnel and corporate experience?

M. How many copies of proposal? To Whom?N: Would a Presentation be in order? .To.Whom? When? Where?

8

IV. GENERAL PROPOSAL OUTLINEA. Introduction (overv+ew or summary of proposal).B. Problem statement,and background.C~ Technical discussion (this might appe?r in the Appendix).D. Approach.E. Value of approach.F. Work statement and development plan.G. Schedule of work and deliverable items.H. Project management and personnel.I. Cost analysis and payment schedule.

AppendixA. Relevant Co rpo rate History, biographies, and references.B. Sample materials.

10

VI. PROPOSAL CONTENT GUIDELINESA. Background or Problem Statement

,lIndicate understanding of the probl~m and the reasons behind

the reques t.2. Discuss approach or orientation to the problem. (Perhaps the

problem as uniquely seen by Praxis).

1.

3. Stress customization of Praxis apprc::h to clients problem.B. Technical Di:;cussion

1. Make discussion relevant to the client problem and organiza-tion.

2. Key the detail and terminology to the reader. There areusually three distinct audiences reviewing proposals:a) Tr?ining people--frequently interest~d in the technology.b) Staff management people--concerned with results and the

approach to the result.c) Line management--concerned that the project will waste

their time and interfere with their getting the job done.Sometimes they are concerned about some results.

3. Consider whether the details of the technical discussionshouldn't be in the appendix, to ease reading by management.

C. A;:Jproachand Value of the Aoproach1. Describe ho';,Praxis ';,illcarry out the project. Depending on

the client, discuss:a) The subtleness or directness of the approach.b) The newness or the time-tested nature of the approach.c) The ability to use existing client data or to start f rom

scratch with an o~jective look.d) The neec'to use cl ient personnel or the abil ity to work

without disturbing on-going operations.2. Describe the value of the approach. (Where the above discusses

features, this should discuss benefits.)3. Des cribe g2n2ra 1 dir.ensions of fin21 oroduc t s

12

e) Decisions to be made at each phase.3. Specify client action or responsibility at each phase, par-

ticularly sign-offs and turn-around;times./

4. Specify project schedule. Hhen scheduling, take into accounta) Holidays.b) Client "down-t imes "

--vacations--peak, busy periods when data is inaccessible.

c) Client decision turn-around. (Be especially careful whenaudio-visual involved).

d) Availability of proper test subjects. Consider--training assignments--work scheduling--numbers of naive subjects in existence at particular

times.E. Deliverable Items

1. List all deliverable items including instructional materials,reports, and administrative or support materials.

2. Specify delivery dates.3. Specify number of copies.4. Specify form or condition (i .e., manuscript, final script,

camera ready copy, master taoes.)5. Specify who is to receive each.

F. Hhat Client Hill Supply1. Specify kind and amount of staff to be supplied by client.

Include:a) Coordi natorb) Test subj~cts and related costs (develop~ental, pilot)c) Subject matter resources.

2. Specify other resources to be provi ced , including:

14

2. In costing-out direct labor, applyincluding production typing, staffelude sales, proposal writing, andin labor figures.

as much direct as possible,artists, and editor. In-projected negotiation costs,

I

3. When determining production costs, considera} Instructional materials, administrative documents, and

reports.b) The number of draft copies, preliminary copies, and final

copies.c) The number of extra copies the client may want plus promo-

tional copies for Praxis.d) The number of test copies.

4. When projecting travel costs, consider field analysis andtesting sessions.

5. Request progress payments.a) State conditions for payment (i .e., deliverable items or

end of phase).b) State amount of payments.c) Reques t heavy "front-end" parti cipati on.

I. Rel evant Exoeri ence1. List general project activities of Praxis.2. List specific related activities of Praxis.3. List client references when appropriate.

J. Contract or ProDosal Conditions1. No performance criteria (eg. 90/90) will be agreed to unless

client specification of entry behavior is agreed to by Praxis.2. Proposal is valid for limited time (60 days) and personnel,

dates, and dollars included therein may b2 subject to chan£2after that period.

3. Praxis has up to 30 days to begin work on a project afteragreer"ent is reached.

16

PROJECT SPECIFICATION

Date: -------------------------Comp1eted By: _

I. BACKGROUNDOrganization: _

Contact Name and Title ----------------------------------------------------Recipients or Problem Area------------------------------------------------Organization Structure of Recipient or Problem Area:

Organi:ation Structure of Contact Area:

) .

II 1. DELlVERABLES

I ANTICIPATED DELIVERABLES DESIGN DEVELOP It\PLEMENT ,INTERNAL REQUIREMENTS~L-\:';PO\\'EROErELOP~IENT .o Selection o Peas ib i1i ty Study ofo Placcment/Promotion o Organization ~lodel of

I o Job Dcfini tion/Dcscription o Economic Mode I ofo CHeer Path/PI:1llS o \\'ork/Info Flol'; Model ofI D Performance Appraisal o .J ob Mode 1s for

o Indices for~L\:';:\GDI[;\T SYSTDIS o Performance Table for

o ~lBO o Performance Logs for

o Performance ~lanagement System o Performance Appraisal Forms foro Feedback System for

PERFOFm-\NCE HIPROVD!ENT o Troubleshooting Guides for~ o Knowl edge Maps foro Performance Information System o LGI foro Learner Guides Instruction o Course Development foro Course Development 0o Training Curriculums 0o Training Evaluation 0o Specialized j'iorkshop 0o incentive Systems 0o Human Factors Appraisal 0

0"O~G:\:\I:ATIO:';AL HlPROVD1ENTS 0

n Performance Department 0i

tJ Training Fac i 1i t i es 0I o Reor gan i za t ionsI o l-~C'(~esign of Jobs

OTHCR\o Re commenda tions on • . . . .

o I~plementation Plan

Io ""ri t t en Discussion

v. INrOR~Ii\TIONABOUT TilE PROPOSAL

A. Nhat is the price range?B. Is it sale source? Who else is bidding?C. Is the proj ect Ok I d and funded or nius t the propo sel sell the idea of

such a project?.D. When is the proposal due?E. When wi ll the decision be made?F. When will. the project start?

How long will it last?G. Who will see the proposal?

Who will be in on the decision?

H. Who will make the final decision about the proposal?T. On what basis will the interested parties make the decisions:

PARTIESPOSS I BLE A\.JARD FACTORS

1 2 3

1. Unique approach of contractor2. Technical approach (PI)3. Experience' of contractor4. Price5. Subject matter expert6. Completion time7. Capability (it of people)8. Personnel

J. h'hat does c1 ient want emphasized in the proposal:1. Approach to problem?2. Technical strategies?3. Final pr-oduct description, (features and henefi ts)?4. Need for or feasibility 'Of the project -- value?5. Personnel and corporate experience?

" .

PRODUCTIOrJ COST ESTIMJ\TE

DEll VERYDELI VERABLES

Fin.)}

REPORT

.JOB ~IODEL

K;--';Ol\'LEDGE ~IAP •

PERFOR~IANCE TABLE .~IETI!ODS TABLE

TRAINI1\G ~IATERIALS

TROUI3LESHOOTI~G GUIDES

I~R_E_Q~U_I_R_ED__ L_E_A_D_T_I_~_IE ~ ~ ~ ~~ _

Editing

LABORTyuingDesignDuplicating

TRlWEL ESTI~lATE

TO FROI1 NO. I~NO. AIR GROUNDTOTAL $ TOTAL NO. PERSON I TOTAL

GRAND TOTALTRIF'StEOPLE FARE FARE PER DID1 NIGHTS ROCti s

.

--

~D. C0f4P. SCHOo ACTL COMMENT

OiECKPOINT 11 (Design)final ..Instructional objectives --

Criterion t.estPopulation profileConstraintsDes iznDelivery alt.ernativesProduction scheduleClient review

CHECKPOINT III (Deve1opmen t)DraftFinal de Iivery modeDeve Iopmerrt al t.1:Stprocedures and datesClient review

CHECKPOINT IV (Deve Iopment aI Test)Deve lopmental test resultsRevisionsField t.est procedures and datesClient review

CHECKPOINT V (Field Test)Field test resultsRevisionsClient review

OiECKPOINT VI (Final Deli very)Deliverables meet proposal/letter of azreementDeliverables meet client e:xpectationsImplementation plan:

step-by-step plan for clientPraxis involvement specified and priced

Add-on business identifiedRaterials

writingproductionart

Presentation:organization of presentationvisual aidsindividual presentationcorrect audiencesetting

Report:organization Iclarity of .••.ri t ingproduction:

layouttypingreproductionbinding

d i sn l uvsResult:;:

client accepted del iverab lesclient implemented

MISCELLA:-lEOUSAs s oc La t cs devl~lopedT~chniraJ resources utilizedTechn iC:I 1--rc,;ouTcesava i Iab ICel ient schcdu Ic adhc rcd toCl lent Tcl:JtionsFolloy-up Dcheduled

Copyright © 1981 by G. A. Runnnler All Rights Reserved