Skip to content

Sprint 1

Past due by 2 months 40% complete

In this sprint, the main feature (anonymization) as well as most of the items associated were not able to be completed. Our first mistake was splitting up the work by components within the feature. We realized that with this feature, it was very hard to divide labour by backend vs front end since front end changes are needed to test the back-end modificat…

In this sprint, the main feature (anonymization) as well as most of the items associated were not able to be completed. Our first mistake was splitting up the work by components within the feature. We realized that with this feature, it was very hard to divide labour by backend vs front end since front end changes are needed to test the back-end modifications. Further, our team made the mistake of assigning this heavy component to just one individual, Owen, who worked on this feature well over the expected number of hours per week for this course, and reached out to his teammates for help later in the sprint. Then, the rest of the team either picked up a task related to the anonymization feature (debugging, UI changes) or picked a new task to work on so we could all have made at least some progress for this sprint. In the end, we made some headway but this task is still left incomplete as of Tuesday evening. For the next sprint, our team is going to ensure that we divide work by feature as opposed to components within a feature, so that other people's work is not blocked by others progress. Furthermore, we will try to ensure that no one persons' feature requires an exorbitant amount of engineering hours to complete. Therefore, this entire feature (anonymization) will be picked back up and owned by Owen, who is confident that given the two weeks of the next sprint will be able to accomplish it.

Furthermore, since our code is left with some bugs, our team all pushed our own individual branches as prs to this github repo, but they haven't been merged. This was done so the TAs can see our progress.

Further, we had to pivot our idea from anonymity feature for all posts and replies to just quick replies. this is due to the discovery that the ui that is responsible for creating new topics and replies (with the exception of quickreplies) is handled by a third party repo.

Elements that fell through:

User Story #8: Randomize nicknames to be assigned to posts that are anonymous (eg. Positive Pony)
This user story was not successfully worked on due to its dependencies. The predicted time for the backend logic to correctly work with the front end was underestimated. Thus, the backend was not successfully integrated and any function to randomize the username would not display, the field that needed to be changed is unknown, and what variable would be the flag for whether a post is anonymous is also unknown. Hence, we decided to not implement this feature yet and pull in more people first to help fully implement the backend so it would be shown in the front end as well.

Loading