---
# System prepended metadata

title: Sprint Retrospective Term 1 - Sprint 1

---

# Sprint Retrospective Term 1 - Sprint 1

* members in attendance:
	![selfie proof of meeting]()
	- [x] Ari
	- [x] Erich
	- [x] Leo
	- [x] Spencer
* what worked well
    * Prototyping on Figma helped us get a better understanding of what features we should focus on. Also, it helped to design the important pages and flow on our website
	* We set up our coding scaffold for the week 1 sprint and set our backend and frontend for the web application. 
	* ![post some progress screenshots]()
	* etc
* what didn't
	* We didn't make progress on accessing the Google and Microsft APIs for Drive and Calendar. However, we plan on working on this aspect this week as we build out our backend. 
	* We weren't able to build up elaborate backend scaffold and only completed the schema and models for the express app. We need more discussions and knock down what the data flow looks like exactly
* self assessment on progress
	* where are you in relation to progress towards product and milestones?
	* give an estimate of how far towards your goals you are, do you think you're on track?
	* **Ari**
	    * We were able to set up the frontend and backend. I was able to get started on the data model in the backend and realized that it will be an important part to develop. As a result, I believe that we will be focusing more as a team and individually on this going forward. We are on track but need to start coding more heavily each week.  
	* **Erich**
	    * We are still very much in the beginning discovery phase of our product, as we just have rudimentary scaffolding in place. Hopefully, we can use this upcoming week to build a working skeleton of our website, allowing flow from between pages, and utilizing our API on a basic level.
	* **Spencer**
	    * For this weekend, I added to the backend structure, creating a few basic API routes with skeleton code to be filled in later for getting and posting new `Notes`. There's still some lack of understanding on the exact API calls we need to include for our project, so the next step would be figuring that out and working on implementation.
	* **Leo**
	    * For this weekend, I set up the initial file structure and the basic backend frameowork with a listening server and connecting the server to mongo database. I think we need to work together more on knocking down the details for the exact backend data flow as much as possible in the next few days.

* lay out *each* of the following weeks till end of term with brief goals for each
	* current week: goals
	    * Develop backend and start to connect with Google and Microsoft APIs. This is important because we need to know how much we can access and what we need to access from Google and Microsoft. 
	    * Build working skeleton of front-end, to allow backend capabilities to function.
	* week #2: goals
	    * Start developing the frontend so that we can start connecting adding notes and accessing them for individual users. 
	    * Knock down the exact data flow for the backend as much as possible and set up a flow where we are able to get metadata from user, send to mongo, and retrieve that data for google api call.
	* week #3: goals, etc
	    *  Start implementing summarizer and transcription services for notes. 
	* week #4: goals, etc
	    * Start connecting with Google and Microsoft calendar APIs. Visualize upcoming calendar meetings on our webapp and connect old notes with calendar meetings 