Retrospective
Something our team did well is... 
- 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 or feel free to keep it anonymous)
- Thanks to the efforts and increased availability ofMiller, Eric (NIH/NCI) [C], we made some really excellent progress on data on-boarding, with 6 studies all being actively on-boarded side-by-side (Musk, Philip (NIH/NCI) [C])
- The Studies page is loading so much more quickly now due to the restoration of the Redis caching service, thanks Miller, Eric (NIH/NCI) [C]Â (Kuffel, Gina (NIH/NCI) [C] ) (Rana, Ambar (NIH/NCI) [C] )
- Nice collaboration between our functional teams working on the Data Retriever Service (performance caching service moving interop between IDC and TCIA out of the Interoperation microservice and into the ICDC BE service) (Kuffel, Gina (NIH/NCI) [C] )
- Thanks Stogsdill, Hannah (NIH/NCI) [C] for quick feedback on QA design fix. (Rana, Ambar (NIH/NCI) [C] )
Something that I think we need to improve for next time is... 
- List anything that we could have done better in this sprint (these comments can be anonymous)
- Having a standing weekly data on-boarding scrum between myself and Miller, Eric (NIH/NCI) [C] will greatly benefit our data on-boarding efforts compared to just ad hoc Slack messages, and hastily convened data loading sessions. In that we can plan such sessions in advance and discuss what activities are coming up and what barriers we might be facing (Musk, Philip (NIH/NCI) [C])
Something I learned about during this sprint is...
AI-based approaches on the horizon of cancer research (Kuffel, Gina (NIH/NCI) [C] )
- Pie chart configuration of Rechart library (Rana, Ambar (NIH/NCI) [C] )
- The data-loading sessions with Musk, Philip (NIH/NCI) [C]and submitters continue to be a great way to learn more about the intricacies of our data model. I've also learned a lot more about how the data loader is validating files and updating records (ex: visit creator plugin, etc.). (Miller, Eric (NIH/NCI) [C])
Actions
- Kuffel, Gina (NIH/NCI) [C] to create at task in order to bundle web fonts with our application.
- Better catalog/documentation of system changes, ie. a DevOps log
- Always reschedule standup meetings
- Be sure to update test cases if and when requirements evolve
- DevOps leads should sign off on new microservice designs
- Create an external service to cache data from external APIs (Performance Caching)
- Mukherjee, Amit (NIH/NCI) [C] to create a DevOps task to implement performance caching and polling/reporting of outages to Slack or email.
- Demos will only be on QA or Dev (QA being the preferred environment) moving forward.
- Use GitHub actions to automate things like deployments for the BE, FE
