Communication Plan

The below table contains information about the stakeholders that the project must communicate with, when the communication should take place (at any given time or event), a justification for the communication, a description of the medium/communication channel to use, an identification of/reference to the team member responsible for the communication and whether feedback is needed from the stakeholder.

The nature of the communication may be, but is not limited to, news letters, status reports and gathering of information needed by the project.

Contents	Recipient	When?	Why?	How?/Medium	Sender	Feedback needed?
Status report	The Steering Group	Every week.	To keep the project owner up to date.	Directly at the Friday meeting.	kfc	No
Status report	The Steering Group	After every iteration	To keep the project owner up to date. Greater detail than the weekly reports. Making important decisions	Meeting	kfc	Yes
Newsletter	Internal Content Owners The SB Librarians	After every iteration	To create interest about the project, and show progress. Matching of expectations. Encourage feedback and communication. Encourage general acceptance at the Library.	The intranet. alle@statsbiblioteket.dk		No
IT maintenance department coordination	The IT Staff	Ongoing communication about storage	To coordinate storage requirements and system setup.	e-mail	te, kfc	Yes
The media department	Internal Content Owners	Ongoing communication about digitization workflow system	To coordinate integratio nwith workflow systems, and to negotiate DOMS GUI	meetings	kfc	Yes
Fedora Community developer feedback	The Fedora Community	When relevant ideas or shortcomings in the Fedora system could/should be communicated	To influence Fedora development. To keep contact with prospective partners. To gain inspiration from the community	e-mail		Preferably

Legend:

Contents: Description of the contents of the communication. Could link to a Wiki template... Good idea?
Recipient: Link to project member page or stakeholder page of the recipient
When: Describe the time, date, interval or event at which the communication should take place.
Why: Describe the reason to carry out this communication.
How?/Medium: Describe how to convey this information to the recipient and the medium to use.
Sender: Link to the project member page of the person in charge of performing this communication.
Feedback needed?: Do we need feedback from the recipient of this communication?

Notes

The current upcoming communication is not yet on the list:

At some point we should make a presentation and demo of the system at a after-hours meeting
When we have internal end-user systems, we should make a training program for librarians and HelpDesk
A supervisory group will at some point follow development and advise on collections that should be ingested in DOMS

At some later stage, some communication may be moved to another table of not currently ongoing communication (a "parking lot")