|
| 1 | +# Course Matrix |
| 2 | +## Iteration 01 |
| 3 | +- **Start date**: 02/15/2025 |
| 4 | +- **End date**: 03/07/2025 |
| 5 | + |
| 6 | +## 1. Process |
| 7 | + |
| 8 | +### 1.1 Roles & Responsibilities |
| 9 | + |
| 10 | +#### Epic 1: Scheduler |
| 11 | +**Team Members:** Austin, Minh, Thomas |
| 12 | +- Develop a calendar interface that allows users to add, modify, and delete both custom entries and predefined course entries. |
| 13 | +- Implement an algorithm that optimally schedules events based on user preferences and constraints. |
| 14 | + |
| 15 | +#### Epic 2: AI Assistant |
| 16 | +**Team Members:** Kevin, Masa |
| 17 | +- Develop an AI-powered chat interface that enables direct Q&A interactions between users and the AI. |
| 18 | +- Ensure seamless integration with the scheduling system to provide intelligent recommendations and assistance. |
| 19 | + |
| 20 | + |
| 21 | +- **Note taking & Documentation**: Minh and Thomas |
| 22 | + - Taking notes during stand-ups |
| 23 | + - Create sprint 2 documentation: iteration-plan-02, RPM, and sprint-02 review |
| 24 | + - Update System Design Document |
| 25 | + |
| 26 | +In addition to their specific roles, all team members have a collective responsibility to support and assist other team members to ensure that the goals (listed in section 2.1) are achieved and develop a working prototype. |
| 27 | + |
| 28 | +#### 1.2 Events |
| 29 | +- **Initial planning meeting**: |
| 30 | + - Location: Virtual |
| 31 | + - Time: 2/16/2025 |
| 32 | + - Purposes: |
| 33 | + - Go over the sprint 2 requirements |
| 34 | + - Define tasks and responsibilities for each team member |
| 35 | + |
| 36 | +- **Stand up meeting**: |
| 37 | + - Location: Online or in-person depending on members availability |
| 38 | + - Time: Every Tuesday from 12 pm to 1 pm, Friday and Sunday from 9 pm to 10 pm |
| 39 | + - Purposes |
| 40 | + - Progress updates: What has each member done since the last stand-up |
| 41 | + - Determine the next steps and deadlines |
| 42 | + - Discuss current blockers and possible solutions |
| 43 | + |
| 44 | +- **Final review meeting** |
| 45 | + - Location: Online |
| 46 | + - Time: 3/6/2025 |
| 47 | + - Purposes: |
| 48 | + - Review features and deliverables implemented in sprint 2 |
| 49 | + - Determine changes that need to be made in sprint 3 |
| 50 | + |
| 51 | +#### 1.3 Artifacts |
| 52 | +- Our team will track the progress through Jira |
| 53 | + - Each user story will be uploaded to Jira as a ticket: |
| 54 | + - Categorized in the backlog by its epic, and execution sprint |
| 55 | + |
| 56 | +  |
| 57 | + |
| 58 | + - Ticket details include: estimated story point to determine its priority, assignees |
| 59 | + |
| 60 | +  |
| 61 | + |
| 62 | + - Tickets of large user stories will be broken down into smaller child issues |
| 63 | + |
| 64 | +  |
| 65 | + |
| 66 | + - Each ticket will also show: |
| 67 | + - Other tickets blocked by it |
| 68 | + |
| 69 | +  |
| 70 | + |
| 71 | + - Other tickets blocking it |
| 72 | + |
| 73 | +  |
| 74 | + |
| 75 | + - Additional tasks required during the development process will also be submitted as a task ticket on JIRA for tracking. |
| 76 | + - Students or groups of students will be assigned first to epic and then to the specific user story. |
| 77 | + - Workflow |
| 78 | + |
| 79 | +  |
| 80 | + |
| 81 | +## 2. Product |
| 82 | +#### 2.1 Goal and Tasks |
| 83 | + |
| 84 | +**1. Develop product features for the product demo:** |
| 85 | + |
| 86 | + - *Account Editing*: [SCRUM-95](https://cscc01-course-matrix.atlassian.net/jira/software/projects/SCRUM/boards/1/backlog?selectedIssue=SCRUM-95) |
| 87 | + - *Account Deletion*: [SCRUM-28](https://cscc01-course-matrix.atlassian.net/jira/software/projects/SCRUM/boards/1/backlog?selectedIssue=SCRUM-28) |
| 88 | + |
| 89 | + - *Epic 1: Scheduler* |
| 90 | + - Timetable Basics/Insertion: [SCRUM-46](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-46) |
| 91 | + - Entries Update/Delete: [SCRUM-47](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-47) |
| 92 | + - Timetable Generation: [SCRUM-52](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-52) |
| 93 | + - Entries Visualization: [SCRUM-50](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-50) |
| 94 | + - Entries Colour Customization: [SCRUM-51](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-51) |
| 95 | + - Timetable Favourite: [SCRUM-57](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-57) |
| 96 | + |
| 97 | + - *Epic 2: AI Assistant* |
| 98 | + - Creation of New Chats: [SCRUM-36](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-36) |
| 99 | + - Chatlog Export/Rename/Delete: [SCRUM-37](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-37) |
| 100 | + - Course Info Retrieval: [SCRUM-29](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-29) |
| 101 | + - Program Requirements Retrieval: [SCRUM-30](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-30) |
| 102 | + |
| 103 | + |
| 104 | +**3. Create sprint2 documentation:** [SCRUM-119](https://cscc01-course-matrix.atlassian.net/browse/SCRUM-119) |
| 105 | + |
| 106 | +#### 2.2 Artifacts |
| 107 | + |
| 108 | +### Pages/Features |
| 109 | + |
| 110 | +#### Registration/Login |
| 111 | +- Dropdown menu displaying username and associated email. |
| 112 | +- Functional password reset and account deletion features. |
| 113 | + |
| 114 | +#### Scheduler |
| 115 | +- Home page for creating new timetables. |
| 116 | +- Timetable management: insertion, updating, and deletion of both course entries and custom user entries. |
| 117 | +- Algorithm for automated timetable generation. |
| 118 | +- Hover effect: calendar highlights selected course entry. |
| 119 | +- Custom colour selection for timetable entries. |
| 120 | +- Option to favourite timetables for quick access. |
| 121 | + |
| 122 | +#### AI Assistant |
| 123 | +- Functional AI chatbot interface with chat log creation, editing, and deletion. |
| 124 | +- AI retrieves relevant course information and program requirements from the course database. |
| 125 | +- AI strictly uses the internal course database without relying on external or irrelevant information. |
| 126 | + |
| 127 | + |
| 128 | + |
| 129 | + |
| 130 | + |
| 131 | + |
| 132 | + |
| 133 | + |
0 commit comments