Page History

Cate Boerema

• Chalmers visit was very productive - Have a clearer understanding of their must-have workflows. Uncovered some gaps which will be logged as features in JIRA and discussed with the relevant SIGs
• Need to decide on sprint review schedule during the holiday, as the normal cadence would have the next demo on Christmas day. Some options:
  • Tuesday Dec, 18
  • Thursday January 3
  • Tuesday January 8 (one week before release - too late?)
  • NOTE: Release is Monday January 14
• Risks:
  • Circulation is a very high risk area for Chalmers' ability to go live
    • In transit to home location (not to fulfill request) - This feature required lots of new plumbing and is at risk of not being completed in Q4. It is a pre-requisite for Fulfill pickup requests (see next bullet)
    • Fulfill pickup requests - This can't begin until In transit to home location (previous bullet) is complete. It is a very large feature and likely to not even be started in Q4.
    • Extending Loan Rules Editor to target additional policy types - Critical to the completion of Requests (request policies) and Patron notices (notice policies). Will likely need to be pushed to Q1.
    • Setup/configure patron notice logic (Patron Notices Policies) - Critical to the completion of patron notices. Likely to be pushed out of Q1.
    • Scheduler - Prerequisite for completion of patron notices and not started (wasn't actually targeted for Q4, but should have been)
• Cap plan model has been updated
  • Need to review feasibility of Q1 targets with POs and get back to Product Council and Chalmers with our findings

Jakub Skoczen

• Mid sprint 51

• Backend issues critical for completing functional work:

  • CIRC-154: check-in by barcode API (IN PROGRESS by William, to be handed off to Marc). William will issue a PR today and Marc will handle the review and any remaining work, once completed it will allow to unblock CIRC-146

  • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS handed over from Jeremy to Marc). Emma, Marc and I had a good meeting about specific uses cases and requirements not flashed out earlier (e.g repeated check-in/scan). We have also discussed extensions to handle pickup requests (a backend prerequisite for  UXPROD-118), they seem quite manageable and contained but we decided that they will not be in scope for CIRC-146 to avoid putting UPROD-601 under threat.

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN PROGRESS re-assigned to Kurt from Jeremy) required to complete UIU-485

  • CIRC-151: Make mod-circulation Service Point enabled (DONE, Kurt)

  • CIRC-156: dereference patron group ID to display the name along with the request (IN CODE REVIEW, Kurt) no longer blocks UIREQ-114, needs handling of permissions

  • UIREQ-144: Aditya has completed development work and put the issue IN REVIEW
    
    

• Cross team

  • Kick-off meeting about the PubSub support in FOLIO based on the earlier proposal from Adam and Jakub happened last Wednesday, it has been decided that the proposal meets EPAMs requirement and the EPAM team will move ahead with implementation of mod-pubsub and "scope" functionality in Okapi.
    https://docs.google.com/document/d/1L0qJ6VEmlKU4UCfznnc7du9qPZpjVq3DhcW68leIgEY/edit
    
    

• OKAPI/RMB, performance NFRs

• MODINVSTOR-215: During the meeting with EPAM Postgres experts on Tuesday it has been decided that Julian will continue with a solution similar to what has been proposed and he will implement the solution in RMB. The Core Team will not need more support from EPAM. (see RMB-301)

• Adam is working on reference data loading; RMB-296 and MODINVSTOR-216
  
  

