Stina Matthiesen
ABSTRACT
We report on an ethnographic study of an outsourcing global software development (GSD) setup between a Danish IT company and an Indian IT vendor developing a system to replace a legacy system for social services administration in Denmark. Physical distance and GSD collaboration issues tend to be obvious explanations for why GSD tasks fail to reach completion; however, we account for the difficulties within the technical nature of the software system task. We use the framework of information infrastructure to show how replacing a legacy system in governmental information infrastructures includes the work of tracing back to knowledge concerning law, technical specifications, as well as how information infrastructures have dynamically evolved over time. Not easily carried out in a GSD setup is the work around technical tasks that requires careful examination of mundane technical aspects, standards, and bureaucratic forms, as well as the excavation work that keeps the information infrastructure afloat.
- Abbott, P. Y. and M. R. Jones (2012). Everywhere and nowhere: nearshore software development in the context of globalisation. Eur J Inf Syst. 21(5): 529--551.Google Scholar
Cross Ref
- Avram, G., et al. (2009). Bridging, Patching and Keeping the Work Flowing: Defect Resolution in Distributed Software Development. Computer Supported Cooperative Work (CSCW). 18(5--6): 477--507. Google ScholarDigital Library
- Bennett, K. (1995). Legacy Systems: Coping with Success. IEEE Softw. 12(1): 19--23. Google ScholarDigital Library
- Bietz, M., et al. (2010). Synergizing in Cyberinfrastructure Development. Computer Supported Cooperative Work (CSCW). 19(3--4): 245--281. Google ScholarDigital Library
- Bjorn, P., et al. (2014). Global software development in a CSCW perspective. Proceedings of the companion publication of the 17th ACM conference on Computer supported cooperative work & social computing. ACM: 301--304. Google ScholarDigital Library
- Bjørn, P. and F. Kensing (2013). Special issue on information infrastructures for healthcare: The global and local relation. International Journal of Medical Informatics. 82(5): 281--282.Google ScholarCross Ref
- Boden, A., et al. (2009). Knowledge Management in Distributed Software Development Teams - Does Culture Matter? In Proc. Conference, IEEE Computer Society: 18--27. Google ScholarDigital Library
- Boden, A., et al. (2007). Coordination Practices in Distributed Software Development of Small Enterprises. In Proc. ICGSE 2007. IEEE Computer Society: 235--246. Google ScholarDigital Library
- Boden, A., et al. (2014). Articulation spaces: bridging the gap between formal and informal coordination. In Proc. CSCW 2014. ACM: 1120--1130. Google ScholarDigital Library
- Bowker, G. C. and S. L. Star (1999). Sorting Things Out: Classification and Its Consequences, MIT Press. Google ScholarDigital Library
- Cataldo, M., et al. (2008). Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity. In Proc. of the Second ACM-IEEE international symposium on Empirical software engineering and measurement. ACM: 2--11. Google ScholarDigital Library
- Cataldo, M., et al. (2006). Identification of coordination requirements: implications for the Design of collaboration and awareness tools. In Proc. CSCW 2006. ACM Press (2006). 353--362. Google ScholarDigital Library
- Christensen, L. R. and P. Bjorn (2014). Documentscape: intertextuality, sequentiality, & autonomy at work. In. Proc. CHI 2014. ACM Press (2014). 2451--2460. Google ScholarDigital Library
- Coulouris, et al. (2005). Distributed Systems: Concepts and Design (4th Edition) (International Computer Science), Addison-Wesley Longman Publishing Co., Inc. Google ScholarDigital Library
- de Souza, C. B. and D. Redmiles (2009). On The Roles of APIs in the Coordination of Collaborative Software Development. Computer Supported Cooperative Work (CSCW). 18(5--6): 445--475. Google ScholarDigital Library
- de Souza, C. R. B. and D. F. Redmiles (2011). The Awareness Network, To Whom Should I Display My Actions? And, Whose Actions Should I Monitor? Software Engineering, IEEE Transactions on. 37(3): 325--340. Google ScholarDigital Library
- Dourish, P. (2007). Seeing like an interface. In Proc. OZCHI 2007. ACM Press (2007). 1--8. Google ScholarDigital Library
- Edwards, P. N., et al. (2009). Introduction: an agenda for infrastructure studies. Journal of the Association for Information Systems. 10(5): 364--374.Google ScholarCross Ref
- Ellingsen, G., and Munkvold, G. (2007). Infrastructural arrangements for integrated care: Implementing an electronic nursing plan in a psychogeriatric ward. International journal of integrated care (7): 1--1.Google ScholarCross Ref
- Ellingsen, G. and E. Monteiro (2003). A Patchwork Planet Integration and Cooperation in Hospitals. Comput. Supported Coop. Work. 12(1): 71--95. Google ScholarDigital Library
- Esbensen, M., and Bjørn, P. (2014). Routine and standardization in Global software development. GROUP 2014. ACM. Google ScholarDigital Library
- Grinter, R. E. (2003). Recomposition: Coordinating a Web of SoftwareDependencies. Comput. Supported Coop. Work. 12(3): 297--327. Google ScholarDigital Library
- Hanseth, O. and N. Lundberg (2001). Designing Work Oriented Infrastructures. Comput. Supported Coop. Work. 10(3--4): 347--372. Google ScholarDigital Library
- Hanseth, O., et al. (1996). Developing Information Infrastructure: The Tension Between Standardization and Flexibility. Science Technology Human Values. 21(4): 407--426.Google ScholarCross Ref
- Herbsleb, J. D. (2007). Global Software Engineering: The Future of Socio-technical Coordination. 2007 Future of Software Engineering. IEEE Computer Society: 188--198. Google ScholarDigital Library
- Herbsleb, J. D., et al. (2000). Distance, dependencies, and delay in a global collaboration. In Proc. Conference, ACM: 319--328. Google ScholarDigital Library
- Hossain, E., et al. (2011). Scrum practices in global software development: a research framework. In Proc. Conference, Springer-Verlag: 88--102. Google ScholarDigital Library
- Jensen, R. E. (2014). Why closely coupled work matters in global software development. GROUP 2014. ACM. Google ScholarDigital Library
- Jensen, R. E. and P. Bjørn (2012). Divergence and Convergence in Global Software Development: Cultural Complexities as Social Worlds. From Research to Practice in the Design of Cooperative Systems: Results and Open Challenges. J. Dugdale, C. Masclet, M. A. Grasso, J.-F. Boujut and P. Hassanaly. Published, Springer London: 123--136.Google Scholar
- Khadka, R., et al. (2014). How do professionals perceive legacy systems and software modernization? In Proc. ICSE 2014. ACM Press (2014). 36--47. Google ScholarDigital Library
- Klein, H. K. and M. D. Myers (1999). A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Q. 23(1): 67--93. Google ScholarDigital Library
- Krishna, S., et al. (2004). Managing cross-cultural issues in global software outsourcing. Commun. ACM. 47(4): 62--66. Google ScholarDigital Library
- Laguna, M. A. and Y. Crespo (2013). A systematic mapping study on software product line evolution: From legacy system reengineering to product line refactoring. Sci. Comput. Program. 78(8): 1010--1034. Google ScholarDigital Library
- Luff, P., et al. (2000). Workplace Studies: Recovering Work Practice and Informing System Design, Cambridge University Press.Google ScholarCross Ref
- Matthiesen, S., et al. (2014). "Figure out how to code with the hands of others": recognizing cultural blind spots in global software development. In Proc. CSCW 2014. ACM Press (2014). 1107--1119. Google ScholarDigital Library
- Meum, T. (2013). "Lost in translation": The challenges of seamless integration in nursing practices. International Journal of Medical Informatics. 82(5): e200-e208.Google ScholarCross Ref
- Monteiro, E., et al. (2013). From Artefacts to Infrastructures. Computer Supported Cooperative Work (CSCW). 22(4--6): 575--607. Google ScholarDigital Library
- Parnas, D. L. (1972). On the criteria to be used in decomposing systems into modules. Commun. ACM. 15(12): 1053--1058. Google ScholarDigital Library
- Randall, D., et al. (2010). Fieldwork for Design: Theory and Practice, Springer. Google ScholarDigital Library
- Ribes, D. and T. A. Finholt (2009). The long now of technology infrastructure: articulating tensions in development. Journal of the Association for Information Systems. 10(5): 375--398.Google ScholarCross Ref
- Ribes, D. and C. P. Lee (2010). Sociotechnical Studies of Cyberinfrastructure and e-Research: Current Themes and Future Trajectories. Comput. Supported Coop. Work. 19(3--4): 231--244. Google ScholarDigital Library
- Schmidt, K. and L. Bannon (1992). Taking CSCW seriously. Computer Supported Cooperative Work (CSCW). 1(1--2): 7--40.Google Scholar
- Søderberg, A.-M., et al. (2013). Global Software Development: Commitment, Trust and Cultural Sensitivity in Strategic Partnerships. Journal of International Management. 19(4): 347--361.Google ScholarCross Ref
- Sommerville, I. (2007). Software Engineering, Addison-Wesley. Google ScholarDigital Library
- Souza, C. R. B. d., et al. (2004). How a good software practice thwarts collaboration: the multiple roles of APIs in software development. In Proc. SIGSOFT 2004. ACM: 221--230. Google ScholarDigital Library
- Star, S. L. (1999). The ethnography of infrastructure. American behavioral scientist. 43(3): 377--391.Google Scholar
- Star, S. L. and K. Ruhleder (1994). Steps towards an ecology of infrastructure: complex problems in design and access for large-scale collaborative systems. In Proc. CSCW 1994. ACM Press (1994). 253--264. Google ScholarDigital Library
- Walsham, G. (1995). Interpretive case studies in IS research: nature and method. European Journal of Information Systems. 4: 74--81.Google ScholarCross Ref
- Zimmerman, A. and T. A. Finholt (2007). Growing an infrastructure: the role of gateway organizations in cultivating new communities of users. In Proc. GROUP 2007. ACM Press (2007). 239--248. Google ScholarDigital Library
Index Terms
- Why Replacing Legacy Systems Is So Hard in Global Software Development: An Information Infrastructure Perspective
Recommendations
The legacy problem in government agencies: an exploratory study
dg.o '15: Proceedings of the 16th Annual International Conference on Digital Government ResearchGovernment organizations continue to be heavily reliant on legacy systems to support their business-critical functions. When practitioners embark on legacy systems replacement projects, they tend to use the legacy software's features as business ...
"Figure out how to code with the hands of others": recognizing cultural blind spots in global software development
CSCW '14: Proceedings of the 17th ACM conference on Computer supported cooperative work & social computingWe report on an ethnographic study of an outsourcing global software development (GSD) setup between an Indian IT vendor and an IT development division of a Danish bank. We investigate how the local IT development work is shaped by the global setup in ...
Global software development at siemens: experience from nine projects
ICSE '05: Proceedings of the 27th international conference on Software engineeringWe report on the experiences of Siemens Corporation in nine globally-distributed software development projects. These projects represent a range of collaboration models, from co-development to outsourcing of components to outsourcing the software for an ...
Comments