Sprint Goal / Focus 

  • Bugfest from 6 Mar

Sprint Schedule

  • Sprint: 160
  • 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

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • NA

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present


  • 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

  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

Implementation tasks should be added directly into the Jira issue


Sprint Focus


  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate


No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Orchid Bugfix)

Backend: 1d

Frontend: 2d

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

(minus)


(minus)

(minus)

Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

(error)Will need time from Steve

  • Triage

    • Dependency of a dependency
    • No update for groovy-handlebars-engine
      • no clear alternative available
      • not clear why we're using this one
    • Potentially an issue for Reshare also
  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

    • groovy-handlebars-engine library not updated since 2014
  • QA: snapshot 

  • Release Target: Orchid Bugfix
  • Development Estimate


Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes














Rolled Over From Previous Sprint


  • Current State
  • TODO
  • Development Estimate

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions


In Code Review

  • Current State
    • behaviour different in OA, poss because different version
    • shouldn't affect us because of GORM intermediation
  • TODO
    • if no resolution by end of day, then will attempt to minor/patch bump version of Grails and then hibernate
  • Development Estimate
    • 1d


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


  • Current State
    • Will not be done
  • TODO
    • Feedback to reporter
    • Close
  • Development Estimate: NA

  • Current State: Unstarted (releases/dependencies)
  • TODO
    • Design analysis to work out approach and options
  • Development Estimate: Review Monday

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Monireh Rasouli 
  • Current State
    • Got rid of some errors
    • Continuing to get http errors
      • check in postman what's received vs what's sent
    • Shape needs to be different when adding v removing
  • TODO
    • Rewrite story to not assume multiselect (OS) (tick)
    • Fix errors
    • Move location of Content Type to above Alternative Names
    • Check shape
    • Add new tests
    • Check changes to view screen based on user feedback
  • Development Estimate: 2d

In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Closed


For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions



Revisit after ERM-2630 is explored


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions








Sprint Summary

ERM


Dashboard

Other

No Label