Communications plan
Internal stakeholders
Development team
- Transparency and open communication
- Systematic communication, keeping specifications, guidelines, research and progress documented. Re-purposing / reuse of materials and documents created in the project.
- Progress of tasks
-
Technological decisions and common guidelines
- Main channels and frequency
-
Github: Software code and finalized specifications
- Waffle: Used for managing project backlog and assignment of tasks
-
* Used for creating specifications and other project documents collaboratively.
- Finalized versions of specifications to be stored in the Github Wiki section.
- Other project documentation is stored in Hackpad.
-
Project meetings:
* The project is organised into two-week sprints.
- Sprint planning occurs on Mondays every other week (or 1st day of sprint)
- Sprint review and sprint retrospective take place on Fridays every other week (or last day of sprint)
- for sprint planning, review and retrospective meetings are stored in Hackpad.
- Daily stand-up meetings to check the current status of tasks in each sprint. (Currently face-to-face meetings. No minutes to be written.)
- Other meetings as per needed. Minutes also to be stored in Hackpad.
-
Chat: There is also a team-internal chat for daily communications.
CEO
- Status and progress of project
-
Any issues that require involvement of management
- Main channels and frequency
-
progress
External stakeholders
Open Source community
-
x
- Main channels and frequency
-
Github, Hackpad, Twitter
API Umbrella
-
x
- Main channels and frequency
-
x
NREL
-
x
- Main channels and frequency
-
x
COSS
-
x
- Main channels and frequency
-
x
API Suomi
-
Gathering requirements? Users for usability studies? Attracting API consumers
- Main channels and frequency
-
x
API owners: Avoin data? IoT companies? Other?
-
x
- Main channels and frequency
-
x