Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Goal / Focus 

  •  

Sprint Schedule

  • Sprint: 177
  • Release: 2023.2 Poppy 
    • Sprint 178: Bugfix Release Deadline (10 Nov 2023) [FOLREL-581]
  • Release: 2024.1 Quesnalia 
    • Sprint 3 of 11 since Release Development Cycle Starts (Sprint 176) to Feature Freeze (Sprint 186: 15 Mar 2024)
    • Sprint 187: Module Release Deadline (22 Mar 2024) [FOLREL-565]
    • Sprint 189: Bugfix Release Deadline (19 Apr 2024) [FOLREL-581]

Development Meetings

  • Wed 8 Nov
  • Mon 13 Nov
  • Wed 15 Nov

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present


Info
titlePlanning 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

Table of Contents

Expand
titleSprint 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


Info
iconfalse
titlePlanning Notes Template
  • 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

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3085


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2631

  • Triage

  • Approach
    • set up new open source project in K-Int gitlab
    • new micronaut service required (not using okapi or grails)
    • set up a test instance
    • will need a different dev workflow (probably using local copy of service)
    • working title: pushkb
    • avoid storing caches of transient data
  • Components and Changes

    • Frontend: na

    • Backend: new

  • Tests / Data / Dependencies

    • Align to when GBV start testing and using pushkb endpoint
    • ERM-3048 Possible package schema changes  with endpoint changes
  • Known Unknowns

    • should be (but not clear yet) about TitleInstance Resolver
    • packageSchemaUpdater: potential conflicts when there are multiple copies of schemas in play where backwards compatibility is broken
  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia
  • Development Estimate

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3078

Ethan or Jack
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia
  • Development Estimate: <2 day

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3091
 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3092

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3093

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2792

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2793
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia
  • Development Estimate: 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3089
  • Triage: Needed

  • Release Target: Quesnalia
  • Development Estimate: 

Tests

NA

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2813



Release Tasks (
Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3094

TBC whether this needs to be applied to Poppy as well as Quesnalia.

Depends on when refresh token rotation is introduced.







Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3084


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3070


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3067


Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3095




Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes


Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3063

(minus)


Rolled Over From Previous Sprint


Info
titlePlanning Notes Template
  • Current State
  • TODO
  • Development Estimate

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySI-34

Mostly done - needs testing once environment restored

Needs input from Steve






Sprint Backlog

Jira Jira3063
Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3082

Waiting for snapshot to be clear of ERM backlog


Jira Legacy
serverSystem

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-

3073

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3073


Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA




In QA


Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySI-41


Need to work out testing strategy

Likely defer until SI-34 is ready to QA also.


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










Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions








Sprint Summary

ERM

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels != release and labels in (licenses, agreements, erm) and Sprint = 1991 and issuetype in standardIssueTypes()
serverId01505d01-b853-3c2e-90f1-ee9b165564fc


Dashboard

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels = dashboard and Sprint = 1991
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components,labels
columnskey,summary,type,assignee,status,components,labels
maximumIssues20
jqlQuery(labels = release or labels not in (licenses, agreements, erm, dashboard)) and Sprint = 1991
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

No Label

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels is empty and Sprint = 1991
serverId01505d01-b853-3c2e-90f1-ee9b165564fc