Versions Compared

Key

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

...

Report Date

Overall Status Update

Q4 Feature Count on Report Date



FunctionalNFR
2018-12-11

Jakub Skoczen

  • Started sprint 53

  • Functional work items update: (Q4 work has been completed)

  • Q4 Release Management updates:

  • OKAPI/RMB, Performance NFRs

    • Performance: MODINVSTOR-215/RMB-301 (IN PROGRESS), more delays, Julian's ETA is later today or tomorrow

    • Performance: no progress on performance issues assigned to William and Jeremy (TAMU).
      • William has been delegated to other tasks this week and is unlikely to be back working on FOLIO in Q1/Q2.
      • Jeremy will be unable to do more work on FOLIO this week and will be working in smaller capacity (to be determined)

Jakub Skoczen

  • Started sprint 53

  • Functional work items update:

    • CIRC-154: check-in by barcode API (DONE, Marc)

    • CIRC-146: Change status to "in transit" upon check-in (DONE, Marc)

    • Above means that all UXPROD-601 stories are now completed and wait for review (UICHKIN-17, UICHKIN-40, UICHKIN-41, UICHKIN-46, UICHKIN-60)
    • UXPROD-118 work, considered at risk, will go ahead in Q4 (Dec/Jan) but likely we will decide against shipping it with Q4
    • CIRC-150: validation of check-in/check-out SP during loan CRUD (DONE , Kurt) required for UIU-485 (IN REVIEW, Aditya)

    • CIRC-156: dereference patron group ID to display the name along with the request (DONE, Kurt) UIREQ-114 is now IN REVIEW

  • Q4 Release Management updates:

    • mod-feefines is required by FOLIO core modules (ui-users) but the release has not been made on time. CT made an out-of-band release. Trying to communicate with UNAM on the matter.
    • External modules (Acq, ERM, MarcCat, etc) release deadline was last Friday (2018-12-07), most modules have been released on time but there are cases where some releases have not been made properly (Acq) or are still pending (mod/ui-marccat, ui-licences). CT is communicating with the POs and leads to try to help with those releases.
    • This Friday (2018-12-14) is core UI modules release deadline. After all core UI modules are released, the DevOps team will attempt to build a fresh Q4 environment (most likely Monday 2018-12-17). The deadline for creating the environment is on Friday
    • Q4 Release Management: all modules, interfaces (APIs) and their Q4 versions are tracked in this spreadsheet (updated at real-time):
      https://docs.google.com/spreadsheets/d/1m966Ch822PUtsdvo01mS605ndB08ZhT7RRP3tnBRuX0/edit
    • Q4 Release is going according to plan:
      https://docs.google.com/spreadsheets/d/1-4fMUyfnMhaMoJuEiwaABGu7ZzePvzhjya-nyV3dvvs/edit#gid=0

  • OKAPI/RMB, Performance NFRs

    • Performance: MODINVSTOR-215: Julian implements solution agreed with EPAM DBAs throuh RMB-301 (IN PROGRESS), unfortunately no status since last week.

    • Starting from this week and intensifying next week core back-enders will focus on various performance issues (Adam, Julian, Jeremy, William). Heikki is going to be away until the end of the year. Nassib will act as a partial replacement.
    • Reference data loading functionality RMB-296 (DONE) and initial implementation in one of the modules (mod-inventory-storage) MODINVSTOR-216) is completed. We have decided against shipping the functionality in Q4 due to necessary deployment changes. It will be shipped with Q1 and all modules will be updated to implement this functionality.

  • Devops:

    • Two new environments created: snapshot-core and snapshot-stable-core, with core modules only to allow for API updates

    • Working on non-standard deployment procedure to included edge-oai-pmh module in Q4, we will adress the tech debt around this in Q1.
    • FOLIO-1577: as mentioned above, an attempt to create Q4 environment will be made on Monday, Okapi can now generate a dependency graph to ease tracking dependency problems

    • FOLIO-1548: STCLI-114 IN PROGRESS (ability to run modules locally and have them communicate with the black-box)

  • Quality/Testing:
    • Initial test coverage for nightmare (integration) UI tests has been completed for selected modules (ui-users) and shows coverage on the level of 30% percent. More work is needed to capture full coverage across core FOLIO modules. This work is grouped under FOLIO-1618, tasks will be handed out from next week.

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-12-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-12-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-12-04

Cate Boerema

  • Index Data having company meetup so I am running the Core team roundups
  • Gap analysis team is working very hard to get the Q1 planning in place. This means:
    • UXPROD feature refactoring
    • Feature distribution across teams
    • Feature estimating
  • Risk: there is a LOT of concurrent circulation work that needs to happen. We need to be very careful about how this is distributed across teams.
  • Goal is to have the cap plan updated tomorrow

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-12-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-12-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-11-27

