Sprint Goal / Focus

Sprint Schedule

  • Sprint: 73
  • Release: Elderflower
  • Quarter: 2019 Q4
  • Start Monday 23 Sep, 2pm UK
  • Finish Friday 4 Oct, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions: NA

Lead Roles:

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



Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

Implementation tasks should be added directly into the Jira issue  

Brought Forward (from previous sprint)

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

TODO:

  • Add/rename endpoints to "current" / "future"/"dropped" / "all" (backend - steve.osguthorpe )
  • Front-end design/integration + tests
  • Owen Stephens to add custom package test data to Jira issue to use for integration tests

TODO: 

  • uses "current" endpoint being implemented as part  of ERM-396
  • original path shows 'all' resources - just need to show 'current'

Count not incrementing for ERM-404 & ERM-407.

Not holding anything else up

Not as high priority as UXPROD-1467 tasks

Counts not incrementing

Not as high priority as UXPROD-1467 tasks


Related to but not blocked by forthcoming release of .

TODO: 

 / 

Nearly done. TODO: 

  • Finish templating for the terms

Should be less than 1hr work


(tick)

Requires UI for  in order to QA.

Fixed: PR pending. 


Ready for QA, once re-deploy complete.


Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Front-end only.

Back-end only. Will deliver as part of backend updates for ERM-394 and ERM-396. 

BE: 1d FE: 3d


Requires  back-end model, which will include calculated/derived dates. 

  • All periods provided as list
  • Current period to be provided on own

Incorporate as part of ERM-466

md331 (Deactivated)

Requires  back-end model

Incorporate as part of ERM-466

BE: 1h FE: 3d

Wireframes not necessary in this case. 

Out of scope: configuration of closure reasons

TODO: 

  • Store closure reasons in tenant initialisation file
  • Migrate Cancelled status to Closed status
  • New 'Reason for closure' property
  • UI + tests


Carried Forward (to future sprint)

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

(error) To Sprint 74

(error) To Sprint 74