• Devops:

  • FOLIO-1577: Created automated builds for 'next-release' (IN PROGRESS, John) – there were missing releases blocking completion of this issue and it has become the focus of the last devops call. We have decided that it is not devops responsibility to request specific backend or front-end module releases, on the contrary – new "next-release" builds should be triggered by availability of new module releases. The specific dependency issues that prevent the current build are being investigated by Marc and John. We have decided to put additional guards in place to ensure that future releases are free from those dependency issues (OKAPI

  • FOLIO-1548: Create a lighter-weight folio/testing-backend VM – the SPIKE has concluded and the approach is to slim down the Vagrant VM and provide ability to load additional modules dynamicall (STCLI-15, STCLI-114)

Cate Boerema

• 15% reduction in Q4 features since last week (124 to 106). Many in deferrals in Acquisitions, but in other areas as well. See PO updates section for details on what was moved and why.
• POs have flagged Q4 features that are at risk of being deferred or split. Full list of at-risk Q4 issues is here:

  Jira
  server FOLIO Issue Tracker jqlQuery project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND Status != Closed AND fixVersion = "Q4 2018" AND labels in (Q42018-at-risk, Q42018-will-split) count true serverId 6ccf3fe4-3301-368a-983e-20c466b11a49

  See Chalmers section of this page for the Chalmers go-live features that are at-risk.
• Cate, Ann-Marie and Khalilah are at Chalmers this week aligning around a new timeline and working to ensure Chalmers' needs are understood.

• Chalmers section of this report has been updated, as has the Chalmers Release Dashboard in JIRA. Roughly the same content as before but organized differently so we could make use of more dynamic updates.

Jakub Skoczen

• Started sprint 51

• Backend issues critical for completing functional work:

  • CIRC-104: store checkin/checkout SP with the loan (DONE by Jeremy)
    

  • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS by Jeremy, blocks UICHCKIN-17) is now blocked on CIRC-154 ("design and implement a "check-in-by-barcode" API)

  • CIRC-154: Marc has proposed an API for the checkout-by-barcode operation (IN PROGRESS by Jeremy)

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN CODE REVIEW, Jeremy) a follow up to CIRC-104

  • CIRC-151: Make mod-circulation Service Point enabled (DONE, Kurt, blocks UIREQ-114 and UIU-485

  • CIRC-156: dereference patron group ID to display the name along with the request (IN PROGRESS, Kurt, blocks UIREQ-114)

  • UIREQ-144: includes more requirements about the needed extensions to the circulation APIs (hold shelf expiration date)
    
    
• Cross team

  • Loan policy/rules and opening hours integration – discussing the design with Sean, Julian and Filip

  • Wednesday: Kick-off meeting about the PubSub support in FOLIO based on the earlier proposal from Adam and Jakub
    https://docs.google.com/document/d/1L0qJ6VEmlKU4UCfznnc7du9qPZpjVq3DhcW68leIgEY/edit
    
    

• OKAPI/RMB, performance NFRs

• MODINVSTOR-215: meeting with EPAM Postgres experts on Tuesday, Heikki is down pneumonia and Julian is looking into the issue while he is gone

• FOLIO-1519: SPIKE: how to load sample and reference data? (DONE, Adam), resulted in two issues that Adam is working on: RMB-296 and MODINVSTOR-216
  
  

• Devops:

• FOLIO-1596: Re-enable platform builds for all ui-* modules PRs in CI (DONE, John)

• FOLIO-1597: Add module dependency resolution quality gate for PRs in CI (DONE, John)

• FOLIO-1577: Created automated builds for 'next-release' (BLOCKED, John) – this will likely be an early approach to the Q4 builds and env

• FOLIO-1548: Create a lighter-weight folio/testing-backend VM (Wayne)

Cate Boerema

• PO deadline for first pass at Q1 targets is end of week. Features that are clearly not going to make Q4 may be moved to Q1 as part of this effort. POs will update on this report if there is feature slippage.
• POs will also be tagging Q4 features that are at risk for deferment or splitting by end of week so we can get a better sense for how we are tracking. I'll link some reports to this page once the tagging is complete. Many features appear to be slipping. Some at-risk themes from Circulation: request fulfillment, In transit to home location, patron notices, title level requests etc.
• Updated the Chalmers table below based on the latest rankings - a couple of new epics appear in the table, as they contain 1 or more feature now needed for go-live
• Theodor will work with Chalmers to revisit their go-live features again to make sure they are accurate and (potentially) reduce scope

• Cate, Ann-Marie, Khalilah and Theodor will be at Chalmers next week. Top priority: review existing functionality in detail (demos), identify gaps, determine if gaps are represented in the UXPROD backlog and prioritized appropriately.  This will ensure we are clear on priorities.

• Spoke with Victoria Rabykina (new scrum master) who highlighted some issues with our JIRA maintenance (stories without features, features without stories, too many features). I talked her through the UXPROD "rules" and she'll be following up with her POs to get things cleaned up. She may also have some good ideas for new reports and processes .

Jakub Skoczen

• Started sprint 51

• Backend issues critical for completing functional work:

  • CIRC-104: store checkin/checkout SP with the loan (DONE by Jeremy)
    

  • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS by Jeremy, blocks UICHCKIN-17) is now blocked on CIRC-154 ("design and implement a "check-in-by-barcode" API)

  • CIRC-154: Marc has proposed an API for the checkout-by-barcode operation (IN PROGRESS by Jeremy)

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN CODE REVIEW, Jeremy) a follow up to CIRC-104

  • CIRC-151: Make mod-circulation Service Point enabled (DONE, Kurt, blocks UIREQ-114 and UIU-485)

  • CIRC-156: dereference patron group ID to display the name along with the request (IN PROGRESS, Kurt, blocks UIREQ-114)

  • UIREQ-144: includes more requirements about the needed extensions to the circulation APIs (hold shelf expiration date)

  • Loan policy/rules and opening hours integration – figuring out a model of collaboration and support between Vega and the core team.

  • Reporting team has requested improvements to certain API docs (FOLIO-1556 and FOLIO-1557)

