-
Notifications
You must be signed in to change notification settings - Fork 48
User Stories
For Phase3 of the project, the team was asked to create user stories, or time estimations for specific tasks that still needed to be completed as a method of prioritization. We used planitpoker, a site which allows teams developers to independently create time estimations for numerous tasks which are then merged for a single team estimation. The time estimations we used are equivalent to an hour, with "0" being less than an hour.
We each voted on a time estimate, and then spent time discussing our reasoning for the estimate, and then coming to an agreement as a group of the best estimate. We were rather accurate with our estimates after discussion, because we mostly defaulted to the votes of the people who would be completing the story.
Story 1: Update Apiary API. We need to include calls so that our data can be accessed for our third module named "engines".
Estimated time: 1(1 - 2 hours)
Actual: 2 hours
Story 2: Scape/Update Scrape to include Engine information. Store in a new JSON. This is what the website would use for data in the engine's table.
Estimated time: 3(3 - 4 hours)
Actual: 4 hours
Story 3: Create a webpage for 3rd model. We need to make a third partial template for the engines page. This page will use the newly create Engines Json to fill it's data table.
Estimated time: 3(3 - 4 hours)
Actual: 3 hours
Story 4: Create UI for searching model attributes. We need to create a search function in our nav bar.
Estimated time: 5(5 - 6 hours)
Actual 4 hours
Story 5: Update technical report. Include PlanItPoker User Stories. Must be 5000 words.
Estimated time: 3(3 - 4 hours)
Actual 3 hours
Story 6: Create links from car models to engines and vice versa. Create a function that allows a user to navigate between the car and engines pages on the website.
Estimated time: 2(2 - 3 hours)
Actual 3 hours
Story 7: Create a page from the SWEetSpot API. We need to include a page using the SWEetSpot data about different tourist attractions and restaurants in different countries.
Estimated time: 8(8 - 9 hours)
Actual: 10 hours
Story 8: Critique SWEetSpot Website. After the deadline for IDB3, we should analyze the website to ask what they did well, what didn't they do well, etc...
Estimated time: 1(1 - 2 hours)
Actual 1 hour
Story 9: Critique our own website. This should be pretty self explanatory. Answer questions similar to the ones asked in the previous story.
Estimated time 1(1 - 2 hours)
Actual 1 hour
Story 10: Implement Search Functionality. We plan to use javascript to display our search results. The search function should also highlight the searched word/words in our results.
Estimated time: 5(5 - 6 hours)
Actual: 8 hours
Story 11: Create Class Presentation. We need to create some power point pages for our 15 minutes class presentation of our website.
Estimated time: 3(3 - 4 hours)
Actual 3 hours