Proposed process:

1. SIGs or liaisons will visit PC to discuss priorities

2. PC Members rate each prioritized feature 1-5 on each factor in DRAFT Prioritization Rubric

3. Should rating be hybrid - PC members rate asynchronously then discuss in meeting before we finalize ranking

4. PC needs a way to add features to the list that might not have been raised by SIGs - engage POs here?

5. Repeat 2 times a year to align with release schedule - what’s the milestone we need to look at here?

6. How do we capture functionality not represented in the SIG priorities

• Two tier

  • Single rank list of vetted, shovel ready UXPRODs ranked by PC

  • Broad list of priorities submitted by community

  • Can PC include priorities that reflect technical debt? How would we get UXPRODs?

    • maybe these would be gaps against a baseline

• Jira Dashboard

  • All priorities must have UXPRODs

    • Is it ok to create placeholder UXPRODs?

  • Only complete, dev ready UXPRODs can be included on PC list.

  • Flag UXPRODs in submitted by community that are high priorities for PC but need more work.

• PC add priorities for gaps against established baseline

  • To accomplish this we need:

    • validated baseline

    • a process for getting these reflected in UXPROD - who is product owner? Do we ask SIGs to add them? etc

  • How to best reflect technical debt?

Proposed Distribution Plan

Long Term Goal - update and distribute this page quarterly in April, July, October, and January.

• Beginning of the month - put out call to SIG liaisons

• mid month - compile and review with PC

• end of month - distribute to the community via Slack

• add recurring agenda item for tri-council meetings and community updates

Observations

• This was a big ask - we will need to give ample lead time and be patient as they ramp up this process

• Not everyone submitted 5 - maybe top 3 would be more focused / lighter lift

• Implementers and some subgroups wished to include their top 5

Review Questions

Content

• How useful are these priorities? How can we make them more useful?

• How does this track with our assumptions about FOLIO development priorities? Is there an additional PC perspective that needs to be reflected here?

• Include scheduled work, unscheduled work, or break out both?

• Are there other slices of priority information that would be interesting to have here?

Scope

• Do we want to include priorities from subgroups as well as SIGs? What is the correct level of granularity?

• How do we ensure “orphaned” groups are accounted for?

• How do we capture different perspectives?

Format

• Is it better to manage this in Jira or Confluence? If Jira, should we be tracking these priorities in PC Jira?

• Would it be better to do top 3?

• What is the best way to collate priorities - by SIG, by app, or something else?