Final SCRUM Reflection (W12)

Positive

• Roles were delegated successfully within the first two weeks, with each team member researching their roles to further develop their understanding on what they needed to do in order to contribute to the project and work as a team effectively
• All communication channels and resources were used to their full capacity and allowed team members to communicate to one another via Slack to ask questions and confirm what work they had done and uploaded this to Trello. Github was used to commit the new changes to the chosen project and review the wiki that was developed to show the schedule, sprint meeting minutes, and final scrum reflection.

Negative

• Not enough time was spent working as a team which meant daily stand up meetings were not done which meant that any questions that team members had along with the review of progress was done through Slack
• Other factors that affected the team was that there were other assessments that need to being completed alongside this project, all 4 assessments are due at the same time. Team members had to prioritise tasks that they had to complete in order to meeting certain deadlines
• Communication was disconnected because each team members role had a number of tasks that needed to be completed for each sprint and this all happened at the same time instead of following the natural order of the SCRUM methodology
• The designers were unable to detect the issues/enhancements straight away and had to search for the source of the problem which took up a large amount of time when designing and developing a suitable solution

Improvements

• If we developed the code from scratch there would have been no problems in understanding the code and the comments made by the developers. The team had to research and gather documentation to understand the code that had been developed by other users

Created by Chelsey Cox