Skip to content

Adjust docs to Jira migration #1020

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

Merged
lbarcziova merged 1 commit into from
Jan 26, 2026
Merged

Adjust docs to Jira migration #1020

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions docs/kanban.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@ Packit team follows the Kanban methodology but does not just use a board with `t

## Packit Kanban Board

The current board is publicly available at https://github.com/orgs/packit/projects/7.
The current board is available at https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=22813.

The Jira board displays the active workflow columns: `new`, `priority` (To Do), `refined`, `in progress`, `in review`, and `done`. To view and manage the backlog items, use the [backlog view](https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=22813&projectKey=PACKIT&view=planning.nodetail&issueLimit=100#). For a complete list of all issues across all states, see the [issues view](https://issues.redhat.com/projects/PACKIT/issues).

### Card states (board columns)

Expand All @@ -16,10 +18,18 @@ This is a column where all the new cards are added (automatically for public rep

This is a pile of cards that have been basically categorized but are not a current priority (such cards are present in the `priority-backlog`), or it is not within our capacity to finish them within the next 3 months. The order of this column is not maintained.

:::note

The `backlog` items are managed in the [backlog view](https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=22813&projectKey=PACKIT&view=planning.nodetail&issueLimit=100#) and are not visible on the main board.

:::

#### `priority-backlog`

This is an ordered list of categorized cards that the team is considering for the upcoming work. Their priority is determined based on impact, user value, urgency and current team plans and capacity. The team revisits the epic-level priorities quarterly and the cards in the `priority-backlog` should be finished in 3 months. This means the number of cards needs to be maintained to be below ~50.

In Jira, the priority backlog is visible on the main board as the `priority` column ("To Do"). Cards are ordered by priority within this column and ready to be pulled into the workflow.

#### `refined`

This column consists of cards prepared to be worked on next when someone has capacity. The tasks should be actionable right away and doable by anyone. To get a card to this state a [refining process](#Refine) is used.
Expand All @@ -39,7 +49,7 @@ This is the column where all the done cards result.
### Card labels

Here is a list of labels we use to categorize cards to help ourselves navigate through the backlog and plan our work.
Note that there is no priority label since this consists of multiple factors like _impact_ and _gain_. Combined with the urgency, our current plans (based on demand) and capacity, this is visible from the place on the board.
Note that there is no priority label since this consists of multiple factors like _impact_ and _gain_. Combined with the urgency, our current plans (based on demand) and capacity, this is visible from the place in the backlog or on the board.

#### Area

Expand Down Expand Up @@ -121,8 +131,8 @@ Process of handling new cards and categorizing them.
5. Add a deadline if applicable.
3. Prioritising
1. **_Is there a strict deadline? Did we break anything crucial? Are we significantly blocking users?_** => [Refine the card](#Refine) right away and move to the `refined` column.
2. **_Is there a `gain/high` and `impact/high` label? Do we need/want to finish this within ~3 months? Is this part of our current high-level plans for the quarter?_** => Move to the `priority-backlog` column.
3. **_Is there a workaround? Doesn't the task make a user start/stop using Packit? Or, otherwise. _** => move to the `backlog` column.
2. **_Is there a `gain/high` and `impact/high` label? Do we need/want to finish this within ~3 months? Is this part of our current high-level plans for the quarter?_** => Move to the `priority-backlog` (To Do) state.
3. **_Is there a workaround? Doesn't the task make a user start/stop using Packit? Or, otherwise. _** => move to the `backlog` state.

### Refine

Expand Down
6 changes: 3 additions & 3 deletions docs/meetings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ If there is a strong decision needed, let people provide feedback also offline (

## Refinement meeting

Weekly meetings to prepare our next cards to work on. This is not to **_plan_** the work for the next week as done in Scrum. Kanban is based on a stream of cards going through [the board columns](./kanban#card-states-board-columns). This activity is about moving the card from the top of the backlog (a [priority one](./kanban#priority-backlog) in our case) into the [_refined_ column](./kanban#refined) by following [our refinement process](./kanban#refine).
Weekly meetings to prepare our next cards to work on. This is not to **_plan_** the work for the next week as done in Scrum. Kanban is based on a stream of cards going through [the board columns](./kanban#card-states-board-columns). This activity is about moving the card from the top of the backlog (a [priority one](./kanban#priority-backlog) in our case, visible in the `priority` column on the board) into the [_refined_ column](./kanban#refined) by following [our refinement process](./kanban#refine).
Basically it's about making sure the task is clearly defined and understood by the team members so they can be taken by anyone to start the real work.

The discussion starts with a quick introduction of the card (done by a [Kanban Lead](./roles#kanban-lead) or a person the most familiar with the task). The card is being updated and the discussion continues until we agree it's clear and can be done in 5 days or less -- to help ourselves reach this agreement, there is a voting going on. We used to do a thumbs-up/down for the following questions:
Expand All @@ -45,7 +45,7 @@ The discussion starts with a quick introduction of the card (done by a [Kanban L

Since there wasn't much disagreement and discussion, we switched to Scrum-like voting by hand about [story points](./kanban#story-points). (A [difference in story points](./kanban#story-point-scale) helps us better find a difference in the understanding.) We collect the story points but it's not the main reason why we do the voting. Be respectful when asking people why they've chosen a different story point number. It's to help everyone with the understanding and also to share the possible risks, not to put someone on the spot!

At the end of the meeting, make sure the order (=priority) of the cards in the _refined_ column is right and respects our priorities as shown on the [epic board](https://github.com/orgs/packit/projects/7/views/29), but also considers any urgent tasks (e.g. maintenance like renewing certificates).
At the end of the meeting, make sure the order (=priority) of the cards in the _refined_ column is right and respects our priorities as shown in the [epic board](https://issues.redhat.com/secure/PortfolioPlanView.jspa?id=3674&sid=3694&vid=16173#plan/backlog), but also considers any urgent tasks (e.g. maintenance like renewing certificates).

## Retrospectives

Expand All @@ -56,4 +56,4 @@ There's a default Miro board template prepared, but any activity or board can be

Action items from the previous retro board should be included to be discussed and checked.

At the end of the meeting, we revisit our [epics](https://github.com/orgs/packit/projects/7/views/29) and how we are standing on our planned epics for the quarter.
At the end of the meeting, we revisit our [epics](https://issues.redhat.com/secure/PortfolioPlanView.jspa?id=3674&sid=3694&vid=16173#plan/backlog) and how we are standing on our planned epics for the quarter.