/
2022-08-31 ERM Weekly Delivery Update

2022-08-31 ERM Weekly Delivery Update

Aug 31, 2022

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2022-08-24 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Owen Stephens
  • Monireh Rasouli
  • Claudia Malzer
  • Peter Boehm
  • Gill Osguthorpe

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities

WIP 

 In Progress
  • ISSUE: 
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • 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-2288 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: Solve Errors
    • New unknowns: NA
    • Help or input needed:
      • Feedback from Ethan would be appreciated
    • ETA for review:  I won't be working on ERM full time on Wednesday an Thursday but might have time to chat and try some stuff intermittently
  • ERM-2315 - Getting issue details... STATUS
    • Progress / Impediments:
      • code changes done
    • TODO:
      • change requests for stripes-erm-components
      • test for EresourceIdentifier
      • verify code changes in UI
    • New unknowns: NA
    • Help or input needed: 
      • don’t quite understand the change request (@Ethan Freestone)
        • see Test Resources not in AOB
      • help with test needed
      • as requested in our erm dev channel I need an example e-resource
        • provided by Owen
    • ETA for review: Monday or Tuesday
  • ERM-2313 - Getting issue details... STATUS
    • Progress / Impediments: Not really started
    • TODO: All
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: Wed 6 Sep

Pending

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


 Needs Elaboration
  • ISSUE: 
    • Who / When: 
    • ETA Ready for Dev: 
  • 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

  • ERM-2314 - Getting issue details... STATUS  
    • Who / When: 
      • outstanding queries for Owen to advise upon
    • ETA Ready for Dev: ?

Sprint Backlog - Next Up

  • Claudia:  NA
  • Ethan: 
  • Monireh:  NA
  • 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

  • ERM-2214 - Getting issue details... STATUS
    • relates to translations that are coming from kint-components
    • therefore related to and being handled as part of migration of kint-components ( ERM-2316 - Getting issue details... STATUS )


Sprint Backlog -  At Risk


In Review

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


Code Review:

  • NA 

QA / UAT 

Bugfix Cycle 

  • NA



Release Candidates

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

Accepted

  • NA

Closed: Nolana R2022.3

Stories / Bugs

  • NA

RTL / Tasks

  • NA

Previously

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

Test Resources