Recommendations for Project Management in Distributed Software Development

• Fábio Levy Siqueira USP
• Paulo Sérgio Muniz Silva USP

DOI: https://doi.org/10.5753/sbqs.2006.15599

Abstract

Traditionally the software development is executed by physically nearby personnel. However, in some situations the stakeholders are separated through time and space by reasons that vary from the necessity to reduce costs to the necessity to use high qualified workers. Considering the difficulty involved in executing the management responsibilities in this kind of projects, a set of recommendations to the project management is proposed in this work. The present work shows the theoretical bases, employed method, and case study conducted to create and analyze these recommendations.

Keywords: Recommendations, Project Management, Distributed Software Development

References

ABNT - Associação Brasileira de Normas Técnicas. (1998). NBR ISO/IEC 12207 – tecnologia de informação: processos de ciclo de vida de software. ABNT.

Bass, M. e Paulish, D. (2004). “Global Software Development Process Research at Siemens”. In: International Workshop on Global Software Development, 3., Edinburgh.

Battin, R. D., Crocker, R., Kreidler, J. e Subramanian, K. (2001). “Leveraging Resources in Global Software Development”. IEEE Software, v.18, n.2, p.70-77, March/April.

Boland, D. e Fitzgerald, B. (2004). “Transitioning from a Co-located to a Globally Distributed Software Development Team: A Case Study at Analog Devices Inc.”. In:International Workshop on Global Software Development, 3., Edinburgh.

BPMI - Business Process Management Initiative. (2004). “Business Process Modeling Notation (BPMN)”, http://www.bpmn.org. Version 1.0.

Carmel, E. (1999). Global Software Teams: Collaborating Across Borders and Time Zones. Prentice Hall.

Charbonneau, S. (2004). “Software Project Management – A Mapping Between RUP and the PMBOK”. http://www.therationaledge.com, The Rational Edge, May.

Damian, D. e Zowghi, D. (2003). “An insight into the interplay between culture, conflict and distance in globally distributed requirements negotiations”. In: Hawaii International Conference on System Sciences, 36., Hawaii.

Ebert, C. e De Neve, P. (2001). “Surviving Global Software Development”. IEEE Software, v.18, n.2, p.62-69, March/April.

Evaristo, J. R. e Scudder, R. (2000). “Geographically Distributed Project Teams: A Dimensional Analysis”. In: Hawaii International Conference on System Sciences, 33., Hawaii.

Gaeta, M. e Ritrovato, P. (2002). “Generalised Environment for Process Management in Cooperative Software Engineering”. In: Annual International Computer Software and Applications Conference, 26., Oxford.

Harrington, S. J. e Ruppel, C. P. (1999). “Telecommuting: A Test of Trust, Competing Values, and Relative Advantage”. IEEE Transactions on Professional Communication, v.42, n.4, p.223-239, December.

Hawryszkiewycz, I. T. e Gorton, I. (1996). “Distributing the Software Process”. In: Australian Software Engineering Conference, Melbourne.

Haywood, M. (1998). Managing virtual teams: practical techniques for high technology project managers. Artech House Publishers.

Haywood, M. (2000). “Working in Virtual Teams: A Tale of Two Projects and Many Cities”. IT Professional, v.2, n.2, p.58-60, March/April.

Herbsleb, J. D. e Mockus, A. (2003). “An Empirical Study of Speed and Communication in Globally Distributed Software Development”. IEEE Transactions on software engineering, v.29, n.6, p.481-494, June.

Herbsleb, J. D., Mockus, A., Finholt, T. A. e Grinter, R. E. (2000). “Distance, Dependencies, and Delay in a Global Collaboration”. In: ACM Conference on Computer Supported Cooperative Work, Philadelphia.

Herbsleb, J. e Moitra, D. (2001). “Global Software Development”. IEEE Software, v.18, n.2, p.16-20, March/April.

Karolak, D. W. (1998). Global Software Development: Managing Virtual Teams and Environment. IEEE Computer Society Press.

Kiel, L. (2003). “Experiences in Distributed Development: A Case Study”. In: International Workshop on Global Software Development, Portland.

Kobitzsch, W., Rombach, D. e Feldmann, R. L. (2001) “Outsourcing in India”. IEEE Software, v.18, n.2, p.78-86, March/April.

Kroll, P. e Kruchten, P. (2003). The Rational Unified Process Made Easy: a Practitioner’s Guide to the RUP. Addison-Wesley.

Laboratório Nacional de Astrofísica (2004). “Sobre o LNA”, http://www.lna.br/lna/lna_hist.html.

Layzell, P., Brereton, O. P. e French, A. (2000). “Supporting Collaboration in Distributed Software Engineering Teams”. In: Asia-Pacific Software Engineering Conference, 7., Singapore.

Lopes, L. T. e Audy, J. L. N. (2003). “Em busca de um modelo de referência para engenharia de requisitos em ambientes de desenvolvimento distribuído de software”. In: Workshop Em Engenharia de Requisitos, 6., Piracicaba.

Maidantchik, C. e Da Rocha, A. R. C. (2002). “Managing a Worldwide Software Process”. In: International Workshop on Global Software Development, Orlando.

Mockus, A. e Herbsleb, J. D. (2001). “Challenges of Global Software Development”. In: International Software Metrics Symposium, 7., London.

Paulk, M., Curtis, B., Chrissis, M. B. e Weber, C. V. (1993). Capability Maturity Model for Software. Technical Report CMU/SEI-93-TR-024. Carnegie Mellon Software Engineering Institute.

Project Management Institute. (2000). A guide to the project management body of knowledge (PMBOK guide). Project Management Institute.

Rational Unified Process. (2003). Version 2003.06.12.01. Rational Software Corporation.

Siqueira, F. L. e Muniz Silva, P. S. (2004). “As Características do Desenvolvimento Distribuído de Software”. In: Simpósio Brasileiro de Sistemas de Informação, Porto Alegre,.

Siqueira, F. L. e Muniz Silva, P. S. (2005). “Mapeamento da NBR ISO 12207 em Papéis da Gerência de Projetos de Software”. In: Simpósio Brasileiro de Qualidade de Software, Porto Alegre.

Zanoni, R. e Audy, J. L. N. (2003). “Project Management Model for a Physically Distributed Software Development Environment”. In: Hawaii International Conference on System Sciences, 36., Hawaii.