ERM Sprint 166

Sprint Goal / Focus 

  • ..

Sprint Schedule

  • Sprint: 166
  • Release: 2023.2 Poppy  
    • Sprint 8 of 9 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 167)
    • Sprint 168: Module Release Deadline (30 Jun 2023) [FOLREL-565]
    • Sprint 171: Bugfix Release Deadline (4 Aug 2023) [FOLREL-581]

Development Meetings

  • Wed 24 May
  • Mon 29 May - cancelled
  • Wed 31 May

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Mon 29 May: Public Holiday

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

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 

(warning) - not ready

(question) - pending triage / planning


Sprint Focus


Planning Notes Template

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate


FEATURE

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2923 - Getting issue details... STATUS

  • Approach

    • should be able to add fields to
      • domain classes
      • migrations
    • check what happens to dataCreated
    • add metadata component to frontend
    • reuse PCI view
  • Components and Changes

    • Frontend: use stripes-components meta section in ui-agreements TitleView rather than custom meta

    • Backend: mod-agreements

  • Tests / Data / Dependencies

  • Known Unknowns

    • check what happens to dateCreated (could be first dateUpdated)
    • what happens with / how does GORM handle an change in collection?
    • does package get updated if title is updated? 
  • QA: snapshot | local | testing | other

    • risk of false positive / negative: check behaviour when no change has been made
  • Release Target: Poppy
  • Development Estimate: 1d

ERM-2919 - Getting issue details... STATUS

  • Approach

    • Truncate note to prevent ingest failure
    • Re-use or apply truncation pattern
  • Components and Changes

    • Backend: mod-agreements

  • QA: snapshot | local | testing | other

  • Release Target: Poppy
  • Development Estimate: <0.5d

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA




Release Tasks (Poppy)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes


ERM-2929 - Getting issue details... STATUS






Rolled Over From Previous Sprint


Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2641 - Getting issue details... STATUS

  • Current State
    • maven is back up, so unblicked
  • TODO
    • inspect hibernate and liquibase versions for discrepancies
  • Development Estimate
    • handover to Steve this week

ERM-2926 - Getting issue details... STATUS

  • Current State
  • TODO
  • Development