Estimated Story Points
Import more vehicle data into existing database tables
This story will consist of transferring massive amounts of car data from CSV files into a database table that was created last spring. In order to do this we will need to either create a program to expedite the process or find some way to import the data in a timely manner.
20 points
Story Completed. This story took a great deal more time that we orignally anticipated. This was due to differing information in the data we were trying to import. In order to combat this a new table in the database was created.
Add new tables into database aligned with what the mobile team adds to the app
This story is dependent on what the mobile teams are able to accomplish. We will be adding more tables into the AWS database in order to hold data for the new components added to the mobile app.
25 points
Story Completed. This story ending up consisting of adding a user login table to the database. This did not take as much time as anticipated.
Write queries in order to allow app access to database
In order for the application to access the data, SQL queries will need to be written. This will most likely done in collaboration with one of the mobile teams.
15 points
Story Completed. This story consisted of adding SQL queries to the php files on an AWS server instance. This story took more time than anticipated.
Allow user to add personal data
This story will consist of multiple parts. The first part will be researching the best way to only allow the user access to their personal information. Next, queries will have to be written in order to insert the data into a table that will be created in user story number two. This story at this point is a stretch goal.
25 points
Story Incomplete. This story was unable to be completed due to the time constraint of the semester. Steps were taken in order to allow this story to be completed in the future. These steps include creating a login table and the mobile team completing the scanning portion of the app.
Database cleanup and maintenance
Throughout the project it will be a goal of our team to always make sure the database is not getting out of hand. A few ways this can be done is by writing efficient and effective queries as well as not creating an excessive number of tables.
10 points
Story Complete. This story never became a problem due to the database being setup well.
Communication with other teams and customer
There are two mobile teams that we will be working with throughout the semester. Therefore, we will be having weekly meetings with both our customer and these other teams. It is very important that all the teams and customer are on the same page since it will directly impact the performance and efficiency of each team.
10 points
Story Complete. Communication was effective due to weekly meetings with our customer and a slack groupchat being created with the three Delta V teams.
Product Size
The current size of the project is approximately 105 story points. As a reference for how story points compare to time, the plan is that the first user story which is 20 story points will take roughly two weeks. At this point in time there are no acceptance test plans; however hopefully they will be developed down the road.
Product Effort
Each team member will work an estimated 10 hours a week on the project. Therefore, the team will put in 30 hours a week.
Defects
The project currently has no defects since it has not been officially started yet. Once defects are found this metric will be updated.