---
# System prepended metadata

title: Untitled

---

* Retrospective on Sprint #8: 
    * members in attendance:
        ![selfie proof of meeting](https://github.com/dartmouth-cs98/19f-pantri/blob/master/resources/Term2Sprint8Retrospective.jpg)
        - [x] Madison
        - [x] Max
        - [x] Mike
        - [x] Raphael
        - [x] Stephen
    * what worked well
        * We submitted the Alexa skill to the store for review! Granted, we submitted a version of the skill that isn't the most updated but passed the certification, but once we push the final version of voice to master, we can resubmit the skill as an update. Not sure if they'll approve it in time for Technigala, but at least we tried!
        * Stephen and Max had good discussions on the components they were both working on, leading to Max realizing he could structure his component a little differently so that it could be used in something Stephen was doing.
        * Madison and Max combed through the updated flows of the app in relation to confirmed items in order to pare down the number of tags so it wouldn't be overwhelming in the UI.
        * Max implemented a feature for easier tagging that is much more intuitive, smoother and prettier than the original solution. 
        * Max was able to be a rubber duck / helper for multiple group members - he helped Raphael realize a problem in his promisified calls for item confirmation.
        * Madison used his math skills to help Max write a function for a prettier UI on the home page.
    * what didn't
        * Working on the Alexa routes to the Node backend. Once those are completely fixed and bug-free, we need to really thoroughly test on the Alexa device so that we cover as many issues as possible. We didn't really thoroughly test Alexa last term, so we hope to make it as smooth as possible for demoing.
        * Although Stephen and Max had productive conversations, the use cases differ in a few key ways that make the component hard to wire in for Stephen's page.
        * Backend schemas are changing without documentation, making it hard for front-end developers to know exactly how things need to be written. 
        * Need some better consensus on who merges a PR - the writer or whoever approves it because things are going approved, but not pulled into master without people realizing it. We decided on the reviewer sounding off in the Slack and writer pressing 'merge' but sounding off as well when it's done as a sanity check for everyone.
    * self assessment on progress
        * where are you in relation to progress towards finalfinal product? 
          * give an estimate of how far towards your goals you are, do you think you're on track? 
              * We're pretty close - front-end boys believe they're pretty close to being done with the product, and we only really need to test Alexa to make it conversational and smooth for Technigala.
              * Probably by Weds or Thurs, we're gonna focus solely on testing and data flow between front-end and Alexa. 
        * lay out *each* of the following weeks till end of term with brief goals for each
          * week 9: goals
              * Polish and finish front-end product and make it presentable at Technigala
              * Thoroughly test Alexa device
              * Provide an easy-to-understand list of commands that the user can say during Technigala. This seemed a little confusing for users last term. 
