Description

Roles

Attributes

Steps

1. Define Paths of Communication:
   
   Detail who communicates with whom on the project. Focus on eliminating project flow noise from the team members actually generating value such as developers, testers, user experience architects, and user education specialists. As much as possible, these team members should be free to work.
   
   Within work groups, team members should be free to communicate amongst themselves. This optimizes their ability to get work done.
   
   Across work groups and external to the project, communications should be channeled. This is typically done through work group leaders such as lead developers and through roles responsible for project flow such as project managers.
2. Define Means of Communication:
   
   For each channel of communication, define the acceptable means of communication such as face-to-face, instant messaging, e-mail, teleconference, video conference, net meeting, and written documents for review and feedback.
   
   Inappropriate means of communication on a defined channel should be flagged as a risk or an issue. For example, if it were decided that all design should be done through a face-to-face meeting, then design which happened through an e-mail thread because team members could not schedule time together would be considered a risk to the project and an issue for resolution.
3. Publish Communication Plan:
   
   Publish the updated iteration communication plan to the project portal.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Communication Plan			(none)

Predecessors

Type	Name	Dependency Type
	Define Iteration Roles and Responsibilities	Finish-Start
	Define Project Roles and Responsibilities	Finish-Start

Successors

Type	Name	Dependency Type
	Iteration Plan Review	Finish-Start