Topic
Waterfall model
About: Waterfall model is a research topic. Over the lifetime, 1125 publications have been published within this topic receiving 8219 citations.
Papers published on a yearly basis
Papers
TL;DR: In this paper, the benefits of the agile project management (APM) framework compared to the traditional waterfall model, and understand how it can help companies add value and gain competitive advantage are analyzed.
Abstract: Purpose
The purpose of this paper is to analyze the benefits of the agile project management (APM) framework compared to the traditional waterfall model, and understand how it can help companies add value and gain competitive advantage.
Design/methodology/approach
The methodology used was the exploratory qualitative research through a case study of a software project, developed with the support and application of the Scrum framework, in a pharmaceutical industry information technology project.
Findings
There were benefits found in the utilization of the agile framework, such as increased motivation and staff satisfaction, better control of requirements and especially higher quality of the delivered system, generating added value to the organization. Additionally, the project allowed the use of features from the first month of the application deployed, enabling a 75 percent reduction in development time, compared to traditional methods. The software development time was four months, 30 percent of what would be the total if the traditional methodology was adopted. Based on the results, the agile framework, especially the Scrum, proved to be a viable option as a project management approach.
Research limitations/implications
Since this research is an exploratory case study, its results cannot be generalized.
Practical implications
The paper provides relevant practical information and experiences to managers interested in implementing APM, as well as those interested in improving the management of projects.
Originality/value
This paper provides a case study with practical implications of using APM, and APM’s benefits and advantages are compared with the traditional waterfall approach. Companies can use this case study to better understand about the advantages and strengths of APM over the traditional approach.
672 citations
Book•
1 Nov 1989
TL;DR: The spiral model of software development and enhancement has been evolving for several years, based on experience with various refinements of the waterfall model as applied to large government software projects as mentioned in this paper, and it can accommodate most previous models as special cases and further provides guidance as to which combination of previous models best fits a given software situation.
Abstract: Publisher Summary This chapter describes a spiral model of software development and enhancement. The spiral model of the software process has been evolving for several years, based on experience with various refinements of the waterfall model as applied to large government software projects. The spiral model can accommodate most previous models as special cases and further provides guidance as to which combination of previous models best fits a given software situation. Development of the TRW Software Productivity System (TRW-SPS) is its most complete application to date. The chapter illustrates the radial dimension that represents the cumulative cost incurred in accomplishing the steps to date and the angular dimension that represents the progress made in completing each cycle of the spiral.
389 citations
31 May 2014
TL;DR: This case study highlights a number of challenges that arise when crowdsourcing software development at a multinational corporation and works better for specific software development tasks that are less complex and stand-alone without inter dependency.
Abstract: Crowdsourcing is an emerging and promising approach which involves delegating a variety of tasks to an unknown workforce - the crowd. Crowdsourcing has been applied quite successfully in various contexts from basic tasks on Amazon Mechanical Turk to solving complex industry problems, e.g. InnoCentive. Companies are increasingly using crowdsourcing to accomplish specific software development tasks. However, very little research exists on this specific topic. This paper presents an in-depth industry case study of crowdsourcing software development at a multinational corporation. Our case study highlights a number of challenges that arise when crowdsourcing software development. For example, the crowdsourcing development process is essentially a waterfall model and this must eventually be integrated with the agile approach used by the company. Crowdsourcing works better for specific software development tasks that are less complex and stand-alone without interdependencies. The development cost was much greater than originally expected, overhead in terms of company effort to prepare specifications and answer crowdsourcing community queries was much greater, and the time-scale to complete contests, review submissions and resolve quality issues was significant. Finally, quality issues were pushed later in the lifecycle given the lengthy process necessary to identify and resolve quality issues. Given the emphasis in software engineering on identifying bugs as early as possible, this is quite problematic.
250 citations
15 Jun 2009
TL;DR: The case study aims at validating or contradicting the beliefs of what the problems are in waterfall development through empirical research, comparing the problems in literature with the results of a case study at Ericsson AB in Sweden, investigating issues in the waterfall model.
Abstract: Waterfall development is still a widely used way of working in software development companies. Many problems have been reported related to the model. Commonly accepted problems are for example to cope with change and that defects all too often are detected too late in the software development process. However, many of the problems mentioned in literature are based on beliefs and experiences, and not on empirical evidence. To address this research gap, we compare the problems in literature with the results of a case study at Ericsson AB in Sweden, investigating issues in the waterfall model. The case study aims at validating or contradicting the beliefs of what the problems are in waterfall development through empirical research.
242 citations
1 Jan 2012
TL;DR: This comparative summarizes the steps an organization would have to go through in order to make the best possible choice when selecting the right software development life cycle (SDLC).
Abstract: Organizations that are developing software solution are faced with the difficult choice of picking the right software development life cycle (SDLC). The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases. The V-model represents a software development process which may be considered an extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape Agile Modeling is a practice-based methodology for modelling and documentation of software-based systems. It is intended to be a collection of values, principles, and practices for modelling software that can be applied on a software development project in a more flexible manner than traditional Modelling methods. This comparative summarizes the steps an organization would have to go through in order to make the best possible choice.
233 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2026 | 2 |
| 2025 | 161 |
| 2024 | 297 |
| 2023 | 391 |
| 2022 | 659 |
| 2021 | 151 |