/
ERM Sprint 124

ERM Sprint 124

Owned by Jag Goraya
Last updated: Oct 06, 2021

Sprint Goal / Focus

  • Module release deadline

Sprint Schedule

  • Sprint: 124
    • Start Monday 27 Sep
    • Finish Fri 8 Oct
    • Sprint Board
    • Jira Sprint: 1037
  • Release: 2021.3 Kiwi  
    • Sprint 124: Module Release Deadline
    • Sprint 127: Bugfix Deadline

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • NA

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 / Constraints
  • Components and Changes
    • Frontend
    • Backend
  • Tests
  • Data
  • Dependencies
  • Known Unknowns
  • QA
    • environment: local | testing | snapshot | other
    • data
    • scripts
  • Development Estimate



Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions


ERM-1628 - Getting issue details... STATUS

Claudia Malzer
  • Approach / Constraints
    • Expand placeholders in accordance with folio stripes i18n guidelines. This will bypass the need for toLowercase.
    • No dynamic input to be concerned about.
    • To find types, interrogate where core docs is called from for recordType prop
      • expected to expand for  
        • amendment
        • license
        • core documents
        • supplementary docs
        • term
  • Components and Changes
    • Frontend
      • coredocs, supplementarydocs, terms: change template string based on type
      • en.json: remove old and add two new translation strings for each type
    • Backend: none
  • Tests: no changes to tests needed
  • Data: none
  • Dependencies: none
  • Known Unknowns: none
  • QA
    • environment: snapshot
    • data / scripts: none
    • will need to wait for Localize to test German translations
  • Development Estimate: <0.5d

ERM-1733 - Getting issue details... STATUS

Owen Stephens

(question)