Skip to end of banner
Go to start of banner

ERM Sprint 132

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 Current »

Sprint Goal / Focus

  • 4 Feb: Feature Freeze

Sprint Schedule

  • Sprint: 131
    • Start Mon 24 Jan
    • Finish Fri 4 Feb
    • Sprint Board
    • Jira Sprint: 1114
  • Release: 2022.1 Lotus  
    • Sprint 133: Module Release Deadline
      • Backend 16 Feb 2022
      • Frontend 18 Feb 2022
    • Sprint 136: Bugfix Deadline (25 March 2022)

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • 24-28 Jan: Peter on 25% time

Lead Roles:

QA Environment: folio-snapshot

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?
  • What front and back end components are affected?
  • What changes need to be made? (additions, removals or modifications)
  • What development tests need to be written?  
  • What data does the developer need to verify their work?
  • What are the known unknowns? 
  • What is needed to QA? (environment, data, scripts)

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 Planning  

(error) - not in sprint

(tick) or @ - in sprint 


Planning Notes Template

  • Approach
  • Components and Changes
    • Frontend
    • Backend
  • Tests / Data
  • Dependencies
  • Known Unknowns
  • QA: local | testing | snapshot | other
  • Development Estimate

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

UXPROD-3172 - Getting issue details... STATUS

ERM-1943 - Getting issue details... STATUS

(error)

Pending UAT on ERM-1938 (Agreements and AWS)


ERM-1800 - Getting issue details... STATUS

Ethan Freestone 
  • Approach
    • match key doesn't cover anything existing
      • to be addressed later
    • Work on ERM-1986/ERM-1988 API to be progressed alongside this
  • Components and Changes
    • Frontend: 
    • Backend: mod-agreements
  • QA: snapshot
  • Development Estimate
    • 5d including API design from ERM-198

UXPROD-3339 - Getting issue details... STATUS

ERM-1986 - Getting issue details... STATUS

ERM-1987: Gill Osguthorpe 

ERM-1988: Ethan Freestone 

ERM-1989: Ethan Freestone 

To follow ERM-1800?

  • Approach
    • API to be developed in tandem with ERM-1800
  • Components and Changes
    • Frontend: ui-agreements
    • Backend: mod-agreementsDependencies: 
    • ERM-1980
    • UX Design 
  • Known Unknowns
    • may not be existing patterns for moving in FOLIO
  • QA: snapshot 
  • Development Estimate
    • UI implementation: ~2d



ERM-1958 - Getting issue details... STATUS

Peter Böhm 
  • Approach
    • each app should do their own, so this would be a PR to ui-organizations
    • pattern in agreements to follow
    • only need to submit a PR for the lookup link
  • Components and Changes
    • Frontend: ui-organizations
    • Backend: none
  • Dependencies
    • environment set up for dashboard and organizations
  • Known Unknowns
    • is there a stripes back and forth?
  • QA: snapshot
  • Development Estimate

ERM-1990 - Getting issue details... STATUS

Claudia Malzer 

  • Approach
    • can derive link destination to use from titleList.class 
    • avoid hardcoding link in ERM comparison, and use registry instead
      • for example, ui-agreements index has eventHandler fired by dashboard (LOAD-STRIPES-REGISTRY) which then triggers setupRegistry
      • examples in OA and Dashboard
      • documentation: Registry
  • Components and Changes
    • Frontend: ui-agreements
    • Backend: none
  • QA: snapshot
  • Development Estimate








Rolled Over From Previous Sprint

For Development


Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3172 - Getting issue details... STATUS

ERM-1938 - Getting issue details... STATUS

Ian Ibbotson (Use this one) 

Blocked by FOLIO-3362 - Getting issue details... STATUS


ERM-1923 - Getting issue details... STATUS / 

ERM-1920 - Getting issue details... STATUS

Ethan Freestone 


UXPROD-3338 - Getting issue details... STATUS

ERM-1980 - Getting issue details... STATUS

Monireh Rasouli 

May have (but unlikely to be) something to do with virtualising the script

ERM-1953 - Getting issue details... STATUS

Monireh Rasouli 


UXPROD-3335 - Getting issue details... STATUS

ERM-1850 - Getting issue details... STATUS

(error)


FAT-82 - Getting issue details... STATUS

ERM-1503 - Getting issue details... STATUS

Ethan Freestone 

For Code Review

FAT-82 - Getting issue details... STATUS

ERM-1496 - Getting issue details... STATUS

Ethan Freestone 

For Code Review

For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1982 - Getting issue details... STATUS

Owen Stephens 



ERM-1981 - Getting issue details... STATUS

Owen Stephens 



ERM-1976 - Getting issue details... STATUS

Owen Stephens 



ERM-1974 - Getting issue details... STATUS

Owen Stephens



ERM-1973 - Getting issue details... STATUS

Owen Stephens


UXPROD-3339 - Getting issue details... STATUS

ERM-1799 - Getting issue details... STATUS

Owen Stephens

Some adjustments expected for alternative approach to updating matched keys over time.

  • Some investigation to work out where to step in to process the changes
  • Dev Estimate: 2d

UXPROD-3140 - Getting issue details... STATUS

ERM-1745 - Getting issue details... STATUS

Owen Stephens


UXPROD-3140 - Getting issue details... STATUS

ERM-1744 - Getting issue details... STATUS

Owen Stephens


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions









Removed

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions







Sprint Summary

ERM

key summary type assignee status components
Refresh


Dashboard

key summary type assignee status components
Refresh

Other

key summary type assignee status components
Refresh

  • No labels