Evaluation of the agile scrum method


Over a 10 week period my group and I were tasked with creating a game by using C++11. As we were all going to be focusing on certain aspects of the game, we needed a method to monitor which task everyone was getting on with. Using GitHub and Codio, we documented our progress on the game and we also attended scrum meetings at the start of each project session. These meetings would usually consist of each individual presenting their current work to the other members, discussing the positive and negative points of their current work, and what they plan on achieving before the next scrum meeting. Once everyone finished delivering their work, we all signed off on which tasks we had individually completed.

Advantages of the method

A major advantage of using this method was how each member of the group could be very clear and thorough with presenting their current work. It did not take long at all for everyone to display what they were working on and how much progress they expect to make on it over the next week. This method does not require a lot of time or resources to make it work effectively which highly benefited the team. As we only had 4 hours working with each other in the same environment, this method was time-efficient as it would only take roughly 20 minutes for the scrum meeting to start and conclude. Overall, this gave us more time to work on the project which I feel was a major positive as the majority of us had never worked together before so we were able to showcase our strengths and weaknesses early on during the first scrum meeting.

Disadvantages of the method

It was somewhat difficult to pinpoint a big disadvantage of the agile scrum method as everything was benefitting us for the majority of the time, but one notable instance where we struggled was when some members were not in attendance at these meetings. We had no real way to gauge what they had done over the previous week other than viewing their recent additions on GitHub. We could get a vague idea as to what they had been working on but we would definitely gain a better understanding if there was vocal communication in person at the meetings. This method requires all members to be committed throughout to work to the best of its capabilities.


The next best methodology I feel that could work as well as the scrum method would have to be the waterfall method. This approach is sequential and with that, we could all focus on an aspect then ensure that is completed before moving on to the next stage. As the project scope is unlikely to change, the chances of this method failing has a low probability and could benefit everyone and promote better teamwork and togetherness.




Jim Bowes. 2014. Agile vs Waterfall: Comparing project management methods. [ONLINE] Available at: https://manifesto.co.uk/agile-vs-waterfall-comparing-project-management-methodologies/. [Accessed 31 March 2017].

scrumalliance. 2015. Learn About Scrum. [ONLINE] Available at: https://www.scrumalliance.org/why-scrum. [Accessed 31 March 2017].

Kelly Waters. 2007. Disadvantages of Agile Development. [ONLINE] Available at: http://www.allaboutagile.com/disadvantages-of-agile-development/. [Accessed 31 March 2017].

Segue Technologies. 2015. 8 Benefits of Agile Software Development. [ONLINE] Available at: http://www.seguetech.com/8-benefits-of-agile-software-development/. [Accessed 31 March 2017].



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s