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)
- thank you @Lewis, Megan for helping to create a new regression suite for ICDC
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)
- ...need to possibly clean up the study metadata files bucket and establish some sort of naming convention that potentially provides more details about the data being loaded. (Miller, Eric (NIH/NCI) [C])
- ...I regularly spend >50% of time on this project, yet in the past several sprints I haven't closed many tickets, tickets are rolling over into new sprints and I can't get out from under the pile. I don't know exactly what to do about this, but it doesn't look good, is frustrating and the velocity needs to improve. (Miller, Eric (NIH/NCI) [C])
Something I learned about during this sprint is...
Creating object types in Cypher Query. (Rana, Ambar (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
- Improve branch management. Need to remove old branches.
