Kanban development With Jira Agile is aimed to provide a smooth, quick, and easy path for developers and IT personnel to adopt Kanban within their organization. If you are already familiar with Kanban, this course will provide a great addition to your toolset: Jira Agile. But if you are not, Kanban is a great solution to development ADD (attention deficit disorder), corporate lack of focus, and company multitasking plague.
Xavier is very passionate about teaching, helping others understand search and Big Data. He is also an entrepreneur, project manager, technical author, trainer, and holds a few certifications with Cloudera, Microsoft, and the Scrum Alliance, along with being a Microsoft MVP.
Why Kanban? What Is Kanban & Who Should Use It? Hello and welcome. I am Xavier Morera and I am a hardcore Agile believer, as well as an avid JIRA fan. I would like to thank you for giving me the opportunity to teach you what I've learned through years of experience as an Agile practitioner through this course, Kanban Development With Jira Agile. Some of you might still be wondering if you should watch this course. So to be able to answer that question let's take a quick a visit to the doctor. So that you think that your development, IT, or support team can do better? Do you feel overwhelmed by the amount of work that you have? Do you think that you lack communication and process visibility? So if you answered yes to these questions you might need Kanban. So come on, let's get started. . . .
Kanban vs. Scrum: Let's Talk Agile Do you know what percentage software projects fail? Depending on whom you ask it can be around 70-80%. In any case, it is a big number. And one of the problems many projects face is poor requirements analysis, meaning that projects are doomed right from the start. However, many more fail because of different reasons. If you're in the software business and given that you are here, you probably have been approached by one friend or many in my case, with a new billion dollar idea; be it the new Flappy Birds or Warranty Tracker native app. All ideas can be good, but ideas are cheap. It is execution that counts. Let's take Agile and see where the glove fits best for you in either Scrum or Kanban and increase your chances of proper execution.
Optional Prerequisite: Quick Jira Overview Hello, and welcome to this optional prerequisite module: Jira Overview. In this training I am focusing on applying Kanban in real-life, using JIRA Agile. I am assuming that you have some general working knowledge of Jira, but if that's not the case don't panic. In this module, in just a few minutes I will give you some short background of what Jira is and how it works. If you want to get more in-depth information I do recommend that you go to the Pluralsight library and look for some more in-depth Jira courses, but what I'll be teaching you in the next few minutes will help you take the best advantage of the upcoming modules. Having said that, if you're more interested in JIRA Agile and Kanban you can skip this module and leave it for the very end. Just go through modules four, five, and six and then just come back in case you need to fill-in the blanks.
Kanban in Action: Getting Started And the fun begins with JIRA Agile and Kanban. Welcome to Module 4, Kanban in Action: Getting Started. You're taking the most important step, which is always the first one. Why? Do you have that friend that talks and dreams all the time about many projects, but never does anything? Well, don't be like that. Be a doer, not a talker. So let's begin. The way that this module and the next two will work is the following: I will walk you through a series of slides where I'll explain the steps I take and options available. My intention is to help you understand and then after the slides I will do a demo of what I just showed you. Why? Because if you want to follow along you can do it while I do the demo, but you already know beforehand the steps and outcome. I believe this is better to avoid confusing you and maximizing the learning process.
Report Mode: Measure Your Work Welcome to Report Mode where you get to measure your work. I would like to start by saying that Report mode is critical because if you can't measure it, you can't improve it. Well, you can say you can improve, but how would you know how much you have improved? Historic information is great because even though some improvements are very small, over time you can look at your baseline and your current status and with a lot of satisfaction you can say, boy, we have come a long way. So let's get started on some of the reports that are here to help us. We will review Agile Kanban specific first, then general reports, and we'll end up by reviewing dashboards.