Requirements had to be prioritized as so we could focus on the more important requirements early on while putting the lower requirements on the back burner. We used a simple ranking method that ranged from 1 to 10, with 1 being not important to 10 being very important. During the meetings, we simply took a vote and were asked to answer honestly. Depending on each requirement, what ranking we felt it needed. After the poll, we then took the sum of each requirement and prioritized them, with the highest score being our main focus and then moving downward to the lowest score. For further detail, refer to appendix.

The requirements were divided into three milestone releases based on the prioritization and their dependencies. Each release had a purpose with the main goal of having a fully functional application by the second release and third release being optional.

The first release of requirements focused on building a foundation for the application to be held together. The main focus of requirements revolved on getting a baseline mockup application that we could build on for future releases.

The second release is built upon the first release but with the emphasis of requirements that will include baseline functionality of core requirements. Also included are additional features that will allow the software to be more attractive and user friendly.

The third release will include stretch goals that can be discarded without losing core functionality in the event that the project gets delayed.

Table 1 - Ranking requirements method

Table 2 - Prioritization result (most important to least important)