Defining [] success' for software projects: An exploratory revelation
Urvashi Rathod2006, International journal of project management
Sign up for access to the world's latest research
checkGet notified about relevant papers
checkSave papers to use in your research
checkJoin the discussion with peers
checkTrack your impact
Abstract
Success is found relatively rare in the world of software projects. One possible reason may be the difference in the perception of the meaning of ‘success’ in the minds of people who evaluate the project performance. Usually, stakeholders external to the project organization use target cost and time for inferring ‘project success’ while those internal to project agree that the attainment of ‘scope’ of development decides the ‘project success’. Hence, project success criteria, as believed by different groups of stakeholders, do not match. In this study, we examine the views of one such internal set of stakeholders: Programmer/Developers, Project Managers and Customer Account Managers. We conducted an exploratory survey to determine their view of a successful project. We found surprising uniformity in different constituents of this particular group of stakeholders and all of them overwhelmingly considered meeting the ‘scope’ of software projects, which comprises the functionality and quality of the project outcome, as the highest determinant of success. We believe that this view of software project success in the eyes of software professionals should be studied further to build a comprehensive project evaluation framework and should be utilized effectively to achieve success in terms of external objectives like customer satisfaction and customer happiness.
Related papers
Software practitioner's perception of project success: a pilot study
… Computers. The Internet and Management, 2002
The success of a software development project is generally defined in terms of budget, schedule and customer requirements. However, it is not clear that all project stakeholders hold the same views of success. In this research, we investigate, by means of a questionnaire, those factors that influence software practitioners' view of project success. Our survey shows that the practitioner view comprises two categories, namely personal factors associated with the work and customer/user factors. The personal factor category includes a sense of achievement while working on a project, a good job was done (i.e. a quality was delivered), the project working was satisfying and resulted in professional growth. The customer/user category includes the customer/users were involved, they had realistic expectations and the project met all their requirements.
What do software practitioners really think about project success: an exploratory study
Journal of Systems and Software, 2005
Due to the increasing globalization of software development we are interested to discover if there exist significant cultural differences in practitioners' definition of a successful software project. This study presents the results of a survey in which Chilean software practitioners' perceptions of project success are compared with previous research with US practitioners. Responses from both groups of practitioners indicate that there is a relationship between team-work and success; our results also indicate that there are similar perceptions related to the importance of job satisfaction and project success. However, Chilean responses suggest that if a practitioner is allowed too much freedom within the work environment, job stress results; this in turn is reflected in increasing demands for both job satisfaction and good environmental conditions. This may indicate the potential for the attribution of failure to conditions outside the team, thus preventing a search for problematic team issues and technical problems. In contrast, the data suggests peer control inside the US teams indicating a less stressful environment.
Successful software project and products: An empirical investigation
… on empirical software …, 2006
The circumstances surrounding the success and failure of software projects have been a topic of discussion among both practitioners and researchers for many years. A classical definition of project success is one that is within budget and on time. Some of the most common factors identified in the literature as leading to software project success are user involvement, management support and realistic requirements. Studies have indicated that managers have different perceptions from software practitioners when it comes to defining a successful software project. The observation of this difference of opinions has led us to the question: Could there be different perceptions about what effect various factors have on software project success among different industries? This paper presents an empirical study. Firstly, it begins with a detailed investigation of software product and project success factors. Secondly, it examines success factors for software projects and products across a selection of different industries, based on data collected from companies in Sweden and Australia. Thirdly, it studies how practitioners in industry define success factors for software projects and products.
What do we know about successful software project factors
2013
This dissertation discusses how different practitioners define project success and success factors for software projects and products. The motivation for this work is to identify the way software practitioners’ value and define project success. This can have implications for both practitioner motivation and software development productivity. Accordingly, in this work, we are interested in the various perceptions of the term “success” for different software practitioners and researchers. To get this information we performed a systematic mapping of the recent year’s software development literature trying to identify stakeholders’ perceptions about the success of a project and also possible differences among the views of the various stakeholders of a project. Some common terms related to project success (success project; software project success factors) were considered in formulating the search strings. The results were limited to twenty-two selected peer-reviewed conferences, papers/...
Software project managers and project success: An exploratory study
Journal of Systems and Software, 2006
Traditionally, a project should deliver agreed upon functionality on time and within budget. This study examines the mindset of software development project managers in regard to how they 'define' a successful project in order to arrive at a richer perspective of 'success' from the perspective of project managers. Senior management and members of the development team can gain a better understanding of the perspective of project managers regarding some of the aspects of their work and the project as a whole. Such understanding can facilitate better communication and cooperation among these groups. We investigated components of the developed system (project) in terms of some of the aspects of the delivered system (outcome/project) in order to place traditional measures of success in context with other organizational/managerial measures that have been suggested in the literature. We also investigated specific work-related items. These items have potential implications for the intrinsic motivation of the project manager. The consensus among the project managers who participated in our study indicated that delivering a system that meets customer/user requirements and works as intended through work that provides a sense quality and personal achievement are important aspects that lead to a project being considered a success.
Case study: factors for early prediction of software development success
Information and Software Technology, 2002
Factors such as poor requirements, lack of management support, and customers and users who do not make themselves readily available significantly affect software development success. The earlier in the development process problems arise the more serious is the outcome [2]. When there are limited resources, a project manager needs to know which factors are likely to have the most severe impact on the project. In order to investigate some of these early factors and their effect on the success or failure of software projects we develop an organizational case study. After engaging in structured discussions with twenty-one IT professionals from a large North American financial institution, we asked each participant to respond to a survey addressing two development projects with which they had recently been associated. Our investigation treats these software development projects as a composite case. In addition, we investigate differences in management and developer perceptions of the success or otherwise of our projects and the prediction of project success from the viewpoint of both groups. We find that both managers and developers consider the level of customer and user involvement contributes most to project success. Developers perceive the next most important factors to be (1) that customers and users have realistic expectations and (2) the scope of the project is well defined. On the other hand, to predict success from management's viewpoint, participation of customers and users in estimating project schedules is significant.
A Comparative Framework for Measuring Project Success
Innovation and Supply Chain Management, 2012
Project success is a vague concept among researchers and practitioners. Many researchers have tried to explain when a project could be called successful, but there is no agreement. The reason is existence of different stakeholders and viewpoints in a project. In this article we aim to make a comparative framework to compare different viewpoints and discover intersections and variances in the concept of project success to decrease these diversities. We review 173 selected papers and make an integrated framework containing nine different viewpoints that could be used as a raw dataset to explore trends in the literature and hidden aspects of project success. Analyzing statistics of this framework we found that: 1) Although the focus on stakeholders' satisfaction are increasing but still cost, time and quality is dominating success criteria for evaluating project success. And also we categorized nine success criteria to three levels of priority i.e. high, medium and low priority, based on the frequency of appearance in the papers. Then we found some corelationships between nine groups of criteria using Association Rules method. 2) During 80s most papers deal with cost, time and quality (project management success), and in 90s it expanded to customer satisfaction (product success), then currently, it expanded to multiple project evaluation (program success). We also found that there are still some forgotten parts of project success and we argue that one of the most important hidden aspects is "Project Selection Success". It should be considered because it defines project success at its origin. Furthermore its influence on the project management and total project success is not clearly defined in the literature.
Identification of criteria and metrics for software projects performance: An outcome of interviews
ARPN journal of engineering and applied sciences, 2016
Ample of research has been carried out on the topic software metrics. Lots of metrics have been projected and validated in the field of software engineering especially for software development. However, metrics that related to software project management are still need to explore more especially from the industrial or practitioners. Identification of metrics for software project management may guide the project managers to manage and control the software projects. This is indirectly may reduce the software project failures in the industrial. This paper presents the processes and activities that used to identifying the performance criteria and the related metrics that can be used to monitor the performance of software projects. The aim of this paper is to identify the performance criteria and related metrics from the perspectives of practitioners. We carried out structured interview sessions among project managers from Malaysian Public Sector to accomplish this task. The results of t...
Defining and Measuring Project Success: A Comparative Analysis of Two Key Studies
Defining and Measuring Project Success: A Comparative Analysis of Two Key Studies, 2025
Project success, project management success, and project success criteria are pivotal concepts in modern project management, drawing considerable academic and professional interest. This paper critically evaluates two studies addressing the challenges of defining and measuring project success: Shokri-Ghasabeh and Kavousi-Chabok (2009) and Lamprou and Vagiona (2018). The first study employs a mixed-methods approach to explore conceptual ambiguities in project success and project management success, identifying stakeholder perspectives as central to resolving these ambiguities. Despite offering practical insights, the study’s findings are limited by a low survey response rate. The second study conducts an extensive literature review, categorizing over 20 success criteria and 400 critical success factors, emphasizing the need for context-sensitive evaluation frameworks. While theoretically robust, it lacks empirical validation. This evaluation compares the studies’ methodologies, findings, and contributions, highlighting their complementary strengths. The paper concludes by recommending a combined methodological approach and the development of a context-sensitive framework to enhance the understanding and application of project success criteria and factors in diverse contexts. These insights aim to bridge the gap between theory and practice in project management research and practice.
A retrospective look at our evolving understanding of project success
2006
Our views on project success have changed over the years from definitions that were limited to the implementation phase of the project life cycle to definitions that reflect an appreciation of success over the entire project and product life cycle. This paper assesses our evolving understanding of project success over the past 40 years and discusses conditions for success, critical success factors and success frameworks. The paper concludes with a holistic view of project success and its implications for practice.
Related topics
Related papers
Successful software project and products
Proceedings of the 2006 ACM/IEEE international symposium on International symposium on empirical software engineering - ISESE '06, 2006
The circumstances surrounding the success and failure of software projects have been a topic of discussion among both practitioners and researchers for many years. A classical definition of project success is one that is within budget and on time. Some of the most common factors identified in the literature as leading to software project success are user involvement, management support and realistic requirements. Studies have indicated that managers have different perceptions from software practitioners when it comes to defining a successful software project. The observation of this difference of opinions has led us to the question: Could there be different perceptions about what effect various factors have on software project success among different industries? This paper presents an empirical study. Firstly, it begins with a detailed investigation of software product and project success factors. Secondly, it examines success factors for software projects and products across a selection of different industries, based on data collected from companies in Sweden and Australia. Thirdly, it studies how practitioners in industry define success factors for software projects and products.
Defining and measuring project success
This paper analyses the related concepts of software project success, software project management success and software project product success and proposes a set of dimensions for defining and measuring software project success. An extension of the DeLone and Mclean (1992, p. 87) model is proposed as a base model for software project success. Even though this investigation is only a first step in defining project success, it is expected to be of interest to both Information System and Project Management researchers and practitioners.
Successful Software Projects and Products
2006
Successful or failed software projects have been discussed in literature for many years. Successful software projects are often defined as meeting business objectives, deliver on time and within budget, and meeting requirements. Different factors that contribute to software project success have been identified in the literature. Some of the most common factors that lead to software project success are: user involvement, management support, realistic requirements, and having good estimations. However, there are different opinions about what a successful software project is. Linberg found in a study that managers had a different perception from software practitioners (developers, testers etc.) about what a successful software project is. Since there are different perceptions of what a successful project is among different roles in software development, there may be differences from other perspectives too. This observation relates to the overall research questions in the thesis: Could there be different perceptions about what success factors are for software projects among different countries and customersupplier relationships? Do people from different countries have different perceptions about what success factors are for software products?
Project Success as an Evolving Concept
cerc.wvu.edu
Identifying project success rate and project success factors has been an interest for researchers quite a long time. Traditionally, project success is measured based on performance in three criteria: Cost, schedule, and delivered functionality. Various studies included other factors. In addition, there are studies analyzing project success from the perspectives of different stakeholders. Currently, there are no universally accepted criteria and definition for project success. Without a well-established definition, the researchers have the risk of mislabeling a project as success or failure or vice versa. Therefore, in this paper, rather than trying to provide a universal definition for project success, we provide another way of thinking such as defining success from each stakeholder's perspective. First, we review and discuss the criteria used in the evaluation of project success and the perspectives of various project stakeholders. Finally, we explain a simple tool called project success analysis matrix (PSAM) that can be used to determine whether a project may be considered success or not from a specific stakeholder's perspective.
The dimensions of software engineering success
Proceedings of the 36th International Conference on Software Engineering - ICSE 2014, 2014
ABSTRACT Software engineering research and practice are hampered by the lack of a well-understood, top-level dependent variable. Recent initiatives on General Theory of Software Engineering suggest a multifaceted variable – Software Engineering Success. However, its exact dimensions are unknown. This paper investigates the dimensions (not causes) of software engineering success. An interdisciplinary sample of 191 design professionals (68 in the software industry) were interviewed concerning their perceptions of success. Non-software designers (e.g. architects) were included to increase the breadth of ideas and facilitate comparative analysis. Transcripts were subjected to supervised, semi-automated semantic content analysis, including a software developer vs. other professionals comparison. Findings suggest that participants view their work as time-constrained projects with explicit clients and other stakeholders. Success depends on stakeholder impacts – financial, social, physical and emotional – and is understood through feedback. Concern with meeting explicit requirements is peculiar to software engineering and design is not equated with aesthetics in many other fields. Software engineering success is a complex multifaceted variable, which cannot sufficiently be explained by traditional dimensions including user satisfaction, profitability or meeting requirements, budgets and schedules. A proto-theory of success is proposed, which models success as the net impact on a particular stakeholder at a particular time. Stakeholder impacts are driven by project efficiency, artifact quality and market performance. Success is not additive, e.g., ‘low’ success for clients does not average with ‘high’ success for developers to make ‘moderate’ success overall; rather, a project may be simultaneously successful and unsuccessful from different perspectives.
Critical success factors for software projects: A comparative study
2011
Although there have been studies completed on the critical success factors of software projects, these studies all have been specific to one particular country. There has been no comprehensive study reporting on different project sizes in various domains and in multiple countries. We present our extensive literature survey of critical success factors that impact software projects. Forty-three articles from the years 1990 to 2010 were found to be significant contributions that could be analysed in order to develop a list of critical factors that specifically affect the success of software projects. The method of content analysis and frequency analysis was adopted. Twenty-six critical success factors were found to be related to software project success. We suggest that organisation or project manager is attentive to control the top five critical factors to drive towards project success since the percentage of frequency of occurrences for each is more than 50%. Also, it appears that non-technical factors (94%) dominated over technical factors (6%). In a result unique to our study compared with previous one, we found that the factors of clear and frozen requirements, realistic estimation of the schedule and budget, along with a competent project manager are the five most critical success factors of software projects.
Stakeholders' Perception of Success: An Empirical Investigation
… , 2009. SEAA'09. …, 2009
Different stakeholders involved in the software development may attribute success to different indicators. Analogously they may support different factors considered the root of successful projects. The study presented in this paper explores how different stakeholders perceive project success and what they deem the effect of specific factors on the project outcome. The study highlighted both commonalities and differences among three main stakeholder classes. A substantial agreement was observed concerning the characteristics that make a project or product successful. As far as the factors that could lead to success are concerned, more bias emerged.
What do software practitioners really think about project success: a cross-cultural comparison
Journal of Systems and Software, 2008
Due to the increasing globalization of software development we are interested to discover if there exist significant cultural differences in practitioners' definition of a successful software project. This study presents the results of a survey in which Chilean software practitioners' perceptions of project success are compared with previous research with US practitioners. Responses from both groups of practitioners indicate that there is a relationship between team-work and success; our results also indicate that there are similar perceptions related to the importance of job satisfaction and project success. However, Chilean responses suggest that if a practitioner is allowed too much freedom within the work environment, job stress results; this in turn is reflected in increasing demands for both job satisfaction and good environmental conditions. This may indicate the potential for the attribution of failure to conditions outside the team, thus preventing a search for problematic team issues and technical problems. In contrast, the data suggests peer control inside the US teams indicating a less stressful environment.
Reconciling the Views of Project Success
Project Management Journal, 2018
This article presents a new model encompassing all the important critical attributes needed to measure project success across different stakeholder groups. The study investigates the possibility that project failure is a result of the interpretations of the criteria and factors used for success by multiple stakeholder groups. Unique projects must have their outcome parameters monitored and controlled to minimize the chances of failure and the likely major financial and managerial ramifications for the organization. Early testing of the model supports its use to increase the shared, multiple stakeholder perception of project success, leading to more informed decision making and motivation of employees.
Subjective evaluation as a tool for learning from software project success
Information and Software Technology, 2000
This paper presents a method for using subjective factors to evaluate project success. The method is based on collection of subjective measures with respect to project characteristics and project success indicators. The paper introduces a new classi®cation scheme for assessing software projects. Further, it is illustrated how the method may be used to predict software success using subjective measures of project characteristics. The classi®cation scheme is illustrated in two case studies. The results are positive and encouraging for future development of the approach. q
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.