Experiences tracking agile projects: an empirical study

Sato, Danilo; Bassi, Dairton; Bravo, Mariana V.; Goldman, Alfredo; Kon, Fábio

doi:10.1007/bf03194495

Cited by 16 publications

(9 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The result is summarized in Table and shows that seven papers report on “classic” SPI approaches to introduce agile methods or practices. As these seven papers consider standard SPI‐related questions that do not include agile methods and practices as core components of an SPI initiative, we only provide a brief overview of these papers in Section . The focus of this section is on the remaining 48 papers (Table , category 2) that utilize agile concepts to steer SPI projects.…”

Section: Study Resultsmentioning

confidence: 99%

“…Authors only showcase this framework by using two exemplarily selected agile practices. Sato et al present metrics to track process transitions and also showcase their approach using agile practices. Fucci et al conduct a series experiments and study the impact of process conformance on the effective use of test‐driven development practices.…”

Section: Study Resultsmentioning

confidence: 99%

See 1 more Smart Citation

How has SPI changed in times of agile development? Results from a multi‐method study

Küpper

Pfahl

Jürisoo

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

The emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI).Through a set of complementary studies, we aim to understand how SPI has changed in times of agile software development. Specifically, we aim (a) to identify and characterize the set of publications that connect elements of agility to SPI, (b) to explore to which extent agile methods/practices have been used in the context of SPI, and (c) to understand whether the topics addressed in the literature are relevant and useful for industry professionals. To study these questions, we conducted an in-depth analysis of the literature identified in a previous mapping study, an interview study, and an analysis of the responses given by industry professionals to SPI-related questions stemming from an independently conducted survey study. Regarding the first question, we identified 55 publications that focus on both SPI and agility of which 48 present and discuss how agile methods/practices are used to steer SPI initiatives. Regarding the second question, we found that the two most frequently mentioned agile methods in the context of SPI are Scrum and Extreme Programming (XP), while the most frequently mentioned agile practices are integrate often, test-first, daily meeting, pair programming, retrospective, on-site customer, and product backlog. Regarding the third question, we found that a majority of the interviewed and surveyed industry professionals see SPI as a continuous activity. They agree with the agile SPI literature that agile methods/practices play an important role in SPI activities but that the importance given to specific agile methods/practices does not always coincide with the frequency with which these methods/practices are mentioned in the literature. KEYWORDSagile methods, software process improvement, SPI, systematic review INTRODUCTIONSoftware has become the key driver in many industry sectors, and software development processes face increasing demands for flexibility, customer-and value-orientation, short time-to-market cycles, and high quality. As a consequence, companies are challenged with finding appropriate software development methods that, on the one hand, allow for flexible project operation and, on the other hand, allow for creating high-quality products. To define, adapt, evaluate, and improve their software processes, companies implement software process improvement (SPI) initiatives. According to Humphrey 1 and Münch et al, 2 SPI comprises a variety of tasks, ie, scoping, assessment, design and realization, and continuous improvement. Furthermore, SPI is considered relevant to companies 3 regardless of their size and industry sector.SPI has been around for decades, 4 and numerous approaches to conduct SPI have been proposed. 5,6 The different SPI approaches range from formal/prescriptive/de-facto (commercial) standards, such as the Capability Maturity Model Integration (CMMI) or ISO/IEC 15504, which are often critic...

show abstract

Section: Study Resultsmentioning

confidence: 99%

Section: Study Resultsmentioning

confidence: 99%

How has SPI changed in times of agile development? Results from a multi‐method study

Küpper

Pfahl

Jürisoo

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Most of the quantitative metrics introduced in the context of agile methodologies provide very limited coverage of the crucial aspects. Most metrics deal with running or finished processes (methodology instances), evaluating the performance of a specific process or technique, and assessing the complexity and stability of the models produced [5,23,24,25,26,27]. There are few metrics available for evaluating a methodology independent of its instances, and these mainly focus on modeling some part of the methodology with a specific language, and then measuring the presence of certain characteristics (such as complexity) in the resulting model [7,28,29,30,31].…”

Section: Background and Related Workmentioning

confidence: 99%

CEFAM: Comprehensive Evaluation Framework for Agile Methodologies

Taromirad

Ramsin

2008

2008 32nd Annual IEEE Software Engineering Workshop

View full text Add to dashboard Cite

Agile Software Development is regarded as an effective and efficient approach, mainly due to its ability to accommodate rapidly changing requirements, and to cope with modern software development challenges. There is therefore a strong tendency to use agile software development methodologies where applicable; however, the sheer number of existing agile methodologies and their variants hinders the selection of an appropriate agile methodology or method chunk. Methodology evaluation tools address this problem through providing detailed evaluations, yet no comprehensive evaluation framework is available for agile methodologies. We introduce the Comprehensive Evaluation Framework for Agile Methodologies (CEFAM) as an evaluation tool for project managers and method engineers. The hierarchical (and mostly quantitative) evaluation criterion set introduced in this evaluation framework enhances the usability of the framework and provides results that are precise enough to be useful for the selection, adaptation and construction of agile methodologies.

show abstract

“…Agile software development proved its power in practice on many small and middle size projects (example success stories [1][2] [3]). Later the agile idea is introduced in the maintenance [4] [5].…”

Section: Introductionmentioning

confidence: 99%

Importance of stable velocity in agile maintenance

Omanović

Buza

2013

2013 XXIV International Conference on Information, Communication and Automation Technologies (ICAT)

View full text Add to dashboard Cite

Agile maintenance is the best choice if you want to keep step with your customer needs. It is a result of trying to respond to customer change requests with the high efficiency. High involvement of the customer in the maintenance process is good but also can have negative effects. Change in the behavior of the customer can influence the execution of the change management process or cause the change of the release plan, etc. All that can destabilize normal maintenance velocity and lead to a chaotic relationship with the customer, if not controlled or prevented. This paper describes problems in agile maintenance caused mostly by the change of the customer behavior at the beginning of the economic crisis. It also presents results of the analysis of these problems and recommendations how to identify them and how to prevent them.

show abstract

Experiences tracking agile projects: an empirical study

Abstract: In

Cited by 16 publications

References 21 publications

How has SPI changed in times of agile development? Results from a multi‐method study

How has SPI changed in times of agile development? Results from a multi‐method study

CEFAM: Comprehensive Evaluation Framework for Agile Methodologies

Importance of stable velocity in agile maintenance

Contact Info

Product

Resources

About