# Kanban Process Questions ## GOALS of the kanban board - see the new high-prio work - what should be worked on next - Ideally this is a solution across timezones, when you are unable to ask someone. - see what is in flight / visualize the WIP - see bottleneck and "remove" them ( e.g. too many PRs that need review, ) - see how much done from the last time ## what should be on the board - new prio-list items - any (not only prio-list) items in-flight or done ## leading questions * What can be done to clear the "done" column? [ipanova] we can use this view to de-clutter done issues https://github.com/orgs/pulp/projects/8/views/3?filterQuery=-status%3ADone+ and every sprint planning we can manually "archive cards" from the Done column, or add automation to this that can be run periodically [Sprint Planning] Done! * Should only prio-list items be shown on the kanban board? [ipanova] yes, because the whole kanban board is built around the prio-list concept * Are associates expected to only assign prio-list items? [ipanova] ideally? [Sprint Planning] Some exceptions for various reasons, be transparent & communicate with teammates * Example: issues used for onboarding new devs are generally not priority * Are prio-list items supposed to only reflect associates/pulp team work? [ipanova] probably not, because it will be us who's going to review that work anyway * Should kanban board include only prio-list items? We are trying for now to include *in progress*, *needs review*, *done* columns to include items without prio-list label too * Do we need to add prio-list items proactively to always have 3 available, or as-needed by stakeholders? * [bmbouter] As-needed by stakeholders because when one mini team "finds backlog work to keep it full" and another mini team has stakeholder work, we can miss an opportunity to focus on stakeholder work +1 * What if team member doesn't feel have prio-list items to work on? * What happens if team decides it doesn't have items to work on in the near term? * Mini team leads, mentors - Kanban check in/Sprint planning meeting and 3 month planning * Confusing on trying to balance and be a part of multiple mini-teams * Bias of choosing what comfortable with, making up prio-list items (@fabricio is this a good summary?) * How can we effectively limit the WIP? * Can we add hard limits on the columns "in progress/review"? * Do we want a shared limit for those colummns? * How can we best visualize our work? * Looking at the Board (insights). * How do we manage the prio-list label with full inclusivity in an async environment? * When adding/removing/modifying the prio-list label leave a comment with @pulp/core for example: https://github.com/pulp/pulpcore/issues/3213#issuecomment-1251065635 * What to do with PRs that never had ‘prio-list’ ( community contributions, some old issue before kanban era, ) * What can we do about items that are in review, but the PR is clearly not ready? * What about an on hold column to let tasks that has been started but, for some reason, had to be "context switched" until the "pending/blocking" thing is solved? - this could be helpful to let others know that something is needed (or a help is needed) and inform why a priority task is not being worked or evolving Understanding on what trying for 2 weeks starting Sept 22, 2022 1. When looking for work, look at needs review 1. Then look at Prio-list column when picking work 1. When file list & put prio-list & leave note ## To do - can we figure out how long an item is in a specific column - make more in progress states - filter out draft PRs - think if we need a in-review state where we manually move things to - [done] rename kanban board to RH Pulp kanban board - make sure to show only RH PRs (low prio) - add Blocked column?, manual (purpose: show what is high priority & blocked), needs more discussion - discuss limits, epics - add automation to archived cards in the done column