This are some suggested approaches to leading the Development Prioritization subteam - they definitely can and should be adapted and refined!

...

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.

...

Metadata and Usability subteam workflow integrations

Some tickets will need input and expertise from the other subteams. The kanban boards currently have “swimlanes” for both Metadata Standards and Usability. The Metadata Standards subteam can work fairly autonomously, beyond having tickets assigned with a metadata tag to their swim lane. 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 helpful to have a representative from Usability and Metadata 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.

...