Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 72
  • Release: Elderflower
  • Quarter: 2019 Q3
  • Start Monday 9 Sep, 2pm UK
  • Finish Friday 20 Sep, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Module Release Prep / Deadline: 11 Sep 

Lead Roles:

QA Environment: folio-testing

Navigation

Table of Contents

Expand
titleSprint 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 Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1472

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-428

"Current" status is being used to test logic, which may cause internationalisation problems, if using label/value. 

  • To avoid this, would need a feature to configure {agreement/link} status
  • Ideally, we distinguish between configurable vs editable refdata
  •  Create new issue to define, for each refdata set, whether configurable/editable, and implications  

TODO:

  • BE: Store amendment link status and notes (1d)
    • mirror how license links are handled
    • nested rather than at same level to support easier front-end handling
    • amendment link array, with amendments sorted in start date descending order
  • FE: implement form and error (3d)

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1472

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-429

Mark Deutsch

FE: 3d including integration tests

  • Amendment notes are presented in UI mockup differently to how notes are handled for future/past licenses. Gill Osguthorpeto confirm that whether we should keep/break consistency.
  • I'm not sure what I'm comparing, could someone confirm please Jag GorayaMark Deutsch

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1472

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-430

BE: 1d to configure rules

Added 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-441

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-585

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-395

BE: 2d

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-585

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-394

BE: 0.5d FE: 0.25d

TODO:

  • Extend existing filters to include date range
  • Missing dates are treated as included, so would need to include NULL check
  • FE: update calls to revised endpoints

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-585

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-392

Existing pattern of counts logging - number of upserts 

Non-trivial maybe is handling single title services

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-585

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-393



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-371

tinymce.emotions_dlg.errorOwen Stephens  to revisit with Gill Osguthorpe

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-422



Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-356
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-361

Estimate: 2d

Aim to prioritise to meet module release deadline to include in Daisy release.


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-338



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-182



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-440



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-438