As many critical communication events are planned (e.g., client reviews, project reviews, peer reviews), why is there still a need for unplanned communication events (e.g., request for clarification, request for change, issue resolution)?

What will be an ideal response?

There are many reasons for unplanned communication. Some of the more important ones are:
• Reduce latency: While developers could wait for the next project review to request clarification on their tasks or
on interfaces provided by other teams, this would slow down development significantly and introduce much
rework (e.g., correcting code that was developed under incorrect assumptions).
• React to unexpected events: Any system of a realistic size cannot be completely specified and understood a
priori. This results in requirements and design changes during development, which often have to be
communicated and negotiated among several stakeholders. While change processes can be set in place to manage
this communication, much unplanned and informal communication complements the formal communication
events to motivate, clarify, understand, gauge, and negotiate the underlying issues introduced by the change.
• Team building: Formal communication events are rarely conducive to a team atmosphere. It is during unplanned
and informal events that participants get know each other and form a community working towards a common
goal.