Global Teaming Model
Global Teaming Model 1. Global Teaming Model------------------------------------------------------------------------------- 3
2. Overview of Global Teaming Model---------------------------------------------------------------- 4
3. The Global Teaming Model and its feature-------------------------------------------------------- 10
4. Global Project management-------------------------------------------------------------------------- 11
5. Conclusion--------------------------------------------------------------------------------------------- 16
6. References--------------------------------------------------------------------------------------------- 18
Global Teaming Model Today, it is not unusual to find software engineers working in an environment that is globally distributed which is known as Global Software Development (GSD). However, GSD has several complexities, which challenge those who have numerous experiences with regard to local software development. Global distance can be discussed from four major viewpoints which are temporal, geographical, linguistic and cultural. Each of these aspects causes particular issues for engineers dealing with softwares as they work in this environment (Richardson et al, 2012, p. 1176).
Geographical distance is responsible for causing physical separation among management and team members. On the other hand, temporal distance limits and hinders opportunities that can create cooperation and direct contact with other people. Cultural distance impacts negatively on how colleagues and teams understand and appreciate activities of each other. Linguistic distance, which can be normally identified by the absence of common native language, leads to communication problems (Richardson et al, 2012, pp. 1178-80). This essay discusses the Global Teaming Model and its essence in the work environment. In software development, there exists increased dependence on architecture which can be attributed to increase of complexities
2. Overview of Global Teaming Model---------------------------------------------------------------- 4
3. The Global Teaming Model and its feature-------------------------------------------------------- 10
4. Global Project management-------------------------------------------------------------------------- 11
5. Conclusion--------------------------------------------------------------------------------------------- 16
6. References--------------------------------------------------------------------------------------------- 18
Global Teaming Model Today, it is not unusual to find software engineers working in an environment that is globally distributed which is known as Global Software Development (GSD). However, GSD has several complexities, which challenge those who have numerous experiences with regard to local software development. Global distance can be discussed from four major viewpoints which are temporal, geographical, linguistic and cultural. Each of these aspects causes particular issues for engineers dealing with softwares as they work in this environment (Richardson et al, 2012, p. 1176).
Geographical distance is responsible for causing physical separation among management and team members. On the other hand, temporal distance limits and hinders opportunities that can create cooperation and direct contact with other people. Cultural distance impacts negatively on how colleagues and teams understand and appreciate activities of each other. Linguistic distance, which can be normally identified by the absence of common native language, leads to communication problems (Richardson et al, 2012, pp. 1178-80). This essay discusses the Global Teaming Model and its essence in the work environment. In software development, there exists increased dependence on architecture which can be attributed to increase of complexities
References: Ali-Babar, M Winkler, D & Biffi, S 2007, "Evaluating the usefulness and ease of use of a groupware tool for the software architecture evaluation process," 1stIntl. Symp. on Empirical Software Engineering and Measurement (ESEM 2007), pp. 430-439. Avritzer, A Paulish, D & Yuanfang, C 2008 " Coordination implications of software architecture in a global software development project," 7th Working IEEE/IFIP Conference on Software Architecture (WICSA 2008), pp. 107-116. Bass, L Clements, P & Kazman, R 2003, Software Architecture in Practice, 2nd Ed., Addison Wesley. Beecham, S Hall, T & Rainer, A 2005, "Defining a requirements process improvement model," Software Quality Journal, vol. 13, no. 3, pp. 247-279. Beecham, S Noll, J Richardson, I & Ali, N 2010, Crafting a Global Teaming Model for Architectural Knowledge, International Conference on Global Software Engineering, 1(1), 54-61. Clerc, V Lago, P & Vliet, H 2007, "Global software development: are architectural rules the answer?" 2nd IEEE Intl. Conf. on Global Software Engineering (ICGSE '07), pp. 225-234. Faria, HR & Adler, G 2006, "Architecture-centric global software processes," Intl. Conf. on Global Software Engineering (ICGSE '06), pp. 241-242. Herbsleb JD & Grinter, RE 1999, "Architectures, coordination, and distance: Conway’s law and beyond," IEEE Software, vol. 16, no. 5, pp. 63-70. Laredo, JA & Ranjan, R 2008, "Continuous improvement through iterative development in a multi-geography environment," IEEE Intl. Conf. on Global Software Engineering (ICGSE '08), pp. 232-236. Richardson, I Casey, V McCaffery, F Burton, J & Beecham, S 2012, A Process Framework for Global Software Engineering Teams. Information and Software Technology, 54(1), 1175-1191.