8000 Kanban Lead · Issue #822 · packit/agile · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Kanban Lead #822

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
4 of 26 tasks
usercont-release-bot opened this issue May 23, 2025 · 0 comments
Closed
4 of 26 tasks

Kanban Lead #822

usercont-release-bot opened this issue May 23, 2025 · 0 comments
Assignees
@lbarcziova
Labels
kind/role Regular chore for the role rotation

Comments

@usercont-release-bot
Copy link
Collaborator
usercont-release-bot commented May 23, 2025 •
edited by lbarcziova
Loading

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 new column of the Kanban board
      • Ask about the
      • 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 discuss for 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

  • Tuesday

    • Stand-up
      • Go through the new column of the Kanban board
      • Revisit the least recently updated card in the packit backlog

  • Thursday

    • Stand-up

    • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lbarcziova lbarcziova

Labels
kind/role Regular chore for the role rotation
Projects
Packit Kanban Board
Status: done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@usercont-release-bot @lbarcziova
0