-
Notifications
You must be signed in to change notification settings - Fork 4
Communication Plan
Where | Who | Why | When |
---|---|---|---|
Piazza | Everybody | Regular Communication Channel | Always |
Communicator | Formal Communication Channel | Always |
It is the main communication channel with the customer. Customer can reach the team via the piazza website of CMPE352.
Official email account for any contact : tursu.help@gmail.com
It will be used as official inquires are needed.
Where | Who | Why | When |
---|---|---|---|
BM Lounge/Zoom | Everybody | Weekly meetings | Wednesdays 19.00-21.00 |
Everybody | Emergency Communication Channel | Always | |
Slack | Everybody | Regular Communication Channel | Always |
GitHub | Everybody | Public Discussion, Issues and Project Details | Always |
Zoom | Whoever Needs | Small group meetings about the weekly tasks | When needed |
Weekly meetings will be hold to decide on the main action items and to discuss about the progress of the project.
Zoom is used as the new platform to host out weekly meetings and small group meetings since the meetings cannot be done in person due to covid-19.
Since everybody in the team uses WhatsApp, it will be used as the emergency communication channel.
Slack will be used as the regular communication channel to discuss issues and share ideas about the project.
GitHub will be used as the main tool for tracking the project.
🏠 Home
- Requirements
- Requirements Questions
- User Scenarios and Mockups
- Use Case Diagram
- Class Diagram
- Sequence Diagram
- Project Plan
- RAM
- System Manual
- User Manual
- Tursu API Documentation
- Database Dump
- CMPE 352 Milestones
- CMPE 451 Milestones
- Backend
- Meeting #1 (13.02.2020)
- Meeting #2 (19.02.2020)
- Customer Meeting #1 (24.02.2020)
- Meeting #3 (27.02.2020)
- Meeting #4 (04.03.2020)
- Meeting #5 (11.03.2020)
- Meeting #6 (01.04.2020)
- Meeting #7 (15.04.2020)
- Meeting #8 (18.04.2020)
- Meeting #9 (29.04.2020)
- Meeting #10 (06.05.2020)
- Meeting #11 (08.05.2020)
- Meeting #12 (11.05.2020)
- Meeting #13 (18.05.2020)
- Meeting #14 (23.05.2020)
- CMPE451 - Meeting #1 (27.10.2020)
- CMPE451 - Meeting #2 (03.11.2020)
- CMPE451 - Meeting #3 (10.11.2020)
- CMPE451 - Meeting #4 (17.11.2020)
- CMPE451 - Meeting #5 (26.11.2020)
- CMPE451 - Meeting #6 (08.12.2020)
- CMPE451 - Meeting #7 (28.12.2020)
- CMPE451 - Meeting #8 (30.12.2020)
- CMPE451 - Meeting #9 (05.01.2020)
- CMPE451 - Meeting #10 (12.01.2020)
- CMPE451 - Meeting #11 (19.01.2020)
- CMPE451 - Meeting #12 (23.01.2020)
- CMPE451 - Android Meeting #1 (13.11.2020)
- CMPE451 - Android Meeting #2 (02.12.2020)
- CMPE451 - Android Meeting #3 (21.12.2020)
- CMPE451 - Android Meeting #4 (03.01.2021)
- CMPE451 - Android Meeting #5 (13.01.2021)
- CMPE451 - Backend Meeting #1 (06.11.2020)
- CMPE451 - Backend Meeting #2 (09.11.2020)
- CMPE451 - Backend Meeting #3 (16.11.2020)
- CMPE451 - Backend Meeting #4 (29.11.2020)
- CMPE451 - Backend Meeting #5 (19.12.2020)
- CMPE451 - Backend Meeting #6 (22.12.2020)
- CMPE451 - Backend Meeting #7 (05.01.2021)
- CMPE451 - Frontend Meeting #1 (08.11.2020)
- CMPE451 - Frontend Meeting #2 (14.11.2020)
- CMPE451 - Frontend Meeting #3 (01.12.2020)
- CMPE451 - Frontend Meeting #4 (17.12.2020)
- CMPE451 - Frontend Meeting #5 (24.12.2020)
- CMPE451 - Frontend Meeting #6 (07.01.2021)
- CMPE451 - Frontend Meeting #7 (14.01.2021)
- CMPE451 - Frontend Meeting #8 (22.01.2021)
- Assessment of Milestone #2