FOLIO Roadmap and Prioritization Update

This update highlights the roadmap prioritization process for the FOLIO Community Development Roadmap. It includes the key components addressed by the Prioritization and Roadmap Working Group, high-level functional areas, team members, 18-month roadmap overview, covered releases, and the teams/developers involved in FOLIO. The process focuses on feature prioritization, identifying themes, maintaining the roadmap with priorities, clarifying intersections with release planning, articulating responsibilities, and generating visualizations.

• FOLIO
• Roadmap
• Prioritization
• Update
• Community Development

neti_485 Follow

Uploaded on Sep 22, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

Presentation Transcript

1. FOLIO Roadmap and Prioritization Update Prioritization and Roadmap Working Group WOLFCon, August 22, 2023

2. Our Group/Our Charge The 18-month Roadmap Prioritization & Roadmap Teams High-level functional areas Releases outlook via Dashboard Prioritization: for the longer view Challenges and next steps

3. Prioritization and Roadmap Working Group

4. Members Jesse Koennecke, Cornell University, Chair Jenn Colt, Cornell University Debra Howell, Cornell University Kristin Martin, University of Chicago Martina Schildt, GBV Charlotte Whitt, Index Data Sharon Wiles Young, Lehigh University

5. Charge Manage a holistic process for developing, reviewing, adjusting, and communicating the FOLIO Community Development Roadmap (Roadmap). What components should this process address? Feature prioritization Identify themes and subthemes Maintain roadmap that includes priorities Clarify roadmap intersections with Release Planning, testing, and release schedule Clarity on what s targeted for development and what s not Articulate who s responsible for identifying priorities Integrate information about non-community development efforts into roadmap and priorities Generate and update documentation/visualizations

6. 18-Month Roadmap

7. Releases covered 2024-11* Sunflower 2024-04* Quesnelia 2023-11-20 Poppy 2024-08* Ramsons 2025-01* Trillium *Release dates not set

8. Teams/Developers on FOLIO Bienenvolk: GBV + Knowledge Integration EBSCO Sif: GBV + Index Data Hebis + IndexData Manages EPAM teams Reminder fees ERM functionality Connections to union catalog Large number of developers Circulation add- ons ERM Dashboards German consortia requirements Core ILS functionality (cataloging, acquisitions, circulation) Dashboard Extension (1st ACQ widgets) FOLIO Harvester American consortial support

9. Teams/Developers on FOLIO University Library Leipzig + Knowledge Integration Usage statistics K-Int, Duke, GBV Individual Developers Institution Teams From American/Europ ean institutions and consortia From multiple institutions Serials Management (incl. claiming) Open Access Join in teams as needed/where interested Number Generator Workflows Calendars Enhance features across all functional areas Core ILS enhancements

10. 18-month outlook Platform Acquisitions Circulation ERM Lists app Process invoices against previous FYs GOKb synchronization re-write Improvements to Requests workflow Bulk edit suppression and deletion Version history Search implementation review Patron notices enhancements Consortia support Display addl order info in inventory Workflow engine integration Fees & fines actual costs enhancements Performance improvements Serials Mgmt/ publication patterns Dashboard Extension Tasklist/checklist support Reminder fees

11. 18-month outlook: Metadata Cataloging Data Import Linked Data Data export Cataloging workflow improvements Manage BIBFRAME records Migration data improved Performance and scaling improvements MARC Authority control linking Entity management for authorized access points Architectural & Workflow improvements Suppressing fields from export Search & browse improvements Scaling & performance improvements Improved in-app reporting Improvements in business logic

12. Anticipated New Apps Lists Workflows Harvester Service Interaction Pulls together data using query parameters Supports creation of workflows from FOLIO UI Supports the data flow from union catalogue to Inventory Settings app for cross-app module settings Supports interaction with active workflows across all FOLIO applications Provides number generator functionality Creates lists across apps and record types Integrates with Harvester Admin functionality Supports multiple workflow engine provider implementations Enables work and actions from lists

13. Dashboards Detailed dashboards (more to come!): https://wiki.folio.org/display/PC/Roadmap+dashboards Feedback and suggestions on dashboards is welcome Dashboard requirements: Minimal creation of new work for POs - use existing label list Attempt to represent the level problem - both UXPRODs and stories/bugs are represented Assigned release is entered by PO but it is an estimate until the release scope is set. Dashboards will need to be updated after each release (update filters) and ongoing communication with POs is essential In addition to PC dashboards, lead PO creates release dashboards and release manager creates calendar, these are also very useful!

14. Prioritization for the Longer View

15. Prioritization Manage the FOLIO feature prioritization process What components should this process address? SIGs priorities empower SIGs to help set priorities Institutions priorities via synchronous and asynchronous SIG work Steps SIGs define their top priorities will be added to JIRA as a SIG rank (new field) Rank top 10 priorities for features with no dev team assigned PC works with SIGs to rotate through different development areas on a regular basis and update those areas keep roadmap up-to-date

16. Prioritization Possible tools Moving away from the idea of using Airtable Status is uncertain Each voting institution or SIG member would require a paid seat May be too pricey for the project Spreadsheets Containing top prioritized features per SIG Asynchronous participation is possible Surveys For institutional prioritization (if necessary) Containing top 10 prioritized features Asynchronous participation

17. Challenges and Next Steps

18. Challenges FOLIO Project as vendor and consumer of the Roadmap Distributed development: Teams and funders Projecting: Assigned work, unassigned work, and undescribed work Prioritization: Level of granularity

19. Next Steps Publishing the Roadmap Prioritization Process(es) Ongoing updates

20. Discussion and Feedback