2021-12-01 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Dec 01, 2021

Meeting Details

Date

 

Time

9:15am ET, 2:15pm UK, 3:15pm Germany

Location

Video Call in

Previously2021-11-24 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Claudia

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-1850 - Getting issue details... STATUS
    • Peter and Ethan to collaborate after the call
    • reviewed documentation and setup vagrant in readiness
  • ERM-1927 - Getting issue details... STATUS
    • stripes dependency approved and merged
    • console error and test run review prior to merge
    • ready on snapshot Thursday
  • feature-s3-file-storage
    • unknowns: 
      • how to progress GBV UAT  
      • whether preliminary (regression) testing can/should be done on FOLIO hosted environments
      • whether a UI (ERM-1929) is a blocking dependency for client UAT
    • call to be scheduled with Ian Ibbotson to clarify

WIP 

  • What progress or impediment on previously stated actions?
  • What's left to do?
  • Any new unknowns?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • ERM-1921 - Getting issue details... STATUS
    • Dev sickness: progress halted
  • ERM-1912 - Getting issue details... STATUS
    • tested as discussed on Monday
    • comment with example left for PO - looks good
    • ready to push to code review
  • ERM-1478 - Getting issue details... STATUS

Pending

Blocked

  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?

Needs Elaboration

  • Who needs to be involved in the elaboration process? 
  • What is the timeframe for getting input?
  • When is the issue expected to be ready for development?

Sprint Backlog

  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

Needs Elaboration

Sprint Backlog - Next Up

  • Claudia: not available
  • Monireh: 
  • Ethan:
  • Peter:  

At Risk

  • What is now at risk of not being started this sprint?
  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

Sprint Backlog -  At Risk

  • ERM-1799 - Getting issue details... STATUS
  • ERM-1923 - Getting issue details... STATUS   / ERM-1920 - Getting issue details... STATUS
    • Ethan to refer to Steve for technical advice re Grails
  • ERM-1922 - Getting issue details... STATUS
  • ERM-1929 - Getting issue details... STATUS

In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review: 

  • ERM-1932 - Getting issue details... STATUS
    • reviewed and passed on call
  • ERM-1475 - Getting issue details... STATUS / ERM-1476 - Getting issue details... STATUS / ERM-1477 - Getting issue details... STATUS
  • ERM-1493 - Getting issue details... STATUS

QA / UAT 

  • ERM-1886 - Getting issue details... STATUS
    • no longer an issue. Closed
  • ERM-1926 - Getting issue details... STATUS
    • change hides some complexity for the QA
    • full testing required

Bugfix Cycle 

  • NA



Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

Accepted

New

  • NA

Carried Over

Waiting for new documentation to be done when ERM-1926 is posted. Will need to re-test, once 1926 is tested, so moving back to QA.

Closed: Lotus R1 2022

Features

  • NA

RTL / Other Tests

<10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • NA

Other