NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page properties
Date

Participants

ICDC Team 


Retrospective

Panel
borderColor#91c89c
bgColor#f3f9f4

Something our team did well is... (smile) 

  • 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] )
  • The team handled Ambar's planned transition off ICDC development onto the BENTO refactoring effort really well (Musk, Philip (NIH/NCI) [C])
  • Getting the new function whereby end users can download a set of example data loading files coded up, tested and out in our most recent software release, despite the requirement to support the function surfaced relatively late in the release cycle. Nice work Udosen, Toyo (NIH/NCI) [C]! This new functionality is going to be really valuable to data submitters (usk, Philip (NIH/NCI) [C]
  • Despite the challenges posed by having to go through the Cloud One team, getting the embargo records for the ORAGNOIDS01 and UC01 studies out onto the ICDC's Production tier (Musk, Philip (NIH/NCI) [C])
Panel
borderColor#d04437
bgColor#fff8f7

Something that I think we need to improve for next time is... (sad)

  • 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])
Panel
borderColorblue

Something I learned about during this sprint is...(lightbulb)

  • (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