Premium
THE STATEMENT OF WORK: IT IS NOT NEEDED
Author(s) -
Lake Jerome Jerry G.
Publication year - 1994
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1994.tb01762.x
Subject(s) - statement (logic) , work (physics) , procurement , computer science , engineering management , reading (process) , exposition (narrative) , set (abstract data type) , phase (matter) , software engineering , engineering , business , marketing , political science , mechanical engineering , art , chemistry , literature , organic chemistry , law , programming language
Caution! Reading this exposition may alter your mind set on the need for a statement of work to direct development of a system, large or small, by a performing activity. The recommendation is made to eliminate statements of work, as we now know them, for acquisition efforts involving system definition (Demonstration and Validation phase within the Department of Defense acquisition cycle) and subsystem development (Engineering and Manufacturing Development phase). This paper points out that the statement of work is a redundant document based on the documents that are currently available in a procurement solicitation, or will be available with publication of Mil‐Std‐499B and IEEE P1220 standards on systems engineering. This paper is addressed to those interested in acquisition reform within the Department of Defense. It is also addressed to program managers in commercial enterprises having to communicate work tasks to a subcontractor.