50 min
| Prioritization rollout in the SIGs | Kristin Martin Martina Schildt | Review of Prioritization process in Acquisition SIG: Acquisitions/Resource Management implementers Prioritization Desired outcome: Jira dashboard of features identified as SIG priorities that may not be slated for a release, but can be picked up by development teams. Questions for discussion: Do you already have a mechanism for your SIG for collecting priorities? Are priorities represented in Jira or through another means? Do you keep a topic backlog/topic page that you can draw on to develop priorities? Are there dormant features that should be revisited? What barriers do you have in collecting priorities? What do you think would be a good time frame for collecting priorities? What can the PC do to help your SIG with this work?
Martina Schildt opens topic by quickly presenting how ACQ SIG is doing prioritisation: Wiki page (see above) for implementer topics; every community member can add topics; topics will be discussed in SIG and wiki page item is amendedFrom topcis Jira tickets are createdupdated For each topic a Jira ticket is created; a ticket is given certain labels special to the SIG; each ticket can be voted with the like button (upper right) High votes do not garantee rapid timely development, but developers can orient on that if they have spare dev time Jira dashboard with most voted tickets Kristin: Roll out of this process to other SIGs; not necessarily exactly the same; every SIG has their own special situation; this shall start a discussion in rolling out prioritisation process
Discussion of Questions above: (not final, Martin needs to consult recordings) Jana: RA SIG has backlog list, no voting process, but prioritzing gapsgap list, every institutions picks theri 5 most important topics, work through it in meetings, no real voting process Gap list RA SIG Existing Jira tickets are searched and linked if no ticket exists in Jira, a ticket is created by person responsible for a the gap should create tickets there are trainings for creating tickets => Kristin: it would be good great to have share this for with others as well; in chat: there are wiki pages for that: Getting Started for Product Owners Martina: if voting would be added, a Dashboard could be created for the list
are tags/labels used for tickets? => currently not; RA SIG has a lot of different apps/modules and providing tags would be a prerequisite for a meaningful dashboard creating/maintaining
Martina: ERM has similar system as ACQ SIG; more reluctant in creating Jira tickets; ERM SIG is willing to adopt adjust process Laura: LD SIG still has small parking lot, currently planning meetings is more of a topic and curently currently there are also no implementers; the prioritisation process will be discussedfuture meeting topic, important for tracking community prios and community impact Laura: MM SIG is more difficult, difficult to come to an agreement on priorities as institutions have very differnt needsdifferent needs; challenge to agree on SIG’s priority Kristin: AI SIG looked at have spreadsheet; more info from spreadsheet should go into Jira; tags should be used to appear in dashboards Surface issues on Dashboards can help people get active if they’re concerned with something unsatisfied in folioFolio
Martina: cleaning up the tickets is important Laura: things that have been thinthreadedthin-threaded/half implemented should be revisited, what approaches are there? Kristin: timing would be good now for that; but thinthreaded such things may not be visible in Jira as they may have been removed or be marked as done; some kind of survey/brainstorming would have to be done Jana: going though backlogs and closing deprecated features may remove was very helpful and removed load
Caitlin: Jira tickets can be bulk updated, eg. add labels; special admin permissions are needed; Holly used to do it; Permissions may need to be adjusted. Peter can look into it. New feature in Jira cloud: Export/Import with Google sheets => there should be a recorded session about creating and maintaining tickets Sharon: Reporting SIG use started in Jira, moved to github issues, as it was easier and faster to organise for their needs; with Reporting app SIG returns to Jira. Meta DB is managed through github issues. Wants to set up dashboard. Charlotte: It would be useful if all members had permissions to use tags to label tickets; ?currently only POs have permission to add labels to tickets; a new user group could be introduced for SIG members so that they can do that as well Kristin: Prioritisation full rollout till Trillium; but usable beginning start early next year; PC can help shape a standardized tagset for better search Martina: How can the PC help convenors discuss / roll out this process in SIGs Sharon: maybe there should be a Jira support group; Caitlin in chat: maybe a slack channel Charlotte: When talking to devs: If it isn’t in Jira, it doesn’t exist Tod: this topic parallels with lifecycle of TC establishing definition of done in different teams; an example definition was really useful in the rollout process
|