ERM Sprint 60
Sprint Planning
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 Retrospective
Review Retro Board (10 mins)
Voting (2 mins)
Discussion (15 mins)
Summary Actions (3 mins)
Sprint Logistics
Sprint Goal / Focus
ERM eHoldings Integration
Sprint Schedule
Sprint: 60
Quarter: 2019 Q2
Start Monday 25 March, 2pm UK
Finish Monday 8 April, 10am UK
Sprint Capacity
Team Availability: Schedule
Notes / Exceptions:
@Kurt Nordstrom joins the team (15h/wk): will be spending getting setup
@Owen Stephens: not available Tue/Wed (week1)
@Ian Ibbotson (Use this one) availability TBC
@Martina Schildt joins for test planning
@steve.osguthorpe unavailable for Sprint 61, so limited capacity for back-end tasks then.
Sprint Planning
Implementation tasks should be entered directly into the JIra issue.
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates |
|---|---|---|---|
Y | Nothing blocking this from happening. | ||
Y | Must be done before ERM-109 | ||
Y | Must be done after ERM-110 Needs eHoldings to complete work to demonstrate end-to-end.
| ||
Y | Almost done, as carried over from Sprint 59. @Claudia Malzer is working on integration tests. | ||
Y | FE: 8h (Claudia) BE 2h | ||
| Y | BE: 4h Only adding to folio-gbv Will not apply on folio testing environment, except where defined at UI permission levels Currently based on Edit/Create/View {license/agreement} @Kurt Nordstrom to shadow @steve.osguthorpe | |
| Y | BE: 1h | |
Y (Back-End) | BE: 20h FE: 35h (break and fix), list (4h), view (routing refactor 25h), delete (2h). edit (15h) Front-end changes routing and data fetching methods. Significant refactor as the Stripes components needed is changing (SearchAndSort). As such, there is significant uncertainty in FE estimates. The functionality will be delivered across multiple sprints. | ||
Y | BE 15h FE: 8h | ||
Y | FE: 1h | ||
Y | FE: 2h | ||
| Y | Triage required, but depending on how much effort, this may not be worthwhile, as the refactor from ERM-82 could make this redundant. | |
| Y |
|