...
While we also experimented with creating “swim lanes” for shuttling tickets to other subteams such as Metadata Standards and Usability, it’s not the easiest to figure out a workflow for getting them back into the Development prioritization queue. For example, if someone applies the “usability” tag, it goes into the Usability subteam queue, which may increase the response time for actually fielding it, especially if the subteam is unable to field it earlier. Additionally, once the subteam has looked at it, it’s not obvious how to route it back to Dev. Pri. Perhaps we should explore using a unique subteam tag to further distinguish it from tickets that don’t need the additional subteam review.
We began experimenting with having Dev. Pri. members volunteer to assign tickets each month. This could potentially be explored further. Benefits are that it will reduce the time commitment for the subteam leader(s) and that other Dev. Pri. members will have greater holistic insight to issues in the Jira system, potential challenges might be that it can be a lot of work and a learning curve for whomever is assigning tickets in that month.
Dev. Pri. might want to consider budgeting time or having a “communications point-person” to compile a list after each meeting to share on the member list of tickets that need community input, to prompt greater participation and feedback in Jira.
Dev. Pri. might want to consider additional approaches to close outdated, irrelevant tickets. Graphs of rate of opened versus resolved tickets show that there’s a large and increasing backlog of tickets. While assigning three tickets per person per monthly meeting is ensuring ensures a large chunk of tickets are being fieldingfielded, there hasn’t been an obvious path forward to aggressively reduce the backlog.