Versions Compared

Version Old Version 2 New Version Current
Changes made by

Jag Goraya

Jag Goraya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2021-11-24 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Claudia

Discussion items

Time

Item

Notes

<5 minsIntroductions
Previous Actions

NA

5 mins

In Review

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

Code Review: 

  •  

QA / UAT 

  •  

Bugfix Cycle 

NA

Call Priorities
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1850
    • Peter and Ethan to collaborate after the call
    • reviewed documentation and setup vagrant in readiness
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1927
    • stripes dependency approved and merged
    • console error and test run review prior to merge
    • ready on snapshot Thursday
  • feature-s3-file-storage
    • unknowns: 
      • how to progress GBV UAT  
      • whether preliminary (regression) testing can/should be done on FOLIO hosted environments
      • whether a UI (ERM-1929) is a blocking dependency for client UAT
    • call to be scheduled with Ian Ibbotson to clarify

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

  •  
  •  

Pending

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)What action is needed to unblock, and by whom?

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1921
      • Dev sickness: progress halted
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1912
      • tested as discussed on Monday
      • comment with example left for PO - looks good
      • ready to push to code review
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1478


    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?

    Blocked

  • Are the blocking conditions still relevant? 
    •  

    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

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1904

    Needs Elaboration

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1929
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1922

    Sprint Backlog - Next Up

    • Claudia: not available
    • Monireh: 

    Sprint Backlog - to follow

    •  

    Needs Elaboration

    •  

    Blocked

      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-1479
        /
        Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-1480
    • Ethan:
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-1927
    • Peter:  
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-1937

    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  

    Backlog - to follow

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1931

    Sprint Backlog -  At Risk

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1799
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1923
        /
      Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1920
      • Ethan to refer to Steve for technical advice re Grails
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1922
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1929

    In Review

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


    Code Review: 

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1932
      • reviewed and passed on call
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1475
      /
      Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1476
      /
      Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1477
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1493

    QA / UAT 

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1886
      • no longer an issue. Closed
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1926
      • change hides some complexity for the QA
      • full testing required

    Bugfix Cycle 

    • NA



    Release Candidates

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

    Accepted 

    Closed

     

    Accepted

    New

    • NA

    Carried Over

    Waiting for new documentation to be done when ERM-1926 is posted. Will need to re-test, once 1926 is tested, so moving back to QA.

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1900
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1882
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1883
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1884

    Closed: Lotus R1 2022

    Features

    • NA

    RTL / Other Tests

    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1469
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1470
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1471
    <10 mins

    AOB


    New Issues

    Added to sprint

    • Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1478
    • Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1479
    • Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1480
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1493

    Not added to sprint

    • NA

    Other