Abstract
What is the best way to foster an environment where development teams feel like they can talk about issues openly and developers feel like they are being kept in the loop? Furthermore, how do you ensure that the cross-functional team members on an Agile team are collaborating in a way that is productive? Finally, how do you make sure that “communication overload” does not happen (too many e-mails, etc.)? This is not always easy to achieve; it may be easy to talk about in concept, but making it work is a different story.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Rights and permissions
Copyright information
© 2015 Tim Brizard
About this chapter
Cite this chapter
Brizard, T. (2015). Communication. In: Broken Agile. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1745-0_3
Download citation
DOI: https://doi.org/10.1007/978-1-4842-1745-0_3
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-1744-3
Online ISBN: 978-1-4842-1745-0
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)