User Stories - kristinedomingo/cs373-idb GitHub Wiki

User Stories

Our user stories were defined and estimated by using PlanITPoker. The site allows us to go through each user story and anonymously vote on the potential complexity of each one of the defined stories. We were then able to talk about why we assigned our designated scores and come to some conclusion on the actual estimation after the fact. The estimations presented below are the average from 0 to 100 of our cumulative score for each individual user story. For more info on planITpoker please visit http://www.planitpoker.com/ !

A Search

Estimation: 69.3

Create the simplest possible search. Make the search return results only containing every search term. Ignore 'ors' and 'ands' included.

Design and Implement Search Result

Estimation: 31.3

Create a table-like interface in which to house the results of the search on the frontend. Display each of the model results in an organized way.

Highlight Search Results

Estimation: 81.6

Make sure to highlight by marking up the search terms in the returned search results on the backend or having the front end insert the markup for highlighting.

Case Insesitive Searching

Estimation: 4

Ensure that of the search query does not matter on our search implementation. Allow the user the freedom to search by whatever case to ensure a more optimal experience.

Connecting Frontend Search with Backend Index Searching

Estimation: 10.5

Connect the front end search functionality with the back end database index searching with an appropriate route endpoint.

Creating a Slide Deck and Visual Aid

Estimation: 30.2

Create a slide deck / visual to aid in organizing our presentation to the class with Prezi.

Loading Models Faster

Estimation: 20.2

We initially were doing client side sorting which was causing heavy loading times on our tables. Our idea is to switch the sorting to server side to speed up the process.

Updating UI to Accommodate Search

Estimation: 31.25

Our UI initially did not account for a search bar in the nav. In order to provide a better UI/UX experience we wanted to implement the search bar within the nav.

Revamping Design

Estimation: 14.5

Our initial design utilized a gradient, and we wanted to have a more "flat" and modern look.

Critique the API of another group

Estimation: 16.8

Critique the API of the group that was assigned to us. Note the positives and negatives that are found within their API.