Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Sprint Goal / Focus
- Support for non-serial resources
Sprint Schedule
- Sprint: 81
- Release: Fameflower
- Quarter: 2020 Q1
- Start Monday 13 Jan, 2pm UK
- Finish Friday 24 Jan, 12pm UK
Sprint Capacity
Team Availability: Schedule | Calendar
Notes / Exceptions:
Lead Roles:
- Front End Code Review:
- Back End Code Review:
- QA:
QA Environment: folio-testing
Navigation
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
Sprint Planning
- not in sprint
or @ - in sprint
Brought Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|
UXPROD-2111
-
Getting issue details...
STATUS
|
ERM-434
-
Getting issue details...
STATUS
| |
|
|
ERM-644
-
Getting issue details...
STATUS
| | Almost code complete. Query about updating the database to reflect code changes. Potentially look at examples in migrations folder in mod-agreements. |
UXPROD-1478
-
Getting issue details...
STATUS
|
ERM-591
-
Getting issue details...
STATUS
| | Functionality complete - cannot be tested yet, as there is an issue with tests suite. |
|
ERM-571
-
Getting issue details...
STATUS
| |
|
|
ERM-454
-
Getting issue details...
STATUS
| | STCON-92 is now resolved, so this is unblocked. |
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|
UXPROD-2081
-
Getting issue details...
STATUS
|
ERM-485
-
Getting issue details...
STATUS
/
ERM-482
-
Getting issue details...
STATUS
/
ERM-481
-
Getting issue details...
STATUS
/
ERM-486
-
Getting issue details...
STATUS
| | Add to e-resource preview panel in the first instance. - Owen Stephens to define rules for these and subsequent items, eg
- (Where) are these defined in GoKB?
- Use author / edition to link potential duplicates in new PCIs / PTis.
|
|
ERM-633
-
Getting issue details...
STATUS
| steve.osguthorpe | . |
UXPROD-2124
-
Getting issue details...
STATUS
|
ERM-510
-
Getting issue details...
STATUS
| | Q: how to identify a record? See notes on ERM Sprints 79-80. Owen to followup with Steve. |
UXPROD-2081
-
Getting issue details...
STATUS
|
ERM-316
-
Getting issue details...
STATUS
| | Needs further definition. May be dependent on ERM-485. |
UXPROD-2111
-
Getting issue details...
STATUS
|
ERM-506
-
Getting issue details...
STATUS
| |
|
|
ERM-647
-
Getting issue details...
STATUS
| |
|
UXPROD-1478
-
Getting issue details...
STATUS
|
ERM-668
-
Getting issue details...
STATUS
| | Novelty: - repeatable filters
- filter by both type and value (different to Org / Roles)
Needs wireframe, and may be dependent on ERM-591. Investigation goals for Sprint 81: - What support / refactoring is needed from custom properties / backend to facilitate repeatable and nested filters possible? (BE)
- How to manage functionality in UI? (UX/PO/FE)
|
|
ERM-634
-
Getting issue details...
STATUS
| |
|
|
ERM-642
-
Getting issue details...
STATUS
|
| No longer effectively blocked by STCON-57 |