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 annonymous)
- Shout out to the Dev team for working hard to capture design details despite challenges in responsive behaviors which make consistency matching no picnic in the park. Always appreciate their patience and taking time to go over issues even if requires a brief slack chat. (Stogsdill, Hannah (NIH/NCI) [C] )
- Testing team for finding out the critical issues for the table. QA Design review also revealed issue with delete action for the table. (Rana, Ambar (NIH/NCI) [C] )
- Easy Configuration for DMN integrate to other bento app. (Rana, Ambar (NIH/NCI) [C] )
- Coordinations with different teams ICDC/Bento for the development of bento-core components (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)
- Bentofication road map was created prioritizing the existing components over the new features like LF and GS. Prioritizing new feature and backend services could have prevented prolonging of the Bentofication. (Rana, Ambar (NIH/NCI) [C] )
- Need to work on documentation more for the bento-core and DMN. (Rana, Ambar (NIH/NCI) [C] )
Something I learned about during this sprint is...
Setting up java spring-boot with graphql and neoj4 database. New features of java 17.
Actions
- 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.
