This are some suggested approaches to leading the Development Prioritization subteam - they definitely can and should be adapted and refined!
...
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
The Dashboard shows the latest activity in Jira and also provides a quick overview of tags
...
TagsLabels: you can select tickets by themes by clicking on the tags labels in the Dashboard view. Obviously, this works only as well as tickets are tagged, so keyword searches are also helpful. Pay attention to their status or scope out any completed/closed/in development tickets.
Old ticket view is a scoped overview of unresolved tickets according to when they were last created. You can scope searches of Jira tickets by navigating from the Dashboard to Filters to “Search Issues” and scope through all of the drop down options.
If you like, you can “Watch” a ticket by pressing the “eye” icon on a ticket. This way, you are emailed every time there is activity on the ticket. You probably don’t want to do this regularly, since you might get a lot of emails, but it’s just another option if you’re interested.
...
After updating ticket status, refresh the agenda and to make sure that all statuses have been updated and are correct according the to “Decision” column in the meeting notes (VERY IMPORTANT).
Note: Sometimes it’s not possible for a ticket to move form one column to another. If that’s an issue, move the ticket first back to “Awaiting Prioritization” and try it again from that status.
...
Some tickets will need input and expertise from the other subteams. The kanban boards currently have “swimlanes” for both Metadata Standards and Usability.
To assign a ticket to Metadata Standards or Usability, add the label “metadata_standards_subteam” or “usability_subteam.”
The Metadata Standards subteam can work fairly autonomously, beyond having tickets assigned with a metadata tag to their swim lane. . They may move any tickets assigned to them to the “Ready for Implementation” status without sending them back to Dev/Pri.
The Usability subteam, because of the interconnectedness and complexity of updating the program, will need to function as a vetting group. Once Usability tickets have been discussed and have recommendations from the subteam, those tickets should be added to the next Dev. Pri. meeting. It would be is helpful to have a representative from Usability and, to a lesser extent, Metadata Standards on the roster for Dev. Pri., or at least make sure the leadership of these subteams keep in touch to ensure that tickets route back to Dev. Pri. for final approval in a timely manner.
...
“Dev. Pri. met once since the joint TAC/UAC meeting in January and addressed 18 13 tickets at the meeting .”
It has been challenging to quantify the work of Dev. Pri. because tickets keep coming in. It can look as if we’re not doing anything because the kanban stats will always be high, even as we pass tickets. It’s uncertain how effective listing the kanban stats [below] are, but this was the precedent established by Dev. Pri. leader Jason Loeffler pre-2016.
Kanban stats:
Feature Requests:
Awaiting prioritization: 107
Awaiting More Info: 58
Ready for Implementation: 72
Bug Reports:
Awaiting prioritization: 13
Awaiting More info: 11
Ready for Implementation: 56
(6 ready for implementation, 5 awaiting more information, 2 closed).”
Use this opportunity at the council meeting to bring attention to tickets needing more information or discussion.
...
There are many, many different types of reports. The Created vs. Resolved tickets report might be the most applicable. This is an example of a report spanning the last five years.
...
The red is the number of tickets created, the green is when the ticket is closed. Dev. Pri. operates somewhere in the middle.
Reports for Average Age and Resolution Time might also be helpful. As one can see, tickets can take a long time to work through the system - hence it is important to be efficiently address a lot of ticket in each Dev. Pri. meeting.
...
Note: these reports may be sobering but can be helpful for visualizing the sheer amount of bug and feature requests that Dev. Pri. wades through, but Dev/Pri has made limited use of them to date.
Special Projects
Dev. Pri. may want to consider special projects that align with its mission including creating surveys, calls for feedback on selected tickets, or recommending Task Forces to address areas of need to Council leadership and the Program Manager.
...