ERM Sprint 178

Sprint Goal / Focus 

  •  

Sprint Schedule

  • Sprint: 177
  • Release: 2023.2 Poppy 
    • Sprint 178: Bugfix Release Deadline (10 Nov 2023) [FOLREL-581]
  • Release: 2024.1 Quesnalia 
    • Sprint 3 of 11 since Release Development Cycle Starts (Sprint 176) to Feature Freeze (Sprint 186: 15 Mar 2024)
    • Sprint 187: Module Release Deadline (22 Mar 2024) [FOLREL-565]
    • Sprint 189: Bugfix Release Deadline (19 Apr 2024) [FOLREL-581]

Development Meetings

  • Wed 8 Nov
  • Mon 13 Nov
  • Wed 15 Nov

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?
  • What front and back end components are affected?
  • What changes need to be made? (additions, removals or modifications)
  • What development tests need to be written?  
  • What data does the developer need to verify their work?
  • What are the known unknowns? 
  • What is needed to QA? (environment, data, scripts)

Navigation

 Sprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions





Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

(warning) - not ready

(question) - pending triage / planning


Sprint Focus


Planning Notes Template

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate



No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-3085 - Getting issue details... STATUS


ERM-2631 - Getting issue details... STATUS

  • Triage

  • Approach
    • set up new open source project in K-Int gitlab
    • new micronaut service required (not using okapi or grails)
    • set up a test instance
    • will need a different dev workflow (probably using local copy of service)
    • working title: pushkb
    • avoid storing caches of transient data
  • Components and Changes

    • Frontend: na

    • Backend: new

  • Tests / Data / Dependencies

    • Align to when GBV start testing and using pushkb endpoint
    • ERM-3048 Possible package schema changes  with endpoint changes
  • Known Unknowns

    • should be (but not clear yet) about TitleInstance Resolver
    • packageSchemaUpdater: potential conflicts when there are multiple copies of schemas in play where backwards compatibility is broken
  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia
  • Development Estimate

ERM-3078 - Getting issue details... STATUS

Ethan or Jack
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia
  • Development Estimate: <2 day

ERM-3091 - Getting issue details... STATUS  

ERM-3092 - Getting issue details... STATUS

ERM-3093 - Getting issue details... STATUS

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

ERM-2792 - Getting issue details... STATUS

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

ERM-2793 - Getting issue details... STATUS
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

ERM-3089 - Getting issue details... STATUS
  • Triage: Needed

  • Release Target: Quesnalia
  • Development Estimate: 

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2813 - Getting issue details... STATUS



Release Tasks (
Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-3094 - Getting issue details... STATUS

TBC whether this needs to be applied to Poppy as well as Quesnalia.

Depends on when refresh token rotation is introduced.







Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-3084 - Getting issue details... STATUS


ERM-3070 - Getting issue details... STATUS