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)
- Kudos to Miller, Eric (NIH/NCI) [C] for his support and collaboration on fixing clinical data issues. (Udosen, Toyo (NIH/NCI) [C] )
- I am always impressed by how we are able to work together across functional teams to solve problems (Kuffel, Gina (NIH/NCI)
- Not much to report except that I value the in person contact we've been having this week and while its not possible to have it happen often, getting the team together in one room makes a huge difference in work morale. Would be glad to see it happen more often (Stogsdill, Hannah (NIH/NCI) [C] )
- Contribution back to bento for Dynamic query bar and help from Toyo (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)
- I'm still trying to fix the Redis issue and am wondering if this ever worked on any of the tiers. I initially misattributed this to the environment variables not being correctly set, but I guess it is something client-related in the node-redis library. Sorry if I wasted your time with investigating this Charles and Mike. (Miller, Eric (NIH/NCI) [C] ).
- Our key processes are too dependent on "human action". As much as possible we should look to automate the steps in our workflow that can be easily automated. (Udosen, Toyo (NIH/NCI) [C] )
- Trying to figure out if requirement gaps should reopen a user story or if its best to create a new user story, in most cases I am thinking the latter. It just gets complicated when a single feature has so many user stories even if organized into an epic (Kuffel, Gina )
- Unable to renew PIV card months before expiration date. Inadequate Local/manual testing (Rana, Ambar (NIH/NCI) [C] )
Something I learned about during this sprint is...
Neo4J vs. Opensearch, Lambda vs. ECS task (Kuffel, Gina (NIH/NCI) [C] )
- Common Data Elements or CDEs that are defined questions and a set of defined acceptable values that can be used to map to ontologies and controlled vocabularies (Kuffel, Gina (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
