Why is software late? An empirical study of reasons for delay in software development

Genuchten, Michiel van

doi:10.1109/32.87283

Cited by 164 publications

(84 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…31 Rational Rose was the tool with the highest market share both worldwide and in Europe. 32 In 1998 it accounted for 33% of the market, with an increase of 79% on the previous year. 33 For this reason, the percentage found by our survey (52% for the year 1999) appears to be as one would expect.…”

Section: The Results Of the Survey And The Potential Demand For An Nlmentioning

confidence: 99%

Market research for requirements analysis using linguistic tools

Mich

MariangelaFranch

PierluigiInverardi

2004

Requirements Engineering

123

View full text Add to dashboard Cite

Numerous studies in recent months have proposed the use of linguistic instruments to support requirements analysis. There are two main reasons for this: (i) the progress made in natural language processing, (ii) the need to provide the developers of software systems with support in the early phases of requirements definition and conceptual modelling. This paper presents the results of an online market research intended (a) to assess the economic advantages of developing a CASE tool that integrates linguistic analysis techniques for documents written in natural language, and (b) to verify the existence of potential demand for such a tool. The research included a study of the language -ranging from completely natural to highly restricted -used in documents available for requirements analysis, an important factor given that on a technological level there is a trade-off between the language used and the performance of the linguistic instruments. To determine the potential demand for such tool, some of the survey questions dealt with the adoption of development methodologies and consequently with models and support tools; other questions referred to activities deemed critical by the companies involved. Through statistical correspondence analysis of the responses, we were able to outline two "profiles" of companies that correspond to two potential market niches which are characterised by their very different approach to software development.

show abstract

Section: The Results Of the Survey And The Potential Demand For An Nlmentioning

confidence: 99%

Market research for requirements analysis using linguistic tools

Mich

MariangelaFranch

PierluigiInverardi

2004

Requirements Engineering

123

View full text Add to dashboard Cite

show abstract

“…Many determinants of the studied projects were the same as the determinants of pre-agile projects [2,3,12,17]. Requirements could only be stabilized when the product and product use were clear enough.…”

Section: Discussionmentioning

confidence: 96%

“…Requirements engineering, in particular, enables effort estimation, project negotiation, progress tracking, and high test coverage [12]. Project management problems such as customer and management changes, unrealistic project plans, staffing problems, and inability to track problems early lead to delays [17]. Other determinants are software architecture, team size, and tooling.…”

Section: Related Workmentioning

confidence: 99%

Perspectives on Productivity and Delays in Large-Scale Agile Projects

Badampudi

Fricker

Moreno

2013

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Many large and distributed companies run agile projects in development environments that are inconsistent with the original agile ideas. Problems that result from these inconsistencies can affect the productivity of development projects and the timeliness of releases. To be effective in such contexts, the agile ideas need to be adapted. We take an inductive approach for reaching this aim by basing the design of the development process on observations of how context, practices, challenges, and impacts interact. This paper reports the results of an interview study of five agile development projects in an environment that was unfavorable for agile principles. Grounded theory was used to identify the challenges of these projects and how these challenges affected productivity and delays according to the involved project roles. Productivity and delay-influencing factors were discovered that related to requirements creation and use, collaboration, knowledge management, and the application domain. The practitioners' explanations about the factors' impacts are, on one hand, a rich empirical source for avoiding and mitigating productivity and delay problems and, on the other hand, a good starting point for further research on flexible large-scale development.

show abstract

“…However, effort estimation, planning, and development management for SPL are more complex and difficult than those for sequential development, because of inter-connected relationships between core assets and products, concurrency of their projects, and multiple deadline management [2]. In addition, there are still general problems with software effort estimation because of unplanned work [3] and requirements volatility [4]. The total cycle time can sometimes be longer than initially planned because of these problems.…”

Section: Introductionmentioning

confidence: 99%

“…Though the reasons why software effort estimation error appears have been shared among software professionals [3,9], it is still difficult to predict the amount of overrun and its variability, or the level of risk, in specific situations. The variability of effort estimation gives us more useful information than traditional minimum-maximum intervals to indicate its uncertainty [10].…”

Section: Introductionmentioning

confidence: 99%

Project Cost Overrun Simulation in Software Product Line Development

Nonaka

Zhu

Babar

et al.

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. The cost of a Software Product Line (SPL) development project sometimes exceeds the initially planned cost, because of requirements volatility and poor quality. In this paper, we propose a cost overrun simulation model for time-boxed SPL development. The model is an enhancement of a previous model, specifically now including: consideration of requirements volatility, consideration of unplanned work for defect correction during product projects, and nominal project cost overrun estimation. The model has been validated through stochastic simulations with fictional SPL project data, by comparing generated unplanned work effort to actual change effort, and by sensitivity analysis. The result shows that the proposed model has reasonable validity to estimate nominal project cost overruns and its variability. Analysis indicates that poor management of requirements and quality will almost double estimation error, for the studied simulation settings.

show abstract

Why is software late? An empirical study of reasons for delay in software development

Cited by 164 publications

References 4 publications

Market research for requirements analysis using linguistic tools

Market research for requirements analysis using linguistic tools

Perspectives on Productivity and Delays in Large-Scale Agile Projects

Project Cost Overrun Simulation in Software Product Line Development

Contact Info

Product

Resources

About