/
ERM Sprint 63

ERM Sprint 63

May 09, 2019

Sprint Goal / Focus

  •  Integration with Organizations

Sprint Schedule

  • Sprint: 63

  • Quarter: 2019 Q2

  • Start / Planning Tuesday 7 May, 3pm UK

  • Merge Cutoff Friday 17 May, 2pm UK 

  • End / Turnover Monday 20 May, 10am UK

  • Retrospective: Wed 22 May, 2:30pm UK



Sprint Capacity

Team Availability: Schedule

  • 320 hours (~ full dev strength)

Notes / Exceptions:

  • 6 May UK Public Holiday, so shortened sprint.

  • 7-10 May ELAG: no additional QA support

  • 8, 14, 15 May: No PO availability 

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

  1. Review Retro Board (10 mins)

  2. Voting (2 mins)

  3. Discussion (15 mins)

  4. Summary Actions (3 mins)

Sprint Planning  

 

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

@Kurt Nordstrom

Previously: BE 16h FE 0h 

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

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

@steve.osguthorpe

Previously BE 15h FE 8h

Needs updates to web-toolkit, so @Ian Ibbotson (Use this one) or @steve.osguthorpe

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

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

@John Fereira @md331 (Deactivated)

Previously

  • BE 4h FE 16h

  • ERM-179 can proceed without the back-end sub-issues.

  • ERM-180 is dependent on the back-end tasks.

 needed for https://folio-org.atlassian.net/browse/ERM-163 which is also scheduled in this sprint.



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

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

Previously BE 0h FE 8h 

 needs https://folio-org.atlassian.net/browse/ERM-162 which is scheduled in this sprint

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

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



BE2h  FE 16h

 needed for https://folio-org.atlassian.net/browse/ERM-165 which is also scheduled in this sprint.

Does not include the workflow to include filters. Ideally they would 

Adding an organization to an agreement will create a new link record.

  • Entity: subscriptionAgreementOrg

  • JSON: Orgs array including those Entities.

  • subscriptionAgreementOrg has name and ID.

TODO

  • Backend (all changes to Org) (2h)

    • Rename UUID from VendorsID to OrganizationID

    • Remove orgRef call 

    • Check for and enforce duplicate Organization assignment to role

    • Remove source URI

  • Front-end (8h-16h)

    • Use ui-plugin-find-organizations

    • Update data returned

    • Create UI (non-cards)

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

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

BE 1h  FE 16h

  • Backend (all changes to Org) (1h)

    • Rename UUID from VendorsID to OrganizationID

    • Remove orgRef call 

    • Check for and enforce duplicate Organization assignment to role

    • Remove source URI

  • Front-end (8h-16h)

    • Use ui-plugin-find-organizations

    • Update data returned

    • Create UI (non-cards)

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

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

Requires 

 UXPROD-1601 is scheduled for this sprint

Concerns:

  • Permissions to view Organizations and passwords

TODO:

  • Backend (16h)

    • Refactor organization API structure for mod-licenses

    • Refactor organization API structure for mod-agreements

    • Validate modOrganizations behaviour

    • Configure embedded Organizations record

  • Frontend (16h)

    • Display interface data using Card design



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

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

Previously: PR to be submitted

  • Ready for Code Review.

@Kurt Nordstromto transition issue to In Code Review and assign to @steve.osguthorpe

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

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

@Kurt Nordstrom

Previously BE 20h FE 20h

Previously: 

  • To store in db to circumvent OKAPI non-persistence issue.



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

@Kurt Nordstrom

No further work needed (apart from submitting)

Previously:

  • PR to be submitted for work completed so far. 

  • Integration tests to be resolved separately.



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

@Owen Stephens

Permission sets to be applied.

There needs to be a higher level discussion about how these groups are defined and categorised, and can be re-used.

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

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

  • What do we post to the back-end?

    • JSON scheme submit_package

    • single operation

TODO:

  • Needs UI

  • Error message descriptions

  • Large import file (asynchronous handling)

  • Define underscore fields notation

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

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



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

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

@Claudia Malzer

Previously: BE 0h FE 8h 

  • In General FOLIO Settings app

  • Code in ui-agreements



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

@John Fereira





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

@John Fereira





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



@John Fereira

Previously: Looks like it needs resolving in web-toolkit, so @Ian Ibbotson (Use this one) or @steve.osguthorpe

@Ian Ibbotson (Use this one)to setup repo access for @John Fereira



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

Merged. Just needs closing now. 

Sprint Retrospective

  1. Review Retro Board (10 mins)

  2. Voting (2 mins)

  3. Discussion (15 mins)

  4. Summary Actions (3 mins)