Introduction

The following is the minutes recorded of the meetings conducted during the first sprint of members with the following roles

• Product Owner - Mr. Jiahao Huo
• Scrum Master - Michael De Carvalho (1852684)
• Scrum Development Team
  • Jeremy Crouch (1598024)
  • Talion Naidoo (1448771)
  • Ureeshah Moodley (1600076)
  • Yaseen Haffejee (1827555)
  • Ziyaad Ballim (1828251)
  • Fatima Daya (1620146)
  • Phoenix Krinsky (2233063)
  • Zahraa (2115850)

Sprint One

Backlog Refinement Meeting and Sprint Planning Meeting (08/04/2021)

During the first meeting with the product owner, we conducted both the sprint backlog and sprint planning meeting with the goal of forming the product backlog as well as committing the top priority PBIs to the first sprint and breaking each user story into tasks.

Backlog Refinement Meeting:

During the backlog refinement meeting several possible PBIs were mentioned, such as:

• Create a login, Registration and home page.
• Implement Linear Regression model to train data
• Implement Naive Bayes model to train data
• Create graphical model visualisations for the user to be able to interpret their data
• Allow users to adjust hyper parameters of the training models in order to influence factors such as learning rates.
• Create tutorials or instructive help buttons to guide the user to understand how the software works
• Save their models to a directory as well as load their models from that directory.

Due to the nature of the project, however, upon refinement it was decided that special types of user stories based on research, named Spikes, would be the main priority in order to first understand the problem domain in order to implement the software solution, these include researching the frameworks that would be used, basic machine learning models and their implementations as well as a basic frontend such as login and registration and so the above bulleted features would not be as important for this sprint.

Sprint Planning Meeting:

Now that the main product backlog had been refined and the main areas of importance defined, the PBIs could be committed to the first Sprint. The user stories that were constructed include:

1. Decide on a framework
2. Research backend implementation
3. Login frontend
4. Registration frontend
5. Home page frontend

Since the main items had been committed to the sprint, they could now be broken up into tasks in the following way:

Decide a framework Deciding a framework was broken down into the following tasks

1. Researching potential frameworks that would be used for python applications
2. Choose the framework

Backend Research Backend was broken down into the following tasks:

1. Research different databases
2. Refine options for the managements system
3. Naive Bayes Model Research
4. The following tasks were constructed:
5. Research existing code implementations
6. Research the theoretical model

Registration Was broken down into the following tasks:

1. Make the User interface of the registration page
2. Once registration button is pressed, the user should be moved to the login page

Login Was broken down into the following tasks:

1. Make the User interface of the Login page
2. Once login button is pressed, the user should be moved to the home page

Home Page Was broken down into the following tasks:

1. Make the User interface of the home page
2. Create the layout and elements of the home page

Sprint One Review Meeting

The user stories committed to the first sprint during the sprint planning meeting, as mentioned above, were as follows:

1. Decide on a framework
2. Research backend implementation
3. Login frontend
4. Registration frontend
5. Home page frontend

The client declared user stories "Decide on a framework" and "Research backend implementation" as complete according to the definition of done as specified by the acceptance criteria, however, regarding the login, registration and home pages, the client requested a change of colour scheme and modifications be made in the design of each page, all other acceptance criteria were passed. The redesigning of these pages were moved back to the product backlog to be committed to future sprints.

Sprint One Retrospective Meeting

The team of developers(Team IllegalSkillsException) met to discuss the results and all concerns regarding the developmental process, productivity and team collaboration during the first sprint. All relevant comments, suggestions and concerns discussed during the meeting are summarised below.

Good job, Team IllegalSkillsException! :D

It is worth mentioning the aspects of our work that we performed well in, these being:

• All team members completed the tasks they were assigned.
• All team members displayed devotion and commitment to completing their work, some member even having not slept on some nights.
• Several members collaborated well with pair-coding as well as verbally communicating for several hours at a time while working.
• Team members get along well together and can work comfortably together.

Better luck next time ;)

A few flaws and hindrances to efficiency and productivity included:

• We waited too long initially in the sprint before making good progress due to external impediments such as other university work.
• Team members did not always clearly communicate what they would be working on

Moving forward :)

• Members proposed that for future sprints we would try communicate more clearly what we plan to work on in order to reduce confusion and reduncencies.
• Members committed to working promptly on commencement of future sprints.