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

Table of Contents

Expand

title	Sprint Planning Agenda

Sprint Goal / Focus
Sprint Capacity
Review sprint candidates
Agree technical approach / define key implementation tasks
Finalise estimates / costings
Confirm sprint scope
Confirm first actions

Expand

title	Sprint Retrospective Agenda

Review Retro Board (10 mins)
Voting (2 mins)
Discussion (15 mins)
Summary Actions (3 mins)

Sprint Planning

- not in sprint

or @ - in sprint

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1511

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-269

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.

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-253

md331 (Deactivated)

BE 0h FE 2w

Incorporates

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-237

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-254

steve.osguthorpe

BE 15h FE 0h

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

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

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.

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-276

steve.osguthorpe

BE 8h FE 0h

Relates to

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-189

and

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-262

.

Investigation is to test there are no issues with

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

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1517

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-265

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

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-11571643

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-239

Requires

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution182

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

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UINVERM-7

Clashes with

183

for logging, and

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-253217

for presenting.)

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-11571643

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-240

Requires

-183

Kurt Nordstrom

BE 8h FE 0h.

Deliverable is domain object for a generic event log. No front-end or user interface.

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1597

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-239

Clashes with

268

Claudia Malzer

BE 0h FE 2h.

Jira Legacy

server	System Jira	columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1302

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UINV-7ERM-190

steve.osguthorpe

Carried forward

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1157ERM-193

steve.osguthorpe

Carried forward

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERMUXPROD-2421159

Requires

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-239

Clashes with

274

Kurt Nordstrom

BE 8h FE 0h.

Jira Legacy

server	System Jira	columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1517

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UINV-7

steve.osguthorpe Should the backend provide the data, or should the frontend fetch this (as done with organizations)?

	ERM-215

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

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-16431601

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-182230

Aditya matukumalli

BE 0h FE 8h.

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-15971159

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-268277

Aditya matukumalli

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-13021159

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-190

steve.osguthorpe

Carried forward

278

Aditya matukumalli

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-193

steve.osguthorpe

261

Aditya matukumalli

Carried forward. BE 0h FE 2h.

To Carry Forward

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-17511157

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-273239

Requires

Jira Legacy

server	System JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UINV-7

Clashes with

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-253

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-11591157

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-274240

Requires

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1517ERM-239

Clashes with

Jira Legacy

server	System JiraJIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERMUINV-2157

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-16011157

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-230242

Requires

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1159ERM-239

Clashes with

Jira Legacy

server	System JiraJIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-277UINV-7

steve.osguthorpe Should the backend provide the data, or should the frontend fetch this (as done with organizations)?

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-11591751

Jira Legacy

server	System JIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-273

Clashes with

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-278253

Sprint Retrospective

Expand

title	Sprint Retrospective Agenda

Review Retro Board (10 mins)
Voting (2 mins)
Discussion (15 mins)
Summary Actions (3 mins)

Versions Compared

Old Version 7

New Version Current

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Planning

To Carry Forward

Sprint Retrospective

Page Comparison

Versions Compared

Old Version 7

New Version Current

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Planning

To Carry Forward

Sprint Retrospective