The Complete JIRA Agile Project Management Course | Danny Liu | Skillshare

The Complete JIRA Agile Project Management Course

Danny Liu, Creating digital products the agile way

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
39 Lessons (1h 44m)
    • 1. Introduction to the Course

      1:25
    • 2. About the Instructor

      1:02
    • 3. Why Jira?

      3:45
    • 4. What makes this course so Special?

      1:26
    • 5. Requirements before taking this course

      1:43
    • 6. The Project Setup

      1:59
    • 7. Create a Classic Project

      4:04
    • 8. The Setup: Take Action - Setting Up Your Project and Components

      0:42
    • 9. Creating Issue Types: Overview

      0:47
    • 10. Creating Epics

      4:03
    • 11. Take Action: Create Your 1st Epic

      0:22
    • 12. Creating Stories

      4:45
    • 13. The Bulk Editor - The #1 Jira Productivity Tool

      2:22
    • 14. Take Action: Create Your Stories and Tagged Epic

      0:27
    • 15. Creating Tasks

      2:37
    • 16. Creating Bugs

      1:48
    • 17. Summary - Creating Issue Types

      0:24
    • 18. What is a Board?

      1:22
    • 19. Create a Scrum Board

      2:18
    • 20. Create a Kanban Board

      5:28
    • 21. Summary: Key Takeaways for Scrum and Kanban Boards

      1:13
    • 22. Customizing Your Board Settings: Overview

      0:37
    • 23. General Board Settings

      2:56
    • 24. Columns Board Settings

      3:01
    • 25. Swimlanes Board Settings

      2:08
    • 26. Quick Filters Board Settings

      2:33
    • 27. Card Colors Board Settings

      1:33
    • 28. Card Layout Board Settings

      2:35
    • 29. Estimation Board Settings

      4:45
    • 30. Working Days Board Settings

      1:44
    • 31. Issue Detail View Board Settings

      2:27
    • 32. Customizing Your Board Settings: Summary

      2:00
    • 33. Understanding Jira Reports

      2:38
    • 34. The BurnUp Report

      6:26
    • 35. The Burn Down Report

      4:12
    • 36. The Cumulative Flow Chart Report

      4:18
    • 37. The Velocity Report

      3:52
    • 38. The Control Chart Report

      5:01
    • 39. Introducing Jira Next Gen

      7:37
33 students are watching this class

About This Class

Learn how to quickly manage Scrum and Kanban Agile projects using JIRA Software Cloud and more!

Have you been tasked by your company to figure out how to use JIRA for your agile software or business projects?

Are you tired of looking for quick and easy ways to implement the best JIRA features to help you streamline your agile projects, only to find boring technical explanations with complex, hard to understand videos?

Then look no further.

In this course, The Complete JIRA Agile Project Management Course, you'll learn how to master JIRA Agile cloud software to help you streamline your projects while turning yourself into a project management professional!

Whether you're new to JIRA or Agile methodologies, an Agile Certified Scrum Master, Product Owner or software developer, this course will provide you the strategic and tactical essentials to get the most out of your JIRA Agile projects using a REAL web design example project, while saving you tons of time during the learning process.

Each lesson has been carefully crafted to focus on the key core elements of JIRA to help streamline your workflow while applying JIRA best practices FAST!

Looking for a quick tip on how to configure something in JIRA? Just skip to the lesson on that topic.

So, if you're ready to master your workflow the JIRA Software way while looking great to your boss and key stakeholders, then click the lesson videos on the right and let's get started!

Transcripts

