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)
- Relieved to see that Re-Bentofication is going smoothly, huge props to Rana, Ambar (NIH/NCI) [C] for leading this effort. (Kuffel, Gina (NIH/NCI) [C] )
- Thanks to Charles and Toyo for working with me through the various integration headaches we've faced. (Eric - my @ still isn't working...)
- Team members always available to troubleshoot and resolve issues on time. (Ngu, Charles (NIH/NCI) [C] )
- Great collaboration with the dev team to solve backend integration issues. (Udosen, Toyo (NIH/NCI) [C] )
- excited to test the implemented new featuresUnknown User (podagatlapalll2)
Something that I think we need to improve for next time is... 
- List anything that we could have done better in this sprint (add your name after your comment)
- Let's make sure to let everyone know if we are reloading the databases so that QA doesn't sound any alarms. (Kuffel, Gina (NIH/NCI) [C] )
- I think we need to try and do a better job of breaking complicated user stories into technical tasks as the work evolves so that we can get a better estimation of the amount of work required to complete a feature. (Kuffel, Gina (NIH/NCI) [C]
- I need to be more attentive to the status of study file processing so that there aren't multi-day lapses in progress. (Eric)
- Regarding QA, I feel there needs to be improvement in response/resolution time regarding testing tickets. We get busy with other projects, but if necessary resolutions or feedback aren't provided, it yet again delays productivity. (Lewis, Megan (NIH/NCI) [C] )
Something I learned about during this sprint is...
- List anything you learned more about in this sprint (add your name after your comment)
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
