Retrospective
Where did we improve? 
- List anything that went well in this sprint including shout out to others that went out of their way to help (add your name after your comment)
- It really seems like we are starting off very strong with the FE Refactoring Effort, nice job and keep up the good work! (Kuffel, Gina (NIH/NCI) [C]
- Frontend team adapted to the new design quickly and finished all planed tasks for this sprint, that's awesome, kudos to the team! (Ying, Ming (NIH/NCI) [C] )
- New approach for component configuration. (Rana, Ambar (NIH/NCI) [C] )
What areas still need improvement? 
- List anything that we could have done better in this sprint (add your name after your comment)
- I still see tickets that don't have story points during a sprint (Kuffel, Gina (NIH/NCI) [C] )
- I think we should try to include "Acceptance Criteria" for user stories that are very technical in nature so that there are clear expectations for the QA team (Kuffel, Gina (NIH/NCI) [C] )
- Our initial plan missed a couple of small components, and also didn't realize dependency between cart component and the table. We (I mean I) need to do better planning next time. (Ying, Ming (NIH/NCI) [C] )
- Short time for learning and applying new concepts (Rana, Ambar (NIH/NCI) [C] )
What you have learned? 
- List anything you learned about in this sprint (add your name after your comment)
- I am getting the opportunity to learn more about URIs (Unique Resource Identifiers) that are a part of the Data Repository Service (DRS) which will ultimately help us to implement an "Export Files" button to the Cancer Genomics Cloud (CGC) (Kuffel, Gina (NIH/NCI) [C] )
- Writing frameworks needs a completely different mindset from writing application. Best practice for writing application might not be best for a framework. (Ying, Ming (NIH/NCI) [C] )
- MVC pattern for configuration. (Rana, Ambar (NIH/NCI) [C] )
Actions
