2018-09-26

  1. Want to put Tools in one place. [John: maybe 2 - deployed and non-deployed]. Examples are - config checker - config upgrade - caget - archive data grabber - ioc generator - installation and upgrade scripts.

  2. OPI Python logic should be tested, for future OPIs test logic.

  3. Change meeting lengths, planning should be 30 mins shorted and prep should be 30 minutes longer.

  4. Create a ticket to look at removing stale branches.#3620

  5. OPI should be sent to scientist for who it is being developer (added to IOCworkflow and OPI Creation)

  6. Add Readme to all submodules explaining purpose, these can link to documents in module especially for standard epics docs. This is so everyone knows what things do. It would also be good to remove old code submodules that are not needed and generate dependency lists.

  7. Finally looked at cycle problems slack channel. This is not a good method of recording these let think of something else.

  8. Friday Days and Tech Debt Days both still important if we have time in the sprint

  9. Story points, is it ok? Yes broadly it seems like a good estimation tool.

  10. Another Nicos dev? Tom said yes.