Exploring the Relationship between Rework Projects and Risk Indicators

When projects fail to adequately meet requirements, organizations are forced to either abandon the project or to initiate a new project to address the original project requirements. Because the organization already has experience with and exposure to many project details, it is possible that the second attempt to address the original requirements (a rework project) will create different challenges for the project team. The purpose of this study was to examine risk indicators for rework projects and to determine whether or not risk indicators were the same or different for rework projects. A risk indicator is a factor that has predictive power about the likelihood of a risk occurring in the course of a project's life cycle. The projects studied for this research were undertaken by a large engineering design organization. The results show that there are some important differences in the types of risk indicators experienced by project managers and project teams in rework projects. Specifically, the risks associated with project urgency, quality, and technological changes were more common in rework projects. By understanding and attending to these differences in rework project risks, project managers will be better equipped to successfully guide rework projects to completion.

[1]  C. Herstatt,et al.  Planning and Uncertainty in New Product Development , 2008 .

[2]  Walid Belassi,et al.  A new framework for determining critical success/failure factors in projects , 1996 .

[3]  J. C. Flanagan.  Psychological Bulletin THE CRITICAL INCIDENT TECHNIQUE , 2022 .

[4]  Ofer Zwikael,et al.  From Critical Success Factors to Critical Success Processes , 2006 .

[5]  Jim Freeman,et al.  The Influence of Experience and Information Search Styles on Project Risk Identification Performance , 2007, IEEE Transactions on Engineering Management.

[6]  Christoph H. Loch,et al.  Lost Roots: How Project Management Came to Emphasize Control over Flexibility and Novelty , 2010 .

[7]  Peter E.D. Love,et al.  BENCHMARKING, BENCHACTION, AND BENCHLEARNING: REWORK MITIGATION IN PROJECTS , 2003 .

[8]  Sabine Kuester,et al.  Externally Directed and Internally Directed Market Launch Management: The Role of Organizational Factors in Influencing New Product Success† , 2012 .

[9]  Sara A. McComb,et al.  An investigation of project complexity's influence on team communication using Monte Carlo simulation , 2011 .

[10]  Harvey Maylor,et al.  Managerial Complexity in Project-Based Operations: A Grounded Model and Its Implications for Practice , 2008 .

[11]  Mark Vandenbosch,et al.  Project Complexity and Efforts to Reduce Product Development Cycle Time , 1999 .

[12]  A. Griffin.  The Effect of Project and Process Characteristics on Product Development Cycle Time , 1997 .

[13]  Jeffrey A. Hoffman,et al.  Procedure rework: a dynamic process with implications for the “rework cycle” and “disaster dynamics” , 2011 .

[14]  Richard R. Reilly,et al.  New Product Development Speed: Too Much of a Good Thing?: New Product Development Speed , 2012 .

[15]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

[16]  Bee Bee Chua,et al.  Examining Requirements Change Rework Effort: A Study , 2010, ArXiv.

[17]  Elizabeth Chell,et al.  A study of entrepreneurship in the restaurant and café industry: exploratory work using the critical incident technique as a methodology. , 1998 .

[18]  Franziska Wulf.  Human Factors In Systems Engineering , 2016 .

[19]  Wei-Tsong Wang,et al.  Knowledge sharing practices of project teams when encountering changes in project scope: A contingency approach , 2012, J. Inf. Sci..

[20]  Peter E.D. Love,et al.  Calculating total rework costs in Australian construction projects , 2005 .

[21]  K. Clark,et al.  The power of product integrity. , 1990, Harvard business review.

[22]  Hareton K. N. Leung,et al.  A Risk Management Methodology for Project Risk Dependencies , 2011, IEEE Transactions on Software Engineering.

[23]  A. Shenhar,et al.  Risk Management, Project Success, and Technological Uncertainty , 2002 .

[24]  Glauco Henrique de Sousa Mendes,et al.  Predicting Success in Product Development: The Application of Principal Component Analysis to Categorical Data and Binomial Logistic Regression , 2013 .

[25]  Richard R. Reilly,et al.  New Product Development Speed: Too Much of a Good Thing? , 2009 .

[26]  T. Fujimoto,et al.  The Effect of “ Front-Loading ” Problem-Solving on Product Development Performance , 2000 .

[27]  Lynda Berends,et al.  Using multiple coders to enhance qualitative analysis: The case of interviews with consumers of drug treatment , 2005 .

[28]  Rainer Seidel,et al.  A project contingency framework based on uncertainty and its consequences , 2010 .

[29]  B.J. Koltveit,et al.  Exploiting opportunities in uncertainty during the early project phase , 2005, IEEE Engineering Management Review.

[30]  Hans Petter Krane,et al.  A Review on Possible Approaches for Detecting Early Warning Signs in Projects , 2013 .

[31]  Peter E.D. Love,et al.  Influence of Project Type and Procurement Method on Rework Costs in Building Construction Projects , 2002 .

[32]  Stefan H. Thomke,et al.  Six Myths of Product Development , 2012 .

[33]  Robert J. Chapman,et al.  The controlling influences on effective risk identification and assessment for construction design management , 2001 .

[34]  Niam Yaraghi,et al.  Critical success factors for risk management systems , 2011 .

[35]  J. O'Neill,et al.  Project management. , 2001, Health management technology.

[36]  Jennifer A. Farris,et al.  Improving Product Development Performance Through Iteration Front-Loading , 2013, IEEE Transactions on Engineering Management.

[37]  Jorge B. Stein,et al.  Contextual Factors in the Selection of Strategic Decision Methods , 1981 .