Skip to end of banner
Go to start of banner

ERM Sprint 67

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 5 Next »

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 67
  • Quarter: 2019 Q2
  • Start Monday 1 July, 2pm UK
  • Finish Friday 12 July, 2pm UK
  • Retrospective: Wed 17 July, 2:30pm UK


Sprint Capacity

Team Availability: Schedule

Notes / Exceptions:

Lead Roles:

QA Environment: folio-testing

Navigation

 Sprint 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 Retrospective Agenda
  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)

Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-1643 - Getting issue details... STATUS

ERM-183 - Getting issue details... STATUS

Kurt Nordstrom

(minus) Blocks  ERM-290 - Getting issue details... STATUS

UXPROD-1643 - Getting issue details... STATUS

ERM-182 - Getting issue details... STATUS

Kurt Nordstrom


UXPROD-1681 - Getting issue details... STATUS

ERM-230 - Getting issue details... STATUS

Aditya matukumalli

Pushed to Code Review. Aim to enter QA stack for Tuesday. 

UXPROD-1517 - Getting issue details... STATUS

ERM-265 - Getting issue details... STATUS

John Fereira

  • Had some issues, then compilation errors
  • TODO: Recompile two files.

PR expected today.

UXPROD-1517 - Getting issue details... STATUS

ERM-215 - Getting issue details... STATUS

John Fereira

UXPROD-1751 - Getting issue details... STATUS

ERM-273 - Getting issue details... STATUS

(error) Front end: pending mockups

(tick) Back-end


(question) BE 

Potentially using Library Data Platform

  • Lookup data provider using plugin provided
  • Add data provider to an agreement
  • Display data provider and link to eUsage app
  • BACK-END: Add usage data provider ID to subscription agreement

TODO: 

  • Needs mockup with card layout

OUT OF SCOPE: 

  • Display reporting information
  • No room for 4 accordians on card layout. HOWEVER, no longer using sub-accordians.

UXPROD-1157 - Getting issue details... STATUS

ERM-239 - Getting issue details... STATUS

Aditya matukumalli

BE: Link field is completed on entitlement record.

FE: 24 hours (3 days)

ISSUES

  • Can show PO Line, Acquisition Method, Title
  • Cannot currently show Vendor Name, Order Status, Order Type: ACCEPTED for current sprint

OUT OF SCOPE: 

  • No need to create PO or POL from within agreement app

UXPROD-1157 - Getting issue details... STATUS

ERM-240 - Getting issue details... STATUS

Aditya matukumalli

NOTE: Would need multiple fetches to display looked up data. For now, no additional calls to be made. 

UXPROD-1157 - Getting issue details... STATUS

ERM-242 - Getting issue details... STATUS

Aditya matukumalli


UXPROD-1512 - Getting issue details... STATUS

ERM-284 - Getting issue details... STATUS

Claudia Malzer

FE: 20h

Placement is different for packages and non-packages, but is essentially the first accordian for both. 


ERM-276 - Getting issue details... STATUS

steve.osguthorpe

BE 7.5h FE 2h

TODO: 

  • Change all affected date/times to ISO dates only

ERM-189 - Getting issue details... STATUS

steve.osguthorpe

Subsumed into  ERM-276 - Getting issue details... STATUS


ERM-262 - Getting issue details... STATUS

steve.osguthorpe

Subsumed into  ERM-276 - Getting issue details... STATUS

UXPROD-1791 - Getting issue details... STATUS

ERM-289 - Getting issue details... STATUS

md331 (Deactivated)

FE: 4h

Required for  ERM-217 - Getting issue details... STATUS

UXPROD-1513 - Getting issue details... STATUS

ERM-290 - Getting issue details... STATUS

steve.osguthorpe

Required for  ERM-217 - Getting issue details... STATUS

  1. Build job domain model (1h)
    1. ID, Name etc
    2. Add API to create/delete/fetch jobs and status (NA)
  2. Add queue management (7.5h)
  3. Trigger existing service from file upload (15h)
    1. trigger action
    2. refacfor to separate file upload into discrete library

ERM-190 - Getting issue details... STATUS

steve.osguthorpe



ERM-193 - Getting issue details... STATUS

steve.osguthorpe



ERM-283 - Getting issue details... STATUS




ERM-288 - Getting issue details... STATUS




ERM-285 - Getting issue details... STATUS

steve.osguthorpe



ERM-287 - Getting issue details... STATUS

steve.osguthorpe



ERM-278 - Getting issue details... STATUS

Aditya matukumalli



ERM-277 - Getting issue details... STATUS

Aditya matukumalli


Sprint Retrospective

 Sprint Retrospective Agenda
  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)



  • No labels