IV | Prioritization process

Status

DECIDED Group made a decision to propose to PC

TBD Needs decision making in prio group

QUESTION There is an open question

TBD PC PC decision needed

REJECTED Idea is rejected

Decisions

Topic	Decision	Argumentation	Notes	Group status
What should SIGs rank on?	All features with status open draft in refinement in progress not on NFRs not on Industry standards What is an industry standard: Definition: A set of criteria within an industry relating to the standard functioning and carrying out of operations in their respective fields of production. In other words, it is the generally accepted requirements followed by the members of an industry. The requests go through the SIGs, they decide on whether this is industry standard or something the SIG should rank on.	same as we ranked before; task was to create a new process around existing tickets new institutions should be able to rank backwards and not only new requests prevent duplicates prevent that institutions create duplicate new requests because they are not allowed to rank on existing open features	SIG decides what industry standards are POs prioritize industry standards and take care that those are developed industry standards need separate label; SIGs should be able to filter on them to e.g. create lists	DECIDED
SIG prioritization	Use ranking tool TBD: which one? How? frequency: regularly, up to PO or SIG convener duration: 3 weeks to rank after ranking process: calculate one total rank per feature cross-app features are ranked by all related SIGs Add one field per SIG for the calculated total rank of each SIGs ranking as part of each ticket Import total rank into JIRA in addition: make variance of ranking available to the community (through the ranking tool) extensive communication	asynchronous prioritization via tool enables all community members to take part no matter the time zone no matter whether there are/can be representatives in the SIG meetings no matter the language barrier one tool across the project: for consistency reasons to ease voting if there are cross-app features to make it easier for new members to get to know FOLIO tools	Check with POs which tool is easiest for them and how process can be as simple as possible for them	DECIDED QUESTION
Institutional ranking	Use ranking tool - TBD: which one? fields to prioritize should include Priority, Impact on work, Urgency frequency: twice a year duration: 8 weeks to rank after ranking process: calculate one total rank per feature Use a combination of fields for the calculated total rank: Priority, Impact on work, Urgency Keep one field for the calculated total institutional rank as part of each ticket Import total rank into JIRA in addition: make variance of ranking available to the community (through the ranking tool)	The ranking tool can be a different one than the one for the SIGs as it fulfills different needs Important: announce ranking period ahead of time	Who is responsible?	DECIDED QUESTION
Ranking values	will be using 5 ranking levels similar to R1 to R5, but clearer in wording for comprehensibility there a limit to how many R1s an institution can use one R1 for every app 2 types of ranking: do we need it → yes/no how long can we wait = use R1 to R4 R1 - R5 R5 should not be "0" or nor needed institutions should not rank features that they do not need calculating total or average		check with POs	DECIDED QUESTION
Surveys	survey to be answered by institutions frequency: once a year libraries can list their most pressing gaps requirements can be added as free text		Who is responsible for sending the survey? Task for service provider?	DECIDED QUESTION