Project Smells for Early Detection of Problems with Benefits Realization

Abstract

Although substantial research has provided guidance on how to identify and manage the benefits of new software solutions, ensuring the realization of those benefits remains a challenge. Inspired by the notion of code smells for software quality, we develop a concept of project smells for benefits realization. We conducted 22 in-depth interviews with participants in nine public-sector digitalization projects, and elicited seven project smells: 1. Dilemma between enthusiasm and formality, 2. Situational differences, 3. Resistance to realization, 4. Slipping opportunities, 5. Loss of focus due to project size, 6. Lacking commitment, 7 Insufficient contact with recipients. We argue that these project smells are a complement to traditional project metrics which focus on time, cost and scope, or the evaluation of benefits after a project is finished. Each smell comes with a set of questions intended to help practitioners identify the odour of their projects. The intention is that project smells can function as low-cost, early indicators helping practitioners adjust work readily and rapidly to ensure benefits realization of their software development investments, thereby focusing actively on the project’s product, rather than myopically on the project itself.