• OKAPI/RMB, performance NFRs

• MODINVSTOR-215: meeting with EPAM Postgres experts on Tuesday, Heikki is down pneumonia and Julian is looking into the issue while he is gone

• FOLIO-1519: SPIKE: how to load sample and reference data? (DONE, Adam), resulted in two issues that Adam is working on: RMB-296 and MODINVSTOR-216

• Devops:

• FOLIO-1596: Re-enable platform builds for all ui-* modules PRs in CI (IN REVIEW, John)

• FOLIO-1597: Add module dependency resolution quality gate for PRs in CI (IN REVIEW, John)

• FOLIO-1577: Created automated builds for 'next-release' (BLOCKED, John) – this will likely be an early approach to the Q4 builds and env

• FOLIO-1548: Create a lighter-weight folio/testing-backend VM (Wayne)

• QA

  • Anton and Jakub discussed the work being done in the three most critical areas for quality:
    • Release management (being addressed by core DevOps and specifically FOLIO-1577)
    • Performance (being addressed by Julian and Heikki, more communication needed with Hongwei/Varun and help w MODINVSTOR-215)
    • Unit test coverage for core UI modules (being addressed by stripes-force for ui-inventory)

Jakub Skoczen

• Mid sprint 50

• Backend issues critical for completing functional work:

  • CIRC-104: store checkin/checkout SP with the loan (IN CODE REVIEW by Jeremy)
    

  • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS by Jeremy, blocks UICHCKIN-17) is now blocked on CIRC-154 ("design and implement a "check-in-by-barcode" API)

  • CIRC-154: Marc has proposed an API for the checkout-by-barcode operation (IN PROGRESS by Jeremy)

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN CODE REVIEW, Jeremy) a follow up to CIRC-104

  • CIRC-151: Make mod-circulation Service Point enabled (IN CODE REVIEW, Kurt, blocks UIREQ-114 and UIU-485)

  • CIRC-156: dereference patron group ID to display the name along with the request (Kurt, blocks UIREQ-114)

  • UIREQ-144: includes more requirements about the needed extensions to the circulation APIs (hold shelf expiration date)

  • Loan policy/rules and opening hours integration – figuring out a model of collaboration and support between Vega and the core team.

  • Reporting team has requested improvements to certain API docs (FOLIO-1556 and FOLIO-1557)

• OKAPI/RMB, performance NFRs

