Versions Compared

Key

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

Sprint Goal / Focus 

  • ..

Sprint Schedule

  • Sprint: 166
  • Release: 2023.2 Poppy  
    • Sprint 8 of 9 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 167)
    • Sprint 168: Module Release Deadline (30 Jun 2023) [FOLREL-565]
    • Sprint 171: Bugfix Release Deadline (4 Aug 2023) [FOLREL-581]

Development Meetings

  • Wed 24 May
  • Mon 29 May - cancelled
  • Wed 31 May

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Mon 29 May: Public Holiday

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

jira


FEATURE

serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3890

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




No Feature

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

  • Triage

    • performance issues from inline edit, which can stop agreement loading
  • Approach
  • Scenario 4:
    • same behind-the-scenes behaviour (with minimal details to create agreement), but without taking user out of context 
    • won't be using existing agreement form
  • use query-parameter to not expand agreement lines in edit view (introduced in ERM-2888)
  • remove call that renders cards
  • implement basket changes
  • leave in place the mechanism that allows us to add agreement linesreview for deprecation once replacement functionality is described

    2923

    • Approach

      • should be able to add fields to
        • domain classes
        • migrations
      • check what happens to dataCreated
      • add metadata component to frontend
      • reuse PCI view
    • Components and Changes

      • Frontend: use stripes-components meta section in ui-agreements TitleView rather than custom meta

      • Backend: nonemod-agreements

    • Tests / Data / Dependencies

      • related: ERM-2892
      • update cypress test set up for ERM-2773
    • Known Unknowns: NA

    • QA: snapshot 

    • Known Unknowns

      • check what happens to dateCreated (could be first dateUpdated)
      • what happens with / how does GORM handle an change in collection?
      • does package get updated if title is updated? 
    • QA: snapshot | local | testing | other

      • risk of false positive / negative: check behaviour when no change has been made
    • Release Target: Poppy
    • Development Estimate: 1d

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

    Issue ID

    Sprint Backlog?

    • Approach

      • Truncate note to prevent ingest failure
      • Re-use or apply truncation pattern
    • Components and Changes

      • Backend: mod-agreements

    • QA: snapshot | local | testing | other

    • Release Target: Poppy
    • Development Estimate: 2d

    No Feature

    • <0.5d

    Tests

    Issue ID

    Sprint Backlog?

    Notes / Estimates / Actions

    NA




    Release Tasks (Poppy)

    Issue ID

    Sprint Backlog?

    Notes / Estimates / Actions

    NA



    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


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







    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
    keyERM-2641

    • Current State
      • license, SI and plugins seem to function
      • new issues arising with mod-agreements (liquibase, hibernate)
        • concern that they may have been missed previously
      • maven is back up, so unblicked
    • TODO
      • inspect hibernate and liquibase versions for discrepancies
    • Development Estimate
      • handover to Steve this week

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

    For Code Review

    • Current State
    • TODO
    • Development Estimate

    Jira Legacy
    serverSystem

    Jira

    JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-3890

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

    • Current State
      • TODO
      • Development Estimate
      • Triage

        • performance issues from inline edit, which can stop agreement loading
      • Approach
        • Scenario 4:
          • same behind-the-scenes behaviour (with minimal details to create agreement), but without taking user out of context 
          • won't be using existing agreement form
        • use query-parameter to not expand agreement lines in edit view (introduced in ERM-2888)
        • remove call that renders cards
        • implement basket changes
        • leave in place the mechanism that allows us to add agreement lines
          • review for deprecation once replacement functionality is described
      • Components and Changes

        • Frontend: ui-agreements

        • Backend: none

      • Tests / Data / Dependencies

        • related: ERM-2892
        • update cypress test set up for ERM-2773
      • Known Unknowns: NA

      • QA: snapshot 

      • Release Target: Poppy
      • Development Estimate: 2d

      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2903
    For Code Review
      • Scenarios 1-3 done
    • TODO
      • finish modal on scenario 4
    • Development Estimate
      • end of day





    Sprint Backlog

    Feature IDIssue IDSprint Backlog?

    Notes / Estimates / Actions


    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-2630
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-2905

    • Current State
      • ERM-2916 mostly done
    • TODO
      • ERM-2916 final 
      • ERM-2917 not started
    • Development Estimate: expected today

    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-4233

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

    For joint QA with Owen

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

    Ethan Freestone 
    • Current State
    • TODO: use useBatchedFetch hook
    • Development Estimate: Wed

    Blocked

    Feature IDIssue IDSprint Backlog?

    Notes / Estimates / Actions

    NA




    In QA

    Feature IDIssue IDSprint Backlog?

    Notes / Estimates / Actions

    NA

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

    Questions arising from QA/review

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



    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

    NA







    Bugfix Cycle

    Feature IDIssue IDSprint Backlog?

    Notes / Estimates / Actions

    NA







    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 = 1679 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 = 1679
    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 = 1679
    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 = 1679
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc