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)
  • Planning poker was a solid way to get the whole team involved for sprint planning (Kuffel, Gina (NIH/NCI) [C] )
  • Some extra work on the ability to view multiple files via JBrowse being completed. (Musk, Philip (NIH/NCI) [C]) 
  • The TCL01 study continuing along its suddenly accelerated path towards release; file transfer went flawlessly, and the study is now ready for formal QA testing, with a set of 5-6 study-level files being assembled by the submitters in the meantime. (Musk, Philip (NIH/NCI) [C])
  • The level of coordination on the development and review of designs for upcoming implementation work (Musk, Philip (NIH/NCI) [C])
  • Getting real time developer feedback on initial iterations of design before much investment happens allows for huge time/cost savings. Thanks Rana, Ambar (NIH/NCI) [C] Udosen, Toyo (NIH/NCI) [C]  (Stogsdill, Hannah (NIH/NCI) [C] )
  • Elastic search integration, improved performance (Rana, Ambar (NIH/NCI) [C] )

Disliked (sad)

  • List anything that we could have done better in this sprint (add your name after your comment)
  • Hoping for better communication so that we can make sure that all tickets being worked on are visible in the sprint (Kuffel, Gina (NIH/NCI) [C] )
  • Extra work on the ability to view multiple files via JBrowse being completed without any mention of that work being done, and without the user story in question being promoted up into the sprint. If you're working on something, it needs to be up on our scrum board; if it isn't, we cannot plan accordingly. (Musk, Philip (NIH/NCI) [C])
  • QA environment properties (Rana, Ambar (NIH/NCI) [C] ) 

Learned(lightbulb)

  • List anything you learned about in this sprint (add your name after your comment)
  • Learned how to set up a Python virtual environment and use Sphinx (a Python-based framework) to build and publish html to the Bento-docs repository (Kuffel, Gina (NIH/NCI) [C] )

Actions

  • Revisit the timeframes of code freeze and testing timeframes
  • Investigate the idea of a "Code Slush" prior to the actual "Code Freeze"