ERM Sprint 178

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:

  • Code Review: @Ethan Freestone 

  • QA:  @Owen Stephens 

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Monireh Rasouli 

  • @Jack Golding 

  • @Owen Stephens 

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

  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  

 - not in sprint

 or @ - in sprint 

- not ready

- 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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-3085

@Claudia Malzer 



https://folio-org.atlassian.net/browse/ERM-2631

@Ethan Freestone 

  • 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

https://folio-org.atlassian.net/browse/ERM-3078

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

https://folio-org.atlassian.net/browse/ERM-3091 

https://folio-org.atlassian.net/browse/ERM-3092

https://folio-org.atlassian.net/browse/ERM-3093

@Monireh Rasouli 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia

  • Development Estimate: 

https://folio-org.atlassian.net/browse/ERM-2792

@Claudia Malzer @Monireh Rasouli 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia

  • Development Estimate: 

https://folio-org.atlassian.net/browse/ERM-2793

@Monireh Rasouli 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia

  • Development Estimate: 

https://folio-org.atlassian.net/browse/ERM-3089

@Ethan Freestone 

  • Triage: Needed

  • Release Target: Quesnalia

  • Development Estimate: 

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-2813

@Monireh Rasouli 




Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-3094

@Ethan Freestone 

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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-3084

@Ethan Freestone 



https://folio-org.atlassian.net/browse/ERM-3070

@Ethan Freestone 



https://folio-org.atlassian.net/browse/ERM-3067

@Ethan Freestone 



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-3095

@Ethan Freestone 





Changes

Added

Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes

Rolled Over From Previous Sprint



Planning Notes Template

  • Current State

  • TODO

  • Development Estimate

In Development

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions



https://folio-org.atlassian.net/browse/SI-34

@Ethan Freestone 

Mostly done - needs testing once environment restored

Needs input from Steve











Sprint Backlog

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions



https://folio-org.atlassian.net/browse/ERM-3082

@Ethan Freestone 

Waiting for snapshot to be clear of ERM backlog



https://folio-org.atlassian.net/browse/ERM-3073

@Jack Golding 



Blocked

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA







In QA



Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions



https://folio-org.atlassian.net/browse/SI-41



Need to work out testing strategy

Likely defer until SI-34 is ready to QA also.



For Elaboration

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA









For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions



















Bugfix Cycle

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions