Prioritization Process for FOLIO development
Revised proposal by Prioritization Process Working Group
May 2022
| www.folio.org
1
Initial proposal - highlights
| www.folio.org
2
Considerations
| www.folio.org
3
Charge
The prioritization working group is to propose a new process for identifying priorities for new development in FOLIO that is equitable, transparent and clear. The group will consider how to get input from the community on priorities, taking into consideration institutional as well as SIG requirements.
The group will as part of this process investigate possible tools that could be used for rankings. For this purpose it may research ways of prioritizing in other open source or commercial projects.
| www.folio.org
4
Background
There is an interest to no longer use JIRA for institutional rankings, as it is not seen as the appropriate tool. Existing JIRA rankings should be exported and made available in a spreadsheet for historical purposes.
We may need a way to import rankings back into JIRA.
There was a pointing process introduced for Kiwi that was based on JIRA rankings, as only R1 and R2 features made it into a spreadsheet for institutions to point on. With JIRA being no longer used for rankings, there is either a new process or a new tool needed.
| www.folio.org
5
Working group members
| www.folio.org
6
Links and documentation
| www.folio.org
7
Flowchart
| www.folio.org
8
Considerations
| www.folio.org
9
Considerations
| www.folio.org
10
Feedback
| www.folio.org
11
Feedback
Maura Byrne in Chat: Should features fit into epics?
Gang Zhou (SHL)in Chat: +1 Kristin
Ian Walls in chat: I think all this assumes that we have a single pool or resources that are working against a single queue of features/fixes. I don't think that's realistic in an open source setting
different groups are going to have different priorities, and they're free to apply their own resources, and those of like-minded institutions, towards those priorities
Harry in Chat :+1 Ian
Von Gang Zhou (SHL) an alle 04:19 PM +1 Ian
Von Thomas Trutt an alle 04:19 PM That is defiantly true.
Von Marc Johnson an alle 04:19 PM Ian, I think that is a really important point. Which becomes even more important when a feature crosses app boundaries and potentially involves multiple teams
Von Ian Walls an alle 04:20 PM as a vendor, should I get to the point of being able to contribute code, I'm going to do what my partner libraries need done. I want to be sure that's given back, but that's where my directive is going to come from
Von Marc Johnson an alle 04:20 PM I would also note that development teams don’t tend to make autonomous decisions about what they build. Those decisions tend to come from outside
Von Kristin Martin (University of Chicago; she/her) an alle 04:20 PM I hear from POs that they want these ranking from both the SIG and the institutions. I'm not hearing that they feel bound, but they want to get input into direction.
Von Kirstin Kemner-Heek an alle 04:22 PM Yes, from the Stakeholder who hires then, for example. That happens in our FOLIO Environment. Other Options are possible. As well as that team decide to do something completely different. All this doesn't exclude any other decisions. But helps to keep an overview.
| www.folio.org
12
Considerations
| www.folio.org
13
Considerations
| www.folio.org
14
Considerations
| www.folio.org
15
Considerations
| www.folio.org
16
Considerations
| www.folio.org
17
Considerations
| www.folio.org
18
Considerations
| www.folio.org
19
Possible ranking tools
| www.folio.org
20
Next steps
| www.folio.org
21
What is your feedback?
| www.folio.org
22
Chat
15:44:04 Von Peter Murray an Alle:
App Ideas page: https://wiki.folio.org/display/PLATFORM/FOLIO+App+Ideas
15:50:07 Von Julie Bickle an Alle:
Or they get added in Jira, but not as a "feature" (which has a clear Definition and structure for dev work), but as [Name tbd] "new request" ?
15:51:07 Von Peter Murray an Alle:
It was the "APPIDEAS" project in Jira.
15:51:14 Von Kirstin Kemner-Heek an Alle:
That work can be done by the SIG's
15:51:39 Von Kirstin Kemner-Heek an Alle:
From the SIG's to PO's after first review
15:55:11 Von Charlotte Whitt an Alle:
Often new requirements is driven by libraries, who have this requirement as a road blocker for them in order to adopt FOLIO
15:56:06 Von Owen Stephens an Alle:
I like that Sharon
16:04:44 Von Owen Stephens an Alle:
I agree with that Ian - and there's definitely potential for frustration from the SIGs to see things they have prioritised not getting developed (and I think some SIGs are already in this situation)
16:06:47 Von Kirstin Kemner-Heek an Alle:
+1 Martina
| www.folio.org
23
Chat
16:08:02 Von Kirstin Kemner-Heek an Alle:
That prioritization is the base to decide on development and open up the opportunities for hopefully future developer Teams to get orientation, what is needed most.
16:09:41 Von Charlotte Whitt an Alle:
And also we need to plan work on features, which span over several apps; so the work being rolled out is useful for the implementing libraries, and not just half-baked functionality
16:12:12 Von Jana Freytag | VZG an Alle:
We have discussed, that NFR and basic industry standards should not be part of the ranking but rather something that will go into development automatically as well.
16:12:27 Von Kirstin Kemner-Heek an Alle:
+1 Owen. Prioritizing gaps / needs/ requirements is just one half of a process to get things done. But it is the necessary start.
16:12:51 Von Harry an Alle:
Owen, I think you have that exactly right. While the priorities help inform interest, it in no way decides what gets worked on next.
16:13:33 Von Gang Zhou (SHL) an Alle:
+1 Owen
16:13:52 Von Harry an Alle:
It has influence. But not a decision maker.
16:15:05 Von Thomas Trutt an Alle:
Sorry, i got tied up.
16:15:46 Von Kirstin Kemner-Heek an Alle:
But development Teams / Stakeholder can base their decisions what they will develop on that Information. That is an indicator what customers want. And other Teams can pick up, what is left over …. it Would be an opportunity to have a transparent process who picks up what - on each Stakeholders own decision. That is not questioned.
| www.folio.org
24
Chat
16:17:35 Von Maura Byrne an Alle:
Should features fit into epics?
16:17:47 Von Gang Zhou (SHL) an Alle:
+1 Kristin
16:19:00 Von Ian Walls an Alle:
I think all this assumes that we have a single pool or resources that are working against a single queue of features/fixes. I don't think that's realistic in an open source setting
16:19:15 Von Ian Walls an Alle:
different groups are going to have different priorities, and they're free to apply their own resources, and those of like-minded institutions, towards those priorities
16:19:16 Von Harry an Alle:
+1 Ian
16:19:35 Von Gang Zhou (SHL) an Alle:
+1 Ian
16:19:42 Von Thomas Trutt an Alle:
That is defiantly true.
16:19:58 Von Marc Johnson an Alle:
Ian, I think that is a really important point. Which becomes even more important when a feature crosses app boundaries and potentially involves multiple teams
16:20:05 Von Ian Walls an Alle:
as a vendor, should I get to the point of being able to contribute code, I'm going to do what my partner libraries need done. I want to be sure that's given back, but that's where my directive is going to come from
| www.folio.org
25
Chat
16:20:38 Von Marc Johnson an Alle:
I would also note that development teams don’t tend to make autonomous decisions about what they build. Those decisions tend to come from outside
16:20:48 Von Kristin Martin (University of Chicago; she/her) an Alle:
I hear from POs that they want these ranking from both the SIG and the institutions. I'm not hearing that they feel bound, but they want to get input into direction.
16:22:18 Von Kirstin Kemner-Heek an Alle:
Yes, from the Stakeholder who hires then, for example. That happens in our FOLIO Environment. Other Options are possible. As well as that team decide to do something completely different. All this doesn't exclude any other decisions. But helps to keep an overview.
16:23:35 Von Marie Widigson, Chalmers an Alle:
No additions, Martina, it was a very good summary!
| www.folio.org
26