ERM Sprint 94

ERM Sprint 94

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 94

  • Release: Honeysuckle

  • Quarter: 2020 Q3

  • Start Monday 13 Jul, 2pm UK

  • Finish Friday 24 Jul, 12pm UK



Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • No Claudia, Ethan or Peter in first week

  • No Steve all sprint

Lead Roles:

  • Front End Code Review: @Aditya matukumalli

  • Back End Code Review:  @Ian Ibbotson (Use this one)

  • 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

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

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

@Owen Stephens

Some changes to the UI will be needed.  Stories for known amends to be elaborated for wireframing. 

Aim is changes to edit screen. AL edit screen and agreement view should be front end only

May need changes to backend to support display of ALs linked to no resource. 

@Ian Ibbotson (Use this one) @steve.osguthorpe to advise on backend model 
@Gill Osguthorpe @Owen Stephens to liaise on shape of requirements 
Define stories for non-dependent changes that @Aditya matukumallican progress after ERM-951
edit agreement
edit agreement line
view agreement



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

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

@Owen Stephens

Revisit dashboard where users see information that they may need to act on. 

Aim is to put options together to start conversations with users. 

  • Q3: agree designs and concept

  • Q4: implementation 

Start in second half of sprint. 

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

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

Standby to display outputs from ERM-510, assuming it passes

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

@Owen Stephens

For QA

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

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

@Aditya matukumalli

TODO

Put report element out for review by Ethan / Claudia
Software demo in Wed 22 Jul

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

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

@Aditya matukumalli

TODO:

Rasmus / John to merge Stripes-component PR required for
colour coding
overlap columns
header formatting / alignment
Raise blocking issue in STCOM
info popover needs wiring up (backend merged this morning) 
comparison report title = user defined name (comparison job name)
minor cleanup 
tests  
Display revised embargo shape (should apply automatically)
dates should be locale-specific

No existing component for popover formatting, so will create new one in ui-erm-comparisons . 

Title needs to be dynamic. Should align with column headings. 

Related to https://folio-org.atlassian.net/browse/ERM-996. Revised shape of embargo should not break current implementation. 

2020-07-20: Merged to snapshot, but permissions are not being returned.

  • Slack conversation

  • Possible module rename issues? Would require new version number to force descriptor refresh, which will need to cascade to dependencies.

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

https://folio-org.atlassian.net/browse/ERM-952 / https://folio-org.atlassian.net/browse/ERM-996

 @Ethan Freestone

Embargo data is last part of package/agreement comparison processing.

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

https://folio-org.atlassian.net/browse/ERM-952 / https://folio-org.atlassian.net/browse/ERM-994

 @Ethan Freestone

To pick up in sprint week 2.



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

https://folio-org.atlassian.net/browse/ERM-952 / https://folio-org.atlassian.net/browse/ERM-992

@Owen Stephens

In QA



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

@Owen Stephens  

In QA



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

@Owen Stephens

In QA



https://folio-org.atlassian.net/browse/ERM-989 / https://folio-org.atlassian.net/browse/ERM-990

 @Ian Ibbotson (Use this one)

Pending input from reporter. 

16 Jul 2020: Closed - no problem has previously occurred, and going forward, a different approach is already taken. 

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

https://folio-org.atlassian.net/browse/ERM-943 / https://folio-org.atlassian.net/browse/ERM-985

@Owen Stephens

Needs elaboration

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

https://folio-org.atlassian.net/browse/ERM-943 / https://folio-org.atlassian.net/browse/ERM-944 / https://folio-org.atlassian.net/browse/ERM-945

@Claudia Malzer

To pick up in sprint week 2.

Brought In

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

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

@Peter Böhm

Data model needs extending, and then to be returned to Backlog for front end implementation.