Requirements Self Evaluation - Final Remarks

Overall, we would give ourselves a Meets Expectations in this area. During Milestone 1, we had done a lot of the requirements discussion during a long planning session at the start where we listed out all the ideas and prioritized them. This was an effective method for the start of the project because it gave us a broad overview of all the ideas we had for our mod. However, it was often unclear what our main immediate objectives were. As the development progressed through Milestone 2, we found that it was better to focus on fewer high-priority requirements, document on Jira and GitHub the progress, and follow up on their progress more closely and frequently with the developers during stand-up meetings. Through Milestone 2, we found that we were able to complete a narrower set of requirements to a higher quality.

Summary of what has changed since first demo:

• Regarding documentation, we have added a lot of content in our wiki as reference
• Regarding approach for the second half of this project, the majority of tickets were created to make this mod closer to a real Minecraft experience and put the finishing touches on the Space Invaders game
• User stories were clearly documented Jira was properly used to respect the sprint timeframe

Potential Improvements

One area that we could improve upon is the addressing of bugs and issues. Luckily, we did not encounter a lot of issues that could not be fixed within our development pairs and we are a small team with good communication. However, once the mod is released to the public or if the team were to expand, we will need a more robust tracking system for bugs and issues. We are hoping to link GitHub Issues with Jira Issues so that we can easily track the original issue report (on GitHub) as well as the progress on addressing the issue (on Jira).