Skip to end of banner
Go to start of banner

2022-03-30 ERM Weekly Delivery Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2022-03-23 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities




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-1986 - Getting issue details... STATUS / ERM-1989 - Getting issue details... STATUS
    • Progress / Impediments: NA
    • TODO
      • Refactoring, eg, variable names
      • Styling
      • Tests
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: COP Wednesday
  • ERM-2045 - Getting issue details... STATUS
    • Progress / Impediments
      • Migrations done and working
    • TODO:
      • Test via Curl 
      • Add value for lifecycleStatus
      • Add array for packagDescriptionUrls
      • Add for new view for domain class
    • New unknowns: NA
    • Help or input needed
    • ETA for review: Thu am Mon pm
  • ERM-2044 - Getting issue details... STATUS / ERM-778 - Getting issue details... STATUS  
    • Progress / Impediments
      • all code written in stripes-kint-components
      • requires ERM-2058
    • TODO: 
    • New unknowns
    • Help or input needed
    • ETA for review

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

  • ERM-2067 - Getting issue details... STATUS
    • Blocking conditions
    • Action needed
  • ERM-2062 - Getting issue details... STATUS
    • Blocking conditions
    • Action needed

Needs Elaboration

  • ERM-2046 - Getting issue details... STATUS
    • Who / When:
      • to discuss with Martina on 30 Mar
    • ETA Ready for Dev: 
    • Who / When: NA
    • ETA Ready for Dev: Sprint 137
  • ERM-2059 - Getting issue details... STATUS
    • Who / When: NA
    • ETA Ready for Dev: Sprint 137

Sprint Backlog - Next Up

  • ERM-2048 - Getting issue details... STATUS
  • ERM-2068 - Getting issue details... STATUS
  • Claudia: 
    • ERM-1313 - Getting issue details... STATUS
    • Pair on licenses for ERM-2048, ERM-778, ERM-2044
  • Ethan:
    • ERM-1850 - Getting issue details... STATUS ?
  • Monireh: 
  • Peter:  
    • ERM-2059 - Getting issue details... STATUS
      • OAI to package schema to package ingest
      • will need adding to package schema
      • then grab from pacjage ingest




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

  • RTL

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

Closed: Lotus Hotfix 1

  • NA

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

<10 mins

AOB


New Issues

Added to sprint

  • ERM-2062 - Getting issue details... STATUS
    • In Triage - not seen on snapshot
    • blocked by ERM-2067
  • ERM-2066 - Getting issue details... STATUS
    • fix in stripes-connect is disproportionate to refactor with react query
    • to be reviewed after others
    • would want to replace separately for agreement (line)s initially to make sure it worked
      • requires untangling from existing setup
    • maybe half a sprint to do properly
    • medium priority for Morning Glory
  • ERM-2067 - Getting issue details... STATUS
    • highest priority of incoming bugs
    • blocked by STCOM-931
  • ERM-2063 - Getting issue details... STATUS
    • Needs some triage
  • ERM-2065 - Getting issue details... STATUS

Not added to sprint

Other

  • ERM-1958 - Getting issue details... STATUS
    • changes made to PR
    • pending acceptance by Orgs team


  • No labels