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)
- Really great Design QA of the latest Release Candidate by Stogsdill, Hannah (NIH/NCI) [C] (Kuffel, Gina (NIH/NCI) [C] )
- Nice work by Miller, Eric (NIH/NCI) [C] and Phil to work through almost all of the scheduled tasks. (Kuffel, Gina (NIH/NCI) [C] )
- Nice work by Rana, Ambar (NIH/NCI) [C] getting the backend set up and running locally; there is a lot involved in doing so (including setting up local DB/OpenSearch and loading both with data) and it's not the most intuitive process. Hopefully documentation will make this easier for others doing this in the future. (Miller, Eric (NIH/NCI) [C])
- Kudos to Rana, Ambar (NIH/NCI) [C] for the help on ICDC related bento-frontend updates.
- I like the way how User Stories are written. Requirements always clear and very detailed.(Epishina, Valentina (NIH/NCI) [C] )
- New Histogram for sample Profile (Rana, Ambar (NIH/NCI) [C] )
- Thanks Rana, Ambar (NIH/NCI) [C] for hitting the Design QA improvements and differentiating between fixable items and hard-coded Bento issues.
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)
- The CloudOne team continues to be a dependency that cannot be planned for. (Kuffel, Gina (NIH/NCI) [C] )
- Deployment hurdles in Dev and QA for design review, Using personal git deploy to work around (Rana, Ambar (NIH/NCI) [C] )
Something I learned about during this sprint is...
New Change Control Board (CCB) for Bento that is defining a path for contributing code back to the Bento Core. (Kuffel, Gina (NIH/NCI) [C]
- Learned - Setting up opensearch in local Thanks 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.
