Project Management

To be mentioned:

Workflow

For this project we implemented a scrum methodology. The team would get together where we decide our sprints, the duration of the sprint and what we want to achieve by that time frame. Our sprints usually are quite fast, usually a week where we want a number of features to be added to deployment. Where smaller implementations towards that goal happen every one or two days. Daily scrums are held at 2pm everyday unless specified otherwise from members being unable to meet. During these daily scrums pull requests, issues, clarifications and other features are discussed to enable a clean set of working code and issues for development until the next daily scrum. At the end of a sprint, code is then reviewed, refactored and explained to test. Once satisfied, a deployment version of the software is then released.

Meeting minutes

Meetings are held everyday at 2pm NZST on Zoom or Discord, discussions in-between these meetings are facilitated through Slack for help or clarification. Details of meeting minutes are at the appendices.

Task Breakdown

All team members were responsible for continuous integration and development of the project, working on all aspects of the project to fully understand the tech stack. Each team member was assigned a feature/issue to implement during the sprints.

• Assignment Code merging and reviewing was handled by members who did not work on the reviewed code. This ensured that each developer would not merge their own pull request so more errors were caught and implemented good coding practices. No scrum master was officially appointed but would switch from members depending on the clearest vision going forward.

Version Control

Our team used a feature branch workflow where new features linked to issues would be created and a branch implementing that branch would be created. The branch will then be closed once that issue is closed. All feature branches would be merged into a develop branch where branches should always be created from. Develop should always be working and without errors as all team members would be creating branches from it. Develop is merged to main once a deployable version is tested and ready.

• Commits Commits are made once a working function of a feature is completed. Commits are made locally on a local branch whenever code is implemented.
• When and what to branch (Source control architecture) Branches are created for each feature. Branches are then reviewed upon pull requests and deleted once the issue is closed.
• Branch naming conventions Naming specified in the issue section
• Commit message guideline Commit messages are specified with a prefix i.e. feat and with a meaningful commit message specifying what has been fixed or done.

Appendix

Meeting Minutes

24/03/2021 Discussed project proposal ideas, tech stack and management strategies Time spent: 2hrs 25/03/2021 Wrote the proposal and integrated research ideas into our features Time spent: 1hr 25/03/2021 1400-1500 NZST Subject: Project proposal research presentation, proposal idea finalisation and work Participants: All

26/03/2021 1445-1530 NZST Subject: Project proposal progress report and revision [Impromptu] Participants: Sunho, Wenxin, Kevin Absentee: Andy (Busy, informed)

28/03/2021 Final briefing of project proposal Participants: Andy , Wenxin, Kevin Absentee: Sunho (Busy, informed)

17:00-17:20 08/04/2021 1300-1400 NZST Subject: Project planning Participants: All

08/04/2021 1600-1700 NZST Subject: Project administration/workload discussion Participants: All Remarks: Andy to complete frontend code Sunho, Wenxin and Kevin each draw up a wireframe prototype of the app Kevin to write up project administration, plan, architecture, workflow and other guidelines/conventions on GitHub wiki Research can be done on Discord Music bots for better understanding and reference of existing technology Next meeting: Monday 12/04/2021 16:00 NZST

12/04/2021 1600-1800 NZST Subject: Project design/wireframing review Participants: All Remarks: Work on Assignment 2 before continuing with project Individual research is to be continued for better understanding the direction of coding Next meeting: Wednesday 14/04/2021 14:00 NZST

14/04/2021 1400-1500 NZST Subject: Assignment 2 Work Allocation Participants: All Next meeting: Thursday 15/04/2021 14:00 NZST

15/04/2021 1400-1500 NZST Subject: Assignment 2 Literature Summary Participants: All Next meeting: Friday 16/04/2021 14:00 NZST

16/04/2021 1800-1900 NZST Subject: Assignment 2 Finalisation Participants: All Next meeting: Tuesday 20/04/2021 18:00 NZST

20/04/2021 1800-1900 NZST Subject: Assignment 2 Work Allocation Participants: All Remarks: Merge landing page Merge develop to main Implement create room page Implement join room page Implement database Extend backend functionality Discussion about issue creation and pull requests Next meeting: Thursday 22/04/2021 18:00 NZST

22/04/2021 1800-1900 NZST Subject: Project - database merge Participants: All Remarks: Close backend branch Merge and close database branch Create merge branch for frontend Look into rebasing Complete and merge frontend before Sunday Next meeting: Sunday 25/04/2021 14:00 NZST

25/04/2021 1400-1500 NZST Subject: Project - music player implementation Participants: All Remarks: Created issues on Github for implementing music player Discussed project management strategies and Github wiki Next meeting: Monday 26/04/2021 14:00 NZST

26/04/2021 1400-1500 NZST Subject: Project - music player sprint scrum 1 Participants: All Remarks: Discussed file structuring Work allocation Set goals to complete music player by the end of week Next meeting: Tuesday 27/04/2021 14:00 NZST

27/04/2021 1400-1500 NZST Subject: Project - music player sprint scrum 2 Participants: All Remarks: Pull request #29, #30 Next meeting: Wednesday 28/04/2021 14:00 NZST

28/04/2021 1400-1500 NZST Subject: Project - music player sprint scrum 3 Participants: All Remarks: Branch merges Future directions Next meeting: Thursday 29/04/2021 14:00 NZST

29/04/2021 1400-1600 NZST Subject: Project - music player sprint scrum 4 Participants: All Remarks: Closed issues Merged feature-search-song-and-add-to-playlist to develop Consolidated local branches Sunho: Display playlist database on UI Everyone else: socket.io Next meeting: Friday 30/04/2021 14:00 NZST

30/04/2021 1400-1600 NZST Subject: Project - socket IO Participants: All Remarks: Work on syncing player, remove ID from local storage and other issues

01/05/2021 1400-2000 NZST Subject: Project - music player sprint scrum 5 Participants: All Remarks: Work on syncing player, work on vote skip functionality

02/05/2021 1400-1600 NZST Subject: Project - music player sprint scrum 6 Participants: All Remarks: Merged update playlist UI on song ADD Merged Player queue functionality

03/05/2021 1400-1800 NZST Subject: Project - Clean up issues Participants: All Remarks: Merged copy room ID on click of room ID

04/05/2021 1400-1800 NZST Subject: Project - Clean up issues Participants: All Remarks: Merged highlight current song Merged confirm song add with modal Merged remove stale rooms

05/05/2021 1400-2100 NZST Subject: Project - Clean up issues Participants: All Remarks: Merged remove special characters to playlist Merged clean up homepage Merged redirect to homepage when out of room

06/05/2021 1400-1600 NZST Subject: Project - Clean up issues Participants: All Remarks: Merged added play duration Merged join room sync fully working

07/05/2021 1400-1600 NZST Subject: Project - Clean up issues Participants: All Remarks: Merged Vote skip fully working Merged Leave room button Merged play bar refactored

07/05/2021 1400-2100 NZST Subject: Project - refactor and documentation Participants: All Remarks: Refactoring code Documentation fleshed out more