What is Kanban?
Kanban is a method for managing knowledge work which balances the demand for work to be done with the available capacity to start new work. It is a popular framework used by software teams practicing agile software development. Kanban is enormously prominent among today’s agile software teams. Kanban is a new technique for managing a software development process in a highly efficient way.It is used for project streamlining.
Though it closely resembles to Scrum, Kanban gives more flexibility in terms of planning and execution. Instead of working in time-based sprints, work is continuously delivered in Kanban. The method resolves one problem at a time and hence the team pulls single piece of work from the “Backlog”, and then moves it to “Done” instead of pulling out huge chunks of work.
Step 1: Creating a Board
User always needs a board to view and work on the issues. A board displays issues from one or more projects. User can either use a board that someone else has created, or create a new board for themselves. User can create as many boards as they like.
There are two types of boards:
- Scrum boards are for teams that plan their work in sprints
- Kanban boards are for teams that focus on managing and constraining their work-in-progress. As the work is not planned in advance using discrete time periods or versions, Kanban boards do not need a Backlog screen
Step 2: General Settings
In this step, the user can describe the project in brief.
Step 3: Configuring Columns
In the Kanban board, a board displays vertical columns. By default, each board contains three columns, called ‘To Do‘, ‘In Progress‘ and ‘Done‘. User can add, delete, rename or move these columns if they wish.
In Columns, user can:
1. Add a Column
2. Change the name of a Column
3. Delete a Column
4. Move a Column
Step 4: Configuring Swim lanes
A swim lane is a horizontal categorization of issues on the Kanban board.
User’s Swim lanes are based on,
1. Queries: By default, two swim lanes will be created
- This swim lane is based on the JQL query: priority = Blocker
- User can change this column’s Name, JQL and Description if required
- Everything Else:
- This swim lane is always at the bottom of the screen, and cannot be deleted
- It acts as a “catch-all” for issues that do not match the JQL of any of the swim lanes above it, hence it has no JQL specified
2. Stories: One parent issue per swim lane (i.e. each swim lane contains all of the parent’s sub-tasks)
3. Assignee: One assignee per swim lane, with unassigned issues appearing either above or below the swim lanes
4. Epics: One epic per swim lane, with issues that don’t belong any to epics appearing below the swim lanes
Step 5: Configuring Quick Filter
The board’s filter is a JIRA issue filter (a JQL query) that specifies which issues are included on user’s board.
- Choose a different filter for their Board
- Edit Board’s Filter
- Add a Sub-filter for Kanban Board
Step 6: Card Colors
Card colors allows user to quickly identify cards on their board as being of a particular issue type, priority, assignee, or — thanks to the power of JQL — practically anything user choose.
User can choose to set up his/her card colors in following ways:
- Issue Types : One color per issue type. A default color will be allocated to every issue type which matches issues on the board
- Priorities : One color per priority. The default colors are the same as used for priorities in JIRA
- Assignee : One color per assignee. A default color will be allocated to every user who is or has been an assignee of issues on this board
- Queries : One color per JQL query. User can specify whatever queries he/she wish. Issues which do not match any of user’s JQL queries will be shown in grey
Step 7: Card Layout
User can use their card colors on issue types, priorities, assignee or JQL queries. Once user have chosen a method, user can change or delete the colors for each type of card. This can be configured per board (not globally).
In Card Layout user can:
- Change a card color
- Delete a card color
- Move a card color
Step 8: Working Days
User can filter out weekends, holidays, and other days on which user’s team might not be working on their board’s project(s).
- Select Agile > Manage Boards
- Click the Configure link corresponding to the board of interest
- Click the Working Days tab
- If user’s team has a different time zone to the server, select the team’s Time Zone
- In Standard Working Days, select all the weekdays on which user’s team typically works
- In Non-Working Days, click Add Date to specify holidays or one-off dates on which user’s team will not be working
Step 9: Creating an Issue
An issue typically represents a user story. Once user have created an issue, he/she will typically create several sub-tasks representing the work items required to implement the story.
Step 10: Issue Detail View
User can customize the ‘Details’ tab of the Issue Detail View to show additional fields.
Step 11: View the Kanban board
- Click the Agile link’s down-arrow in the top navigation bar, then select your preferred board
- Click Kanban board (Kanban boards)
Step 12: Releasing a Version (Kanban)
User can create and release a new version from a Kanban board, in a single step.
This page only applies to Kanban boards.
- To create and release a new Version:
1. Click the Agile, then select preferred board
2. Click Kanban board
3. Click the Release link at the top of the done (rightmost) column
The ‘Release‘ window will display the fields as follows:
- Version name — enter a short name for new version
- Release date (optional) — enter the date of release for new version. This will default to today’s date
- Description (optional) — Enter a longer description for new version. For details, see the JIRA documentation on Managing Versions
- Click the Release button to save new version and mark it as ‘released’ throughout JIRA and JIRA Agile
Features of KANBAN Board with JIRA
- Customized Workflow:
The Kanban board is divided into columns. The board complete snapshot of the current situation in a single go.
- WIP limit:
User can avoid bottlenecks in your process by limiting the tasks that you are allowed to have in a certain column.
By dividing task into sub tasks you can more easily track the progress made on it.
- Recurring Task:
Mark the task as repeating, specify how often it should be done and we’ll take it from there.
- Documents and File attachments:
Attach documents, spreadsheets, presentations and other files to tasks. Attach the files directly from personal computer or from Dropbox or Google Drive.