Date

17 Apr 2020

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

• Join Zoom Meeting

  • https://uqam.zoom.us/j/97459712262

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack 

Attendees

 Indicating note-taker

1. Andrew Woods
2. Brian Lowe
3. Matthias Lühr
4. Nicolas Dickner
5. Michel Héon
6. Alexander (Sacha) Jerabek
7.  Rachid Belkouch
8. Ralph O'Flinn

Reference

• Sprint Board - JIRA
• 2020-04 - Sprint Stand-up Reports

Agenda

1. Retrospective
   1. What went well?
   2. What went wrong?
   3. What did we learn?
   4. What should we do differently?
2. What was completed?
3. What remains to be done?
   1. When/How should we plan on completing the effort?
   2. Does the team have on-going availability?

Notes 

1. Retrospective

   1. nd:
      just got up to speed near the end, lost a few days due to easter
      better git workflow in etv
      hard to get a team together, everybody working in concert etc.

      ml:
      problems with getting testing environment up and running

      
      rb:
      learning curve is slow, first time in a sprint is a lot of overhead

      bl:
      only joined towards the end
      great to surface things from fresh eyes and testers
      incrementally testing and verify is better, so getting pull requests tested and merged as it goes along is best

      mh:
      impressed with amount of work we did
      team spirit is good
      problems with jira, git, whitespace, took more effort than anticipated, had to acclimate to structure
      need time to learn new tools, and teach tools to other team members, heavy case load and supporting team members at same time

      rof:
      wished i had more time to spend on sprint
      not much else to say

      aw:
      echo nd thoughts on team and team spirit,
      impressed with level of testing,
      good to clean up whitespace
      some process points could be improved, more clarity around test/verify/merge/iterate
      availability could have been better, more people signed up than were available
      understanding git and github, it is an ongoing practice, git is an issue that needs its own time
      making prerequisites more clear, installation should not be a barrier

2. What was completed:

aj: testing not quite finished, did not install new language, did not get around to documentation

nd: testing completed, did not get prereq. of install to document process

mh: worked on selenium test bench, automated testing is step by step, and advancing in phases. lots of work to set things up, reset/reload, results in a heavy unit test. work to separate out dependencies from language/vivo

bl: worked on language filters

3. What remains to be done?

1. When/How should we plan on completing the effort?
   1. aw: a week sprint per month?
   2. mh: we will continue work on i18n branch outside of sprint
2. Does the team have on-going availability?
   1. variable, some like mh, nd,ml have broader availabitlity, others may have more difficulty finding time in next two months or so.

Actions