ERM Sprint 76

ERM Sprint 76

Sprint Goal / Focus

  • Wrap up new agreed priority feature development ahead of Edelweiss module release deadline

Sprint Schedule

  • Sprint: 76

  • Release: Edelweiss 

    • last sprint before contingency

    • no new features expected to be included after this sprint in official release

  • Quarter: 2019 Q4

  • Start Monday 4 Nov, 2pm UK

  • Finish Friday 4 Nov, 12pm UK



Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • @Gill Osguthorpe unavailable until 11 Nov

Lead Roles:

  • Front End Code Review: @md331 (Deactivated)

  • Back End Code Review:  @steve.osguthorpe

  • QA: @Owen Stephens

QA Environment: folio-testing

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 

 

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Brought Forward

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

@Aditya matukumalli

Mandatory agreement status fix implemented. 

Data Integration tests

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

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

https://folio-org.atlassian.net/browse/ERM-394 / https://folio-org.atlassian.net/browse/ERM-396

@steve.osguthorpe

Due today / Tuesday



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

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

@Peter Böhm

Unable to get detailed log 



ERM-356: Expose license terms over APIClosed

@steve.osguthorpe





ERM-463: Agreement | Add Amendment 'Conflicting status' to preview screenClosed

@Gill Osguthorpe

Return to UX for further clarification. Pick up by @Ethan Freestone after clarified (post 11 Nov).



ERM-544: Agreement | Warning messages in edit pane should use MessageBanner componentClosed

@Ethan Freestone

Mostly done. Cleanup to follow up. 

Some disappearing control issues (trying to make it work like messages)

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

ERM-546: Interpret <status> element on GOKb TIPPClosed