Communication Plan
The purpose of this document is to establish a plan for communication between the various stakeholders of the Faculty Tenure project.
Communication Matrix
Communication Type | Objective | Channel(s) | Frequency | Communicator | Target Audience | Deliverables | Notes |
---|---|---|---|---|---|---|---|
Development Team communication |
| as needed | Project Team |
| none | tenure-technical@lists.hawaii.edu | |
Functional Specifications | as needed | Functional Lead |
| FDS | |||
Task Definition, assignment, and tracking | as needed | Technical Lead |
| ||||
Technical Design Meetings |
| as needed | Technical Lead |
| |||
Project Team Status Meetings |
| bi-weekly | Project Team |
|
|
|
Procedure for Assigning Project Tasks
- All project tasks that are assigned to an individual will be accompanied by a JIRA ticket
- Project documentation and specifications will reside in the wiki.
- Specifications that are embedded within JIRA tickets will be transcribed into the appropriate section(s) in the wiki
Procedure for Change Requests
- All requests for changes must be made via JIRA
- Functional Lead will assess the change request and get approval from the functional team
- Upon approval, affected documentation must be updated within two (2) business days