|
Size: 5000
Comment: Created by the PackagePages action.
|
← Revision 3 as of 2010-03-17 13:12:32 ⇥
Size: 5011
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| ||<style="vertical-align: top;">[:StatusReportCommunicationChecklist:Status report] ||<style="vertical-align: top;">[:StakeHolderSteeringGroup:The Steering Group] ||<style="vertical-align: top;">Every week. ||<style="vertical-align: top;">To keep the project owner up to date. ||<style="vertical-align: top;">Directly at the Friday meeting. ||<style="vertical-align: top;">["kfc"] ||<style="vertical-align: top;">No || ||<^>[:StatusReportCommunicationChecklist:Status report]||<^>[:StakeHolderSteeringGroup: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|| ||<style="vertical-align: top;">[:NewsletterCommunicationChecklist:Newsletter] ||<style="vertical-align: top;">[:StakeHolderInternalContentOwners:Internal Content Owners][[BR]][:StakeHolderTheSBLibrarians:The SB Librarians] ||<style="vertical-align: top;">After every iteration ||<style="vertical-align: top;">To create interest about the project, and show progress. Matching of expectations. Encourage feedback and communication. Encourage general acceptance at the Library. ||<style="vertical-align: top;">The intranet.[[BR]]alle@statsbiblioteket.dk ||<style="vertical-align: top;"> ||<style="vertical-align: top;">No || ||<style="vertical-align: top;">IT maintenance department coordination ||<style="vertical-align: top;">[:StakeHolderTheITStaff:The IT Staff] ||<style="vertical-align: top;">Ongoing communication about storage ||<style="vertical-align: top;">To coordinate storage requirements and system setup. ||<style="vertical-align: top;">e-mail ||<style="vertical-align: top;">["te"], ["kfc"] ||<style="vertical-align: top;">Yes || ||<style="vertical-align: top;">The media department||<style="vertical-align: top;">[:StakeHolderInternalContentOwners:Internal Content Owners] ||<style="vertical-align: top;">Ongoing communication about digitization workflow system ||<style="vertical-align: top;">To coordinate integratio nwith workflow systems, and to negotiate DOMS GUI||<style="vertical-align: top;">meetings ||<style="vertical-align: top;">["kfc"] ||<style="vertical-align: top;">Yes || ||<style="vertical-align: top;">Fedora Community developer feedback ||<style="vertical-align: top;">[:StakeHolderTheFedoraCommunity:The Fedora Community] ||<style="vertical-align: top;">When relevant ideas or shortcomings in the Fedora system could/should be communicated ||<style="vertical-align: top;">To influence Fedora development.[[BR]] To keep contact with prospective partners.[[BR]]To gain inspiration from the community ||<style="vertical-align: top;">e-mail ||<style="vertical-align: top;"> ||<style="vertical-align: top;">Preferably || |
||<style="vertical-align: top;">[[StatusReportCommunicationChecklist|Status report]] ||<style="vertical-align: top;">[[StakeHolderSteeringGroup|The Steering Group]] ||<style="vertical-align: top;">Every week. ||<style="vertical-align: top;">To keep the project owner up to date. ||<style="vertical-align: top;">Directly at the Friday meeting. ||<style="vertical-align: top;">[[kfc]] ||<style="vertical-align: top;">No || ||<^>[[StatusReportCommunicationChecklist|Status report]]||<^>[[StakeHolderSteeringGroup|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|| ||<style="vertical-align: top;">[[NewsletterCommunicationChecklist|Newsletter]] ||<style="vertical-align: top;">[[StakeHolderInternalContentOwners|Internal Content Owners]]<<BR>>[[StakeHolderTheSBLibrarians|The SB Librarians]] ||<style="vertical-align: top;">After every iteration ||<style="vertical-align: top;">To create interest about the project, and show progress. Matching of expectations. Encourage feedback and communication. Encourage general acceptance at the Library. ||<style="vertical-align: top;">The intranet.<<BR>>alle@statsbiblioteket.dk ||<style="vertical-align: top;"> ||<style="vertical-align: top;">No || ||<style="vertical-align: top;">IT maintenance department coordination ||<style="vertical-align: top;">[[StakeHolderTheITStaff|The IT Staff]] ||<style="vertical-align: top;">Ongoing communication about storage ||<style="vertical-align: top;">To coordinate storage requirements and system setup. ||<style="vertical-align: top;">e-mail ||<style="vertical-align: top;">[[te]], [[kfc]] ||<style="vertical-align: top;">Yes || ||<style="vertical-align: top;">The media department||<style="vertical-align: top;">[[StakeHolderInternalContentOwners|Internal Content Owners]] ||<style="vertical-align: top;">Ongoing communication about digitization workflow system ||<style="vertical-align: top;">To coordinate integratio nwith workflow systems, and to negotiate DOMS GUI||<style="vertical-align: top;">meetings ||<style="vertical-align: top;">[[kfc]] ||<style="vertical-align: top;">Yes || ||<style="vertical-align: top;">Fedora Community developer feedback ||<style="vertical-align: top;">[[StakeHolderTheFedoraCommunity|The Fedora Community]] ||<style="vertical-align: top;">When relevant ideas or shortcomings in the Fedora system could/should be communicated ||<style="vertical-align: top;">To influence Fedora development.<<BR>> To keep contact with prospective partners.<<BR>>To gain inspiration from the community ||<style="vertical-align: top;">e-mail ||<style="vertical-align: top;"> ||<style="vertical-align: top;">Preferably || |
| Line 26: | Line 26: |
| * When we have internal end-user systems, we should make a training program for librarians and [:StakeHolderHelpdesk:HelpDesk] | * When we have internal end-user systems, we should make a training program for librarians and [[StakeHolderHelpdesk|HelpDesk]] |
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? |
Every week. |
To keep the project owner up to date. |
Directly at the Friday meeting. |
No |
|||
After every iteration |
To keep the project owner up to date. Greater detail than the weekly reports. Making important decisions |
Meeting |
Yes |
|||
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. |
|
No |
||
IT maintenance department coordination |
Ongoing communication about storage |
To coordinate storage requirements and system setup. |
Yes |
|||
The media department |
Ongoing communication about digitization workflow system |
To coordinate integratio nwith workflow systems, and to negotiate DOMS GUI |
meetings |
Yes |
||
Fedora Community developer feedback |
When relevant ideas or shortcomings in the Fedora system could/should be communicated |
To influence Fedora development. |
|
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")