Q: Provide a project plan showing team member responsibilities, work arrangements and any information team members will be using to coordinate their activities. You should also mention any software tools used by the team to assist project management.
We perform Agile sprint in Jira software with 2 weeks sprint, we will be holding standup meeting every 2 days.
We performed scrum to improve the capability of the team, we using Jira’s issue board to decide tasks/stories/bug tickets for the sprint, then we allow team members to take the task they confidence of.
We have a scrum master (Sam) who is in charge of writting tickets, negotiate requirement with assignee, control the overall workflow
we will be holding retrospective meeting at each ends of the sprint, we will be refined our decision making, concept learned, and share gratitude of others.
Team Member Responsibilities:
Phase 1
Lin Thit Myat Hsu: Fullstack developer. Business Analytic. Keeping meeting notes and doing revision on the report. Also records and handles team management.
Zifan Wei: Fullstack developer. API Development and Planning; Explains how the API works in the report
Tingzhuang Zhou(Sam): Product Owner, Scum Master, Fullstack developler. Explaining how interactions work with examples in the report.
Mashira Farid: Fullstack developer Explaining languages, development tools, frontend and backend tools, and libraries that are being used in this project, as well as how they will integrate into the system proper. (Some roles shared with Lin Thit Myat Hsu)
Avijit Prasad: Fullstack developer . Software Architect Github Readme repo
Co-ordination Software:
Meetings are done via Microsoft Teams. In between meetings, communication is kept with the use of Facebook Messenger.
Reports are written in Confluence, the code is hosted in GitHub and the entire thing is sorted in Jira.
To co-ordinate with the members and to make sure that we’re keeping up with agile software development practices, we use the scrum tools in Jira to keep ourselves in check.
Github Management
Initially we create branches which are independent mostly of other aspect of software like API and frontend.
We work on the branched in accordance with our tasks allotted in Jira.
Any member if wishes to suggest a change in someone else’s branch does it through raising issue in Jira.
Any merges that happens takes place in team meetings with supervision of the team leader and merge conflicts are dealt together.
Meeting Notes
3/3/2022: 8pm Meeting - Meetup before the deadline, finalizing anything that needs to be written down and assigning jobs for the deadline tomorrow.
4/3/2022: 2pm Meeting - We met and discussed what else there is needed to be written, as well as reviewing the topics to make sure everything was covered and was added to the report beforehand.
4pm Meeting - Final Quality Control meeting to check if everything was correct before we fully submitted things.
16/3/2022: Weekly meeting with tutor, we demoed the API we have to him and got advice as to how to proceed
17/3/2022: Meeting to finish off the API as much as possible.
18/3/2022: Entire-Day Meeting - Cleaning up final code and getting things done for the report