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 Rana, Ambar (NIH/NCI) [C] for the help identifying the cause of the sample count discrepancy between the stats bar and samples tab. Also thanks for generally being willing to help with backend tickets. (Miller, Eric (NIH/NCI) [C])
- Thanks Kuffel, Gina (NIH/NCI) [C] and Musk, Philip (NIH/NCI) [C] for taking the time to start keeping track of study data related work on my end. (Miller, Eric (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)
- I really need to find a timeslot during which I can consistently hold our Data On-Boarding scrum call with Miller, Eric (NIH/NCI) [C], ideally with Kuffel, Gina (NIH/NCI) [C] also available. This past week's been a dismal failure in terms of having a second call to carry on where we left things as of our really productive initial call of 05-16-24.
- I need to spend some more time doing some preliminary research for more complicated tickets so I can hit the ground running once the actual sprint starts. (Miller, Eric (NIH/NCI) [C])
- I need to find time to go through all test case and label old and obsolete (Epishina, Valentina (NIH/NCI) [C] )
Something I learned about during this sprint is...
Just how useful having a weekly Data On-Boarding "scrum" call with Miller, Eric (NIH/NCI) [C] and Kuffel, Gina (NIH/NCI) [C] will be.
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