Cate Boerema

  • Several Core team Q4 features are at risk, but I am reluctant to move them out of the quarter, as we are hoping we can make at least some progress before feature freeze. POs for other teams are probably doing the same. Here's the full list of at-risk features across teams. There are 22 (of the total 107 targeted).
  • I have tagged the features and stories coming out of the November Chalmers visit. View the list here.
  • Circulation is still a risk area for Chalmers go-live. Specifically:
    • Request policy still be designed (re-designed) and some elements may be moving to the Loan policy. Cate, Sean and Tania working to get this nailed down for the developers asap
    • While some aspects of circulation are independent enough to be worked by a team other teams (e.g. loan and request policy CRUD, extending the loan rules editor) making these new policies effective will really need to be done by the Core team.
    • Making policies effective needs to be done in exactly the same code being modified for other ongoing circulation features such as in transit to home location and fulfilling pickup requests. Not a lot of work can be done concurrently here.
    • Title requests - still not clear what the plan is here.
    • Library opening hours calendar - Sean is finding bugs and issues with this Qulto-developed app. Which team is responsible for maintaining it? Sean would be the best fit from a PO perspective given his other features are primary consumers of calendar data.
    • Here is a list of circ related features likely needed by Chalmers to go live which will need to carry over in some form to Q1. The list is long and there are dependencies.
  • Leipzig is hosting a self-built article index and are providing the data to a number of German libraries, most of them using vuFind discovery systems (are mostly hosted by Leipzig). The infrastructure/community is named finc. They are now getting ready to re-implement their configuration software on FOLIO. The code will of course be open source and re-usable, if there are any institutions interested in this kind of set-up. I have implemented a JIRA project (UIFC) for them to track their requirements.

Jakub Skoczen

  • Started sprint 52

  • Backend issues critical for completing functional work:

    • CIRC-154: check-in by barcode API (IN PROGRESS by Marc) will be completed by the end of the week.

    • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS byt Marc) will be completed by the end of the week.

    • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN PROGRESS by Kurt) required for UIU-485, will be completed by the end of the day

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

  • Cross team


  • OKAPI/RMB, Performance NFRs

    • MODINVSTOR-215: Julian implements solution agreed with EPAM DBAs, see RMB-301 (IN PROGRESS)

    • Adam is working on reference data loading; RMB-296 (DONE) and MODINVSTOR-216 (IN PROGRESS)

  • Devops:

    • FOLIO-1577: two new Okapi feature implemented (OKAPI-683 and OKAPI-684) to better report dependency issues and catch unreleased dependencies at release time. John will perform a Q4 build on Monday (2018-12-03)

    • FOLIO-1548: STCLI-15 completed, STCLI-114 (ability to run modules locally and have them communicate with the black-box) starting

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-11-27) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-11-27) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-11-20

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:
  • 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

  • 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)

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-11-20) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-11-20) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-11-13

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
    serverFOLIO Issue Tracker
    jqlQueryproject = 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)
    counttrue
    serverId6ccf3fe4-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
  • 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)

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-11-13) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-11-13) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-11-06

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)

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-11-06) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-11-06) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-10-30

Cate Boerema


Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-30) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-10-30) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-10-23

Cate Boerema

Release Planning:




  • Discussed Loan Policies integration with the Opening Hours module with Sean (PO, EBSCO) and Istvan (Qulto). We discussed two options to proceed:

    • Extending Opening Hours module with endpoints to calculate loan periods

    • Performing calculation within mod-circulation using existing endpoints from the Opening Hours module

    • Both are viable solution and would be developed by the Vega team

  • Discussed next steps for FOLIO CI environments with the following conclusions:

    • Short-term: introduce PR build and “previews” to catch issues early before they reach master branches of individual projects, to catch dependency issues at PR time, allow POs to review features before they are merged to master branches

    • Long-term: we have identified a need for a truly clustered, multi-tenant CI/CD environment to address both the functional (e.g ability to run multiple versions of the same module to support different UI configurations and allow developers to “hot plug” modules) and non-functional (scalability problems that the current environments face). We have discussed that the current devops resource gap will not allow us to make substantial progress on building the env in Q4 so we will begin with a technical design for such environment.

More information: https://issues.folio.org/browse/FOLIO-1550?focusedCommentId=38292&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-38292

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-23) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-10-23) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-10-23

Cate Boerema

Release Planning:




  • Discussed Loan Policies integration with the Opening Hours module with Sean (PO, EBSCO) and Istvan (Qulto). We discussed two options to proceed:

    • Extending Opening Hours module with endpoints to calculate loan periods

    • Performing calculation within mod-circulation using existing endpoints from the Opening Hours module

    • Both are viable solution and would be developed by the Vega team

  • Discussed next steps for FOLIO CI environments with the following conclusions:

    • Short-term: introduce PR build and “previews” to catch issues early before they reach master branches of individual projects, to catch dependency issues at PR time, allow POs to review features before they are merged to master branches

    • Long-term: we have identified a need for a truly clustered, multi-tenant CI/CD environment to address both the functional (e.g ability to run multiple versions of the same module to support different UI configurations and allow developers to “hot plug” modules) and non-functional (scalability problems that the current environments face). We have discussed that the current devops resource gap will not allow us to make substantial progress on building the env in Q4 so we will begin with a technical design for such environment.

More information: https://issues.folio.org/browse/FOLIO-1550?focusedCommentId=38292&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-38292

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-23) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-10-23) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-10-16

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

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-16) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-10-16) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2018-10-09

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
    • 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.

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-09) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49


Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2018" ON (2018-10-09) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

...