ERM Sprint 66
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:
17-20 Jun FOLIO Washington + Travel (Ian, Owen, Jag)
@Claudia Malzer not available after 19 June
@md331 (Deactivated) not available 13-14 June
@Peter Böhm only available 13, 14, 19 June
Lead Roles:
Front End Code Review: @md331 (Deactivated)
Back End Code Review: @steve.osguthorpe
QA: @Owen Stephens
QA Environment: folio-testing
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
@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. | ||
| @md331 (Deactivated) | BE 0h FE 2w Incorporates https://folio-org.atlassian.net/browse/ERM-237
| |
| @steve.osguthorpe | BE 15h FE 0h Driven by https://folio-project.slack.com/archives/CAYCU07SN/p1557421022302700
@steve.osguthorpeto confer with @md331 (Deactivated)on the explainer requirements Explainer documentation in Github. Dev questions raised as tasks/bugs in Jira. Peer review by dev team. | |
| @steve.osguthorpe | BE 8h FE 0h Relates to https://folio-org.atlassian.net/browse/ERM-189 and https://folio-org.atlassian.net/browse/ERM-262. Investigation is to test there are no issues with
| |
@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:
| ||
@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:
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 https://folio-org.atlassian.net/browse/ERM-183 for logging, and https://folio-org.atlassian.net/browse/ERM-217 for presenting.) | ||
@Kurt Nordstrom | BE 8h FE 0h. Deliverable is domain object for a generic event log. No front-end or user interface. | ||
@Claudia Malzer | BE 0h FE 2h.
| ||
@steve.osguthorpe | Carried forward | ||
| @steve.osguthorpe | Carried forward | |
@Kurt Nordstrom | BE 8h FE 0h. | ||
BE ?? FE 0h. Some potential reuseable code in stale branch for MODERM-23. To complete Scenarios 1 and 2, but not Scenario 3. Should this even be an ERM job? OKAPI authentication is project-wide. @Owen Stephensto rewrite story to clarify requirements | |||
@Aditya matukumalli | BE 0h FE 8h. | ||
@Aditya matukumalli |
| ||
@Aditya matukumalli |
| ||
| @Aditya matukumalli | Carried forward. BE 0h FE 2h. |
To Carry Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
Requires https://folio-org.atlassian.net/browse/UINV-7 Clashes with https://folio-org.atlassian.net/browse/ERM-253 | |||
Requires https://folio-org.atlassian.net/browse/ERM-239 Clashes with https://folio-org.atlassian.net/browse/UINV-7 | |||
Requires https://folio-org.atlassian.net/browse/ERM-239 Clashes with https://folio-org.atlassian.net/browse/UINV-7 @steve.osguthorpe Should the backend provide the data, or should the frontend fetch this (as done with organizations)? | |||
Clashes with https://folio-org.atlassian.net/browse/ERM-253 |
Sprint Retrospective