Specification for next sprint page

Sprint 3 is our final sprint and as such, all of our most important/project foundation work is done. Anything left of Sprint 2 should be finished first before tasks based on user stories for Sprint 3. For Sprint 3, we have decided to focus on user stories that deal with administration and management of the database and its information.

At the top of the list, our highest priority user stories deal with the admin page and managing database info [AHH-40-41], which include creating an admin page on the website, and deleting buildings/complaints from the database. Admin control is important as it allows the admin users to make sure the data is accurate, or remove information as needed.

The next highest set of user stories on the priority list involves the collection of user (those making complaints) information and exporting that data set for ACORN use [AHH-46-47]. The client has asked for this information so that they may follow up with the complaints and provide better services to these users.

The user stories lowest on the priority list all deal with functionality that would help ACORN direct its resources, but are not as important to the client as the above user stories. These stories include the ability to filter buildings on the map by time [AHH-37], giving relevant ACORN contact info to users [AHH-89], and collecting analytic data about the website to find out which pages are popular so that ACORN [AHH-44].

A successful sprint would have at the very least, all remaining (if any) Sprint 2 tasks and Sprint 3 tasks pertaining to the top five user stories finished. An administration page must be created, which has access to the complaints database and management functionality, including the correction and deletion of data. The admin page should also have access to a user information database and the ability to export this information for future use in an organised and readable format (such as .csv).

Additional goals would be to finish tasks for the last three user stories. A time filter for the map on the website should indicate buildings with recent complaints (ex. Within the last x months). Based on the type of complaint, ACORN should also be able recommend and give relevant ACORN contact information to users either immediately after a complaint has been submitted or via user contact information given. Website analytic data (ex. Most visited pages) should be neatly organised and easily understood so that ACORN can direct its resources.