• Postgres performance optimisation (Inventory search) has hit a roadblock with certain kinds of queries not using an index. Heikki is working on a test case isolated from the FOLIO code base (see MODINVSTOR-215) and we will be looking for help from a Postgres experts.

• FOLIO-1519: SPIKE: how to load sample and reference data? (IN PROGRESS, Adam)

• Devops:

• FOLIO-1596: Re-enable platform builds for all ui-* modules PRs in CI (IN REVIEW, John)

• FOLIO-1597: Add module dependency resolution quality gate for PRs in CI (IN REVIEW, John)

• FOLIO-1577: Created automated builds for 'next-release' (BLOCKED, John) – this will likely be an early approach to the Q4 builds and env

• FOLIO-1548: Create a lighter-weight folio/testing-backend VM (Wayne)

• QA

  • Anton and Jakub discussed the work being done in the three most critical areas for quality:
    • Release management (being addressed by core DevOps and specifically FOLIO-1577)
    • Performance (being addressed by Julian and Heikki, more communication needed with Hongwei/Varun and help w MODINVSTOR-215)
    • Unit test coverage for core UI modules (being addressed by stripes-force for ui-inventory)

Cate Boerema

• Deadline for early adopter rankings is end of week (November 2nd)
• Once rankings are complete, gap analysis team will need to discuss how best to approach Q1 planning
• E-Resource Usage data and related reporting features and Q4 targets have been revised by the Leipzig team - will want to update the Cap plan to incorporate these (can wait until after the early adopter rankings have been completed)
• Risks:
  • Requirements continue to be a risk for Vega team commitments: Title-level requests, Extending Loan Rules Editor to target additional policy types, Patron notice policy. Paging requests discussions have progressed well. Backlog should be available by middle of next week.
  • Complex data modeling in circulation is blocking many stories (circulation status, service point logging and display etc) - As a result, almost all of Core team unassigned backlog is blocked. To keep the UI developers busy, we have begun tagging "ui-only" stories and bugs for them to work on while they wait for things to be unblocked (these are not always top priority changes).
  • Scheduler is a key piece of infrastructure that is blocking important circulation work (e.g. Recently returned, Setup/configure patron notice logic (Patron Notices Policies),  Automatically Anonymizing/Scrubbing Loan Data (through Settings) and Request statuses "Closed - pickup expired" and "Closed - unfilled"). Scheduler is currently not targeted for Q4 which means features will continued to be blocked well into Q1.

Cate Boerema

Release Planning:

• Working to bring the Core team's commitments down to a more manageable level while at the same time making progress on Chalmers' production pilot needs:

• Have adjusted Core team resources so more functional work can be accommodated:

  • Moved some bandwidth off platform (Stripes and OKAPI) onto functional features

  • Allocated time for Marc Johnson who should be returning at beginning of November

