2 of 8

Prioritization and Roadmap Working Group

Members:

Jesse Koennecke, Cornell, Chair

Jenn Colt, Cornell

Debra Howell, Cornell

Kristin Martin, Chicago

Martina Schildt, GBV

Sharon Wiles-Young, Lehigh

Gang Zhou, Shanghai Public Library

3 of 8

Conducted a review of previous roadmap themes

Reviewed themes and their associated issues in JIRA
Attempted to encapsulate the current state of the work
https://docs.google.com/document/d/1vKJAnb4zEejxo0DAtwOBDac2JvJGHmwQE7eXxheSJzk/edit
Findings related to specific themes are listed but discussion of how well the previous process worked is relevant for implementing the new process

Previous roadmap - difficulties

Themes were sized differently – some areas had multiple themes focused on smaller details, while other themes were very large with little detail
While all themes had some progress, understanding the state of the work for some these was quite hard
Themes are reflective of the development organization rather than the work area in some cases – themes with multiple POs/dev teams represented differently than areas with single PO/team
Not all FOLIO work represented in Jira mapped to the Roadmap
Expertise of the type present in the SIGs would be helpful for evaluating progress

Previous roadmap - positives

Most themes had at least some progress
Having the themes tied to JIRA issues was useful for evaluating progress
Articulating priorities, having them on a roadmap and seeing whether or not they get resourced over time is helpful
Ability to assess the correlation between the priorities identified by the community and the work/planned work on the roadmap

Considerations for a new roadmap

Right-sizing themes and choosing the correct level of detail for descriptions – epics vs finer grade issues
Removal of themes no longer needed – the roadmap will evolve with FOLIO’s development
Balance between influence and reflection – prioritization attempts to influence development by articulating priorities and needs, while the roadmap reflects what is being planned for development (at a minimum for the themes identified as priorities), but cannot control development timelines
Prioritization should help POs understand community product needs and priorities so that work can be picked up when there are resources, and plans for the work can be used to update the roadmap

continued…

More communication about themes with development teams/POs to most accurately reflect what is happening
More SIG involvement in setting up and determining themes, as well as at other stages will be helpful
New prioritization process will help identify key themes and work to be represented in Roadmap
Additionally, provide a mechanism in JIRA for SIGs and POs to suggest new themes for the roadmap, which would be reviewed by the roadmap group for inclusion
Lightweight process to take place before full implementation of new prioritization process
Your ideas?

Prioritization Pilot

Following up on Prioritization Working Group previous recommendations, moving forward to set up pilot