2018-09-14 Team Lead Meeting notes

Date

14 Sep 2018

3.5 Release will be at the end of 111 so much (all?) of that sprint will be spent in the QA/Release process
- Sam: Concerned about multiple supplier feature in that time frame
  - Still scoping feature
  - May need to add people to get done in time
Reminder: explain tickets before demonstrating in the showcase
Reminder: update sprint goals on backlog grooming & JIRA sprint boards
Periodic Regression Testing
- MtG currently evaluating tests to remove old/unuseful tests
- Currently expected to do this every other sprint - not sure if this is realistic
  - QA Team handles this for all teams
  - Sam to discuss this on Monday
Sam would like to schedule a 3.5 scope discussion with Mary Jo and Josh, would this be helpful for anyone else to join?
- Is everyone clear on their team's scope for 3.5?
  - Sebastian: Helpful to discuss what parts of release improvement will be completed for 3.5

Mind the Gap (Sam):

Fast Parrot (Sebastian):

What is/will be the outcome from OLMIS-4886 - Getting issue details... STATUS and how does this compare to OLMIS-5302 - Getting issue details... STATUS ?
- OLMIS-5302 Deaded
- Setting Tests to Dead when not needed or handled by contract tests
- Updating tests to make sure they are still current
Priority is SBR (OLMIS-5395)
- Still working on remaining columns but easy work
- Total cost is not calculating correctly
- Approved qty is not defaulting correctly
Primary focus is on release faster, working on overall strategy with CCE service
Also working on a few bugs and tech debt

Ona (Craig/Clay): Not present

JSI (Ashraf): Not present

Wesley Brown Get firm date for 3.5 release, which sprint will be the last before the release
- The release will be at the end of Sprint 111
Wesley Brown Follow up with Craig/Clay and Ashraf regarding reminders
Wesley Brown Follow up with Ashraf about 3.5 scoping meeting
Discuss how to better introduce and give context to the work that each team is doing during the showcase