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)
- Addessing bugs classifed as critical to our release in a very timely manner (Kuffel, Gina (NIH/NCI) [C] )
- Keeping the Release Dashboard up to date during the release cycle (Kuffel, Gina (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 (add your name after your comment)
- Making sure that the "Release Info" tab always reflects every build (big or small)
- Getting two embargo records pushed up through Stage and onto our Production environment courtesy of the Cloud One team took far too long considering the trivial nature of the records that needed to be loaded, and the simplicity of the loading task. Very much wish we could still perform these loads for ourselves, completely independently of Cloud One (Musk, Philip (NIH/NCI) [C])
Something I learned about during this sprint is...
- (add your name after your comment)
- More about the Data Repository Service (DRS) which is a generic interface to data repositories so consumers can access data in a single way regardless of how the data is stored or managed. DRS uses URIs or Uniform Resource Identifiers in API calls to their server to fetch data objects. (Kuffel, Gina (NIH/NCI) [C] )
- Finally learned how to make updates to the ICDC's static content pages. Using Visual Studio with the word wrap function turned on made viewing the rather cumbersome YAML files relatively easy (Musk, Philip (NIH/NCI) [C])
- Also learned, or at least confirmed what I expected the process by which changes to static content are promoted up through the ICDC's various environments to look like (Musk, Philip (NIH/NCI) [C])
Actions
- Better catalog/documentation of system changes, ie. a DevOps log
- Always reschedule standup meetings
