Skip to end of banner
Go to start of banner

2022-08-24 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 5 Next »

Meeting Details

Date

 

Time

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

Location

Video Call in

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

Goals

Participants

Apologies

  • Owen Stephens
  • Monireh Rasouli

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-2328 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • ERM-2306 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • ERM-2288 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 

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: 
    • ETA Ready for Dev: 

Sprint Backlog - Next Up

  • Claudia:  
    • ERM-2315 - Getting issue details... STATUS
      • extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
      • tweak test for getResourceIdenitifier
      • update ui-agreements to apply logic
      • add tests to eResourceIdentifier to check multiple cases
  • 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


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

Closed (No ERM Release)

  • NA
  • <10 mins

AOB


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other



  • No labels