A free video tutorial from Kosh Sarkar
4.5 instructor rating • 2 courses • 53,011 students
This lecture touches on how the Kanban methodology works
Learn more from the full courseLearn JIRA with real-world examples (+Confluence bonus)
Learn to work on, manage & administer agile projects with this comprehensive course on JIRA Software & Confluence
11:21:46 of on-demand video • Updated June 2020
- Understand what JIRA is, benefits of JIRA and how to use JIRA
- Understand Scrum - the stakeholders, events and overall flow of work
- Understand Kanban flow of work
- Use JIRA as a user working within an agile team - creating, working on and searching for issues, customizing dashboards etc.
- Use JIRA as a manager of an agile team - configuring agile boards, managing the backlog, sprints and releases etc.
- Administer all aspects of JIRA - create users, groups, set permissions, configure issue types, screens, fields, workflows etc.
- Use examples presented in this course to customize and use JIRA based on your own unique needs
- Get ideas (through examples presented in the course) on how JIRA can be utilized for different scenarios or situations
- Learn the basics of Confluence
- Learn how you can use both JIRA and Confluence together to work better and be more productive in general
English [Auto] Now moving on to Kanban Kanban is another in more simpler form of development. It also entails having a board to visualize the flow of work. However there are no sprints involved in this case. The main goal is to have a smooth flow of work from start to completion without any stoppage or bottlenecks and in order to do this the team must define what that flow of work entails as in How does a particular work item go from start to completion. What are the various steps or stages that it would go through and what is involved with transitioning the work items through each stage and ultimately getting it to a done state. All this would be represented through a Kanban board where the goal is to move all work items from left to right just like on a scrambled can then teams can also set a limit on the number of work items in each column of the board. These limits basically represent the capacity of the team as the work starts flowing through the Cambon board. The team can monitor the state of the board to adapt their processes identify bottlenecks and make improvements. Here's an example of a Kanban board on gear. It looks almost exactly like a scrum board. Here there are four columns so the backlog can represent all the tickets or features that need to be worked on but the selected for devolvement call them would only include the highest priority tickets and developers would only start working on tickets that are in this column. You can see here that the in-progress column is highlighted in red and this is actually a feature of Jira as I mentioned Kanban teams can set a work in progress of them. And in this case the limit is set to 1. As you can see at the top of the column right beside in progress it states a maximum limit of 1. So since there are two tickets in progress Jira alert to you about it. And this is where the team can collaborate to look at potential bottlenecks and work to get the board back to in normal state. This is basically the essence of Canavan workflow. So in summary we've talked about how work flows in both scrum and Cambon methodology as an example of where the scrum process would benefit the most is when you have a project with defined features that can be estimated by the development team. This could be a completely new product or a project or group of features where the requirements are fully laid up Kanban on the other hand I feel would be a good process to follow forth things like support tickets as in bugs that are found in the system or a support request sent to end by end users. The reason is because most of these things most of the time are difficult to estimate or predict and so the best way to get them done would be to keep the highest priority tickets at the top of the backlog and have your support development team work on them one by one and get them to a done state in the quickest manner possible. While monitoring the work in progress I also want to end this lecture by pointing out that we have just scratched the surface of these concepts and discussed them at a very high level. But there is a ton of content on agile scrum and can been on the web and I have provided a few resources that would be worth checking out. If you have time and would like to learn more. So let's now get back into Jira and define some terms.