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)
- Prod release thanks to dev ops team (Rana, Ambar (NIH/NCI) [C] )
- Excellent work and support from Ngu, Charles (NIH/NCI) [C] and Mike to get the new Fargate infrastructure up and running (Kuffel, Gina (NIH/NCI) [C] )
- Congratulations to the team on ICDC 4.0, so many contributions for each member of our team. We should all feel very proud (Kuffel, Gina (NIH/NCI) [C] ).
- Prod Release: Thanks to the dev team and qa for assisting in reviewing, testing and identifying some DevOps related issue. This really helped in reducing troubleshooting time. Ngu, Charles (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)
- Lets make sure after we implement something that engineers are taking the time to review each requirement in the user story and fully reviewing functionality on dev before handing off to the QA team
- Related to the comment above this one, no more demos of new functionality on local environments, where critical flaws can be conveniently navigated around, hidden by the lack of the appropriate data, and/or simply not exposed by the higher levels of scrutiny applied by others (Musk, Philip (NIH/NCI) [C])
- I noticed that there is never any caching occurring on the Studies page, so it always takes ~10+ seconds to load (waiting for the TCIA API response). I added caching for this to interoperation 8+ months ago and am not sure why it isn't working in the environments (it works locally) - will need to investigate. I realize the data fetching service will ultimately make this obsolete, but we might as well provide the best UX possible in the meantime. (Miller, Eric (NIH/NCI) [C] )
- We need to do a better job of preventing alterations to the data from even happening, and of somehow being alerted to changes having been made. Simply stumbling into a study or 3 having vanished from the Dev tier isn't good enough (Musk, Philip (NIH/NCI) [C])
- I am going to create new manual regression suite, that will include the test cases that will cover all the functionality and the re-write the test cases if needed. (Epishina, Valentina (NIH/NCI) [C])
Something I learned about during this sprint is...
I learned how Global Search looks for content in OpenSearch in order to derive hits for the results page (Kuffel, Gina (NIH/NCI) [C]
- Something that many of us learned, unfortunately the hard and stressful way, was how easily the data on different environments can appear to have been lost, when it's actually been hidden, which is still highly problematic (Musk, Philip (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.
