ERM Sprint 66

Owned by Jag Goraya
Last updated: Jun 13, 2019

Sprint Goal / Focus

  •  Tie up loose ends, and prepare ground for Q3.

Sprint Schedule

  • Sprint: 66
  • Quarter: 2019 Q2
  • Start Thursday 13 June, 2pm UK
  • Finish Friday 28 June, 2pm UK
  • Retrospective: Wed 3 July, 2:30pm UK


Sprint Capacity

Team Availability: Schedule

Notes / Exceptions:

Lead Roles:

QA Environment: folio-testing

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 Retrospective Agenda
  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)

Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-1511 - Getting issue details... STATUS

ERM-269 - Getting issue details... STATUS

Claudia Malzer

BE 0h FE 8h

TODO: differences in SASQ routing from Licenses to Agreements, so slightly different. 

Aditya matukumalli to support Claudia Malzer  on accomodating the differences.

Expected to be complete by end of week. 


ERM-253 - Getting issue details... STATUS

md331 (Deactivated)

BE 0h FE 2w

Incorporates  ERM-237 - Getting issue details... STATUS



ERM-254 - Getting issue details... STATUS

steve.osguthorpe

BE 15h FE 0h

Driven by https://folio-project.slack.com/archives/CAYCU07SN/p1557421022302700 

  1. Generate json schema for mod-agreements and mod-licenses.
  2. Write explainer documentation: https://folio-project.slack.com/archives/CAYCU07SN/p1557491555305700?thread_ts=1557421022.302700&cid=CAYCU07SN

Explainer documentation in Github. Dev questions raised as tasks/bugs in Jira.

Peer review by dev team. 


ERM-276 - Getting issue details... STATUS

steve.osguthorpe

BE 8h FE 0h

Relates to  ERM-189 - Getting issue details... STATUS  and  ERM-262 - Getting issue details... STATUS . 

Investigation is to test there are no issues with 

  1. using java-local and java-date types
  2. front-end conversion of proposed approach

UXPROD-1517 - Getting issue details... STATUS

ERM-265 - Getting issue details... STATUS

John Fereira

Carried forward.  Remaining: BE 8h FE 0h.  

Controllers and servers are in place. Some potential reuseable code in stale branch for MODERM-23. 

TODO:

  • verify all fields required
  • plan to commit changes for output review

UXPROD-1643 - Getting issue details... STATUS

ERM-182 - Getting issue details... STATUS

Kurt Nordstrom

BE 2h FE 0h.

Feeds into a piece of work around data integrity. 

Requirement is still to validate a coverage statement, but not reject it:

  • coverage end < coverage start

Output of this is to introduce the mechanism to not fail the import for recoverable errors. 

Logging of errors should be done in a way that can be easily reported to user, but is out of scope (see, eg  ERM-183 - Getting issue details... STATUS  for logging, and