Communication: more guidance on good communication

[amyjko]

The article did a good job of explaining why communication is so important to software engineering, however I felt that it didn't explain enough about how to have good communication. Knowledge sharing tools was mentioned as one way to have good communication, but that section could of been a bit longer, explaining a couple more ways to have good communication. This would also help tie up the article, as I felt like it ended a bit abruptly.

This chapter on communication has been really helpful in understanding why communication is important and the risks are involved if there is not good communication within a software engineering team. One thing that is left out is a discussion of meetings in a team. Some questions I might like the chapter to answer: Are there best practices for meeting with teammates? How often should teams formally meet? What conversations and topics are best suited for meetings? On the other side, which topics are more appropriate for other methods of communication? Meetings are an integral part of team communication, and having information on how to make the most of them would be a useful addition to this chapter.