Agile Practices for the Global Teaming Model

Abstract

Abstract-The Global Teaming Model (GTM) is a CMMI R -style process model comprising 64 recommendations that synthesizes empirical evidence on how to overcome the obstacles faced by global software development projects.While the Global Teaming Model recommendations specify what a global software development project should do, it does not specify how. In order to provide concrete guidance for projects that wish to employ Agile methods in a global software development context, we asked, could the practices described in the Scaled Agile Framework R (SAFe R ) provide examples for how GTM recommendations could be realized?We found 79 of 90 SAFe R Team level practices partly or wholly implement GTM recommendations. The SAFe R mapping onto the Global Teaming model provides a concrete roadmap for teams who need specific advice on how to implement GTM practices that have been identified as necessary to their success.

Plan-Driven Approaches Are Alive and Kicking in Agile Global Software Development

“…Traditionally, GSD follows a plan-driven, structured, waterfall approach, where tasks are allocated according to where they appear in the software development lifecycle [10,11]. By contrast, agile practices are considered capable of mitigating the challenges faced by GSD, as reported by several studies [12,13,[20][21][22]. However, Akbar and Safdar [6] find that the complexity of GSD and need for agility meant that organizations transitioning from co-located to distributed development were more inclined to adopt and tailor agile methods.…”

“…While mostly repackaging and re-branding previously wellknown and appreciated software development practices, the agile movement can be considered an alternative to traditional software development methods [24]. Agile development methods were believed to best suit small, co-located teams, and their success with small teams has inspired their use in large-scale software development [12] as reflected by the many scaled agile frameworks that have emerged over recent years [25]. However, fundamental assumptions regarding agile development are challenged when applying the methods at a large scale [26].…”

“…However, GSD has traditionally followed a plan-driven approach, where tasks are allocated according to where they appear in the software development lifecycle [10,11]. The belief that agile methods, which were mainly used for small projects and co-located teams, cannot be used in GSD no longer stands [12,13]. Agile methods tend to rely on informal processes and regular face-to-face communication to facilitate coordination, whereas distributed software development relies on formal mechanisms [12].…”

“…The belief that agile methods, which were mainly used for small projects and co-located teams, cannot be used in GSD no longer stands [12,13]. Agile methods tend to rely on informal processes and regular face-to-face communication to facilitate coordination, whereas distributed software development relies on formal mechanisms [12].…”

Toward Unveiling How SAFe Framework Supports Agile in Global Software Development

“…The method chosen to evaluate the mapping was the peer review, which consists of a static review of the results using objective criteria and examined by a person who knows the content to be reviewed [27], [132]. The structure of peer review is designed to encourage peer impartiality [133].…”