Abstract
Communication is challenging in any IT project. In distributed projects distance, timezones and cultures are thrown into the mix making it even more challenging. By focusing on getting communication to work within these constraints as opposed to ignoring them, we have seen great results among those who have taken a pragmatic yet rigorous approach to making communication work—even in distributed projects. Although a significant additional cost of distributing the effort is still there—the cost can be managed and the disadvantage of distributing a project can be reduced by applying some best practices that are emerging.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Eckstein, J. (2004). Agile software development in the large. Cambridge: Dorset House.
Eckstein, J. (2010). Agile software development with distributed teams. Cambridge: Dorset House.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Sandberg, JE., Skaar, L.A. (2010). Getting Communication Right: The Difference Between Distributed Bliss or Miss. In: Šmite, D., Moe, N., Ågerfalk, P. (eds) Agility Across Time and Space. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-12442-6_20
Download citation
DOI: https://doi.org/10.1007/978-3-642-12442-6_20
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-12441-9
Online ISBN: 978-3-642-12442-6
eBook Packages: Computer ScienceComputer Science (R0)