NIH | National Cancer Institute | NCI Wiki  

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

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)
  • Communications between teams (Rana, Ambar (NIH/NCI) [C] )
  • After having a team meeting, the QA Team came up with a plan on how to efficiently go about updating test case requirements in order to improve the testing process. (Lewis, Megan (NIH/NCI) [C] )
  • Eric's sequence diagram really helped me to understand the end to end flow of the "Export to CGC" button (Kuffel, Gina (NIH/NCI) [C] )
  • Collaboration between frontend, backend and devOps (Udosen, Toyo (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 (add your name after your comment)
  • More work in bento-core-filter(Rana, Ambar (NIH/NCI) [C] )
  • There seems to have been a distinct lack of urgency over the past couple of sprints, and I feel we need to increase our collective cadence. We have two more software releases until the end of ICDC's 5 year contract period, and we have a very significant amount of ground to cover (Musk, Philip (NIH/NCI) [C]).
  • Its challenging to understand what Bento components offer out of the box. We need to build our understanding so that we can have a balance between form and design (Kuffel, Gina (NIH/NCI) [C] )
  • ...to ensure that front-end and back-end both understand workflows for certain processes (ex: file manifest transfer to SBG-CGC --> where/how the data hand-offs are occurring, which end is responsible for which task/step) prior to starting implementation. (Eric --- my @ isn't working for some reason...)

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

Actions

  • Better catalog/documentation of system changes, ie. a DevOps log
  • Always reschedule standup meetings
  • Be sure to update test cases if an when requirements evolve
  • No labels