Versions Compared

Key

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

Sprint Goal / Focus

  •  Wrap up new agreed priority feature development ahead of Edelweiss module release deadline

Sprint Schedule

  • Sprint: 76
  • Release: Edelweiss 
    • last sprint before contingency
    • no new features ahead of thisexpected to be included after this sprint in official release
  • Quarter: 2019 Q4
  • Start Monday 4 Nov, 2pm UK
  • Finish Friday 4 Nov, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

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 Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-376

.
https://issuesfolio-org.folioatlassian.orgnet/browse/UXPROD-835

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-508

Unlocks 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-549

Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-459

Mandatory agreement status fix implemented. 

Data Integration tests

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1932

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-457
 / 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-394
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-396
Due today / Tuesday

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-392
 / 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-393
Unable to get detailed log 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-356

steve.osguthorpe

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-463

Return to UX for further clarification. Pick up by Ethan Freestone after clarified (post 11 Nov).


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-544

Mostly done. Cleanup to follow up. 

Some disappearing control issues (trying to make it work like messages)

https://issuesfolio-org.folioatlassian.orgnet/browse/UXPROD-2122

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-546

(tick)(tick)