ERM Sprint 151

Owned by Jag Goraya
Last updated: Oct 28, 2022
3 min read

Sprint Goal / Focus

  • Nolana: Module Release Deadline

  • Orchid: Development Starts

Sprint Schedule

  • Sprint: 151
  • Release: 2022.3 Nolana  
    • Sprint 9 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
    • Sprint 151: Module Release Deadline [FOLREL-549]
      • Backend 26 Oct 2022
      • Frontend 28 Oct2022
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]
  • Release: 2023.1 Orchid  
    • Sprint 1 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 (2 Dec 2022) [FOLREL-???]

Development Meetings

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Monireh: AL 24-28 Oct

Lead Roles:

QA Environment: 

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


Planning Notes Template

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




FAT-82 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2263 - Getting issue details... STATUS

Monireh Rasouli 


ERM-2264 - Getting issue details... STATUS

Monireh Rasouli 


ERM-2265 - Getting issue details... STATUS

Monireh Rasouli 


ERM-2266 - Getting issue details... STATUS

Claudia Malzer 
ERM-2267 - Getting issue details... STATUS

Monireh Rasouli 


ERM-2268 - Getting issue details... STATUS

Claudia Malzer 


ERM-2269 - Getting issue details... STATUS

Monireh Rasouli 


ERM-2270 - Getting issue details... STATUS

Monireh Rasouli


ERM-2271 - Getting issue details... STATUS

Monireh Rasouli

ERM-2273 - Getting issue details... STATUS

Claudia Malzer 


ERM-2274 - Getting issue details... STATUS

Claudia Malzer 

ERM-2275 - Getting issue details... STATUS

Claudia Malzer 


No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2382 - Getting issue details... STATUS


  • Triage

    • no obvious reason why this should happen
    • could be stripes, could be memo-ising issue
    • kint-components / search and sort
  • Approach
    • q-index is grabbed from url
    • stripes might be memo-ising > timing / race condition issue
    • set another parameter to intercept

  • Components and Changes

    • Frontend: 

    • Backend: potentially a kint-components issue

  • Tests / Data / Dependencies.

  • Known Unknowns

    • not clear why it's triggering once q-index is not being replaced

  • QA: snapshot | local | testing | other

  • Development Estimate: 

    • timebox 1d

ERM-2387 - Getting issue details... STATUS

Peter Böhm 

  • Triage

  • Approach
    • Add package name to list of properties handled 

  • Components and Changes

    • Frontend: none

    • Backend: mod-agre