Classes of Distributed Agile Development Problems

Kajko-Mattsson, Mira; Azizyan, Gayane; Magarian, Miganoush Katrin

doi:10.1109/agile.2010.14

Cited by 20 publications

(12 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The performance of every method relies on various parameters like difficulty of the project, scheduling, staff expertise, development methods, etc. Studies and experiments are being conducted in order to improve accuracy of the estimates of several factors linked with projects to help the leaders to give more satisfying software development cost and schedule estimates [13].…”

Section: Literature Reviewmentioning

confidence: 99%

Appraisement of different software estimation models: A rumination and contradistinction

Mishra

Dhir

2015

2015 International Conference on Soft Computing Techniques and Implementations (ICSCTI)

View full text Add to dashboard Cite

In software project development, proclamation of programming happens after a few programming, reporting, testing and bug settling. The coordinated philosophy helps the product venture improvement in giving distinct options for customary task administration by presenting a few effort and expense estimation models, yet the best technique to appraise productively has still not been found. As few models are agreement based and others are relapsing based so it gets to be troublesome for the analyzer to settle on a choice. In this paper, a few models on agile methodology are being looked at on a few parameters, in order to check the disadvantages and also the advantages of the same furthermore to become acquainted with the distinctive estimating models.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Appraisement of different software estimation models: A rumination and contradistinction

Mishra

Dhir

2015

2015 International Conference on Soft Computing Techniques and Implementations (ICSCTI)

View full text Add to dashboard Cite

show abstract

“…The purpose of this work is to provide support to the community of practitioners and researchers for identifying and managing DAD risks for the achievement of the success goals of the project. Identification of high impact DAD risks with respect to the project goals is based on the prior research (Kontio, 2001;Mattsson et al, 2010;Islam et al, 2014;Jiang & Klein, 2000) and the practitioners' perception. We have used Goal driven Risk Management (GSRM) framework (Islam et al, 2014) in order to study risks in DAD projects while considering the performance goals that are important for project success.…”

Section: Theoretical Considerationmentioning

confidence: 99%

“…Research studies that have explored on risk factors in agile development impacting the project success include (Bass, 2016;Sheffield & Lemetayer, 2013;Coram & Bohner, 2005). A number of research studies have also explored the risks occurring in DAD projects (Jalali & Wohlin, 2010;Hossain et al, 2009;Mudumba & Lee, 2010;Mattsson et al, 2010;Paasivaara & Durasiewicz & Lassenius, 2009). Further work in identification of the most important risks in DAD projects and the most frequently used methods to manage those risks have been done by (Shrivastava & Rathod, 2014;Shrivastava & Rathod, 2017).…”

Section: Related Studiesmentioning

confidence: 99%

“…For this work, the researchers used the list of the DAD risk factors from the earlier studies (Balasubramaniam et al, 2006;Herbsleb, 2007;Mattsson et al, 2010;Mudumba & Lee, 2010) and asked the practitioners playing different roles in DAD projects, through two-staged survey to rank their impact on the project goals of "Time", Cost" and "Quality". The analysis of survey responses revealed that the risk factors have statistically significant perceived impact on the project goals of Time and Quality.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Goal-driven Risk Management approach for Distributed Agile Development Projects

Shrivastava¹,

Rathod²

2019

AJIS

View full text Add to dashboard Cite

Software companies are now using Distributed Agile Development (DAD) in order to create high quality solutions, which aligns with the business priorities of lesser time and cost. Although, DAD is beneficial, there are significant risks involved in such projects. In order to minimize the adverse effect of risks on DAD projects, it is imperative to understand, how the risks impact the project performance goals including ‘Time’, ‘Cost’ and ‘Quality’. In this paper we present a goal driven approach for managing risks in DAD projects. This approach of risk management will enable project managers to identify the most important risks with respect to the goal to be achieved and focus on managing those risks first. The study shows that if ‘Time’ is a considered goal for a DAD project, the most important risks that would need consideration are related to requirement management, architecture changes and coordination issues between stakeholders. Similarly, if ‘Quality’ is the primary performance goal in a DAD project, it would be necessary to first deal with risks related to internal and external communication in the organization, team collaboration and requirement documentation availability. The awareness of top ranking risk factors that impact a particular project goal will assist the projects managers to control the risks in a way that the desired project goals can be achieved.

show abstract

“…Agile methods continually gain attention and face extensive adoption but there is also a trend towards distribution, where teams facilitate modern communication technologies to bridge the challenges of spatial dispersion [1]. In 2016 around 25% of German software developers reported to have experience with working remote [2].…”

Section: Introductionmentioning

confidence: 99%

Agile Distributed Software Development in Nine Central European Teams:challenges, Benefits and Recommendations

Stadler¹,

Vallon²,

Pazderka³

et al. 2019

IJCSIT

View full text Add to dashboard Cite

Although initially designed for co-located teams, agile methodologies promise mitigation to the challenges present in distributed software development with their demand for frequent communication. We examine the application of agile practices in software engineering teams with low geographical distribution in Austria and Germany. To gather insights on challenges and benefits faced by distributed teams we conduct interviews with eleven representatives and analyse the interview transcripts using the inductive category formation method. As a result, we identify four major challenges, such as technical obstructions or the impediments different language abilities have on communication, and four benefits, regarding collaboration and information radiation, that agile methods yield in distributed teams. Based on our analysis of challenges and benefits, we deduct seven recommendations to improve collaboration, overcome distance and avoid pitfalls. Key recommendations for teams with low geographical distance include that teams should get together at certain points to build relationships and trust and share information face-toface.

show abstract

Classes of Distributed Agile Development Problems

Cited by 20 publications

References 16 publications

Appraisement of different software estimation models: A rumination and contradistinction

Appraisement of different software estimation models: A rumination and contradistinction

A Goal-driven Risk Management approach for Distributed Agile Development Projects

Agile Distributed Software Development in Nine Central European Teams:challenges, Benefits and Recommendations

Contact Info

Product

Resources

About