Sprint Meeting Minutes - GroupFourBestGroup/Assessment2 GitHub Wiki

Sprint 1 - Stand up meeting and group discussion

Each team member agreed on the communication channels that we would use which as Trello, Slack and GitHub
Each member created account for each of these channels so that we could arrange extra meetings, discuss what work needed to be done and upload any work that needed to be reviewed
Reviewed a number of different sources to find a suitable project such as GitHub and Code Triage
Need to consider what documentation is needed to highlight and identify the different information that is needed for each role
Extra meeting agreed on Wednesday out of designated time given

Made a decision on the project that the team was going to work on which is RapidJSON
Decided to try and have either: Three 2 week sprints / Six 1 week sprints
Discussed the roles of the team members here: o Designers: Ryan and Chelsey o Programmers: Kat and Marc (Kat as SCRUM Master this week) o Testers: Adam, Daryl, and David

Designers (Chelsey and Ryan)

Issues/Enhancements #671 and #810 have created UML diagrams and Use Case diagrams alongside possible fixes that can be given to the programmers and testers
Task for sprint 2 is to choose a number of issues and prioritise them in order to decide between us which one we should undertake

Programmers (Kat and Marc)

A basic fix was created for issue #849 because they had trouble understanding the code therefore it could have been improved upon
Next issue to look at and fix is #852

Testers (Adam, Daryl and David)

Carried out a primary test on the code for RapidJSON that was already present
Next task is to review the code after it has been edited to gain a better understanding of the open source code.

Unable to attend meeting but was able to catch up on messages whilst also explaining what I had done and what the next step was in creating content for trello to show the other team members what I had done so we could progress onto the next sprint

This has been added to trello to show a number of different issues and enhancements that could be chosen for the coming weeks by the designers
Stickers have also been used within trello to identify what has been accomplished and what needs to be understood more thoroughly Sprint Review for Sprint 1 (W9) (Same meeting held in W10 but held a critical reflection on what had happened in the previous sprint) Programmers – Tuesday
Unable to fully implement a fix for the issue #849 because they were unable to efficiently understand the code as they had to learn during the first sprint how to read the different files and the comments within (if they were any)

Internet was down along with the university intranet, was unable to do any work during this 2hour session but held this meeting
Everyone needs to review the Trello and Slack communications to see where changes have been made and documents have been shared.
David was not present but was updated on the situation via slack

Designers

Ryan is still developing a resolution for his issue from the last sprint as he was unable to download Microsoft Visio at home to complete his UML and use case diagrams, he will aim to complete these by the end of the week
Chelsey has completed the UML and use case diagrams for issue #836 and will be looking for another issue or enhancement that could be implemented into the software that has been chosen. These will be updated on trello and will inform other group members via slack. (I also redeveloped trello boards into a simple more visually way to understand what each team member is doing or must do for each sprint/product backlog updated)

Programmers

Kat continuing to look at issue #798 as there has been some issue understanding the code that was provided.
Marc was able to support Kat in reviewing this error and but focused more on his role as scrum master and updating trello and slack to keep the group updated on changes made.

Testers

Daryl has completed his previous tasks but is unable to begin developing new test cases as the internet is down and there is nowhere for the group to work together, aim is to have these completed in his own time
Adam has completed his previous tasks but is unsure how to progress and does not know what he should do next. Needs to have a meeting with other testers to figure out what needs to be completed.
David has completed a document that contains extensive test logs for thorough testing of code that will reach him after the programmers have made changes Advanced Software Engineering – Second meeting for Sprint 3 (W11)
Internet is now up and running, a continuation of what was discussed at the previous meeting can now be carried out
A discussion was held whether to carry out a sprint over the holidays or wait until we return (still not decided)