...
For FOLIO, the roadmap brings together the priorities described by the FOLIO Project and Community with assumptions about development capacity in order to set goals and milestones for several upcoming developed through many mechanisms: conversations within the Special Interest Groups, FOLIO institutional users working through their hosting providers, contributed development resources, and development happening on behalf of a client or for specific contractual obligations. The roadmap attempts to bring all of this development work together to provide an 18-month outlook, with emphasis on the next two FOLIO "flower" releases. The roadmap will help the community plan releases, coordinate resources, and communicate the strategic goals of the project as they relate to feature development. Ideally, the roadmap should address any development related to the FOLIO software, from platform to apps to connections between apps and third-parties. To be explicit, the Roadmap is intended to bridge between the strategic directions and the actual development sequence and priorities.
Although the FOLIO Project does not have direct influence over the work of external developers and teams, we will endeavor Much of work done for FOLIO development is done by developers and teams who may have specific client goals and needs to address, That's okay! The roadmap endeavors to include the goals and accomplishments of these external development efforts in the roadmap when possible.
FOLIO Project: The organization described in the FOLIO Governance Model (https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Governance+Model) and the resources managed by the Project.
FOLIO Community: The broader global effort to develop, implement, and maintain the FOLIO software.
Themes: Goal-driven groupings of related features, epics or initiatives.all development efforts to are contributed to FOLIO–we just need to hear about them.
Process:
The FOLIO Product Council (PC), or designated group, will manage an ongoing process to gather requirements and priorities from the community, identify major themes, align these with the priorities identified in the FOLIO Vision, Strategic Objectives and Initiatives or equivalent statements, and integrate them into the roadmap as milestones. As releases come out, the PC will update the roadmap to reflect the realities of development and highlight what has been accomplished. The roadmap should look beyond one yearattempts to cover an 18-month time horizon.
The process should involve gathering information from the broader FOLIO community, including the other FOLIO Councils, SIGs, advisory groups, the Capacity Planning team, Tech Leads, external Release Management Stakeholders, and Product Owners, development teams, already implemented institutions, upcoming implementers, and other interested parties.
From this information, the PC will identify themes that best address the high-level needs of the FOLIO Community within the scope of the available development resources. Each For the upcoming two releases, each theme will encompass the appropriate epics and features that describe the efforts necessary to make the theme a realityalso have the opportunity to drill down into Jira to see specific features and stories under development. The Roadmap should cover a variety of activity upcoming in FOLIO, including:
- Feature development
- Architectural/platform priorities and investments
- Strategic priorities
- Tech debt remediation/prioritization
- Cross-app requirements and dependencies
- Testing functionality and APIs
- Dependencies/sequences between development areas
- Performance
- Upgrade processes
- Non-Functional Requirements (NFRs)
- Documentation
...