Empirical Analysis on the Satisfaction of IT Employees Comparing XP Practices with Other Software Development Methodologies

Mannaro, Katiuscia; Melis, Marco; Marchesi, Michele

doi:10.1007/978-3-540-24853-8_19

Cited by 49 publications

(30 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, a longitudinal study by Syed-Abdullah et al [9] revealed that XP methodology has a positive impact on an individual's disposition to be happy, across time and situations. This finding is supported in a comparative study, where job satisfaction was found to be higher in developers using XP practices as opposed to developers not using XP practices [10]. Practitioners showed a strong preference for working in an XP environment, using XP practices.…”

Section: Motivation and Xpmentioning

confidence: 58%

“…[8][9][10], that gives greater job satisfaction [11,12], reduces the software development cost [13] and increases code quality [14]. Yet no study has placed the known and accepted XP values and characteristics directly in line with developer preferences coming from a traditional background, to show where needs are met and where values are challenged or in some cases are missing altogether.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Does the XP environment meet the motivational needs of the software developer? An empirical study

Beecham

Sharp

Baddoo

et al. 2007

Agile 2007 (Agile 2007)

View full text Add to dashboard Cite

show abstract

Section: Motivation and Xpmentioning

confidence: 58%

Section: Introductionmentioning

confidence: 99%

Does the XP environment meet the motivational needs of the software developer? An empirical study

Beecham

Sharp

Baddoo

et al. 2007

Agile 2007 (Agile 2007)

View full text Add to dashboard Cite

show abstract

“…An additional benefit is the regular feedback on development progress provided to customers [Ilieva et al(2004)]. From a work-environment perspective agile projects are perceived as comfortable as they can be characterized as respectful, trustful, and help preserving quality of working life [Mannaro et al (2004)]. …”

Section: Plan-driven Developmentmentioning

confidence: 99%

The effect of moving from a plan-driven to an incremental software development approach with agile practices

2010

View full text Add to dashboard Cite

So far, only few in-depth studies focused on the direct comparison of process models in general, and between plan-driven and incremental/agile approaches in particular. That is, it is not made explicit what the effect is of moving from one model to another model. Furthermore, there is limited evidence on advantages and issues encountered in agile software development, this is specifically true in the context of large-scale development.Objectives: The objective of the paper is to investigate how the perception of bottlenecks, unnecessary work, and rework (from hereon referred to as issues) changes when migrating from a plan-driven to an incremental software development approach with agile practices (flexible product backlog, face-to-face interaction, and frequent integration), and how commonly perceived these practices are across different systems and development roles. The context in which the objective should be achieved is largescale development with a market-driven focus. The selection of the context was based on the observation in related work that mostly small software development projects were investigated and that the investigation was focused on one agile model (eXtreme programming).Research Method: A case study was conducted at a development site of Ericsson AB, located in Sweden in the end of 2007. In total 33 interviews were conducted in order to investigate the perceived change when migrating from plan-driven to incremental and agile software development, the interviews being the primary source of evidence. For triangulation purposes measurements collected by Ericsson were considered, the Author One School 1 Institute 1 Address 1 Institute 2 Address Tel.: 00-10-00000000 E-mail: mail@domain.com Author Two School Institute Aaddress 2 measurements relating to unnecessary work (amount of discarded requirements) and rework (data on testing efficiency and maintenance effort). Triangulation in this context means that the measurements were used to confirm the perceived changes with an additional data source.Results: In total 64 issues were identified, 24 being of general nature and the remaining 40 being local and therefore unique to individual's opinions or a specific system. The most common ones were documented and analyzed in detail. The commonality refers to how many persons in different roles and across the systems studied have mentioned the issues for each of the process models. The majority of the most common issues relates to plan-driven development. We also identified common issues remaining for agile after the migration, which were related to testing lead-time, test coverage, software release, and coordination overhead. Improvements were identified as many issues commonly raised for the plan-driven approach were not raised anymore for the incremental and agile approach.Conclusion: It is concluded that the recent introduction (start in 2005 with the study being conducted in the end of 2007) of incremental and agile practices brings added values in comparison to the plan-driven approach, whi...

show abstract

“…Although there are some papers about the perception from adopters of Agile methods, however, these studies were mainly carried out in Western countries such as Canada, the European region and the United States [6][7][8]. We need to understand the perceptions of practitioners particularly from other region.…”

Section: Background and Motivationmentioning

confidence: 99%

Emergence of Agile Methods: Perceptions from Software Practitioners in Malaysia

2012

View full text Add to dashboard Cite

Abstract-Agile methods are an established process for developing software nowadays. There is, however, less evidence on their usage among software practitioners in Malaysia. While the methods have become mainstream in other regions, that is not the case in this country. This paper empirically investigates the perceptions of Agile methods usage from seven organisations involving 14 software practitioners in Malaysia. Our participants are using Scrum and have a maximum of five years experience. We categorised our findings in terms of awareness, introduction, and challenges they are facing, together with the suggested and practiced solution from them. Interestingly, a change in mind set when practicing Agile was identified to be helpful in reducing the challenges. Lastly we present the practices in Agile they perceived to deliver the most benefits. We found that the use of Agile is still emerging in the country, and awareness is still lacking especially within the government sector. Although several challenges have been encountered when introducing Agile in their organisations, the benefits of Agile are reported to be in Agile practices such as: the involvement from all parties from the beginning, daily stand-up meeting, iterative and incremental, applying burn down chart, sprint and continuous integration. We aim to provide awareness and knowledge about Agile methods to the practitioners in the country and the nearby region. This paper can serve as a reference to the early adopters who intend to use Agile methods in the future.

show abstract

Empirical Analysis on the Satisfaction of IT Employees Comparing XP Practices with Other Software Development Methodologies

Cited by 49 publications

References 1 publication

Does the XP environment meet the motivational needs of the software developer? An empirical study

Does the XP environment meet the motivational needs of the software developer? An empirical study

The effect of moving from a plan-driven to an incremental software development approach with agile practices

Emergence of Agile Methods: Perceptions from Software Practitioners in Malaysia

Contact Info

Product

Resources

About