Release Planning

Before allocating user stories to each sprint, we first prioritized them by their importance of being finished and which tasks (based on the stories) would have to precede others. We then had to take into account the difficulty of each task to balance and spread the workload across the sprints.

For our current sprint, Sprint 1, we chose to allocate user stories to do with the foundations of the core features of the project - namely, getting all of the important information in a complaint to properly store in the database, and being able to display that information on a map. The product champion, Judy, has expressed that the categorization of information in the database and visual representation on the map are the most important.

For Sprint 2, we are choosing to allocate stories for features that were important, but were not foundations in the project so that they can build upon what we've finished so far. These features include filtering information (by category, building/area, time, etc.) in the database and on the map, the ability to view public complaints by users, and an admin page to manage the information in the database. These features were also expressed as important by the product champion, but build upon the foundations from Sprint 1.

We decided to include a Sprint 3 so as to organize user stories about features that are nice to have, but are non-essential to the project. These include the admin's ability to delete information, getting a user's contact information, collecting analytic information about the pages on the website, and exporting all of this information. The product champion has expressed that these features are not as important as getting the rest of the project up and running.