This are some suggested approaches to leading the Development Prioritization subteam - they definitely can and should be adapted and refined!
| Table of Contents |
|---|
Dev. Pri. leaders need permissions granted by the Program Manager to move the cards on the board. This can be a tricky process, so be in touch with Christine if there are any technological hiccups.
Creating Agendas
Sample Agenda: 2019-12-18 Meeting notes
...
The leader/co-leaders move the tickets on the board a few days after the Dev. Pri. meeting. This gives the subteam members time to comment and follow up on their tickets.
Dev. Pri. leaders need permissions granted by the Program Manager to move the cards on the board. This can be a tricky process, so be in touch with Christine if there are any technological hiccups.
Update ticket statuses either by dragging tickets on the Kanban board into the appropriate columns or by updating the status on the individual tickets (this may be slightly less error-prone).
Screenshot of changing the status in the ticket view:
...
When closing tickets, leave a comment on the rational and end the message “on behalf of Dev. Pri.” so that ticket reporters have a rationale and know who is making this decision.
...