2023-09-13 Meeting notes

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
Roadmap page updates

Publishing the Roadmap - post slides as a PDF to Roadmap page?  Turn previous roadmap page into a "historic" version.  Show the 4 top level view slides on page, link to pdf of all slide, link to dashboards.  Explore deeper dive by development teams as FOLIO Forum or elsewhere - as "future session" above.

FOLIO Roadmap


Prioritization

Prioritization Process(es) - next meeting - discuss next steps

Not planning to put a large prioritization process in place

Frame why this is necessary or beneficial:

  • New libraries are sometimes driving the development priorities.
  • Existing libraries have on-going gaps/blocks that were never resolved and have new ideas

How much time/effort compared to the outcome?

  • Can we put a lighter weight process in place 
  • Even new idea feature description can take a lot of time and intellectual effort - can we find easier ways to do this?
    • To have full descriptions of features
    • UX concerns
    • Way to revisit these if they have been sitting a long time - to address platform, UX, other changes that impact the feature. (more than 18 moths old?)
  • Implementers topics list? Add ability to show support for ideas?
    • Possible to "assign to a SIG or other group?"

Steps to define:

  • Get from Implementer list idea, or meeting notes, or discussion to description to Jira
  • Ability to vote/+1/suggest changes
  • What to do with described features that are not being addressed?  SIG?
    • Help identify why not being addressed?  Options may include funding/outsourcing - opportunity for developers/vendors to market their services?
  • German SIGs work out their priorities, →see if they align with existing plans→find partners internationally/nationally-->fund separately as needed.
  • Communication Task: As a PO cannot attend all SIG meetings, Implementers, PC, etc... 
    • How to feed awareness and priorities to POs/Teams
  • Surface "new features" to POs

Possible steps:

  • Work with Implementers on "feature survey" - ideas for new features, raising awareness of features that never got made.
    • Concern about this reinforcing disappointment if/when things still don't get done. Institutions feeling like they are not heard.
    • Implementers feature idea list may cover this.

Continuous progress review

Making sure what is being developed aligns with Roadmap projections

  • Role for Release management or Roadmap updating process to compare
  • Roles for SIGs to compare priorities to work accomplished and report out
    • Some of this may be possible with SIG updates to PC

Future meetings
  • Ongoing updates - next meeting - define process for updates to roadmap, dashboards, and how to ensure current P&R groups isn't a lifetime appointment
  • Critical Service Patch process - as dashboards?  Oleksii maintains one for release management group.  Something that helps the Release Management Group make decisions and/or helps community see if/when their critical issues being addressed.  Oleksii and Khalilah are probably the closest to the process.

Action items

  •