
Cagle R.B. - Blueprint for Project Recovery[c] A Project Management Guide (2003)(en)
.pdf
G L O S S A R Y |
215 |
Total Quality Management (TQM) – ‘‘A structured system for satisfying internal and external customers and suppliers by integrating the business environment, continuous improvement, and breakthroughs with development, improvement, and maintenance cycles while changing organizational culture.’’ (From the Web site of Integrated Quality Dynamics, Inc.)
Vendor – A person or company that provides a product or line of products to a Specification that is usually his own.
Version Description Document (VDD) – A document that references and describes the changes included in this version of software.
Vision – The highest view of what a company is and where it wants to go.
Work Breakdown Structure (WBS) – A WBS is a description of the project/
program in tree form. It is composed of the hardware, software, services, and |
||
data that completely define a project/program. |
||
|
|
F |
|
|
M |
Work Package (WP) – The lowest level ofYthe WBS that is the most efficient |
||
and cost-effective way of controlling schedule,Lcost, and technical performance |
||
|
A |
|
consistent with the requirements of the customer and the performing agency |
||
(the company). |
E |
|
|
|
|
|
T |
|

This Page Intentionally Left Blank

ATTACHMENTS
Attachment 1—Standard Program Plan Outline
Attachment 2—Standard Technical Plan Outline
Attachment 3—Risk Mitigation Plan
Attachment 4—Contract/Subcontract Outline
Attachment 5—Configuration Management Plan Outline
Attachment 6—Quality Assurance Plan Outline
Attachment 7—Requirements Traceability Matrix
Attachment 8—Requirements Flow-Down Matrix
Attachment 9—Data Delivery Matrix
Attachment 10—Capability Matrix
Attachment 11—Policy-to-Plan Trail
Attachment 12—Experience Window
Attachment 13—Standards Traceability Matrix
Attachment 14—Vendor Evaluation Process
Attachment 15—Design Review Approval Form
Attachment 16—In-Process Review Approval Form
Attachment 17—Negotiation Checklist
Attachment 18—Critical Success Factor (CSF) Matrix
217

This Page Intentionally Left Blank

A T T A C H M E N T 1
STANDARD PROGRAM PLAN OUTLINE
The Program/Project Plan is one of the most important documents you will create to manage a project or program. The outline of the plan should be consistent from project to project. Obviously, the content of much of the plan will vary from project to project, but some of the content will also be consistent. Which is which should be a part of the enterprise policies that drive such plans.
Following is a suggested outline you can use to generate your first Project or Program Plan, even if you don’t have an enterprise policy to drive it. Over time, you will find which parts of the plans are constant and which change. By using a word processing application you can create a new plan very quickly. This is particularly helpful in bidding new projects or programs. Start with the outline below and change it to fit your needs.
219

220 |
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 |
PROGRAM
STANDARD PROGRAM PLAN OUTLINE
TABLE OF CONTENTS
1Introduction
2Scope
2.1Program Description
2.2Deliverables
2.3Schedule
2.4Sell-Off Criteria
3 Applicable Documents
3.1Contract
3.2Customer Documents 4 Unusual Contract Clauses
5 Management
5.1Organization and Responsibilities
5.1.1 |
General |
5.1.2 |
System Management |
5.1.3 |
Subcontracts and Materials |
5.1.4 |
Data Management |
5.1.5 |
Configuration Management |
5.1.6 |
Quality Assurance |
5.1.7 |
Team Members and Alliances |
5.1.8 |
Training |
5.2Make/Buy Decisions
5.3Safety
5.4Security
5.5Facilities
5.6Standardization

S T A N D A R D P R O G R A M P L A N O U T L I N E |
221 |
5.7 Program Risks
6 Program Controls
6.1Cost and Schedule Controls
6.2Communication Control
6.3Status Meetings
6.4Design Reviews
6.5Specification Control
6.6Documentation Control
6.7Customer Furnished Property Control
6.8Action Items
6.9War Room
7Schedule
8Requirements Flow-Down
9Work Breakdown Structure (WBS)
10Project Work Authorization
11Technical Approach
12Training
13Packing and Shipping
14Delivery
15Field Operations
16Operations and Maintenance GLOSSARY
APPENDICES
ADEFINITIONS
BDELIVERABLES
CCONTRACT DATA REQUIREMENTS LIST (CDRL)
DCUSTOMER STANDARD REQUIREMENTS
EWORK BREAKDOWN STRUCTURE (WBS) AND WBS DICTIONARY ATTACHMENTS
1Capital Management Plan
2Communication Control Plan

222 |
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 |
3Configuration Management Plan
4Data Management Plan
5Delivery Plan
6Facility Plan
7Field Plan
8Customer-Furnished Property Plan
9Make or Buy Plan
10Subcontract and Material Management Plan
11Operations and Maintenance Plan
12Packing and Shipping Plan
13Project Work Authorizations
14Quality Control Plan
15Requirements Flow-Down Plan
16Risk Mitigation Plan
17Safety Plan
18Schedule
19Security Plan
20Small Business Plan
21Standardization Plan
22Test Plan
23Training Plan
24Engineering Plan
25Transition Plan
26Manufacturing Plan
27Sell-Off Plan

A T T A C H M E N T 2
STANDARD TECHNICAL
PLAN OUTLINE
Because the purposes of companies vary widely, their Technical Plans will vary widely as well. Once established within an enterprise however, the outline and purpose of the Technical Plan will be relatively constant. The content will, of course, change from project to project.
The basis of the following Technical Plan Outline is MIL-STD-490. It is purposely comprehensive. Start with this outline and modify it to your needs.
223

224 |
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 |
STANDARD TECHNICAL PLAN OUTLINE
TABLE OF CONTENTS
Part I—Technical Planning and Control
Paragraph Title
1.0Organization
1.1Objectives
1.2Responsibilities
1.3Authority
2.0Decision and Control Process
3.0Configuration Management
3.1Hardware
3.2Software
3.3Documentation
4.0Review Process
4.1Design Reviews
4.2Subcontractor Reviews
4.3Design Approval and Certification
5.0Continuous Acquisition and Logistic Support (CALS)
6.0System Test Planning
7.0 Technical Performance Management
Part II—System Engineering Process
Paragraph Title
1.0Technical Strategy
2.0Functional Analyses
3.0Requirements Allocation
4.0Generation of Specifications
5.0Alternative Designs
6.0Trade-offs
7.0Synthesis