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; topics will be discussed in SIG and wiki page is amended From topcis Jira tickets are created; each ticket can be voted with the like button (upper right) High votes do not garantee rapid development, but developers can orient on that if they have spare dev time Jira dashboard with most voted tickets
Discussion of Questions above: (not final, Martin needs to consult recordings) Jana: RA SIG has backlog list, no voting process, but prioritzing gaps, work through it in meetings Gap list RA SIG Existing Jira tickets are searched and linked person responsible for a gap should create tickets are tags used for tickets? => currently not There is need for volunteers for creating/maintaining the tickets
Martina: ERM has similar system as ACQ SIG; ERM SIG is willing to adopt process Laura: LD SIG has small parking lot, currently planning meetings is more of a topic and curently there are also no implementers; the prioritisation process will be discussed, important
MM SIG is more difficult, difficult to come to an agreement on priorities as institutions have very differnt needs Kristin: AI SIG looked at have spreadsheet Martina: cleaning up the tickets is important Laura: things that have been thinthreaded/half implemented should be revisited, what approaches are there? Kristin: timing would be good now for that; but thinthreaded things may not be visible in Jira as they may be marked as done; some kind of survey would have to be done Jana: going though backlogs and closing deprecated features may remove load Caitlin: Jira tickets can be bulk updated, eg. add labels; special permissions are needed; Holly used to do it; Permissions may need to be adjusted. Peter can look into it
=> there should be a recorded session about creating and maintaining tickets Sharon: Reporting SIG use github issues, easier and faster to organise for their needs; with Reporting app SIG returns to Jira. Meta DB is managed through github issues. Charlotte: It would be useful if all members had permissions to use tags to label tickets; ? Kristin: Prioritisation rollout till Trillium; but usable beginning next year; 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 definition of done in different teams
|