ERM Sprint 137

ERM Sprint 137

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 137

    • Start Mon 4 Apr

    • Finish Thu 14 Apr

    • Sprint Board

    • Jira Sprint: 1216

  • Release: 2022.1 Lotus  

    • Sprint 137: Bugfix Release Deadline (8 Apr)

  • Release: 2022.2 Morning Glory  

    • Sprint 142: Module Release Deadline

      • Backend 22 June 2022

      • Frontend 24 June 2022

    • Sprint 145: Bugfix Deadline (29 July 2022)

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Claudia: reduced Mon 4 / Tue 5 Apr

  • Monireh: off 4-8 Apr

  • Peter: reduced Thu 14 Apr (on leave to 27 Apr)

  • Fri 15 Apr: Good Friday

Lead Roles:

  • Code Review: @Ethan Freestone

  • QA: @Owen Stephens 

QA Environment: folio-snapshot

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 

 

Planning Notes Template

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

Sprint Focus

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-2079

@Claudia Malzer 

  • Approach

  • Components and Changes

    • Frontend: stripes-kint-components

    • Backend: none

  • Tests / Data

  • Dependencies

    • stripes-kint-components to merge

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate: Wed

 

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

@Claudia Malzer 

  • Approach

    • test against the shape of the data, while waiting for ERM-2045 to merge

    • Peter to add shape to issue

    • Owen to add mockup to issue

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data

    • no sample data yet, but can be added

    • Peter to add details of how to PUT sample data onto issue

  • Dependencies

    • Peter to add shape to issue

  • Known Unknowns

    • Owen to add mockup

  • QA: snapshot 

  • Development Estimate: Wed

 

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

@Ethan Freestone 

  • Approach

    • tweak tags in stripes-erm-components to get better control over 

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

 

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

@Ethan Freestone 

Required for Lotus

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

    • blocking QA on ...

    • blocking merge on ERM-1066

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

 

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

@Ethan Freestone 

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

 

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

@Ethan Freestone 

  • Approach

    • to be done alongside ERM-2044 and ERM-778

  • Components and Changes

    • Frontend: stripes-kint-components

    • Backend: none

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate: 

 

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

@Owen Stephens  for wireframes

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

 

Release Tasks - Lotus Hotfix 1

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

 

 

Rolled Over From Previous Sprint

For 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/ERM-2069 / https://folio-org.atlassian.net/browse/ERM-2070 / https://folio-org.atlassian.net/browse/ERM-2071

@Ian Ibbotson (Use this one) 

For Code Review

https://folio-org.atlassian.net/browse/UXPROD-3581

https://folio-org.atlassian.net/browse/ERM-1986 / https://folio-org.atlassian.net/browse/ERM-1989

@Monireh Rasouli

Previous Estimate: 3d (end of Wed 23 Apr)

  • TODO: 

    • Draft PR in place

  • Development Estimate: 

https://folio-org.atlassian.net/browse/UXPROD-2337

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

@Claudia Malzer 

Licenses part of https://folio-org.atlassian.net/browse/ERM-778

  • deprecated error not working as expected in new (not OA) context (stripes-kint-components)

  • batch count error not working as expected - counting unset primary properties (stripes-kint-components)

  • TODO (Claudia): 

    • remove supplementary properties routes where call is not used

    • amendments routes

    • amendments should not show parent view

  • Dependencies

    • patch release fix on stripes-kint-agreements (deprecated and batch count bug) (originally ERM-1608/1607)

    • related license terms in ui-agreements (untracked) not using new custom properties from stripes-kint-components

  • Known Unknowns: none

  • Development Estimate: 0.5d / Tuesday

https://folio-org.atlassian.net/browse/UXPROD-3591

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

@Peter Böhm 

Previous Estimate: 3d (Wed 3 pm end of Wed 23 Mar)

  • Current State

    • hasMany fields expands in package.gson file

    • expansion to ermResource.gson not working

  • TODO: 

    • move expansion to ermResource.gson

    • try complete removing Set<AlternateResourceName>

    • otherwise reach out to Steve

  • Development Estimate: 

https://folio-org.atlassian.net/browse/UXPROD-3407

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

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

@Ethan Freestone 

Previous Estimate: 3d (Wed 3 pm end of Wed 28 Mar)

  • TODO: 

    • deprecation bug identified as part of licenses 

  • Development Estimate: 1d (including Batch Count)

https://folio-org.atlassian.net/browse/FAT-80

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

@Claudia Malzer  

 

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

 

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

@Peter Böhm 

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

https://folio-org.atlassian.net/browse/UXPROD-2337https://folio-org.atlassian.net/browse/ERM-778

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

@Claudia Malzer 

Ready to QA once ERM-1066 changes are merged

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

For QA

For Elaboration

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-2046

@Owen Stephens

Previous: GBV discussion on Wed 30 Mar

For Release Prep