1. Introduction to the Course: Hello and welcome to the complete Juro Agile Project Management Course, where you're going to learn how to master your digital projects using Ghira, the number one online project management system. I'm Danny. And over the last 15 years, I have told companies built amazing digital products and services by leading high performance teams using tools like your. I created this course with one simple goal in mind, and that is to help you focus on the essentials so that you could quickly start and manage your projects with. So let's take a look at what's inside. In this course, you'll be following along to create a sample project for a new website called WordPress. Web Design Agency will cover a basic overview of agile terminology and each section. So if you're already familiar with agile, that's great. But if not, don't worry. You learn all that you need to know to apply it. Agile concepts such as Kon Bon scrum epics and stories quickly injera companies like Audi orbits and hose, but are using Jura to deliver their digital products and services. So whether you're looking to save more time on your personal projects or find a new position in this offer development industry. This is the one stop shop for mastering Jiro to go on. Click the next video and I'll see you inside. 2. About the Instructor: hi and welcome to the Complete Jura Agile Project Management course. My name is Danny Jaleo, and over the last 15 years I've enjoyed a variety of technology rolls everything from being hands on and building server and network infrastructure and cabled apologies to developing and building cloud applications, using Amazon Web services, agile best practices and lean best practices. And doing all of this while leading high performance technology teams to fully aligned to it. Service management, Best practices. I'm also a proud father of three little boys. I really enjoyed playing tennis whenever I get the free time, and I'm a big productivity EQ. So anything I can do to save more time and get more results a big fan of that. And then I also love to play the acoustic guitar. So that's enough about me. Why, dear, if in the next video we're gonna cover exactly why Juror is the number one agile project management solution 3. Why Jira?: So why Jura, out of all the project management solution set, are available on the market? What makes your better than all the rest? Well, if there is one compelling reason it would be this and this is a fun fact, that juror actually is derived from the Japanese word Godhra, which means Godzilla. So I think that's pretty cool if Godzilla fan so using a tool that is named after Godzilla is kind of a pretty cool thing. And when you're thinking about squashing software bugs, it kind of goes hand in hand. Also founded in 2002 in Sydney, Australia here is one of the most widely used, powerful, inflexible, agile project management solutions on the market. It's being continuously developed by at last end the company, which makes Jura and has by far the most features out of the box versus most of its competitors. It also has an extensive plug in library for things like workflow automation. Get hub integration to help you really automate your development workflow if you're developing software, but probably one of my biggest and favorite reasons for using juror is it has a sappier integration, and for those of you are not familiar with happier sappier is a tool to help you automate between different cloud based applications. So I mean by that is it's essentially an A p I. So in this case, what do you want to automate today? This is kind of the Explorer dashboard for his happier, and I've selected the application Jura and I want to connect it with, Let's say, as soon as I click on the box, it sees there's immediately a bunch of different, um, options that I can integrate with slack Gmail, Google sheets, Twitter male gym with even marketing software. But I'm gonna go ahead and type in WordPress so you can see here. If I click on that, I can connect Geritol where press and then select a trigger. So whatever that say I and create a new post in WordPress. I want to ad a new issue, so create a new issue and you're a and then I can click may exact, and there's additional configurations that can make us well, so it's a really powerful tool if you have applications that you want to integrate that are outside of gear up to help automate your workflow and then last but not least, Juries for teams of all sizes, either in the cloud or hosted on your own server. So in the past, when Jiro first came out, it was really kind of hosted on your own server. So it really was popular with a lot of of companies that did their own their own software development, and not necessarily for the average user that didn't have their own data center or service to install software on. And if we go over to at last season's website, you can see that we've got the cloud version and the self hosted version. And there's variety different of flat fee for help to 10 users, which is insanely competitive with a lot of the lower tiered offerings for online project management solutions. Or you can you can go for larger teams that actually decreased your cost per license. I really think this is a insane value here for 10 users for $10 for a monthly flat fee. A lot of small teams can really get a lot out of of Jura for just a nominal fee for of $10 so I think that's that's insanely valuable. If you're looking for a self hosted version, which a lot of enterprise enterprises take advantage of to host on their own servers. You can just play with the licensing here to find out what your payment is per year, or if you have a much larger enterprise footprint, what the data center option would would give you. And that's just several different reasons why you should use Jura and what we're gonna cover next is why take this course? 4. What makes this course so Special?: Why should you take this course? Well, the first reason is compared to a lot of other courses on Jura and project management. This course is geared to save you time and get more work done by only focusing on the key concepts of implementing your fast. There's a lot of bells and whistles, and we're going to methodically knock down each of the most critical ones in a systematic fashion. Also, need a quick solution. Just skip to the video section or title on the lesson topic that you need or ask a question . I personally respond to all of my students questions, and I'm really passionate in helping other people automate their work flows and get more time back in their day. And last but not least. And maybe I didn't even put this at the top, really, is to become a better, agile leader, you'll be able to easily visualize stories in tasks. It's one of the challenges, and delivering software and services today is being able to do it on a predictable and consistent basis. And as far as career opportunities, the career opportunities are endless. In the digital world we live in today, if you're looking to get into agile software development. There's plenty of opportunity to do that by learning Jura again, since it's one of the most recognized project management solutions in the digital space today, as well as manager own software and non song for projects or not self for projects within enterprises. So there's a lot of value they can bring to the table for companies or your own projects by learning how to master here. 5. Requirements before taking this course: okay, a few requirements. So first off, the desire to manage projects of any size with ease. I imagine you wouldn't be here if you didn't have the desire to do just that. Also, a basic understanding of agile terminology and concepts is recommended, but it's optional again. We'll cover some of the most important concepts of agile and the terms that applied to each of the lessons as we work through. Of course, also having access to jeer server or Juror cloud and your cloud particularly is preferred, since we'll be using that for all of the lesson videos. But the concepts overall can be applied to both versions. You just might want to toggle between the server and cloud versions in the knowledge base on your to determine which are the exact steps you might need. And you can do that right here at confluence dot at last name dot com. You can see there's a little little cloud and server toggle button here to help you with the question that you ask. So it's a really nice place to find support and again also asking You can ask me for support, and I highly recommend you do that and I'll get back to a swell. So next up, what do you learn from the scores? First, we're going to cover this set up in in creating your first project. When I called that project, my WordPress Web design agency as will be building a website for a Web design agency that's looking to build WordPress sites as a service will be creating dear issue types and learn how to how and when to use them. Will also be creating scrum in combat boards and learning when to use. Each of the additional training modules and courses and updates are also going to be added to this course in an ongoing fashion. Everything from released management strategies to advanced filtering and much more. Okay, so next up the set up how you create your first project, see you in the next video. 6. The Project Setup: In this lesson, we're going to create our first juror project. But before we start, I just want to say, don't overthink it. It's far too easy to get lost in the tool and create too many projects based off of the work that you're already working on, the projects you might be working on. And it Quigley could end up looking just like this. And the last thing you want your project management tool to do is just that. So instead, keep things simple. We're going to keep our projects down to one, sorry. So we're gonna create one project and we're going to split that project down into different logical components. So different work types will be broken down into our components. But what does a component? Component fields are used in your project for organizing the different types of work. So maybe you are a freelancer or an agency and you're looking to break down your work by client. Well, you can use components to do just that. It's also great for managing single software projects and breaking them down according to their various functional components. For example, maybe you are building a web application and you want to have work that's tagged as a front end work or backend work. Or maybe you're developing APIs and so forth. Or maybe you're not developing software, but you are trying to manage digital content projects. Maybe you're working on blogs for WordPress or another platform, creating videos in YouTube. Maybe you're creating courses like this one on a site like Udemy or plural site. Or maybe you're an evil publisher on the Amazon Kindle platform. So there's a lot of different ways that you can utilize JIRA, not just for software development projects, but anything that's pretty much online. So with that said, let's switch over to JIRA and we're going to create our first project and our first several components for our Wordpress web design agency. 7. Create a Classic Project: Okay, so back in JIRA, we're going to create our first project. So the first thing we wanna do is click on the projects navigation link here. Now if you don't see this in your left navigation pane, just click on the manger of software local. And that'll take you to your homepage. And you should be able to see this navigation pane. There's also this little minimizer collapse button. Perhaps if you don't see it, you have it minimized. So just make sure that you click on the expand. And there you go, you can see projects. So we're gonna click on projects. Once you put projects, you can see it in my instance, I've got a bunch of project demonstrations. You may not see these if you're just getting started. So don't be alarmed. We're going to create our first project. But what you'll notice here, there are two different types. We've got a next gen software, which is a newer stripped-down interface. And the classic software, which is the project type that we're going to be focused on for the majority of this course. So click on the create, project button in the upper right-hand corner. And here's the the menu to create your project type. We're going to be prompted for a few different selections. So the first thing we're going to do is just select Classic project at the bottom and then enter our project name, in this case, WordPress, website design agency. And since I already have a project with that name for demonstration purposes, I'm just going to label it. All right, I'm going to leave this share settings with an existing project unchecked. And I'm gonna change the template from Kanban to Scrum. So click Change template. And you can see there's a lot of different types here for templates. There's some real great use cases for a lot of these other ones, but for our purposes, we're just going to select scrotum. So let's move from business over to software. And then select Scrum. And we'll cover some of the other project types in a future lesson video. Okay, so now that your project is created, we're gonna create our components before we start creating any JIRA issues. So the first thing we're gonna do is click on the components in the left-hand navigation, as gonna say, this project doesn't have any components yet. So we're gonna click Create Component. And in here I'm going to create three different components. So the first one I'm going to create is called design. So this is going to be for all design tasks for website project. Since we are creating a website for our web design agency, these are gonna be all the tasks that are design-related tax for my website projects. So that might be choosing a WordPress theme or choosing some other type of design for the site, right? And this also allows you to select a component leads. So if you have several people in your team, you can designate a person as the lead for design. Let's just say then hit save. We're going to create another one. And this is going to be called content. And this is for all content tasks. Then when I click Save, and then we're gonna click another one. And this one we're going to call conversion. Okay? We need to have all conversion in marketing. Lead generation tasks, okay? After all, what's the sense of having a business website if you're not able to attract and convert visitors to your website into potential customers. Okay, we're gonna click Save. All right, now you have three different components that you can bucket your stories and when we create them, content conversion and design. 8. The Setup: Take Action - Setting Up Your Project and Components: All right, so recap this lesson. We covered some of the basic set of practices for creating your first dear a project, and those include keeping things simple. So just start with one project and create your project components to break down the different work types in your project. So it's now action time. Time to take action. If you haven't already created your first project using a default scrub board, go ahead and do that. Now we're going to title your project WordPress Web Design Agency website and then create your three components and in the next lesson will cover the Jura issue types and how to categorise your issues into the various components we created. See you in the next lesson. 9. Creating Issue Types: Overview: in this section, we're gonna talk about creating jeering issues and particularly the epics, stories, bugs and tasks that will make up the work within your project. Okay, so with issue types, there are four different types of issues. We have epics at the top level. They can contain lots of stories or tasks or bugs, and we have stories, tasks and bugs which are basically sit at the same level. And those were just different types of issues, depending upon what kind of work it is that you need to complete. So in the next video, we're going to actually create our first epic, and we're also going to learn in this section what the number one year productivity. Tulis. It's a huge, huge advantage that saves you tons of time, especially when you have lots of different Jura issues to manage 10. Creating Epics: right In this lesson, we're gonna cover epics and create our first epic in Jura. What is an epic and epic is really just a larger issue that contains smaller ones and could think of is an epic as something that will actually take longer to complete. But you have smaller subsections of work that can be completed in different sprints. So if you have a two week sprint or when we experience, you'll be able to complete those stories within the defined time box and under epics. You can also have tasks, so tasks would be something that you can quickly get done. You might have bugs, software bugs that were discovered, and those things can all be bundled up under epics. Okay, so an example of an epic we only example here for WordPress Web design agency, the epic ISC idled develop minimum what minimum viable products are develop our website minimum Viable product or M V P. And you hear that a lot in agile terminology is that people discuss what is an M V P right minimum viable product, the smallest amount of features and functionality for a workable production ready customer facing application or in this case, our website. So the summary of this is going to be as a freelance Web designer. So when we talk about our story, a story is written in this format where we talk about as a particular user role in this case freelance Web designer. I want, in this case a Web site that looks professional. So we're talking about the feature or functionality that we're looking for. So that and this is important. This is the value that we're bringing to the table with this. The story visitors sign up for my services. So, for for a freelance Web designer website, we want to be able to have a website that looks professional so that people are actually going to become qualified leads by signing up for services. Okay, so let's go and hop on over to Europe in your WordPress Web design agency project, you're going to go to the backlog section. Now. It's important that you're in the scrum boards, So if you had didn't create scrum board, you can do that now. Okay, so we're in our backlog view and we're going to go to the epic slings blink here in the left slide out, You're going to see the words that air kind of sideways vertical here, Right click on Epix. I'm going to click Create Epic. So in this case, we're going to Ah, copy and paste are epic name from the where Press slide. Ah, there's also good to be down those for the lesson so you can copy and paste that or you can type them manually in. And then in the summary Ah, the summer here is going to be the story. And so the story that we put in our slide OK, copy and paste that and they're gonna pace that in there. All right? And I've made this story points field mandatory by default. It's not. You can you can definitely make that mandatory if you'd like. And we'll cover that in a future video on how to make fields mandatory. But I'm just gonna put in for this epic I'm gonna put in, let's say, seven for seven days. Okay? That's how that's how I do my point. My point estimation by days. So the all of the stories that are part of this epic should take about seven days to complete, and the stories should total up to no more than seven for each one of those stories. So if I have seven stories, they should be one point each. All right, so I should total up to no more than that, right? And they were gonna click create so you can see here. When you look at your epic panel here, you'll see that we have one epic here, and if we click on the link, you can see it. Says as a freelance Web designer. I want a website that looks professional so that visitors sign up for my services. The epic name here, which is develop website Minimum Viable product and that is it. That's how you create your first epic. 11. Take Action: Create Your 1st Epic: Okay, take action time. So if you haven't already, go ahead and create your first epic again. Use the download sheet with the epic summary and title to copy and paste in there. Or you can just quickly reference the video and type them in manually in the next video gonna cover stories and also discover the productivity trick to help update all of our issues with the right epic. 12. Creating Stories: in this lesson, we're going to cover what stories are and get a few created as well as associate them with the epic that we just created. A story or a user story is a software system requirement that is expressed in a few short sentences, ideal using non technical language. What this does is it describes what functionality is being requested in a values statement . So by developing this particular feature, we're going to be enabling this particular value for the user. So that's in the simplest forms. That's what a user stories is. But you can use a user story writing in any other sort of project task, not just software system software system requirements for software development. For example, If you were writing a block post or news article, maybe you want to have the user take a particular action or come away with a particular perspective, so that could be your value statement. In creating your story. So important to note, the user story can be utilized for both software projects and non software projects alike, and your agile A story is represented as an issue, and individual tasks within the story are represented as sub tasks. Now this is optional, and this can help you further segment the actual action items that need to be completed in order to satisfy the user story requirements. Okay, Our first store example. We're going to use this WordPress theme set up story, and we're going to tag it to the design component. And the story goes as a potential customer, I want to see that the designers website looks professional and is using WordPress so I can feel confident I am in the right place. So let's break this down really quick as a and then we're talking about the user, but a potential customer in this case, I want to see that the designers website looks professional. So that right there is telling me this is sort of the feature set that I'm looking to accomplish and is using WordPress because if I'm not using WordPress and I'm a WordPress Web design agency, that kind of goes against some of the credibility that I have now. Some might argue differently, but that's the requirement we're putting in this story, and the value statement is so I can feel confident I am in the right place, so we want our audience that comes to visit our agency website to feel confident that they're in the right place so they don't quickly click the back button and go to a another competitors. Okay, And the acceptance criteria for this story would be select and install a WordPress theme with demo content. Okay, so hopping back over to our gear aboard. Make sure you're in the backlog section if you're following along with this, or just watch this and then pause the video and go back and do it yourself. But what we're going to do is create our first issue so you can see here in the backlog. We've got no issues. There's a little plus button here, and it says, create issues. So what? I click on that I could immediately create different types of issues now, by default. There's a story here, but I can click on this and create tasker bucks. We're just gonna create the story and I have copied in my clipboard. You can use the download sheet, which I highly recommend, because there are additional stories that you are going to need to enter in to your backlog that are on the download that's included with this lesson. So go ahead and do that and download that and have that on the side so that you can quickly refer to that to type in or copy and paste your users stories. So I've got that pasted in my user story name. I'm just gonna hit Enter. Now I have a required field that I have set for a story point, so I'm just going to hit one. So my estimation here's one is for ah, one day. So I'm looking to say this is gonna roughly take me about one day to finish, and the component I'm going to select is design. The good thing about components is, even if you didn't create one that say we wanted to create a new one on the fly, you could certainly do that. So let's say Web design. And since it's not there, it says new component next to it. So since we already have it, we're just gonna leave design and in a description, I'm just going to put the acceptance criteria here, which is to select and install a war press theme with demo content. So not to create any sub tasks just to make this really, really easy and civil and we're going to click create. All right, so there you have it. Our first story is in the backlog. 13. The Bulk Editor - The #1 Jira Productivity Tool: okay, So early in the course, I hinted at the number one dear productivity tool. And I really think that this is really at the top of the list because of the amount of time it can save you. And that is the bulk editor. When you have a lot of stories or other issues that you want to update, it can be an administrative nightmare and take a lot of time and just become really tedious to get done. So where the ball getter is gonna help us speed the process up, Okay, So back into euro to access the bulk editor it really isn't playing in plain sight. And what we're gonna need do is go into issues and filters to access it. So I'm gonna click on issues and filters, and we're going to do is click all issues. We really only have three there. We have an epic eras. Well, what I'm going to do is click advanced Search. I want to do that. It's going to give me a list off my issues, and it's going to give you the ability here to click on these three more dots in the upper right hand corner of your screen as to say, both change all four issues. So when you click on that, you can select all of these. I'm going to not selected the epic, since that's the issue that we want to tag all of these stories too. I'm gonna click next. And when you edit the issues and then I'm gonna search for here. What I like to do is, you know, when there's a lot of fields in here I just like to do a command f for it. Control F If you're using a PC and then go ahead and click in Epic and it'll say change epic link, you'll find it right there really quick. I'm gonna click on that, and we only have this one right here for this project. So I'm gonna click on develop website Minimum Viable product and there we go. I'm gonna click next. I'm gonna click. Confirm it's going to show you that the change of the updated fields at the top So that's exactly what we want. We're gonna click that it's gonna edit these three issues. When it's done, it's going to take knowledge and you're all sets and I could see all three of these have the epic. Now, if you only have a couple issues, you might as well just go in to the individual issue and do a quick update. But when you have to go back and edit maybe 50 or 100 issues over time, I can be very duties. You could see how the power of the bulk editor and how can really help you save a ton of time, which is important to keep your data consistent and particularly if you're generating reports on your issues. 14. Take Action: Create Your Stories and Tagged Epic: okay, it's take action time. So if you haven't already, go ahead and create your stories by typing or copping the story. Examples in the download provided you can also use your own stories. So you know again, if you don't, if you have your own project already. Ah, lot of times people do and they already have their own set of stories. You go ahead and use your own stories and use some of these thes tips and strategies to update them and then go ahead and use the bulk editor to update your stories with the epic name. 15. Creating Tasks: injera. You also have a task issue, and a task is a unit of work contained outside or within a story, so you can think of it as on the same level of, ah, story or a bug. But the unique part about it is that you can create sub tasks within a story. So going back to juror, we can see that in our backlog we can create an issue. And when we do that, we can click on the actual icon of the issue, and we can select task. Okay, so that will create a task for maybe it's just a quick and easy thing you need to do maybe check your email or sent an email so you just It's not really a a feature requirement. You're not building anything. There's not a lot of things that need to get done as part of that body of work. So that's what a task would be used for. Now, if you are trying to create some tasks as part of your acceptance criteria for a story, then you would just simply go into the story itself. Okay, once you're in this story scream, you can click the three dots in the upper right hand corner. And when you look at this, you've got lots of options here. But these two options here create a sub task or convert to a sub task. So if you wanted to have you decided that this this story really is a sub task as part of another story, you can convert it to a sub task and tag the parents story that you want to put it under. But we're going to create a sub task. So we're just gonna click that task one. Just gonna put that as an example and then hit create because he it creates it down here. Now, once the first sub task is created, then you have the option to quickly to sit the plus book design here to quickly add a new task. So task to okay, so go ahead and play with that. If you have a story that you want to track with sub tasks, it's really up to you. Some people like to just track the acceptance criteria as an open text field and then review it in their retrospectives or when they're closing out stories to make sure that everything was actually done okay, so that's a quick overview of tasks. But the important thing to note about tasks, or that they're not necessarily delivering features, sets their functionality. It's really just a quick, ad hoc work item that could be completed in a shorter amount of time, such as setting up a meeting or maybe a retrospective or a stand up so we could think of more along the lines of admin work or just really simple independent work. 16. Creating Bugs: bugs, injera or defects are identified issues that prevent software from running as expected. And bug tracking software like JURA can help in reducing the time from identifying the bug to developing and deploying. A released fix back in our Jiro project will create a new issue. Select the drop down on the issue icon. It's like a bug going into the bug. We can add a description of what the impact is. So in this case will just put ah, shopping cart blink, not working as expected. Okay, just something very brief. And this case, our shopping cart link is not working is expected. So we would track this as a bug or defect separate from all of the things that were developing to add as new features. And this is a great thing to separate, because when you release your software, you want to be able to identify. Now, what are the new features and enhancements as well as what are some of the bugs that maybe have been fixed so that the users can know what to expect from this new release software? And if you're using this for projects that are not software development, you could still use bugs as issues in your project that have come up, or risks that have come up that you need to track and you need to solve for so a good example. Maybe that you know, you you've got, ah staffing issue all of a sudden, So maybe you have, you know, one person that's left your team that had a bulk of the work, and you need to track that, so you add that as a bug. So there's a lot of different ways that you can repurpose the bug issue type. It just really depends on the nature of your project and how you want to use bugs accordingly. 17. Summary - Creating Issue Types: All right, So to recap this section, we've learned how to create epics, stories, bugs and tasks and learn when they use each issue type. We've also created our stories and tagged our components, and lastly, we updated our big links using the bulk editor. So go ahead and take care of those tasks. If you haven't already, I'll see you in the next section, where we'll learn how to create effective scrum and combine boards. 18. What is a Board?: In this lesson, we're going to learn how to create highly effective scrum and combine boards in traditional project management or waterfall project management. The way that work has been broken down and visualized a lot of times comes in this form of a gang char, and what you can see here is that we've got a project that shows all of the tasks assign ease, whether or not critical the amount of the rate, estimated duration and sort of a map to the right giving you a timeline, including any overlap, and it just looks very messy. And if you want to switch something, it can cause some problems if you have some other overlaps in dependencies. Well, the great thing about agile and specifically agile injera is that we can visualize are work in progress in a column type format. Here you can see this is an example we've got a column for for to do column. We've got in progress stories, stories maybe that are being tested and those that have been completed, and this allows you to visualize each phase of the work, limit the work in progress that you have so that you can make sure you're focusing on delivering what it is that you've committed to for a particular sprint, and it gives clear visualization across the entire project portfolio for anyone that wants to look at your particular board. 19. Create a Scrum Board: There are two different types of boards that we can create injera, and the 1st 1 is the scrum board. The use cases for this, or developing or updating new products, for example, are were pressed Web design agency, website. Or maybe you're developing a new piece of software. Another thing the scrum board brings to the table are sprint goals. You have spring goals that are defined to allow you to identify what should be completed by the end of this sprint. Also, you've got more available reporting options than Kon Bon. Let's take a look injera. So the current board working with is a scrum board and you can see if we go to the reports here. You've got a laundry list of different options that you can select. You've got burned down charts burn up charts, Sprint reports. In addition to the more traditional Cahn von style reporting where we have cumulative flow diagrams and control charts, we've got a lot of additional ways to take a look at our work. Using a scrum board can also we have the option to create sprints on when we create a sprint. You can then move issues into your sprint to plan it out and then start the sprint so that it becomes active. You can select one week, two weeks, three weeks you can customize it. The recommendation is anywhere from 2 to 4 weeks on average, you can do one week if you'd like. That's a little intense, but if you're willing to give that a try to it seems to be a sweet spot. I like to use two weeks and then we can use the goal here so we can type in. The goal here is to install a professional looking theme with demo content. Okay, Justin example. We might want to put some additional stuff in there if we have other stories that were lined up in this front. But that will be our sprint goal. Will it start? You can see in our active sprint board. What this does is it puts the goal right at the top so you can read exactly what it is that you're working on. Your story should aligned to that. If they don't, then you really need to have that discussion with your product owner to say, Well, maybe we need to move this out of this sprint if it doesn't online with our sprint goal. Okay, That's a quick overview and some key components of a scrum board. 20. Create a Kanban Board: Another board that you can try to use is a con Bon board. Ah combine board also has a backlog feature Injure, which is relatively new as of this recording, and it's similar to the scrum style backlog where you can create a listed backlog where you have items that you need to pull into your work in progress and we'll cover that in just a moment. Also supports continuously blowing work versus your sprint goals so you don't necessarily have a time box when it comes to combine, where you have a sprint goal and any defined sprint cadence where maybe you have ah 112 or four week time box to take on work and then slot work into future sprints with a common board. It's just prioritizing work as it comes into your Q and only taking on just enough that does not go over your work in progress limits. Also with combine, you could leverage control charts and cumulative flow diagrams to see where any bottlenecks might be showing up in your workflow. Now, one important thing to know with Kon Bon is that you have limited reporting options here by default. You don't necessarily have access to the scrum reports and things that the scrum board will give you out of the box. So use cases for combine. Could be maybe your development operations team, where you build new infrastructure to support applications may be your support team or your or team that works with pre existing products and applications. So it has a lot of different use cases. But really, it's gonna be up to you to experiment with both styles to see which one works best for you . Okay, so let's go switch back to the era and show you what the calm bon looks like here. So I have a convo on board here for actually for creating the course that I'm working on right now. Ah, and that is, um, set up where you can see here. Now you don't have an active sprint for the board. You have conv onboard. You also have the backlog which is similar to the scrum style. However, one thing you'll notice here is that there are no sprints up here. There is no start sprint. There isn't a Sprint goal icon. You simply will take things from your backlog and drag them into selected for development. And what that looks like on your board is the selected for development column shows up here in the beginning. So anything I moved from here from the backlog to select a four development is going to show up in my first column in my combat board by default. Now you can set up this and customize it any way you like, but this is how it's been set up by default by using the Kon Bon board selection for setting up this project. Now, if you want to set up additional boards per project, you can totally do that. So don't think if you if you create one board for your project that you've got edit, you've got a scrap your project or get rid of the board, you can create multiple boards. You can see here where it says create board. You can click on that and create ah scrum board alongside a combo on board for this project to see you know which 1 may work better for me and then go and choose to use that one more . So I want to cancel out of that. And just to show you began with the reporting you can see with the reporting you're a little bit more limit, actually a lot more limited here. With the reports out of the box, you have accumulate flow diagram and a control chart back. Grab that. You can measure cycle time between your versions or between certain statuses of your work. Or you can leverage the cumulative flow diagram chart, which will help you see the status of issues over time and identify bottlenecks that you might want to look at and why. It might take more time for work to transition to ones from one status to another. So these are two great reports. If you're leveraging, combine. One great thing about using combine is to set work in progress limits in the In Progress column. Here I have a work in progress limits as a max of free. So there any given point of time, I should have no more than a maximum of three, and this could be issues. This could be bugs, but three issues injera that I'm working on or if my team is working on. So I got aboard settings under columns, I can see that I have set a maximum of three. So if you highlight if you if you scroll over that field, you see a maximum constraint for this columnist three. And you can also set minimums as well. But in most cases, you'll probably want to select a max who can take no more than a certain number of issues to work on in any given point in time. Another thing to note here, too, is there's an ethics panel Now with Scrum, you don't have this option, but in combine you do have this option two Toggle this honor off with scrum, you automatically have the epics panel enabled in your backlog view. So if we click on backlog, you can see that there is an Epix slide out here by default. That's not there. So you're gonna want to make sure that if you do want to leverage epics with conv on that, you go into your board settings and toggle this on. So if I toggle this off could go back to the backlog. You'll see it just shows the versions case one to tackle it back on, and we're all set 21. Summary: Key Takeaways for Scrum and Kanban Boards: Okay, so the wrap up this lesson, there are some key take away. So the first thing is that boards were great and efficient way to visualize in manage project tasks and stories. So whereas traditional project management, in particular waterfall style Project Management, you can utilize Gant charts to visualize work breakdown structures. But it really benefits to use that store of reporting maybe more at a higher level. So maybe more at the program level where you're looking at the road map, you can look at that more of again like style. But with the actual tactical day to day, work in progress is very beneficial to leverage either a scrum or combine board. So scrum is great for new products. Combine is great for support teams in development operations and uses a continuous flow versus time boxed sprints and again, remember, experiment with both. You may find that scrum is a better fit for you, even though you are a support team or you may find that combine is a better fit based on your needs. And there's also 1/3 option, which I'll cover in a future lesson, and that is scrum bon. Will you take the best of combine in the best of scrum and utilize what works for your particular workflow 22. Customizing Your Board Settings: Overview: in this section, we're going to customize our boards using the Jura board settings option. This is going to help us visualize our board in the best way possible by turning on and off certain features and making sure that our columns and swim lanes are set appropriately. When you click on a board settings, you'll see that there are a lot of options. So when you're working in this section, really take the time to go through each of these settings and toggle on certain features and just play around with the options available to you so that you can optimize the way that you visualize your work in the coming videos will dive more in depth on how to get that done. 23. General Board Settings: so the first option in our board setting configuration is general before we get started. One important thing to note is that if you're using scrum versus a combine board, the options that you are available to you maybe a little bit different. So keep that in mind and I will cover what those differences are as we move through each section. So back in my WordPress Web design agency scrum bored, I'm going to click on the upper right hand icon that shows that three dots, and as soon as I do that, I'm gonna seaboard settings Top click on that, and that's going to give me all of the board setting options listed on the left of you of your screen right here. We're going to start with General, so the general and filter setting is gonna help you determine which issues appear on your board. So whether or not you are on Lee going to select issues by certain assign e or team or project, you can do that by setting the default board filter. You can think of this as your global bucket Utkan put everything in this large bucket and then we can use some of the other types of configurations, such as swim lanes and columns, toe how to slice our work up in in different ways on viewing on the board. So just keep in mind you want to make sure that this filter is as relaxed as possible to include everything in your project. When people start customizing the general filter, they wonder why some of their filters are missing. And it's usually because they put too much of a restrictive filter on their default general settings. And you can get very creative with this because it's such a powerful option and you can even use custom. Jake, you well, which is your query language, depending on your needs, and we'll cover that in a future lecture on how to leverage Jake. You will. But for now, we're just gonna leave our default general filter the way it is, and it's the same in your conv on board. Now, the only thing you may see different in your convo on board is at the very bottom here. So at the very bottom here in your combine board, you may see this, which is a con bond board sub filter, and this shows the fixed version. Which injera fixed version means your release version so fixed version in unreleased versions or it's empty. So the field in each issue is not tagged to a release, and it's so it's going to show up on my combine board. Once I release it, it's no longer going to show up on the board. Well, for Scrum. It doesn't show that because we are working based off of Sprint work. So the sprint tag is what's going to show whatever is in our active sprint. So we don't see that there because we are working and driving our work based off of the sprint tag on each card. 24. Columns Board Settings: Next up, we have the columns configuration board options. Columns can be added, removed, reordered and renamed, and they really help us. Visualize are work in progress, whether using the conv on board or a Sprint board they're based upon. Global status is and can be moved between columns minimum. A maximum constraint can also be sent for each map column. So basically, if you want to create a work in progress limit, you can do that by selecting issue count or issue counts excluding sub tasks. So when I click on that, you can see a new minimum maximum amount of issues I can set on each of these columns. Okay, I'm just going to click. Go back to none. It's also using a workflow, and a workflow is essentially the transition. Status is the status is you can see here we've got to do. We've got in progress. We've got done, and they just so happen to have the same column names. Well, I can change these names that I don't have to keep the to do name just because there's a to do transition in here. I could just I could call this ready if I wanted to all right, but for our purposes, we want to keep it simple. Ever want to make sure that we don't introduce confusion? We're just going to keep it mapped to the column title. But if you click on the workflow here, you can see that this is the software simplified workflow. And this is a default workflow, and you can see it as a diagram to show you these are the transition status is you have in your workflow. Okay, so this is a very basic, simple workflow you can create as Ajira admin. You can create additional work flows. It's a little bit more vets, and we'll cover that in a future lesson. But for now, just understand. Use the default workflow, and that year's unmet statuses need to be set in one of these columns that air in view for your board. Otherwise, if you have issues, you can see I have seven issues and to do. If I'd move this out, I would no longer see it in my to do column. Okay, so I'm just gonna put that back. The other difference that you'll notice now I am in a scrum board. But if you go and look at the columns section in the conv on board. You'll see there's additional configuration option here, which is the epics panel. And this is for being able display epics in the panel in the backlog, not his cards on the board. So it'll set up your calm bomb board similar to the backlog of a scrum board. So what I mean by that is when I click on the backlog, you can see that right now there's a versions panel and an ethics panel, so I'm gonna close this out so you can see it better. So we've got versions and we've got epics, all right, But I can I can turn that off by default. This does not show up. So I've turned that on so that I can leverage epics similar to how we leverage it with a scrum backlog 25. Swimlanes Board Settings: another great way to help further visualize your work better is by taking advantage of the swim lanes board configuration options. So swimmingly is just a row on the board that could be used to group issues. So many types can be changed below, and you'll be able to save that automatically so you don't need to hit it through the save button for this to take place. You can just go back to your board and see them in progress. So the default option you have is no swim lanes. You can select queries, stories, sign ease epics and projects. So these are the different ways that you can segment your horizontal swim lanes based off of these sorts of issues. So I can. What I can do is show you. Since we've got epics, we only have one epic, but I can show you what this looks like. We'll go back to our board, you can see it says develop website minimum buyable product. That is our epic. So any issues that are tagged in this epic well that are in this sprint will show up in this swim lane. Okay, Now, if you want to get a little bit more customized. You want to be able to leverage different fields or different combined queries. You can use Jura query language, which is more advanced method of visualizing your work. But we can go back and select queries, and now you can see that you can customize the name of your swim lane. You can put the Jake you well in there for the query and just a little description on what it might do. So good example is on my combine board here, I've got one that says Expedite, which is creating a expedite swim lane and the priority for any issues that are tagged as the highest priority will show up in that swim lane. So going back to the combine board, you can see I haven't expedite Swim Lane here, and I've got this story. And this is for my online course tracking, right? The interest group modeled after a react course. Okay, so swim lanes are extremely powerful. Toe help you further segment and visualize the different types of work that you have in your sprints or in your work in progress. 26. Quick Filters Board Settings: quick filters allow us to focus on just a certain set of issues on our board while filtering out the rest. Okay, so back injury you can see in your active sprint board. If using scrum or your combine board of fusion conven, you'll see that you have at the top of the search far here. There are quick filters that you can drop, hit the drop down and select ones that you have configured out of the box. These are the two that I've got set up. And then there's also one here for a sign e and type in the person that you want or just select from the available options here that will filter in on the correct assigning. So to configure this, you go even to your board settings and other quick filters. You see, I have a couple here. These were created by default, and I'm gonna create one here for priority. Since I would like to view quickly which one are the highest priority. So I'm gonna call this one high priority. I'm gonna sign a priority value to select the auto predict equals Hi. Just select the available options. All right, so this is for displays issues which are high priority. Okay, on to click add. So now I've got a new filter on the board that is for high priority. Okay, High priority. Now I don't If I click on it now, nothing shows up because I didn't tag anything. But if I take one of these issues and I edit and just to sign the priority too high update All right, So now I've got this list. It is high priority. If I click on high priority, it simply filters out everything else. So this is great when you have a lot of issues in your to do column or in progress just on your board in general. And you just want to focus on the ones with a certain set criteria. One popular quick filter to use would be fixed date. If you use fixed dates for when things or do, you can quickly just click on that and filter out everything that's due or overdue so that you can quickly focus on those issues in your daily stand ups. And there we have it. That's how you set up quick filters in Jura 27. Card Colors Board Settings: inter board settings. We can also customize the card colors to display different colors on the issues based off of certain work types. Back in Judea, in our board settings, go to the card colors option. This is great for those of you who are color or visual based people. This is perfect for categorizing your work based on specific colors. So if we just click on the drop down, you can see here you can create card colors based off of priorities. Sign ease. Queries are none. So these are the default ones. Issue types. Priorities assign easy. If you want to get more customized, you can put in a query but would just select priorities for now. And so you can hear. You can see here based off of the the lowest to highest priority. You can set these and these are already in place. So now before I set this, I'm just going to show you what it looks like with nothing. So when you go into your active sprint, you can see I've got nothing, usually on the side edge, a little show color. There's nothing here if you go back to your board settings and so like priorities and then go back to your active sprints. You can see now here in the front I've got a little red line For some people, this is not really important. But for again, for those of you who like toe have that additional visual pop out based off of what you've set up for your colors to be, then this is Ah, great option. So go ahead and try to customize the colors based on your priority or any other criteria that you like in Europe. 28. Card Layout Board Settings: one board settings. Configuration options, called card layout is a very powerful wave To help you further visualize the work on your board. Card layouts allow you to take a look at your card to see certain types of field or data within your issue on the display card itself. So in this case I have here an epic. You can see the epic link show up on the card, so to activate or disable different options for your car, let's go back to board settings in the card layout settings. Cards can be configured to show up to three extra fields, so you can add three additional fields in the backlog, as well as three additional fields in the active sprints, for a total of six extra fields. So let's say in the backlog you'd like to add assigning. You can put the assigning you can click add. Maybe you also want to see the story points. It's like story points. Look, add and that say we want to see the component, so let component. Good God! All right, so in our backlog, if we go back, we can see will now be able to see components. Story points and a sign is so go to the backlog so you can see I've got the component, the story point and the assigning couple these air unassigned. So that's how you can add additional fields to your cards in the backlog. Now active Sprint. We can go back to our board settings and we'll go in and add for active sprint in our sprint board view component because I'd like to see component, we'll add that will also add a due date for any fixed dates, and we'll add story points. You can also add this days in column toggle, which would just basically show you how many days on each card that the time was spent in that particular column. So this can really help you identify bottlenecks in your workflow. So I'm gonna just go ahead and click on that. Now we've enabled that as well and go back to my active sprint sport so you can see here. I've got a no due date set for this one. There's this one point for story points, and this is part of the design component, and if I hover over these two little dots here over, I can see There's two days in this column, and that's how you set up your card layout. So go ahead and do that. Now pick a few fields that you'd like to see in your backlog, as well as in your active Sprint or CONVEN layout. 29. Estimation Board Settings: If you're using scrum, then you're going to have the additional board setting option for estimation. This is not an available option in the conv on board layout view. So this is one distinction to make. If you are seriously considering using estimation for your backlog planning. Okay, so back in our scrum backlog before we get started on exploring the estimation options, I really want to focus on one important key factor. And that is the configuration options you select. In your estimation, settings are going to be reflected here in your backlog. Only if I hover over the number, it will say story points. And this is the option that I have selected in the estimation configuration settings. So let's hop on over to that. Could your board settings and under estimations? You see, we have story points. Well, I can select original time estimate issue count, and I have a custom field that I've added, which is cost, and we'll talk about custom fields in a future lesson. But really, what we're going to do is select the story points, and then if you look under here, you have additional options for time tracking. Now this is something worth diving into because you may or may not have this available field on your issues, and I'll show you exactly how you can enable that. So let's go ahead and click on remaining estimate and time spent. So if we click on that, we go back to our backlog and I try to edit a story and I configure the fields. I have all the field selected, and I see I don't have time estimation tracking here as an option so I can click on Where is my field and type in time. And there is time tracking some click on time tracking, and it will show me where this particular field is map to. And I don't have this in the default screen view that I have here. So solve this problem. I want to go to this scrum default issue screen configuration views. I can click on that which will take me to the issue configuration screen, and I see it's not in this list. What I can do is type in time. There is time tracking at it now. If I go back, I'm gonna go back here, cancel. Let's refresh the screen. It should automatically refresh, but I always like to refresh just in case. And now when you go back and edit your issue, you should be able to see a time tracking there it is. So time tracking. I've got an original estimate and I've got in a remaining estimate field. Okay, so I'm just gonna cancel I that I've got one day set in there as an example. If I go back to my backlog, I still see I've got story points set here as the method of estimation. But let's say I would rather use the time estimation feature. I can go into board settings back to estimation here, remaining estimate and time spent. I'm just going to make sure that that is selected and saved. And now if I go back to backlog, I still see that it has this one story point next to it. Why is that? Well, I didn't select it as my estimation. Tracking option estimation can be a little bit tricky, so you need to make sure that you play around with it a little bit to understand it. So I need to sell to take off story points and put on the original time estimate. In order to be able to track some of these sub, I estimate time fields, which is remaining estimate and time spent. So I'm gonna go back to my backlog and I should see one day there. So now I can see one day there. So it's important if you are using this, just take a few minutes to familiarize yourself with being able to edit the being able that those fields and ah, you know, when in doubt, keep things even simpler. You know, what I really like to do is not mess with this too much and just leave it at story points. Um, I use my point estimations in days anyway, so I do one one day for one story 10.2 days for two story points, five days for five story points and so on and so forth. So really, it's up to you to play around with that and decide what works best for you. But that is estimation. Go on, give it a shot. Tryto configure as time estimates in your backlog for planning purposes, if you have any questions, let me know. Be happy to help you out on this section. 30. Working Days Board Settings: working days injured were allowed to set working days. So maybe you have a set of days that you only allow for working such as Monday through Friday. Well, by default here, we've got the selected. You can also select nonworking days, maybe holidays or things like that that you'd like to put in here by your system. Default. Here is New York setting. So that's where I am on the East Coast. So I'm gonna leave that alone. But you can also toggle that and change that based off of your time zone. Now, the important thing to note here is that you can leverage this in your burned down charts or some of your other reporting toe. Highlight some of the working days versus non working days over your reporting, so I'll show you why this might be important. So let's hop over to the report section. I want to look at the burn down chart in particular, and we're going to see that you have this little button here to toggle between showing nonworking days versus showing them. Now, whatever is don, working days will. So up in the gray now, you might want to look at this to see Well, how are we burning down points over non working days, and if so, why? So, for example, you might have a real push or drive to meet a certain date for a release. And so you have teams that are working overtime on the weekends to get work done. So this will be a great way to report and highlight that There is, ah, larger volume amount of work that's being completed over the weekend to recognize your staff for going above and beyond by working on weekends, but also to recognize that there is a work life balance. Maybe there's there's a lot of sprints that are actually the trend is becoming that people are working on non working days. And so how can we better dr and help solve for a better work life balance? 31. Issue Detail View Board Settings: in this lesson will create our issue. Detailed view. So back in our board settings, you'll see the last option here is titled Issued Detailed View, and all this is is a quick way to look at your issue details without necessarily leaving the board view that you have. And I'll show you that in just a moment. But what's important to note here is you have several different sections. You have the general date and people, and I have this one showing up for links. Now, I really can't configure do anything except remove the linked issues from the actual issue details for you. And I don't want to do that because I want to know if there are any dependencies linked to my issue. I want to leave that one alone. I'm gonna leave all of these alone, but basically you can add additional fields, will remove them or reorder them by dragging and dropping them accordingly. Now, one important thing to know is that some fields may be hidden. So depending upon your field configuration scheme on your project, you might also find some that are unedited herbal, such as the link section at the bottom. It must be added to the edit issue screen for a project of an issue, and you can click on these links in order to set that up. If you find that you have any fields meeting that criteria, okay, so back in our backlog, let's take a look by default. You might see just a full screen here with your back lock items listed similar to this assumes. You click on an issue you'll see in the right, it's slide out the details. So this is your issue detail view. You'll see that I have the general, which is the details here. Status, priority components, labels, etcetera all the way down to people dates and I don't have anything linked here, so it's not going to show me anything. But if I go back now, I can see I can actually remove some of these details that say, I don't really care about the affected versions or labels. I could go back and delete, and let's say I want to have the epic all the way at the top. You just drag and drop that. Go back to the board and if I look at my details to see the epic link is now at the top, and the labels have been removed in the affected versions. So customizing your issue detail view is just another bell and whistle that you can use to help further streamline the management of your issues without necessarily having to leave your backlog or your active board. 32. Customizing Your Board Settings: Summary: so to wrap things up, we've covered a lot of ways that we can customize our board settings. So first we cover the general settings and how toe customize our default board filters. Also, we've covered columns and how we can leverage the transition statuses in the default workflow in order to help better manage a work in progress and even set work in progress limits. We've also covered swim lanes to help us segment the type of work based on priority epics or other important data we created. Quick filters help us focus on the issues that we want on our board view. We've also customized the card colors based on high priority or other types of status is that you like to highlight via color with the card layout. We've set specific field data that we wanted to view on our board on each issue. In the estimation setting, we learned how weaken designate story points or time estimates so that we can use that for our planning. We've also covered working days and how working days to help drive reporting and toddling on and off to see where we might need to address some issues for staff working extra hours on non working days. And last but not least, we discovered how to customise the look and feel of your issue detail view to quickly identify and view data in your issues without leaving your backlog board or your active sprint or conv on board. Okay, so that is it for the section. Now it's time to take action, go through the configuration options on your board settings and start buying, creating a swim lane for high priority issues. Then go ahead and set a column for issue count constraints to a value of three. This will help you limit the work in progress 23 stories in your in Progress column, and then go ahead and continue the experiment. Configure some of the other settings and take a look at your board after making each change so that it looks exactly the way you want it to look 33. Understanding Jira Reports: In this video, I'm going to cover the different reporting that you have available to you, depending on the project type and board type for your juror projects. So if you're looking at my screen, you can see I'm in a classic software project and I'm also using a Scrum board. In this configuration, you'll have more reporting options available to you. So as you can see here, in the Agile reporting, I have ten different agile reports available to me. There are some Issue Analysis Reporting down here. But for the most part, this is where the main focus of reporting will be centered on. You've got about ten here in a classic software Scrum project. And if we take a look at the classic Kanban project type, you can see it's a little more limited in the Agile reporting because there is a focus on really removing bottlenecks and optimizing your workflow. So that's where the cumulative flow diagram can really come handy when looking in your combine reports. So that covers the classic software project type combine and Scrum reporting views. If you take a look into next-gen example, if you're using Jira next-gen, which is more of a leaner project type. And I have another course on that if you're interested in it. But to take a look, you're really essentially using these four reports. And so juror NextGen has really done a great job in cleaning up some of the available reporting. To really focus on the reports that most users leverage in their day-to-day. So in this scrum configuration, you can see that there is a burn up Report, burndown report, velocity report, and a cumulative flow diagram report. Now based on the Board type that you're leveraging in a NextGen project. You'll also see there are a limitation in report options. So you have four here in a scrum configuration. If I go and switch over to a Kanban NextGen project, you'll see that I have just one. Because sprints required are required for burn up, burndown and velocity reports, you will only have the ability to to leverage cumulative flow diagram reports and a next-gen Kanban project type. 34. The BurnUp Report: In this lesson, we're going to dive a little deeper into our available reports to show you how you can leverage them to optimize your workflows. Now will be focusing on the next-gen software project reports for simplicity. And they just really look a lot better than the classic ones just from a design perspective. So we'll, we'll utilize these, but the concepts are the same if you're using a classic project type. Again. So just looking at classic, you'll see you have the same burndown charts that you'll have available to you in a next term project. It's just the UI is a little different in the way that the burndown charts are displayed are a little different. Same thing with the cumulative flow diagram. You'll see it's a little bit different here than compared to that here. It's very, very, very, very simple here. So let's dive in and see how these reports can, can help us leverage our improvement opportunities within our teams. So in the reports overview section here I see I've got four different Available Reports. So what you'll notice is that these are also available to you. If you're in a classic project type, they're just going to look a little different in the overview section here. So you have your burndown charts and you have your your burn up charts are similar to your bird up Report is here and your burndown charts here. Also see your velocity chart here. That's the same as having your velocity chart in next-gen. And then your cumulative flow diagram, which is all the way at the far right here in a classic project. Okay, so the two reports here to compare would-be burn up reports and Sprint burndown charts. And so these are two inverse related reports. 11 goes down from left to right and one goes up from left to right. So going down in our burn up the report, this is going to show helped show us our sprints completed work and compare it with its total scope. So we'll get the total scope, which is that total point number. And we're going to compare it with how much work is actually being completed by the end of the sprint. So it shouldn't burn up, it should trend as we move through it. So that's the burn up. And then this sprint burndown chart will help us with managing the total work remaining and burning down to 0 by the end of this rep. Ok. This was great for summarizing both team and individual performance. By comparing what sort of work did we complete? Complete everything that we committed to, or did we carry over some work? And if we did carry over some work, how do we optimize so that we're delivering a 100% on what we commit to. All right, so we'll dive into them more. But let's take a look at the Burnham report. So the Burnham report, you'll see your date of the report. So that date range for your sprint, as well as the story points or the issue counts to keep things simple and a scrum configuration like to use the, the story points so that we can stick to a common denominator when it comes to workflow optimization. So we have our story points. So you can see here the sprints started, started with ten points with a total of two issue counts. You can also see that an issue was added to the sprint and the gray line here being your guideline, being your ideal burn rate. This is the one, this is the line that you would ideally like to trend up against on. Alright, so it's a burn up Report. As time goes on, we should be burning up, up, up, up to the right until we get to the top of the story points, the total story points that we're committed to in the sprint, alright? And that's going to be calculated as your team's moving things over to done. And with your product owner accepting this work will help to make this graph go in the trending upward kind of phase. And you can see the green line here is the completed work that actually have done so transition to done. Actually it's only five story points. So you can see that at the initial onset, that's what was completed. And as we go through the spread, this is just flat. So this is not ideal. And this is a great use case to tell you that, that, you know, if they are seeing stuff like that's not really trending up on a burnout perspective conversation. You can have your through team to identify like, are there any issues with getting the work done as well as your demos? Are your team members working with your product owner to demonstrate. So if you're a Scrum Master, this is a great opportunity for you to work with your team. Say, hey, are you guys demoing your work? I'm seeing a lot of stories are just not, they're not being closed out until the end of the sprint perhaps. But this is really not going to show you as much as when the product owners, or how much the product owners are trending, as far as how much they're accepting. We'll get to that in the burndown report. But in here you'll see that in the work here that completed work in green, the guideline of where you want to trend too, and the work scope, that total number of story points to the completed in the particular spread. And you also see some details down here as far as which which issues were in the sprint start, as well as ones that were completed. If the estimates for the points have changed at all. And if you had anything else that was pulled in after the sprint started, so you actually pulled in work that wasn't originally committed to. So that is the burn up Report. 35. The Burn Down Report: Let's take a look at the Burndown report. And this is one of my favorite ports. And I'll show you why. So if we go to the burndown chart, we can see how our work trends downward in, throughout our sprint. By the start of our spirit, we have a total number of points that we've committed to. And then by the end of the sprint, we, we should be trending at the 0 mark, the end of the sprint. Everything needs to be closed out and accepted by your product owner. And this is a great report to leverage to help identify are that are there issues with two team communication? I go back to the scrum master all because this is a very, very good report to help facilitate conversations with your teams. I mean, it really, it goes with any role, but for your Scrum Master, definitely if your product owner, it'll help you look at this and see how you can improve as a product owner with working with your team. Or if you're, if you're a developer or team member, are you moving your stories throughout the spread? This is a team effort and so this, this really this focus on making your team as efficient and high performance as possible to make sure they're getting work done in an ongoing fashion, but demonstrating them to your product owner so that you can accept, enclose these stories. That's how this will trend in the burned down and the top down guideline that you can see with this grey line. So that's our ideal burn rate trending down. So you can see in the start of our sprite here, we have eight story points that were added. We started with ten. So again, here you can see there's a, there's a discrepancy here. If we had only taken in what we committed to, you would see this red line match with this starting point. So this red line would be a little bit lower here at the ten and all the way across. Its added here because there after the sprint started, we pulled in an additional eight points after the sprint start. So this is a great report to look at, to see, well do we, are we bringing in more work than what we've committed to so that we can go back to our teams, maybe in our retrospectives or our standups to just quickly identify and say, hey, look, we are taking in more than we can handle what needs to come off of the plate for this sprint. So this is a great prioritization and compacity management tool to really identify those improvement opportunities and transition to done. This just shows us that in the start of our sprint, we've moved five story points to done. And you can see across this line here, this particular burndown is not doing very well because, I mean, this is just an example, but in an ideal situation, this will be trending down, down and buy. By the time you get all the way to the far right, which is the most present time towards the end of the sprint, everything should be accepted. If you're seeing this sort of line here, kind of trend down all the way at the very end of the sprint. So it gives you this more straight line. And then like falling off a cliff going down. That means that we are product owners not really looking at the work. Maybe they are, but at least in the report is telling you that they have not action their stories and they haven't accepted them until the very end of the sprint. And so the goal is again, tried to trend is close to this, this smooth downward line as possible. So it really helps with ensuring that your teams are continually on a daily basis, making sure that as work is completed, it's being communicated and it's being displayed in demoed and accepted or rejected. 36. The Cumulative Flow Chart Report: And our last report we'll cover here is the cumulative flow diagram. Now this is great for kanban teams. You can, you can use this with Scrum as well. But I've really liked this with Combine teams because there are, there's no shortage of report options when it comes to Scrum. With Kanban, the focuses more on continuous delivery, continuous flow, and improving your team's workflow. So if you're an operations team or if you're as production support team or customer service team. These are great sorts of use cases for teams to leverage the Kanban work type. And you can see how things are starting to pile up in your backlog or in your workflow. So taking a look at the various transitions, statuses that your work is sitting in and how long it sitting in there. You can see where areas for discussions to have improvement opportunities, a brainstorming session on what we can do to improve our flow. Maybe it's sizing our stories better, or maybe it's limiting our work in progress. So these are some different areas that we can take a look at. So look at looking at the report here, you see you've got to do ready in progress review and done. All of these are enabled so you can see all of the various workflows. Now. Ideally, all of these different workflow statuses should be an even parallel across the board. So when you look at the overview here, this is sort of the image that you have for your, this is a nice, healthy image because you've got an equal amount in each of your, your phases, your stat workflow statuses that trends over to done. And so you're always taking in a decent flow in the backlog and you're completing a decent flow. And as a result, so it's proportionate. That shows that you have a healthy backlog and a healthy workflow. There's always room for improvement. So we'll take a look at the cumulative flow diagram. You can see like in my diagram here, all this stuff into do, I'm starting to create a lot of issues and starting to build my backlog of as time goes on. And when you look at the done stuff, it's pretty wet, pretty pretty good. I mean, as far as you're looking at the issue counts in total, I've got a lot of green here. It does look pretty proportionate when, you know, when I go crossed and look through the various statuses, if I were to see that this purple section where it was just getting really, really, really, really wide. And my DON section was just kind of even keel and not really not really increasing, then I would I would see that there are some potential issues with me taking on too much in the backlog versus completing them. So you want to look at the different statuses to be able to compare them. And so that's a great way to sort of look at it. An apples to apples comparison. You can see todo, I've, I've just toggled off the other statuses to get rid of that noise and just see out of the things I have to do versus the things I've done. Am I taking on more in the backlog that I'm actually completing? Or it does everything look kind of healthy? The thing to remember about combat reports is it's again, it's focused on workflow. It's focused on your performance. It's not focused on your goals, it's not focused on, you know, I need to ship this product by this date. Those are conversations that you'll have to have within your team to say, based on our workflow and based on our productivity, are we able to meet the dates that we've committed to our stakeholders? Alright, and so this is just one tool of many that you can use to help make sure that the teams are working on things. They're not sitting around. If you're taking too much in the backlog, working with your product owner to say, Do we really need all this stuff in the backlog? Is this stuff really necessary? Or are we just creating a lot of junk to just sit in the backlog over time that may not be may not necessarily need to be worked on and take action and clean those up accordingly. 37. The Velocity Report: And the velocity report will be able to predict the amount of work that our teams can commit to in future sprints by taking a look and reviewing the amount of value delivered in the previous ones. So how much of our commitments did we actually deliver on? So this is important when you're trying to forecast and when you're trying to give your stakeholders a warm and fuzzy feeling on whether or not you're going to meet your goals, right? So your future dated goals. So when we're taking a look at this example, you can see that I've got various sprints here side-by-side. And you can see the gray is the commitment, is the amount of work in the Sprint when it first began. So as soon as you hit start sprint, that's the calculation of the total total commitment. Then we've next to that and in green we have the amount of work actually done during the sprint. So if we look at each of these, we can see that in this sprint ate, the name's a little bit off here, but you can look at the dates that are put in here to just take a look. So for Sprint 8122619, there were six that we're committed to and nothing was completed. So this it tells me it's like, well, the team just didn't do anything that sprint. Alright, these are drastic examples, but just it just made so that you can see the comparisons. So you can see on the other end of the spectrum. And this example for the sprint, there were seven points committed and seven points completed. So this is awesome. Uses exactly how we want our teams operate is make sure that we're delivering are a 100% of our commitments. And now my stock going to be perfect. But that's the whole point of having our agile retrospectives and some of the other ceremonies to help us optimize and increase our cohesion and performance as a team. So again, you can see the next sprint committed five and didn't complete any. And then in the next sprint, there were six that were committed and one that was completed. And this one here, this looks like a spirit was started with nothing in it. And then there were three points are added within the Sprint and completed. We've got over here in the last one, it looks like there were seven committed and to completed, right? So you've seen the trend on and look and feel of how to read the report. So this bottom half is very important to help us calculate our future capacity. So how we do this? We can take a couple of these sprints and add up the completed points and do an average. And just, you know, so we're going to, let's just say we're going to take all of these. We're going to say 123456. Let's just take these six and we add them all up. Seven plus one is eight, plus three is 11. Plus two is 13. Right? So we've got 13 points in total. And if we divide that 13, divided by six, you're going to get a rough number of 2 something, right? So we average that and we, we estimated about two. So we've about two points per sprint on average that we would be able to say, hey, we can commit to two points to make sure that we're able to deliver a 100% of our commitments. So this is a great way to kind of leverage historical data to help you identify your team's capacity and what they can commit to in future Sprints. 38. The Control Chart Report: So understanding the control chart, the control chart shows the cycle time for your product version or sprint, and also helps you identify from the data of your current process and see if it can be used to determine future performance. So some wasted do this are for the visibility. So you see here there are little dots with circles in it. And that will help us see outliers and investigate their cause to reduce them in the future. So some of the things we want to look at when we look at outliers, click on, I have a story here that's our outlier. And outlier means that it falls within the outside of the predictability zone here, which is in the shaded blue. Predictability is a narrow standard deviation through process improvements to improve predictability of cycle time. And so when you look at that standard deviation window, this is where we want to kinda be, be falling within. As we get outside of that. We're looking at our one issue here that's showing us that it's t it's in progress. It's just stuck in progress for five weeks, four days, 23 hours, and 49 minutes. So it's, it's outside of the realm of our predictability. So we wanna look at that and drill into that and have a discussion and are retrospective to be able to talk with the team to figure out, well what's going on? Why is this story just stuck in an in progress? Sometimes it's a matter of, well, teams just haven't transitioned the story, but it drives the conversation to be had to say, if you're doing your work and you're completing your work, you need to be moving your work in to the next stage. Get it out of the in-progress and move it to review or wherever it has to be an order to make sure that we are staying within that standard deviation and that our flow is being optimized throughout our project. Okay, efficiency. Efficiency is the blue line here and you can see the blue line shows us the elapsed time in days. Over top here, our issue transition date. So the date that the story is moved from one state to the next. That's our cycle time. We want to make sure as we look at the transition states from one to the next, that we're looking at what that cycle time is. And so we can see here, we've got a date range at the average for looking at the legend above, we have the red line, which is our average. Our average is about a week. So when we hear in seven hours, okay, our average, so the closer we can get to an average, the better. But if we get a little bit below that, that's good too. So we can see we've got some efficiencies here. Now that we are looking at our standard deviation and a rolling average. A rolling average is 0.9 days. So it's taking us about 0.9 days to transition, which is, which is not bad. It's almost the full David. Before we update our stories to move them from one phase to the next if they are in fact, being completed in that particular cycle. So in progress, moving it out, et cetera, you have your standard deviation of 1.3 days. So if we fall within that range, that a good healthy sign. But again, you're looking at this report, you're going to need historical data. So control charts are great when you have that, when you have historical data to reference. But if you don't have a whole lot, is going to be not useful for you to try to optimize until you have a workflow in place that's been going on for, I recommend at least a full quarter or program increment free months to leverage that historical data and then go back and see how you can improve. Ok. You can choose down here at the bottom, all your timescale, all time, past three months, custom dates. And you can also drag and drop gate. So if I drag and drop, I can go back here and just drag and drop on a subset of historical data and it drills into that drag and drop start and end range. So I can get some better metrics based off of that date range. Okay. But I'm just going to select all time. And I don't really have anything recent. So that's why you're just seeing this completely empty. But again, this is a good report to see. Do I have things that are outliers for my my existing process? And if they are used, those as discussion points in your retro is to see how you can optimize and get those stories to be updated and transitioned in a more controlled manner. 39. Introducing Jira Next Gen: Welcome to this video on JIRA Next Gen Ju your NextGen is a new project type for Jura software cloud users that allows you to have more of the stripped down, more user-friendly experience when it comes to administering your JIRA projects. There is a stark comparison, indifference to functionality that you're able to leverage compared to the classic juror versions that you might be familiar with. So if you're new to JIRA, definitely check it out. I suggest you check it out if you're if you're already been used in JIRA for, for some time, it can be a little bit of a, a difficult move, just simply if you're used to using more of the advanced administrative capabilities in the classic projects, you might not get that functionality here, but I can definitely tell you as a longtime JIRA user and do your portfolio plug-in user for creating dynamic roadmaps. I can definitely vouch for the simplicity of what your NextGen offers. And so this video, we're just going to dive in high level of what you can do in JIRA next-gen. So right now as of this video, the key thing here to understand is you have a roadmap view. And the roadmap view will be able to give you sort of the feature targets, starts, and end dates that you are shooting for to create this nice roadmap view for your issues. Okay, so I got a little roadmap here for, for creating my Agile product owner course and publishing it to various platforms. But you can see here you can create multiple epics. And they are also unleashing features where you can tag dependencies to these epics. So that's really exciting as well. Now, the backlog, when you go to the backlog, it looks pretty much the same. You have your, your ability to add two years your sprint goals here. When you click on the dots here and you edit the sprint, you're able to do that address sprint. Sprint goals changed the name time of the start and end dates. And then on the board, you'll notice that it does look a bit different. And I like the UI here because it's reminiscent of a lot of the newer apps, such as Trello and some of those other visual style task Kanban style boards. But this is for the scrum, scrum sprints that you would, you would basically create here. So you've got a complete sperm button here, shows you how many days remaining. And then it also allows you to drag and drop and create new columns on the fly, something that the old classic projects don't necessarily allow you to do, which is just to create a column right from within the board. You actually have to go in and edit the board. It configure it. And there are some challenges with that, but, but then there are also some limitations with this as well. So you give up control for. More easier, easier user-friendly type of functionality. But you can see here, I've got this sorted by the epics and then all of the child stories from those epics show up on my board really nicely. So I really like this and it's really, really simple to use the reports. There's four currently four different reports right now that you have your burn up report, your burndown chart, velocity Report, and your cumulative flow diagram. So similar to the classic projects where you do have a lot of different reporting. I really like the way that they are bringing some of the old stuff in and they're really kind of trying to pare it down and filter out from a lot of noise over the years that JIRA classic has kind of brought in and they're doing a nice job with that. So pages is just for Confluence. If you're, if you're going to try to create, you know, documentation and things like that, I really don't use it. I use Google Drive from my documentation, the user story map. This is just the plug-in that I, I installed from easy agile. So you won't see this in your installation. This just gives you an ability to map stories from, from an epic perspective and downward. And same thing here with okay, our board for objectives and key results. You won't see these two in your installation. I still haven't even determined whether or not I really want to keep these. I'm seeing a lot of functionality overlap in what I'm able to do in the NextGen project, which is pretty amazing. One of the things that they did release here is a new feature. And so if we go into features, we can see here, you can toggle on the roadmap if you want to see it or not. You can you know, the backlog plan and prioritize your, your your teamwork. You can toggle that on and off and you can basically take the sprints off as well. So you can create more of a Kanban board, that of a sprint board. But then there's also the ability to, which they just added as of this video. This is releases and versioning as is a huge one. Because if you are releasing software or if you're just looking to create milestones, because really in JIRA, context, releases are just milestones within your project. And this is really key if you're going to leverage it for creating just that. So this is something that I'm going to be diving deeper in, in the coming weeks and months to see how it pairs up with deer Classic and how it can leverage this, not just within my software projects, but within my digital content marketing efforts, by online course creation efforts and see how I can just organize the amount of work that I have in my, in my project backlog and share that with you. So really excited to see what, what, what releases and versioning brings to the table. I can, you can see right away as soon as you enable that new little boat here with releases comes up. And this gives you sort of a blank slate to create a version. And you can basically create a version and we'll call it the, since I'm working on my product owner course, I'll say Agile product owner course one dot o. Ok. So my initial MVP for launching my course on Udemy. And it's MVP for initial Udemy launch. We'll do today, which is the 28th. And we'll say released a m will say, Well, I'll just say 14. Okay, and just save it. And now you can see you have a release here and you can tag your stories or your features, whatever epics you have. Two-way release. And, and then, then keep a nice list of your releases within, within the GR NextGen project, at least from a high level, that's a I mean, as I'm as I'm doing this with you, this is the first time I'm seeing it in NextGen. So I'm going to stop the video here and share with you more details on what it looks like, but really excited to see this functionality coming in. And I'll see you in the next video.