Skip to content

Conversation

@MasahisaSekita
Copy link
Contributor

@MasahisaSekita MasahisaSekita commented Mar 13, 2025

Description

SCRUM-127

Updated sprint 3 documentation for iteration-03.plan.md and RPM.md

Type of change

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings

Copy link
Contributor

@kevin-lann kevin-lann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation aligns well. No comments from me

- Develop custom color customization so that users can select what colors they want for different courses
- Develop a calendar interface that allows users to export and share their timetables with other users
- Develop an algorithm that allows users to compare two different timetables together

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is an algorithm but an Interface. They will select 2 timetables from a drop down and it will display the 2 timetables side to side for comparison

- Create sprint 2 documentation: iteration-plan-02, RPM, and sprint-02 review
- Update System Design Document

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be moved to the very end


- Develop a calendar interface that allows users to retrieve, add, modify, and delete timetables and events both user custom event entries and predefined course entries.
- Develop an algorithm that optimally schedules events based on user preferences and constraints.
- Develop an algorithm that emails notification its users based on upcoming timetable events
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To add on what Minh wrote, email notification also is not an algorithm

- Develop a calendar interface that allows users to retrieve, add, modify, and delete timetables and events both user custom event entries and predefined course entries.
- Develop an algorithm that optimally schedules events based on user preferences and constraints.
- Develop an algorithm that emails notification its users based on upcoming timetable events
- Develop custom color customization so that users can select what colors they want for different courses
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"colours" to make spelling of the entire document more consistent

Copy link
Contributor

@Austin-X Austin-X left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For Sprint 3, we also need Integration Test Cases (as highlighted in green from the rubric screenshot below), so you can change the Epic name from "Unit Testing" to something else like "Unit and Integration Testing" and modify all the other areas of iteration-03.plan.md and RPM.md appropriately.

image

@MasahisaSekita MasahisaSekita merged commit f8adc57 into develop Mar 20, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants