NIH | National Cancer Institute | NCI Wiki  

Date

Participants

ICDC Team 


Retrospective

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 or feel free to keep it annonymous)
  •  Coordination between team (Rana, Ambar (NIH/NCI) [C] )
  • Having a Frontend separate meeting which is really helpful for our team to coordinate and update each other. Thank you Ambar for setting this up Ankerso, Seni (NIH/NCI) [C] 
  • Shout out to engineers who take the initiative to bring questions and concerns up early before implementing user stories (Kuffel, Gina (NIH/NCI) [C] ).

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

  • List anything that we could have done better in this sprint (these comments can be anonymous)
  • Should have used GraphiQL tool to test the query (Rana, Ambar (NIH/NCI) [C] )
  • During the last release cycle I failed to capture a task for error handling on the frontend for the Interop service (Kuffel, Gina (NIH/NCI) [C] )
  • I don't have a solid understanding of the relationships between different types of data in ICDC (ex: cases, samples, case files, study files, etc.) and how the facet filtering should alter what is shown on the Explore dashboard. Improving this would likely help with query troubleshooting. (Eric)
  • I feel that we need a re-think of how we handle external API responses (Mukherjee, Amit (NIH/NCI) [C] ). Also, related we might want to have an automated notification mechanism to log and send responses internally/external API stakeholders.

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

  • Adding filter configuration to bento-core component (Rana, Ambar (NIH/NCI) [C] ) 
  • I learned that svg icons in Figma can sometimes have hidden layers and frames that do not allow for them to be exported properly. A quick review before signing off on a design can help! (Stogsdill, Hannah (NIH/NCI) [C] )

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