2022-05-04 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: May 04, 2022
2 min read

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2022-04-27 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

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-2059 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
      • Complete schema changes
      • Changes to ingest
    • New unknowns: NA
    • Help or input needed: 
      • Testing the schema: drop tenant (to wipe agreements db), restart ingest (no need to restart vagrant), observe and make changes needed, repeat.  
    • ETA for review: Thu / Mon
  • ERM-2066 - Getting issue details... STATUS / ERM-2085 - Getting issue details... STATUS  
    • Progress:
      • Migrated all of agreements
      • Close to getting licenses ready for QA
      • Example Create Route moved over for reference
      • Added outline of parked / outstanding areas, plus QA notes on the issue
    • TODO:
      • Complete licenses changes 2-3 days + comprehensive QA (esp cross-route interactions)
      • Add constants for agreements endpoints
    • ETA for review: Mon

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

NA

  • ISSUE
    • Blocking conditions
    • Action needed

Needs Elaboration

NA

  • ERM-2046 - Getting issue details... STATUS  
    • Who / When: Owen
      • Move ERM-286 to task defining UXPROD-3591
      • Preserve ERM-2046 for ERM-287, ERM-288 and ERM-289
      • Split other subtasks into separate stories for different related subtasks
    • ETA Ready for Dev: 

Sprint Backlog - Next Up

  • Claudia:  RTL
  • Ethan:  Kiwi #3 and Lotus #1 Hotfixes and Release
  • Monireh: RTL
  • Peter:   ERM-2121 - Getting issue details... STATUS

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


In Review

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


Code Review: 

Plan:

  1. Complete 3066
  2. Clear code review 
  3. Merge 2066

Issues:

QA / UAT 

  • ERM-2060 - Getting issue details... STATUS / ERM-2076 - Getting issue details... STATUS / ERM-2046 - Getting issue details... STATUS
    • Waiting on ERM-2045 and ERM-2059
  • ERM-1850 - Getting issue details... STATUS
  • ERM-2073 - Getting issue details... STATUS
  • ERM-2079 - Getting issue details... STATUS
  • ERM-2086 - Getting issue details... STATUS

Bugfix Cycle 

  • NA



Release Candidates

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

Accepted

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

Other 

Closed (No ERM Release)

<10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • ERM-2130 - Getting issue details... STATUS
  • ERM-2132 - Getting issue details... STATUS
  • ERM-2052 through ERM-2056: Next/Previous Pagination

Other

Deprecation

  • Add /* DEPRECATED */ note to top of component
  • Add console.warn
  • Add Jira issue to remove