...
Convene the Usability Subteam by scheduling the zoom calls and facilitating the meeting
Note: How to schedule zoom meetings
The subteam usually meets every other week, which seemed to be the easiest way to keep the projects on track. The meetings would usually not take up an entire hour but have time to recap work accomplished an , troubleshoot issues, and delegate work for the next meeting.
The work of the Usability subteam usually falls into two approaches:
Fielding tickets with the Usability_subteam label in the swimlanes for Feature Requests or Bug Reports, or
Deep-diving holistically into a complex usability issue. The subteam might decide to do this particularly if there are multiple, possibly contradictory tickets relating to an issue
Before deep-diving into a particular issue, it would be a good idea to run the idea by the ArchivesSpace program manager to make sure that the subteam effort wouldn’t be superseded by other planned initiatives.
The proposed workflow for Jira tickets:
As the Dev. Pri. leader(s) survey tickets for assignments, they might give a label of “Usability_subteam” (note the underscore) for tickets which would not be straightforward enough not to pass easily. This tag will automatically route the ticket into the Usability swimlane. During Dev. Pri. meetings, if a ticket is lacking sufficient specification on the desired outcome, it should be routed to Usability.
One possible approach (of many options) is that the Usability leader divvies up the tickets within their swim lanes and the subteam members investigate and provide further specification on the tickets, which they discuss at their meetings.
If the ticket still isn’t sufficient, the Usability subteam might consider inviting the reporter and/or other stakeholder(s) for the topic to a subteam meeting to brainstorm and gather further information.
If the ticket is sufficiently specified, the Usability leader will either
If the Usability leader is not also serving on Dev. Pri., they remove the Usability_subteam tag from the ticket, which will route the ticket back into the Dev. Pri. general pool. Note: this may require giving them permissions to edit tickets. If this is not possible, than a Usability team member should comment the final determination for the ticket and tag the Dev. Pri. leader(s).
If the Usability leader happens to also serve on Dev. Pri., they can add Usability tickets to their ticket assignments to discuss at the meetings.