Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:

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

.pdf
Скачиваний:
34
Добавлен:
28.10.2013
Размер:
1.3 Mб
Скачать

A T T A C H M E N T 8

 

 

Y

 

F

REQUIREMENTS FLOW-

 

M

 

DOWN MATRIXL

A

 

E

 

T

 

 

You can look at a Requirements Traceability Matrix (RTM) as a horizontal

function and a Requirements Flow-Down Matrix (RFM) as a vertical function. The RTM traces where a requirement appears in the overall process while the RFM shows where a requirement has been allocated. Both apply to both prime and subcontractors. The subcontractor versions are usually preceded with an ‘‘S’’ for differentiating between the two.

If you do not have a Requirements Flow-Down Matrix (or Plan), you can use Table A8-1 as a start. Modify the table for your own needs. Just be sure to not change the concepts of content and flow.

In the case of the RFM, there are two levels or sets of requirements to be flowed down. The first is the requirement from the customer as contained in

245

246

 

 

 

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

 

T a b l e A 8 - 1 — R e q u i r e m e n t s F l o w - D o w n M a t r i x ( R F M )

 

 

 

 

 

 

 

 

 

 

 

 

Company

 

Design

 

S/C Plan

S/C A

 

S/C B

Spec Para

 

Reqt

WBS

Plan Para

 

Para

Para

 

Para

1.3.2

 

 

02-03-01

5.3.2

 

5.3.2

1.3.2

 

1.3.2

 

 

 

 

 

 

 

 

 

 

1.3.3

 

 

02-03-02

5.3.3

 

5.3.3

1.3.3

 

N/A

 

 

 

 

 

 

 

 

 

 

1.3.4

 

 

02-03-03

5.3.4

 

5.3.4

1.3.4

 

1.3.4

 

 

 

 

 

 

 

 

 

 

 

 

QA Plan

04-01-01

8.2.6

 

8.2.6

4.3.6

 

4.3.6

 

 

CM Plan

05-01-01

9.3.1

 

9.3.1

5.6.2

 

5.6.2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the SOW or specification. The second is a requirement demanded by enterprise policy.

In some cases, a requirement may be flowed down to one subcontractor and not another. Observe Spec Para Requirement 1.3.3 in the table cross-referenced to Subcontractor B. Such requirements could be those that are product-specific; perhaps Subcontractor A provides that kind of product but Subcontractor B does not.

A T T A C H M E N T 9

DATA DELIVERY MATRIX

Some tool is necessary to compile data delivery requirements from the requirements document (contract), put them in a common place, and assign word dates and delivery dates and responsibilities. The Data Delivery Matrix is a simple and effective tool for accomplishing this overall purpose and providing a central location of past activities as well. A Data Delivery Matrix can be created by using a spreadsheet such as the one shown in Table A9-1. The columns can be extended to the right for multiple deliveries or the right column can be updated periodically as necessary.

If your data manager is so inclined and so talented, a Relational Data Base (RDB) such as Access can be used to do the same thing as the matrix in Table A9-1. The RDB takes more time to set up in the beginning but will save time and possibly mistakes in the long run. If the RDB is used, set the report format so that at least the ‘‘Data’’ column, the ‘‘Frequency’’ column, the ‘‘Next Due’’

247

248

 

 

 

 

 

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

 

 

T a b l e A 9 - 1 — D a t a D e l i v e r y M a t r i x

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Doc No

Title

Resp.

 

Format

First Del

Frequency

A-0001

Monthly Progress

Jones

 

DID 1234

30 days

Monthly

 

 

Report

 

 

 

 

 

ARO1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

T-0001

System Test

 

Smith

 

DID 2345

System Test minus

 

One time

 

 

Package

 

 

 

 

 

30 days

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

T-0002

System Test

 

Harris

 

DID 4567

System Test plus

 

One time

 

 

Results

 

 

 

 

 

 

30 days

 

 

 

1ARO: After Receipt of Order.

column, and the ‘‘Responsibility’’ column are shown in the report format. Usually, the Data Delivery Matrix is routed frequently to all responsible individuals as well as being posted in a central location in a ‘‘paper’’ program. On a ‘‘paperless’’ program the Data Delivery Matrix is provided on the Program Web site.

It is also useful to identify a cognizant individual (project manager, chief engineer, engineer, etc.) associated with each ‘‘X.’’ These people can act as internal experts (consultants) during the execution of your project.

A T T A C H M E N T 1 0

CAPABILITY MATRIX

