Premium
1.6.2 An Approach to Tailoring Major Technical Reviews Based on Project Characteristics and Stakeholder Interests
Author(s) -
Richstein Alan B.,
Nolte Jerome T.,
Pfarr Barbara B.
Publication year - 2004
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2004.tb00488.x
Subject(s) - milestone , stakeholder , presentation (obstetrics) , process (computing) , process management , project management , work (physics) , engineering management , project stakeholder , best practice , schedule , project manager , identification (biology) , project charter , project team , computer science , project management triangle , engineering , knowledge management , systems engineering , political science , public relations , medicine , history , mechanical engineering , botany , archaeology , biology , law , radiology , operating system
Both NASA and DOD have well defined, proven technical review processes that include numerous technical reviews that occur throughout the systems engineering process life cycle. Many are well known by project managers and stakeholders such as developers and end users, an example of which is the critical design review (CDR). This major milestone for a large, complex new project may last two or more days, include an extensive agenda of topics, and entail hundreds of hours of developer time to prepare presentation materials and associated documents. Additionally, the weeks of schedule spent on review preparation is at least partly at the expense of other work. This paper suggests an approach for tailoring technical reviews, based on the project characteristics and the project manager's identification of the key stakeholders and understanding of their most important issues and considerations. With this insight the project manager can communicate to, manage expectations of, and establish formal agreement with the stakeholders as to which reviews, and at what depth, are most appropriate to achieve project success. The authors, coming from diverse organizations and backgrounds, have drawn on their personal experiences and summarized the best practices of their own organizations to create a common framework to provide guidance on the adaptation of design reviews to other system engineers.