• Have agreed to offload some features from the Core team to Vega. Specifically: Title-level requests, Paging requests, Loan Policy: Impact on loans part 2 (Q4 2018 release), Extending Loan Rules Editor to target additional policy types, Patron notice policy AND Loans: Policy Overrides (this last one was proposed only today and still needs to be discussed with the relevant POs (Khalilah and Emma).

• Risks:

• Requirements - Backlog is sparse to non-existent for many of these features. Patron notice policy requirements have stalled due to lack of clarity on request policies. It is likely that several Vega features will not complete in Q4 due to lack of requirements. Specifically: Title-level requests, Extending Loan Rules Editor to target additional policy types, Patron notice policy

• Library Opening Hours Calendar - This feature is used by Loan Policy: Impact on loans part 2. Adjustments to calendar API endpoint will likely be needed and Qulto doesn't have sufficient time remaining to complete the work. Vega will be asked to make the required changes instead.

• Annika Schröer will be revising the E-Resource Usage data and related reporting features targeted for Q4.

Cate Boerema

Release Planning:

• Working to bring the Core team's commitments down to a more manageable level while at the same time making progress on Chalmers' production pilot needs:

• Have adjusted Core team resources so more functional work can be accommodated:

  • Moved some bandwidth off platform (Stripes and OKAPI) onto functional features

  • Allocated time for Marc Johnson who should be returning at beginning of November

• Have agreed to offload some features from the Core team to Vega. Specifically: Title-level requests, Paging requests, Loan Policy: Impact on loans part 2 (Q4 2018 release), Extending Loan Rules Editor to target additional policy types, Patron notice policy AND Loans: Policy Overrides

• Risks:

• Requirements - Backlog is sparse to non-existent for many of these features. Patron notice policy requirements have stalled due to lack of clarity on request policies. It is likely that several Vega features will not complete in Q4 due to lack of requirements. Specifically: Title-level requests, Extending Loan Rules Editor to target additional policy types, Patron notice policy

• Library Opening Hours Calendar - This feature is used by Loan Policy: Impact on loans part 2. Adjustments to calendar API endpoint will likely be needed and Qulto doesn't have sufficient time remaining to complete the work. Vega will be asked to make the required changes instead.

• Annika Schröer will be revising the E-Resource Usage data and related reporting features targeted for Q4.

Cate Boerema

• Working to bring the Core team's commitments down to a more manageable level while at the same time making progress on Chalmers' go-live needs:

  • Have agreed to offload some features from the Core team to Vega. Specifically: Title-level requests, Paging requests, Loan Policy: Impact on loans part 2 (Q4 2018 release), Extending Loan Rules Editor to target additional policy types and Patron notice policy

    • Goal is for Vega to begin work on these in sprints 50 - 51 (after completion of Local password management)

    • Risks:

      • Requirements - Backlog is sparse to non-existent for many of these features. Sean and Darcy will be working hard to get backlogs in place. Tania will receive support in getting the Requests stories in place (Cate, Mark Keepper etc)

      • Library Opening Hours Calendar - This feature is used by Loan Policy: Impact on loans part 2 and will need adjustments based on the requirements analysis being done by Sean Thomas. How quickly can Qulto deliver the needed changes (their contract ends at the end of October)?

  • Capacity plan is being updated

    • Have made adjustments to the Core team resources to reflect team member leave of absence, increased allocations on Camunda PoC (from 6 to 15 days) and the fact that many backend developers work almost exclusively on OKAPI and NFRs.

    • Mark Veksler is re-running the cap plan with the new information to get a better picture of what can be accomplished by Core

  • Jakub, Mark V, Anton, Mike Gorrell and Cate are meeting tomorrow to discuss how to prioritize and plan for NFRs

Cate Boerema

• Baseline set of Q4 features established (20 + Acquisitions features have been removed due to resource constraints). This list will need to change further to reflect changes to:

  • Team makeup - Core team member leave of absence. What impact will that have on committed features?
  • Resource allocation
    • Allocation to Camunda PoC seems to have increased - what effect will that have on Core team deliverables?
    • Can we offload circulation features needed by Chalmers to go live from Core to Vega? For example, UXPROD-272, UXPROD-1061, UXPROD-744, UXPROD-1217 and UXPROD-676. What impact would that have on the plans for password management and ERM support?
  • Release milestones - Need to review the release milestones (e.g. feature freeze) and make sure we haven't overestimated the amount of development time we have available to us in the quarter
  • NFRs - Based on conversations with Jakub, it seems like we are not allocating sufficient time for the necessary NFR work in the cap plan
• No backlog exists for Request features needed by Chalmers to go live. Tania doesn't have bandwidth anymore and Darcy was interested in taking over, but has Patron notice work remaining. Marc Keepper offered to help out writing some stories, but he is on vacation for the next two weeks. I will see if Tania and I can get at least a couple stories written in the meantime.
• Many features needed by Chalmers to go live are not targeted for Q4, meaning they will not be ready for January go live. Chalmers is reviewing their rankings (some of the features may not actually be needed for go live). EBSCO/Chalmers meeting planned for Nov to discuss priorities, workarounds and implementation plan.