Cagle R.B. - Blueprint for Project Recovery[c] A Project Management Guide (2003)(en)

266 B L U E P R I N T F O R P R O J E C T R E C O V E R Y

F i g u r e A 1 6 - 1 — I n - P r o c e s s R e v i e w A p p r o v a l F o r m

IN-PROCESS REVIEW APPROVAL FORM

The ___(1)____ In-Process Review Minutes containing the __(1)_____In-Process Review Package

labeled ___(2)_______ and dated ____(3)_______

and

The __(1)___In-Process Review

conducted on ___(3)_______ together with the In-Process Review Action Items are hereby approved

therefore

____(4)____ is hereby directed to proceed to the next stage of the program.

Signed ___(5)_____ of ______(6)________ Date _______________

Where:

(1)The In-Process Review (Step 1, Step 2, etc.)

(2)Modification or issue

(3)Date of package or event

(4)The contractor or lead engineer

(5)The appropriate authority

(6)The organization of the appropriate authority

is not being achieved, you must either ask for—or declare—a recess and return to the approval authority to get additional authority, or you must conclude the negotiations as being unsuccessful.

The basic Negotiation Envelope is frequently modified by additional scope/ price arguments sometimes referred to as ‘‘Bubbles.’’ Bubbles are single-issue items that contain their own price. Usually, Bubbles are not stand-alone but are dependent on a basic contract scope and price in order to be incorporated. Each Bubble should clearly state its precedence requirements or conditions such as: This element may be included only if such-and-such is included in the basic contract. You must be very careful with Bubbles. A smart negotiator may try to get your Bubbles included without including the necessary precedents/conditions or cost.

Your Negotiation Checklist should containing headings like:

Program

Scope

Objective Price

Acceptable Price Range

Negotiator

Authority

Each Bubble should have its own Negotiation Checklist that contains headings like:

Program

Addition

Scope

Precedence/Conditions

Objective Price

Acceptable Price Range

Negotiator

Authority

Rothenberg, Robert. The Plain-Language Law Dictionary. New York: Penguin,

1996.

Rubenstein, Reuven Y. Simulation and the Monte Carlo Method. New York: John Wiley, 1981.

Senge, Peter. The Fifth Discipline: The Art and Practice of the Learning Organization. New York: Doubleday, 1990.

Sobol, Ilya M. A Primer for the Monte Carlo Method. Boca Raton, Fla.: CRC Press, LLC, 1994.

Stamatis, Dean H. Failure Mode and Effect Analysis: FMEA from Theory to Execution. Milwaukee, Wis.: ASQ Quality Press, 1995.

U.S. Army Field Manual (FM) 770-78. Available from the Superintendent of Documents, Government Printing Office (GPO), Washington, D.C., or the Consumer Information Center, Pueblo, Colo., and in digital form, online at: www.incose.org/stc/fm77078.htm.

Articles

Barnes, Brenda J., and James W. Van Wormer, Ph.D. ‘‘Process Thinking and the 85:15 Rule Applied to Education.’’ Source: www.grandblancommu nityschools.com/qip/processthinking.htm (last accessed Aug. 5, 2002).

Chen, P. ‘‘The Entity-Relationship Model: Toward a Unified View of Data.’’

ACM Transactions on Database Systems, 1, no. 1 (1976): 9–36.

Luttman, Robert & Associates Online Articles, ‘‘Cause and Effect.’’ Source: www.robertluttman.com/cause-effect.html (last accessed Aug. 5, 2002).

Patrick, Francis S. ‘‘Program Management—Turning Many Projects into Few Priorities with TOC.’’ Newtown Square, Pa.: Project Management Institute, 1999. (Project Management Institute Seminar/Symposium [30th : 1999 : Philadelphia, Pa.], PMI 1999 Annual Seminars & Symposium Proceedings.)

Plsek, P.E. ‘‘Management and Planning Tools of TQM.’’ Quality Management in Health Care 1, no. 3 (Spring 1993): 59–72.

Private Documents

Early, John F., ed. ‘‘Cause-Effect Diagrams.’’ Quality Improvement Tools. Wilton, Conn.: Juran Institute, 1989. The training kit entitled Quality Improvement Tools is produced by the Juran Institute, and is a part of their inventoried items.

Systems Application Architecture—Common User Access Guide to User Interface Design. IBM Corporation, 1991. IBM Document Number SC34-4289. Available through IBM field offices.

The Windows Interface Guidelines for Software Design. Redmond, Wash.: Microsoft Press, 1995. ISBN 1556156790. Available from Best Buy Books.

TRADEMARKS

Brainstorming is a trademark of Infinite Innovations, Ltd. DOORSrequireIT is a trademark of Telelogic DOORS, North America

EDGE Diagrammer and EDGE Programmer are trademarks of Pacestar Software

Flowcharting Cause & Effect Module for Six Sigma Software Suite is a trademark of Quality America, Inc.

MacWrite is a trademark of Apple Corporation

MBTI is a trademark of Consulting Psychologists, Inc.

Microsoft , Microsoft Word , MS Word , Microsoft Excel , MS Excel , Microsoft Access , MS Access , Microsoft Office , MS Office , Microsoft Works , MS Works are trademarks of Microsoft Corporation

PathMaker is a trademark of SkyMark

PMBN is a trademark of Best Practices, LLC.

Post-it is a trademark of 3M Company

REASON 4 is a trademark of DECISION Systems, Inc.

Root Cause Analysis (RCA) is a trademark of Root Cause Analyst

Six Sigma for Excel is a trademark of BaRaN Systems LLC.

SmartDraw is a trademark of SmartDraw.com

This Page Intentionally Left Blank