Skip to end of banner
Go to start of banner

2023-03-22 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

Version 1 Next »

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-03-15 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

  •  

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • SI-12

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-2630 - Getting issue details... STATUS
    • Progress / Impediments: 
      • Packages 
    • TODO: 
      • extend and set validation for content item schema for titles 
        • validating that nested content items cannot happen
        • can then throw exception if title not present
        • then move on to ingest
        • this unlocks manual testing and regression testing 
      • Tweak schema that is being used to interpret from TIPP
      • Add switch so harvest and push are exclusive
      • Apply changes for logging 
    • New unknowns: 
      • How to do QA on this piece?
        • Won't - wait until feature is ready (so, after ERM-2631)
      • Interpret from TIPP record what is needed, as we currently do
    • Help or input needed: 
    • ETA for review: ?
    • QA:
      • On completion: regression test harvest
      • Roll QA for this into ERM-2631
  • ERM-2064 - Getting issue details... STATUS
    • Progress / Impediments: just starting
    • TODO: 
      • convert to functional components
    • New unknowns / Help or input needed: NA
    • ETA for review: today

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

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

Allocations

  • Claudia: NA
  • Ethan: NA
  • Monireh: NA

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

Removed

  • NA

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 


Release Candidates

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

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

  • NA

Release Tasks

Closed: Orchid R2023.1 Bugfix

  • NA

Release Tasks

  • NA

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

  • BF-464 - Getting issue details... STATUS
  • ERM-2884 - Getting issue details... STATUS

Added to sprint

Not added to sprint

Other

Component Updates

  • NA

Release Planning

Testing

Security

  • No labels