• Corpus ID: 208133055

Impact of Scope Creep on Software Project Quality*

@inproceedings{Thakurta2016ImpactOS,
  title={Impact of Scope Creep on Software Project Quality*},
  author={Rahul Thakurta},
  year={2016}
}
Despite advances in project management methodologies and tools, the chances that a software project is able to achieve its process estimates is about 30% (The Standish Group, 2004). A major reason behind such phenomena is the frequent change of requirements during project progress, brought about by the dynamic nature of development activities (Winters, 2010). This phenomenon where there is a change in the set of requirements due to addition, deletion, and modification during project progress is… 

Figures and Tables from this paper

Role of Requirements Engineering in Software Project’s Success
TLDR
This thesis is a study the impact of requirements documentation quality on software project’s outcomes through a random sample of software projects from 12 different hospitals within a large healthcare provider.
The Impact of Scope Creep on Project Success: An Empirical Investigation
TLDR
The outcome of the study may help the practitioners to understand the dynamics of factors, which undermine scope creep in software SMEs and to assist them in the development of effective control and mitigation strategies, therefore, to increase the project success rate.
An Assessment of risk response strategies practiced in software projects
TLDR
The paper attempts to address the risk response factors that lead to successful achievement of project scope & quality, schedule and cost targets, by using a series of regressions followed with Seemingly Unrelated Regression Equations (SURE) modelling.
An automated unit testing framework for the OutSystems Platform
TLDR
In this work, a framework for automated test case generation in the OutSystems platform is proposed, which targets the Core Business layer in Out system's proposed 4-Layer Canvas.
Ascertaining the impact of contractors pre-qualification criteria on project success criteria
Purpose The selection of a suitable contractor for a project has a significant impact on project success. In order to avoid the selection of an incapable contractor, the capabilities of contractors
Scope Management Strategies for Engineering Leaders to Improve Project Success Rates
Scope Management Strategies for Engineering Leaders to Improve Project Success Rates by Kevin Lee Ramage MBA, Brenau University, 2013 BS, Florida International University, 1998 Doctoral Study
Reflections on Being a Successful Academic Researcher
Research is central to the life of the career academic. However, the framework in which academic research is conducted is not generally well understood and neither is it often articulated or
The success rate of software projects in South African businesses
..................................................................................................................... i Abbreviations and definitions
Stability Assurance in IT-Projects Management Systems
TLDR
Theresa May’s decision to scrap the £20m IT compensation package was based on a review of existing evidence, not on new research, which found it to be a waste of taxpayers’ money.

References

SHOWING 1-10 OF 23 REFERENCES
A study of the impact of requirements volatility on software project performance
TLDR
An extensive survey based empirical study of requirement volatility and its impact on software project performance reveals that requirement volatility has a significant impact on schedule overrun and cost overrun in software projects.
Understanding Requirements Volatility in Software Projects - An Empirical Investigation of Volatility Awareness, Management Approaches and their Applicability
TLDR
The results indicate study participants' heightened perception of the risk of requirements volatility, and the influence of business emerged as the highest determinant of the seven identified factors governing execution strategy selection.
Analysis of requirements volatility during software development life cycle
TLDR
The findings reveal that the main causes of requirements volatility were changes in customer needs, developers' increased understanding of the products, and changes in the organization policy.
Improving the ROI of Software Quality Assurance Activities: An Empirical Study
TLDR
The result of the study gives some implications on how to identify which type of QA activity is insufficient while others might be overdone, how to balance the effort allocation and planning for future projects, and how to improve the weak part of each QA activities and the whole process effectiveness under the specific organization context.
An examination of the effects of requirements changes on software maintenance releases
TLDR
Using data collected from one organization on 44 software releases spanning seven products, this paper presents two quantitative techniques for dealing with requirements change in a maintenance environment, and a regression model helps managers communicate the cost and schedule effects of changing requirements to clients and other release stakeholders.
The Economics of Software Quality Assurance: A Simulation-Based Case Study
TLDR
A comprehensive system dynamics model of the software development process was developed that serves as an experimentation vehicle for QA policy and was used to identify the optimal QA expenditure level and its distribution throughout the project's lifecycle.
Components of Software Development Risk: How to Address Them? A Project Manager Survey
TLDR
Software risks can be best managed by combining specific risk management considerations with a detailed understanding of the environmental context and with sound managerial practices, such as relying on experienced and well-educated project managers and launching correctly sized projects.
A Contigency Model for Requirements Development
TLDR
The model integrates the literature on requirements and software development; sets the scene for future research; and, finally proposes how practitioners can manage risks in requirements development projects.
Integration of formal specification, review, and testing for software component quality assurance
TLDR
It is discussed how formalization, review, and testing work together at different levels of software development for improving software quality through detecting and removing errors in documentation.
...
...