Approaching Software Localization in. Agile Software Development. Malte Ressin*, José Abdelnour-Nocera**, and Andy Smith**. Thames Valley University ...
Lost in Agility? Approaching Software Localization in Agile Software Development Malte Ressin*, José Abdelnour-Nocera**, and Andy Smith** Thames Valley University, Centre for Internationalisation and Usability, St Mary’s Road, London, UK, W5 5RF {malte.ressin,jose.abdelnour-nocera,andy.smith}@tvu.ac.uk
Keywords: agile, software, development, localization, internationalization.
1 Introduction Adapting software for different languages is required to gain market access by increasing product acceptance and usability, and satisfying legal requirements. This process commonly consists of two steps: Internationalization, i.e. the generalization of any language- and culture-specific properties and elements of the software in question, and localization, i.e. the specialization of said elements for specific languages, cultures and countries [1]. It is a topic with increasing relevance as new technologies enable new software uses and interaction modes, which in turn create new cultural dependencies which need to be localized, and new ways to do it, e.g. crowdsourcing [2] and machine translation [3]. Technical challenges in localization, e.g. display of foreign characters [4], have been examined within the academic community. The relationship between localization and software development processes has been mostly absent in research [5]. In practice, localization is often separated from development [6], resulting in serious issues [7] particularly in agile development. An example is the practice of simshipping, an occupational slogan for releasing all language versions of a product simultaneously [8]: this might require localization to start before development is finished, increasing the risk of unlocalized late changes. Alternatively, localization might be positioned within development [9] and an adaption for iterative methodologies has been considered [10]. However, the requirements of agile development [11] can be in conflict with the holistic model of localizers [12]. Localization is time-consuming, expensive [13] and often done by external partners who have little access to the developers and rely on documentation and formalized processes. This is in contrast with minimal documentation and on-site presence cultivated in agile methods. * **
Student. Supervisors.
A. Sillitti et al. (Eds.): XP 2011, LNBIP 77, pp. 320–321, 2011. © Springer-Verlag Berlin Heidelberg 2011
Lost in Agility? Approaching Software Localization in Agile Software Development
321
2 Software Localization in Agile Software Development Our research aims to create a scientific model for applied software development by correlating theoretical predictions and practical findings. This will be used to deduce recommendations that will help developers improve their localization practices in agile projects. We will examine applied agile development and software localization by conducting case studies in situ, e.g. observing planning, execution and evaluation meetings. This will incorporate qualitative and quantitative data gathering and analysis in a mixed-methods approach and will be complemented by surveys, interviews and focus group sessions. Our interest lies in processes, concepts and experiences of teams developing localized software using agile methodologies. We intend to confirm issues predicted by previous experience, literature and theory, and gain a firm understanding how development methodologies are related to effort and product quality. Further research aims to produce recommendations to facilitate localization in agile development, e.g. tool usage such as translation memory systems or machine translation, a collection of guidelines for interface design and software architecture, or templates for processes and organization.
References 1. Carey, J.M.: Creating global software: a conspectus and review. Interacting with Computers 9, 449–465 (1998) 2. Garcia, I., Stevenson, V.: Translation trends and the social web. MultiLingual 20, 28–31 (2009) 3. Yunker, J.: The end of translation as we know it. MultiLingual 19, 30–31 (2008) 4. Dr. International: Developing Internatinonal Software. Microsoft Press, Redmond (2003) 5. Stanley, J.W., Speights, W.S.: Website localization. In: Proceedings of the 17th Annual International Conference on Computer Documentation, pp. 127–130. ACM, New Orleans (1999) 6. Esselink, B.: A practical guide to localization. John Benjamins Pub. Co., Philadelphia (2000) 7. Caesar, M., Fehrenbach, C.: Management von Lokalisierungsprojekten. In: Reineke, D., Schmitz, K.-D. (eds.) Einführung in die Softwarelokalisierung, pp. 27–38. Narr, Tübingen (2005) 8. Kahler, T.: Projektmanagement in der Softwarelokalisierung: Eine Einführung. In: Schmitz, K.-D., Wahle, K. (eds.) Softwarelokalisierung, pp. 11–19. Stauffenburg, Tübingen (2000) 9. Ciarlone, L.: Evolving global product content practices. MultiLingual 20, 50–52 (2009) 10. Trillaud, S.: Content management consultancy for MLVs. MultiLingual 20, 34–38 (2009) 11. Turk, D., France, R., Rumpe, B.: Limitations of Agile Software Processes. In: Third International Conference on Extreme Programming and Agile Processes in Software Engineering, Alghero, Sardinia, Italy, pp. 43–46 (2002) 12. Hogan, J.M., Ho-Stuart, C., Pham, B.: Key Challenges in Software Internationalisation. In: Hogan, J., Montague, P., Purvis, M., Steketee, C. (eds.) Proceedings of the Second Workshop on Australasian Information Security, Data Mining and Web Intelligence, and Software Internationalisation, vol. 32, pp. 187–194. Australian Computer Society, Inc., Dunedin (2004) 13. Ryan, L., Anastasiou, D., Cleary, Y.: Using Content Development Guidelines to Reduce the Cost of Localising Digital Content. Localisation Focus 8, 11–28 (2009)
