ERM Sprint 154

Sprint Goal / Focus

  • Nolana: NA

  • Orchid: ??

Sprint Schedule

  • Sprint: 154
  • Release: 2022.2 Morning Glory  
    • Sprint: Hotfix Release Deadline (2 Dec 2022) [FOLREL-536]
  • Release: 2022.3 Nolana  
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]
  • Release: 2023.1 Orchid  
    • Sprint 4 of 8 since Release Development Cycle Starts (Sprint 151) to Feature Freeze (Sprint 158)
    • Sprint 159: Module Release Deadline [FOLREL-???]
      • Backend 22 Feb 2023
      • Frontend 24 Feb 2023
    • Sprint: Bugfix Release Deadline (31 Mar 2023) [FOLREL-???]

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Monireh: Sick 28 Nov

Lead Roles:

QA Environment: 

  • folio-snapshot

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

  • Development Estimate

UXPROD-3147 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2417 - Getting issue details... STATUS

See issue comments for example

Requires ERM-2416