Skip to end of banner
Go to start of banner

ERM Sprint 161

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 

  • Bugfest 

Sprint Schedule

  • Sprint: 161
  • Release: 2023.1 Orchid  
    • Sprint 162: Bugfix Release Deadline (31 Mar 2023) [FOLREL-581]
  • Release: 2023.2 Poppy  
    • Sprint 2 of 8 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 166)
    • Sprint 168: Module Release Deadline (16 Jun 2023) [FOLREL-565]
    • Sprint 170: Bugfix Release Deadline (21 Jul 2023) [FOLREL-581]

Development Meetings

  • 15 Mar
  • 20 (Mid Sprint Review)
  • 22 Mar

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • NA

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

UXPROD-3861 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-1026 - Getting issue details... STATUS

(question)

ERM-1061 - Getting issue details... STATUS

(question)

ERM-1795 - Getting issue details... STATUS

(question)

ERM-2064 - Getting issue details... STATUS

(tick)

  • Triage

    • Not showing all the applicable validation messages
      • Potentially increase the drag and drop file upload space to accommodate
    • Currently: 
      • If upload error, could be displaying 3 messages
      • final form and validator behaviour clashes resulting in erroneous error behaviour
  • Approach
    • Move drop validation to toast message (to eliminate state-based error display)
    • Move logic to toast notification (callout rather than field validation)

  • Components and Changes

    • Frontend

    • Backend: none

  • Tests / Data / Dependencies / Known Unknowns: none

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate 

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2773 - Getting issue details... STATUS

(error)

ERM-2812 - Getting issue details... STATUS

(error)


Release Tasks (Orchid Bugfix)

Backend: 1d

Frontend: 2d

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2640 - Getting issue details... STATUS



ERM-2648 - Getting issue details... STATUS



ERM-2649 - Getting issue details... STATUS



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-2633 - Getting issue details... STATUS

ERM-2624 - Getting issue details... STATUS

ERM-2625 - Getting issue details... STATUS

Ethan Freestone 

  • Current State
    • In Code Review
  • TODO
  • Development Estimate

ERM-2612 - Getting issue details... STATUS

Ethan Freestone 

  • Current State
    • In Code Review
  • TODO
  • Development Estimate

ERM-2643 - Getting issue details... STATUS

Ethan Freestone 

  • Current State
    • In Code Review
    • Rhino removed
  • TODO
  • Development Estimate

ERM-2630 - Getting issue details... STATUS

Ethan Freestone 

  • Current State
    • Unlikely to be parallelised at this point
    • Confidence in how it will act in production service
    • Verified that can remove Remote KBs from domain model
    • Package ingest almost done
  • TODO
    • Finish package ingest from endpoint: make sure it can save to db
    • Issues to address around pushKB service
      • Separate (non-blocker) to package ingest development
    • Tweak title ingest and schema 
    • Refactor title and package ingest services
      • to ensure correctly attaching from outside package
    • Write external pushKb service (ERM-2631)
      • Unknown: how will a developer service work around this for debugging and developing?
      • May need enabling tooling to support development workflow
  • Development Estimate: 2 sprints


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions









Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2645 - Getting issue details... STATUS

Claudia Malzer 
  • Current State
    • Blocked
    • Want to avoid re-writing these by avoiding using the interactors (resulting in extra redundant patterns)
  • TODO
    • Needs conversation between Bienenvolk, AQA and Stripes Testing team to support reusable test data for unit and e2e tests across pre-prod and production environments. 
    • Could
      • make non-progress on tests that don't rely on date-picker 
      • try overriding selector (line 9)
      • if not, try writing new date-picker interactor 
        • create new interactor in stripes-erm-testing based on date-picker from stripes-testing
        • need to address a different way to grab data-div
        • add unit test (to support JEST debugging)
        • verify in cypress 
    • Unknowns
      • how to find which element is selected?
  • Development Estimate




In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


SI-12 - Getting issue details... STATUS

  Monireh Rasouli 

  • Current State
  • TODO
    • Filter the input by whitelist
      • In widget type form component
      • Use as field validator, employed from a reusable utils file in dashboard
    • Add URI encoding in form submission
  • Development Estimate
    • Wed


For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA





For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2506 - Getting issue details... STATUS




Bugfix Cycle

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

No Label

key summary type assignee status components
Refresh

  • No labels