Skip to end of banner
Go to start of banner

ERM Sprint 166

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

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 Availability: Schedule | 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

Jack Golding 

  • 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-erm-components metadata component in ui-agreements TitleView

    • 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

Ethan Freestone 

  • 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










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

Ethan Freestone 

  • 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

Claudia Malzer   

  • Current State
  • TODO
  • Development Estimate

UXPROD-3890 - Getting issue details... STATUS

ERM-2421 - Getting issue details... STATUS

Jack Golding 

  • Current State
    • Scenarios 1-3 done
  • TODO
    • finish modal on scenario 4
  • Development Estimate
    • end of day





Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2630 - Getting issue details... STATUS / ERM-2905 - Getting issue details... STATUS

(question) Ethan Freestone 

  • Current State
    • ERM-2916 mostly done
  • TODO
    • ERM-2916 final 
    • ERM-2917 not started
  • Development Estimate: expected today

UXPROD-4233 - Getting issue details... STATUS

ERM-2918 - Getting issue details... STATUS

Ethan Freestone 

For joint QA with Owen

ERM-2920 - Getting issue details... STATUS


  • Current State
  • TODO: use useBatchedFetch hook
  • Development Estimate: Wed

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA




In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA

ERM-2790 - Getting issue details... STATUS

Owen Stephens 

Questions arising from QA/review

ERM-2903 - Getting issue details... STATUS

Owen Stephens



For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA






For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA







Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA






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 labels
Refresh

No Label

key summary type assignee status components
Refresh

  • No labels