# Sprint 6
## 20190403: Sprint 6 Planning Meeting Minutes



Attendees: Daniel Young, Mohammed Syed, Dr. Prabakar, Dr. Rangaswami, Leo (Momentos)

Start time: 2:00pm

End time: 2:30pm

Started with a demo of the current system (simple flows from course home to the lecture pages, new breadcrumbs)

Evolved into a planning session once Leo attended, reviewing the current planned goal and going over possible next steps.

Results Below:



2nd. Course Level	1st. Lecture Level	3rd. Student Level
Overview of students - Ranking, Completion, View Date	Total view time, absolute + percentage	Ranking on view time across lectures (Course Level)
Ranking on View Time across lectures	Ranking/Sort on Student View	Ranking on view time single lecture (Lecture)
Total number of hours a given course has been watched for	Average amount of time viewed	
Timeline of activity (think of a graph x:time y:# of users watching)

Timeline of actitivity (think of a graph x:time y:# of users watching)	Number of students to comple X% (ex 80%)	

List of uses that have watched this lecture and how much of it	

Timeline of actitivity (think of a graph x:time y:# of users watching)	



Changes to make	

Add date field to view data	

Add lecture time to lecture	

low Device Usage	

v. low subtitles	

Analytics were broken down into levels (Course, Lecture, Student) and given priorities (1st-3rd). Below the levels are possible views/analysis to expose on each page. "Changes to make" referred to some code changes that would be needed to expose the data/views in the above levels.



After discussion, the velocity of the team were estimated to be 20 hours.



The product owner chose the following user stories to be done during the next sprint. They are ordered based on their priority.

ASMT-13 - Further configuration for data seeder DONE


The team members indicated their willingness to work on the following user stories.

Daniel
ASMT-13 - Further configuration for data seeder DONE

## 20190405 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
 Started work on refactoring models for new data-seeder functionality
Dates on viewData
Dates on Lectures
What is planned to be done until the next scrum meeting?
 Finish work, look up how to add default in Mongoose
What are the hurdles?
 


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?
 
## 20190408 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
 Dates properly working for Lecture/View mongo models
What is planned to be done until the next scrum meeting?
Refactoring of Seeder to use same code flow the API uses (remove redundant code for creating the objects in Mongo) 
What are the hurdles?
 


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?
 
## 20190409 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
 Converted first function (User Creation) to run with the User service instead of custom code flow
What is planned to be done until the next scrum meeting?
 Wrap head around handling async call
What are the hurdles?
 Issues with async processing of requests in User service


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?
 
## 20190410 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
 Some trial/sandbox work trying out the async keyword to handle the User service issue
What is planned to be done until the next scrum meeting?
Use async keyword with Service calls 
What are the hurdles?
 async keyword for concurrent jobs


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?

## 20190411 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
 Have User/Lecture/ViewData/Course creation all going through the proper Services, but code runs in lock-step requesting one after another (not parallelized)
What is planned to be done until the next scrum meeting?
 Use promise arrays to make requests for object concurrent
What are the hurdles?
 Learning async JS facilities for synchronous work


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?
 
## 20190412 - Daily Scrum Meeting Minutes

Attendees: Daniel Young, Mohammed Syed

Start time: 2:00pm

End time:



Daniel Young :

What was done since the last scrum meeting?
Have moved all Service calls in Seeding to use promise arrays for performance and code cleanliness 
What is planned to be done until the next scrum meeting?
Showcase/Poster preparation. 
What are the hurdles?
 


Mohammed Syed :

What was done since the last scrum meeting?
 
What is planned to be done until the next scrum meeting?
 
What are the hurdles?
 
## 20190205 - Sprint 1 Retrospective Meeting Minutes

Attendees: Daniel Young

Start time: 2:20pm

End time:



What went wrong?

Did we do a good job estimating our team's velocity?
The refactoring of the data seeder to use the proper Services to create models took longer than expected
JS learning Async issues
Did we do a good job estimating the points (time required) for each user story?
Not exactly
Refactor took longer
Model changes were simple
Did each team member work as scheduled?
Needed extra time on the weekends


What went right?

Was able to finish the story eventually


How to address the issues in the next sprint?

How to improve the process?
Leave in padding for possible learning needed for last tasks
How to improve the product?
Continue Refactoring