The purpose of the Capability Matrix is to evaluate your past experience against current requirements and thus reveal the level of capability you have to perform the current requirement. By default, the Capability Matrix will reveal those areas of requirements (tasks) where you do not have capability and must either buy the capability (includes hiring knowledgeable personnel), develop the capability, no-bid the task or requirement, or take a risk in performing the task or requirement.

The Capability Matrix either feeds or is fed by the Experience Window (see Attachment 12) and/or the Risk List (see Attachment 3).

Create a matrix similar to the one shown in Table A10-1 and list all the requirements or tasks (this includes the contents of referenced documents as well as explicitly included documents) along the side and the programs (including IR&D programs) that the enterprise has performed across the top. Every

249

250

 

 

 

 

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

 

 

 

T a b l e A 1 0 - 1 — C a p a b i l i t y M a t r i x

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Project A

Project B

Project C

Project D

Project E

Project F

Task 1

 

 

 

X

 

 

 

 

Task 2

 

X

 

X

 

X

 

 

 

 

 

 

 

 

 

 

Task 3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 4

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 5

X

 

 

 

 

X

 

 

Task 6

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 7

 

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

Task 8

 

X

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

Task 9

 

 

 

 

 

 

 

 

 

requirement or task should have an ‘‘X’’ at the intersect with at least one program. If not, continue with the process to try to bring the requirement to within your capabilities.

A T T A C H M E N T 1 1

POLICY-TO-PLAN TRAIL

A Policy-to-Plan trail is necessary to ensure that the policies required by the enterprise are incorporated into the Project Plan and the Technical Plan. After the first use, this document can be set aside if you create your own Project Plans and Technical Plans. Incorporate the required policies into the respective plans, together with a reference back to the policy. Mark, in your own way, those paragraphs as standard and use them for all subsequent projects and programs.

If you do not have a Policy-to-Plan Process, you can use Table A11-1 to start your process.

Once developed, the Policy-to-Plan Table can be used as an input document to the Standards Traceability Matrix (STM) (see Attachment 13).

The numbers appearing in the policy column reflect the enterprise policy number. The numbers appearing in the plan columns reflect the paragraph number of the plan where the policy is invoked.

251

252

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

T a b l e A 1 1 - 1 — P o l i c y - t o - P l a n T a b l e

 

 

 

 

Policy

Project/Program Plan

 

Technical Plan

11011-Startup

4.1.1

 

2.1.1

11013-Funding

5.1.2

 

 

 

 

 

 

11024-PWA

6.2.2

 

4.3.2

 

 

 

 

11025-Work Packages

6.2.3

 

4.3.3

 

 

 

 

11027-Performance Measurement

7.4.4

 

5.4.3

11041-Program Reviews

8.2.2

 

6.2.3

 

 

 

 

11044-Action Items

9.1.1

 

7.2.2

 

 

 

 

15012-In-Process Reviews

 

 

6.2.4

 

 

 

 

15026-Engineering Drawings

 

 

8.1.1

15033-Specifications

 

 

9.2.2

 

 

 

 

A T T A C H M E N T 1 2

EXPERIENCE WINDOW

The purpose of the Experience Window is to provide a quick check of your experience and evaluate that experience against your capability to perform a particular task. This is particularly important if you are in the process of bidding a task. It can also be used as the first step in determining whether you should seek additional capability in order to perform a task you already have. Table A12-1 shows the inputs for the Experience Window.

If you determine you do not have the experience, the next step is to use the Capability Matrix to refine your needs. A sample Capability Matrix is shown in Table A12-2 and described in Attachment 10 with further information provided in Cause Description 1b and 1b (NO).

253

254

 

 

 

 

 

 

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

 

 

 

 

T a b l e A 1 2 - 1 — E x p e r i e n c e W i n d o w

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Have Customer

 

 

Have Product

 

Capability to

Condition

 

 

Experience

 

 

Experience

 

 

Perform

 

1

 

 

 

Yes

 

 

Yes

 

 

 

High

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2

 

 

 

No

 

 

Yes

 

Moderate

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

Yes

 

 

No

 

 

 

Low

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

 

 

 

No

 

 

No

 

Unknown

 

 

 

 

T a b l e A 1 2 - 2 — C a p a b i l i t y M a t r i x

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Project A

 

Project B

 

Project C

Project D

Project E

 

Project F

Task 1

 

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 2

 

 

 

 

X

 

 

 

X

 

 

 

X

Task 3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 4

 

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 5

 

X

 

 

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 6

 

 

 

 

 

 

 

 

X

 

 

 

 

Task 7

 

 

 

 

 

 

 

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 8

 

 

 

 

X

 

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Task 9