Open
Description
General instructions
- Watch Jira and Kanban boards and ensure they are up to date.
- Be a moderator for stand-ups, refinement, architecture and retrospective meetings.
- If there is a longer meeting, make sure that there is a clear structure of the meeting so that it is easier for remotees to follow.
- Manuals
Stand-ups
- Think of a question and ask it at the beginning of the meeting.
- Remind people to describe their cards/work when providing an update on their progress.
- After everyone presents their update, ask about any further topics that need to be discussed, i.e., post stand-ups.
Usual structure of the week
-
Monday
- Make sure you check the document (linked above) for any changes since you held the Kanban Lead role previously
- Announce the new roles on Monday in the chat on Slack, pin the message and unpin the one from previous week
- Annount the Community Shepherd role in chat on Matrix (as there is limit for max mentioned users), pin the message and unpin the one from previous week
- Stand-up
- Go through the
newcolumn of the Kanban board - Ask about the
blockedcardsin-progresscards- urgent cards
- priorities in the
refinedcolumn
- Make sure everything is up-to-date
- Check for cards that are stuck in a certain state for 3 weeks or more (check the issue timeline) and discuss those; if needed, label with
discussfor the architecture meeting on Thursday, or further breakdown during the refinement meeting - Revisit the least recently updated card in the packit-service backlog
- If needed, refine some cards from the
priority-backlog
- Go through the
-
Tuesday
- Stand-up
- Go through the
newcolumn of the Kanban board - Revisit the least recently updated card in the packit backlog
- Go through the
- Stand-up
-
Thursday
-
Stand-up
- Go through the
newcolumn of the Kanban board - Revisit the least recently updated card in one of the backlogs:
- Go through the
-
Architecture meeting
-
Retrospective (only every other week, check calendar for the schedule)
- Create a retro board (use this template in Miro)
- Copy actions/improvements from previous retro board, so we can check whether we did everything we wanted to
- Attach the link to the retrospective event in our Google calendar
- At the end ask about epics and whether we're working on the right ones
-
Refinement
-
Metadata
Metadata
Assignees
Type
Projects
Status
new