NIH | National Cancer Institute | NCI Wiki  
Date

Participants

ICDC Team 


Retrospective

Liked (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)
  • Helped write an abstract with one of the ICDC researchers (Kuffel, Gina (NIH/NCI) [C] )
  • from a QA perspective - I liked having the consolidated test execution board to work from. It cut the tests in half, which allowed me to focus and spend more time on each test that remained. (Lewis, Megan (NIH/NCI) [C] )
  • Really significant progress in the on-boarding of two new studies - the ORGANOIDS01 and UC01 studies. Both look to set new land speed records for the time from the kick-off call to the study being on-boarded in full (Musk, Philip (NIH/NCI) [C])
  • Quick turnaround on the functionality whereby users will be able to download a set of example data loading files via the DMN's Available Downloads option (Musk, Philip (NIH/NCI) [C])
  • Relatively painless release process and new figma set-up for design. (Udosen, Toyo (NIH/NCI) [C] )

Disliked/Lacked/Needs Improvement (sad)

  • List anything that we could have done better in this sprint (add your name after your comment)

Learned(lightbulb)

  • List anything you learned about in this sprint (add your name after your comment)
  •  Investigated IDC & TCIA APIs and brushed up on Postman (Kuffel, Gina (NIH/NCI) [C] )
  • Learned about additional image collection data available via IDC/TCIA APIs, how to update data in a specific db node and how to shallow clone git repos to avoid copying extraneous data. (Miller, Eric (NIH/NCI) [C] )
  • Learned just how little I know about how data submitters go about getting imaging data into the TCIA and then the IDC (Musk, Philip (NIH/NCI) [C])
  • Learned how to work Figma's Comment capabilities for increased efficiency with Design QA reviews and related communication between designer and developer. (Stogsdill, Hannah (NIH/NCI) [C] )

Actions

  • Better catalog/documentation of system changes, ie. a DevOps log
  • Always reschedule standup meetings