2012International Convention on Information and Communication Technology, Electronics and MicroelectronicsRequires access

Agile experiences in software development

Denis Duka

Open publisher page 8 citations

Abstract

From the traditional waterfall model to streamlined ways of software development and to Agile, is a long journey for each organization. In that journey, transition into Agile way of working means a significant change. For any change to happen there is a significant involvement expected from the people, more so in case of Agile, as it involves individuals, interactions and collaborations over different processes. This paper deals with different Agile experiences. It proposes when to use Agile and what are the advantages of such approach. It also describes agility criteria helping to determine if the Agile is followed indeed. The special highlight is put on people and teams investigating their size and impact of geographical distribution on project success. Some reflections after using Agile in our own organization are also presented.

About this research paper

What this paper is about

From the traditional waterfall model to streamlined ways of software development and to Agile, is a long journey for each organization. In that journey, transition into Agile way of working means a significant change. For any change to happen there is a significant involvement expected from the people, more so in case of Agile, as it involves individuals, interactions and collaborations over different processes. This paper deals with different Agile experiences. It proposes when to use Agile and what are the advantages of such approach. It also describes agility criteria helping to determine if the Agile is followed indeed. The special highlight is put on people and teams investigating their size and impact of geographical distribution on project success. Some reflections after using Agile in our own organization are also presented.

Why it matters

OpenAlex reports 8 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

From the traditional waterfall model to streamlined ways of software development and to Agile, is a long journey for each organization. In that journey, transition into Agile way of working means a significant change. For any change to happen there is a significant involvement expected from the people, more so in case of Agile, as it involves individuals, interactions and collaborations over different processes. This paper deals with different Agile experiences. It proposes when to use Agile and what are the advantages of such approach. It also describes agility criteria helping to determine if the Agile is followed indeed. The special highlight is put on people and teams investigating their size and impact of geographical distribution on project success. Some reflections after using Agile in our own organization are also presented.

Key concepts: Agile software development, Waterfall, Agile Unified Process, Lean software development, Agile usability engineering, Extreme programming practices, Waterfall model, Process management

Related papers

Back to paper searchBrowse research topicsOriginal source
Agile experiences in software development — Research Paper | ScholarLens