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)
- Team collaboration Ankerso, Seni (NIH/NCI) [C]
- Like the way how thoroughly the user stories are written. The user stories are well updated without delay as/when the requirements evolve, which is very helpful for the QA team. Radhakrishnan, Gayathri (NIH/NCI) [C]
Integrating Local Find using existing service + QA design improvement after bentofication (Rana, Ambar (NIH/NCI) [C] )
- Being available for impromptu phone-calls or meetings. Communication continues to be a strong point for QA. - Megan Lewis
- The presentation to major stakeholders of the ICDC went exceedingly well. Content covered specifics of features in the last release and a summary of major accomplishments from the last 5 years. (Kuffel, Gina (NIH/NCI) [C] )
- I really appreciated the communication from @toyo as we worked together to solidify requirements for handling errors on the FE for Interop. (Kuffel, Gina (NIH/NCI) [C] )
- We are the first team within the CRDC to implement the "Export to a Cloud Resource" button, this is a pretty major accomplishment and I can really appreciate the fact that this took work from all of us, a true group effort. (Kuffel, Gina (NIH/NCI) [C] )
- ...collaborating to resolve various ongoing issues (the IDC/TCIA API errors crashing the Studies page, CGC export not fully working). - Eric
- There was maximum collaboration from the developers in troubleshooting failed deployments.
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)
- It would be great if we come up with some easier solution to publish Bento-core packages. Ankerso, Seni (NIH/NCI) [C]
I should gather adequate technical requirements before creating a ticket for GS. (Rana, Ambar (NIH/NCI) [C] )
Something I learned about during this sprint is...
- I have learned how to extend configurations to support multiple projects. And how storybook makes development/bug fixing easier by providing development playground. Ankerso, Seni (NIH/NCI) [C]
- Testing Design QA tickets are new to us. We are learning this new approach. Radhakrishnan, Gayathri (NIH/NCI) [C]
- I've mainly been testing the last several months, so this sprint I've had a refresher course in my writing of detailed test cases - Megan Lewis
- The task order for the ICDC has been extended for an additional 3 options/5 years. We will review the statement of work together as soon as I have approval to do so. (Kuffel, Gina (NIH/NCI) [C] )
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.
