Applying Multi-Criteria Decision Analysis to Global Software Development with Scrum Project Planning

Almeida, Luis Henrique; Pinheiro, Plácido Rogério; Albuquerque, Adriano Bessa

doi:10.1007/978-3-642-24425-4_41

Cited by 14 publications

(10 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Agile methods are seen to term this self-assignment differently such as "volunteering", "signing up", "committing", and "pulling" (Beck 2005;Lee 2010;Deemer et al 2012). Empirical studies have been conducted on novice (Almeida et al 2011;Lin 2013) and experienced agile teams (Masood et al 2017a;Masood et al 2017b) to study task allocation decisions, strategies and workflow mechanisms. These studies inform us that tasks assignment in Agile teams is not the sole responsibility of the manager or other team members.…”

Section: Related Workmentioning

confidence: 99%

How agile teams make self-assignment work: a grounded theory study

2020

View full text Add to dashboard Cite

Self-assignment, a self-directed method of task allocation in which teams and individuals assign and choose work for themselves, is considered one of the hallmark practices of empowered, self-organizing agile teams. Despite all the benefits it promises, agile software teams do not practice it as regularly as other agile practices such as iteration planning and daily stand-ups, indicating that it is likely not an easy and straighforward practice. There has been very little empirical research on self-assignment. This Grounded Theory study explores how self-assignment works in agile projects. We collected data through interviews with 42 participants representing 28 agile teams from 23 software companies and supplemented these interviews with observations. Based on rigorous application of Grounded Theory analysis procedures such as open, axial, and selective coding, we present a comprehensive grounded theory of making self-assignment work that explains the (a) context and (b) causal conditions that give rise to the need for self-assignment, (c) a set of facilitating conditions that mediate how self-assignment may be enabled, (d) a set of constraining conditions that mediate how self-assignment may be constrained and which are overcome by a set of (e) strategies applied by agile teams, which in turn result in (f) a set of consequences, all in an attempt to make the central phenomenon, self-assignment, work. The findings of this study will help agile practitioners and companies understand different aspects of self-assignment and practice it with confidence regularly as a valuable practice. Additionally, it will help teams already practicing self-assignment to apply strategies to overcome the challenges they face on an everyday basis.

show abstract

Section: Related Workmentioning

confidence: 99%

How agile teams make self-assignment work: a grounded theory study

2020

View full text Add to dashboard Cite

show abstract

“…Strategies, measures, and controls have yet to be fully explored in the literature [129] . The lack of comprehensive communication plans and models that could support project manager decisionmaking in GSD contexts has been identified [115] . The use of search methods and surveys with industrial collaborators would be a good option for identifying approaches that can address these challenges.…”

Section: Discussionmentioning

confidence: 99%

“…CBR is therefore a solution option that eases the problems associated with the recovery and application of knowledge in GSD. Unlike GA technology, the CBR [77,85,92,93,106] Decision management [107] Project scope management Knowledge management 8 [11,40,41,53,69,80] Requirement management [94,104] Project time management Planning and scheduling 7 [50,56,60,71,95,100] Time estimation [115] Project cost management Cost estimation 8 [44,58,65,74,75,81] Effort estimation [86,115] Project human resource Table 9 Benefits and limitations of the approaches used in SPM for GSD (MQ7). [ 51,86] (To be continued) Table 9 Benefits and limitations of the approaches used in SPM for GSD (MQ7).…”

Section: Benefits and Limitations Of The Use Of Spm Approaches In Gsdmentioning

confidence: 99%

Software project management approaches for global software development: a systematic mapping study

Bajta¹,

Idri²,

Nicolás

et al. 2018

Tinshhua Sci. Technol.

View full text Add to dashboard Cite

Global Software Development (GSD) is a well established field of software engineering with the benefits of a global environment. Software Project Management (SPM) plays a key role in the success of GSD. As a result, the need has arisen to study and evaluate the downsides of SPM for GSD, to thereby pave the way for the development of new methods, techniques, and tools with which to tackle them. This paper aims to identify and classify research on SPM approaches for GSD that are available in the literature, to identify their current weaknesses and strengths, and to analyze their applications in industry. We performed a Systematic Mapping Study (SMS) based on six classification criteria. Eighty-four papers were selected and analyzed. The results indicate that interest in SPM for GSD has been increasing since 2006. As a class of approaches, the most frequently reported methods (40%) are those used for coordination, planning, and monitoring, along with estimation techniques that can be used to better match a distributed project. SPM for GSD requires further investigation by researchers and practitioners, particularly with respect to cost and time estimations. These findings will help overcome the challenges that must to be considered in future SPM research for GSD, especially regarding collaboration and time-zone differences.

show abstract

“…The model was developed using cognitive mapping and MACBETH (Measuring Attractiveness by a Categorical Based Evaluation Technique) [6]. In [4], Almeida et al applied (MCDA) [3] on the choice of DSD Scrum project plans that have a better chance of success. The application of the model was demonstrated and based on initial results, seemed to significantly help managers to improve the success rates of their projects.…”

Section: Task Allocation In Distributed Software Developmentmentioning

confidence: 99%

Task Allocation Approaches in Distributed Agile Software Development: A Quasi-systematic Review

Filho

Pinheiro

Albuquerque

2015

Advances in Intelligent Systems and Computing

Self Cite

View full text Add to dashboard Cite

Abstract. Increasingly, software organizations are investing in distributed software development. However, this new scenario introduces a number of new challenges and risks. Organizations have sought alternatives to the traditional software development models by applying agile software development practices to distributed development. The key point in a distributed scenario is related to task allocation. This paper conducts a quasi-systematic review of studies of task allocation in distributed software development projects that incorporate agile practices, trying to establish issues for additional research. The study allows us to conclude that there are few works on task classification and prioritization what suggests a fertile area for work.

show abstract

Applying Multi-Criteria Decision Analysis to Global Software Development with Scrum Project Planning

Cited by 14 publications

References 8 publications

How agile teams make self-assignment work: a grounded theory study

How agile teams make self-assignment work: a grounded theory study

Software project management approaches for global software development: a systematic mapping study

Task Allocation Approaches in Distributed Agile Software Development: A Quasi-systematic Review

Contact Info

Product

Resources

About