Jira Essentials for the Workplace | Jira for Agile Project Management | Mauricio Rubio | Skillshare

Jira Essentials for the Workplace | Jira for Agile Project Management

Mauricio Rubio, Serial entrepreneur, techie, life hacker, PM & MBA

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
9 Lessons (2h 19m)
    • 1. Promotional Video

      2:24
    • 2. Introduction to Jira

      11:44
    • 3. A bit of Jira's History

      10:54
    • 4. An Overview of Jira

      26:02
    • 5. Components and How to Use Them in Jira

      6:22
    • 6. The Jira Board

      43:35
    • 7. What Reports Look Like in Jira

      9:57
    • 8. The Backlogv2

      15:44
    • 9. Roadmapping in Jira

      12:05

About This Class

Jira Essentials for the Workplace | Jira for Agile Project Management: this course covers everything you really need to know about Jira and how to use it in your Agile Projects.

If you're here, more likely than not, you're already aware that Jira is one of the most widely used (if not the most widely used) of all the Agile Project Management tools out there.

Jira, is simple, intuitive, mature, robust and powerful. It is also a reflection of an Agile product itself and constantly gets enhanced, updated, upgraded and improved. So expect to see frequent new and improved versions of Jira coming out regularly.

Why take this course and not another one?

  • It focuses on quality over quantity and what you really need to know about Jira. No bs, no fluff, only the good stuff.

  • Don't spend hours and hours of your valuable time learning about Jira, when you can learn the Agile way with this course!

  • Learn everything you need to get started with Jira in your Agile projects.

Who is behind this course?

An Agile Guru, author of The Mini Book of Agile and founder of The Agile Knowledge Base (AgileKB). I use Jira on a daily basis and have been using it for years! :)

What is Jira?

  • The #1 software development tool used by agile teams

  • The most popular tool used by Scrum teams and Scrum Masters to manage their projects

Is there value in learning about Jira?

  • Yes, a lot! More and more companies are now starting to value people who have experience using Jira. Especially if they are applying for an Agile or Scrum role.

  • Jira can help you position yourself as a qualified professional knowledgeable in Agile practices and tools.

  • You can include this Certification in your Resume or CV. It will help you stand out from the crowd.

  • Having a Jira Certification is a bit like having a Microsoft, AWS or Salesforce Certification. Companies love this stuff!

How can Jira help me to advance my career?

  • By allowing you to manage your projects the Agile way! With a tool that was designed with Agile in mind and for Agile projects.

  • The most important thing you will learn in this course are practical applications of Jira in the real world. This will help you when running your own projects with Jira.

  • Jira will allow you to efficiently and effectively manage your Agile projects. This will in turn allow you achieve recognition not only from your supervisor but also from your stakeholders.

Transcripts

1. Promotional Video: Hey, guys, Welcome to these Jeer A course in these course, we're gonna cover everything you need to know about Vera And how you can use jeer A to manage your agile project. Gee, era from a class. And the company who created this great and amazing product is by far the most popular and widely used. All the agile tools, All this crown tools out there. So we are natural. In these Jiro course, you're gonna learn about the basics, the essentials, the fundamentals of Jiro Jiro terminology, best practices. We're also gonna cover real world examples and even direct configuration. So by the end of the scores, you will know literally everything you need to know. My name's Merisier Rubio and I'm the founder of the Agile Knowledge Base or agile K B. I'm most of the author off the mini book of Fragile. I'm gonna ajira expert like I actually worked with gear up on a day to day basis. I use it all the time, and I have been using Jiro for years, so I can definitely share with you about all of my experience and about how you can use Ghira on your agile projects. and I can also still talk to you a little bit through the different things that Jura has that a lot of other of the ideal tools and scram tools don't have and why it's so popular on why people love it so much. All right, guys, I look forward to seeing you later in the course and just give in mind that even though these Gereb pores was created mainly for beginners, so this isn't has a focus on beginners. It doesn't mean that if you're not a beginner, you can take the course. Of course you can if you're an intermediate user of gear up for an advanced user of gear up and you just want to have a quick recap about some Jura concepts or you just want to see how some other people are managing their projects using Jura off course, you can enroll in this course as well. But just keep in mind that the scores with the sighing and develop for beginners and with beginners in mind we're right, guys. I'm sure you're gonna get a lot over the scores and I hope you enjoy it. I'll see you on the next one. Cheers. Bye. 2. Introduction to Jira: Hey, guys. So in these Jiro cores, we're gonna cover everything you need to know about JI era and how you can use these great tool for managing your projects, especially your agile projects. All right, so without further ado, let's just go to google dot com. And then let's just search for Ghira. That's J I R A. All right, Jezeera. Here you go. So Ajira issue and predict tracking software from inflation, right or flash? So let's click here. Multiple take us directly to Ajira on Dhere. It is. Here is a main website, the main page for Jiro. And as you can see here, they claim that they are the number one. So for development tool used by agile teams. And I think that is pretty much true if you looked at all the different tools that are out there for managing annual projects. Gee, Iraqis, by far the most popular and widely used agile project management tool out there, all right. And in this website, you can see here a little bit of information about Vera. You know, see how we're remaining Jerusalem for plowed reimagining, juris awkward, plowed on. And the best software teams ship early and often, and you can see here a little bit about, you know, dearest, agile camera on board. They just call it board here gives you a little bit of a snapshot of the product. You can plant track release report as well, so we scroll down. You can see a bit more information about Jiro on, and he'll know this natural. Here seem variation releases when we're talking about software project management. Obviously, you don't have to use gear, adjust for suffer or for I t project management. You could use it for any other industry, but it is very commonly used in I T. Which is why you'll see a lot of the terminology and a little things in Jiro referencing I t on technology jargon, I guess. And then, if you go here workflow. So there's one of the cool things of our gear eyes that they have, like the full work flows. And then you can also customize those work flows will get into that a little bit later in the course and knowledge management, you know you can integrate Jiro with different things. Confluences also opened a probe product from inflation. Um, Big Bucket there's a little are things that they have on you can integrate here with. Many of them, like Electra Low, are like planner or like a lot of other things that are out there. And here's a bit more examples of things that you can integrate with. You know, sales horrors are things you know you can see here. There's a bunch of our things. And just so you know, year olds who has kind of its own marketplace a little bit like the app store in Apple or, you know, the Google Play Story and Android, where you have a bunch of ads in advance, you can add onto your smartphone. Jiro has the same thing. They have a bunch of are things you can add on so you can have extra functionality or extra things. Add it on to gear up. Some of them are free, but most of them are paid, of course, because that's how that's how developers and companies make money out of gyros. Well, and they're not, by the way, created by a flash in a lot of them are, you know, from different companies. Their party companies were even developers. And yeah, you know, trusted by over 65,000 customers worldwide, we all recognize, of course, all of these companies are using Jeras Square Base fortified Cisco Airbnb, and they have simple plans hosted in the cloud on and a lot of people don't know. But they actually do have a free version, which is for up to 10 users. Free forever, an obligation. And then they have, you know, another other versions, which, of course, have a bit more events functionality. And we'll see that in a in a moment, go agile with ease. Flexible planning, accurate estimations valued even per organization. Transferring execution, actionable results, scalable solution. So Ajira, like I said, is definitely a great tool. I definitely recommend anyone that he's running idle projects to use Jiro, one of my favorite ones. Estrella, you've heard me talk about trailer before as well, which is in our in our tool to manage agile projects. But about Ghira, it's also great. It is widely used. It is by far the most popular application used for managing your idea projects. And in these scores, I'm gonna show you re a world examples about how using your it to run. So my agile projects, and that will give you a taste for what you can do with Gironde what it actually looks like . But I'm also gonna show you from scratch what you can do with Ghira like like, if you were just starting how to do it. Let's just start by going to the features as well off the era. So features for suffered development scrum boards or Cambon Boerse's will, or what we call agile Campbell boards. So to dio doing were in progress and done as you can see these example of one of them right there injera, rope mapping as well, which is in our really cool things Or Jiro does allow for you to have road maps and agile reporting, connect issues to code slurs, a bunch of different functionalities and features that Jiro has. And there's a lot are things you can do with it, which will cover in the course. But mainly G Race used to manage Idol projects or mainly used by project management teams. But it's also used by product management teams as well, and they have your brought guy enterprise pricing. Just quickly look at the pro guy, So how do you steer a software to help into little guides a brief or view of direct weeks. Our guy, that's practices. So I definitely recommend that if you're just that brand new user, first time newbie using gerund you've never used to before, have a look at this guided tours and guided articles and to your on inflation provide. There's one of the really cool things about a clash in or inflation. Sorry. If you hear me interchange with the name of the company doesn't really matter. Some people pronounce it that let a flesh in others like, you know, like myself. Something's pronounced inflation. But anyway, beyond that, the point here is Jezeera, which is a practice one of their many products Flash and does have a little our products. But Jerry is the most popular for other products, and it's pretty much a product that they're known for. And you can see here a bunch of fake use, you know, they have ah document. You know, the commendation. Like a knowledge base. They have Ajira community, and they have, you know, a place where they post everything that's coming up. New enterprise. Of course, if you're in a big corporation, you want to use jeer? Uh, you can also do that. And then they give you You know how you scale, how you do things. You know, the big corporate level as well, which is why they have desire, you know, information for you available here on pricing. It's pretty stable, by the way. The pricing that can say I've seen it changed much over the years. It is pretty table generally on, you know, hear it. They give you a bit off comparison between the different versions off era. I think you know, if you have less than 10 people on your projects, starting with the free version is good, because it will just give you more than what you need. And then, of course, if you need to upgrade, you can always have greater at any point in time to one of the other plans. It's not super expensive. You know what, seven bucks per user per month or 14 bucks per user per month on the premium version, but also, of course, this depends. If you have a very big team, then, of course, that can become quite expensive. When you get this. You know this prising but generally most companies provided to their employees. So you're working for a company that is just using Jiro you most of time. You won't have to pay for it yourself, but they do have a free option. Like they said, it's living it to up to 10 users. So if you're in a small team, used a free option. If your company's paying for Jiro, well, you don't even have to think about. Pricing is probably busy. Little Bee is probably not very relevant for you, but I just wanted to show you in, in any case, even if your company's paying for it. Just so you know how much your company Spain for Ajira on. Obviously, this will depend also on boarding. When are things, But that's that's pretty much. And they have here off course, a bunch off pricing if it use for you. And yet they also have off Self Man National they over a cloud based version. But there's those, of course, a self managed version, which means you would actually hosted yourself on day have here. You know, of course, different different payment options, depending on the volume as well. But let's go back to the cloud version. If you ask me in terms of what I would prefer or what I would recommend it in cloud and self managed, I would always go. Cloud Cloud is the future that is, with where almost everything is. You don't have to worry about hosting things yourself. You don't have to worry about pushing upgrades yourself to the suffer, either. When you're using the cloud version, it automatically pushes everything for you. So if you know, if you were asking me between whether to choose a cloud or self hosted, I would definitely go plowed. The only in scenario I will recommend self manages when you you know there's some companies that have very restricted and constrained about putting things in the cloud because of privacy concerns, or they might be in a country that has issues with things being the cloud or whatever. If that's the case, then yet you have the self managed option and then I would recommend it, but nor normally and typically I would definitely go for the cloud option. All right, so that's basically a very quick intro to what you find on the Gee Rob website on a very high level overview off era, and we'll get into that in a moment in more details. Like I said, if you go to the pricing tab, there is a free option, which is what I'm gonna use initially in this part of the course just to show you how to get started, etcetera. But there's also I'll show you later on a paid version way, even with some extra Adams that we pay for in the company that I work for and how we're using here are in, you know, in the real world, any real products, right? So if you were going to sign up for the free version, will you go to surprising page free? Get started? You don't take it, too is very basic. Sign a page. Like I said, cloud free from to 10 users to go. I don't stretch etcetera. It gives you the option to sign up with Google or with email. So I generally I prefer summing up with email. That's just me, but give you prefer exciting with Google. That's fine. So there's gonna go here, no break are required. Like I said, this is the free option. C. Enter your email address your past. You create a password you know you possible for gear up? First name, last name, agree and sign up. That's it. Pretty easy. Pretty simple. So I just do that. If you're signing up for Jiro for the first time. And Dan, you can get started with work. What? We're gonna be seen next. All right. See you on the next one, guys. Cheers By. 3. A bit of Jira's History: Hey guys. So before we deep dive into gear A and get to know Giresse a product, I thought I'd spend a few minutes talking to you a little bit about Gee era and its history on a collision and its history and a little bit about the company, etcetera. And of course I'm not going to spend a lot of this, but I just wanted to give you a little bit off a background because I always think it's important for you to understand a little bit of history and background, the process that you're using so a low, if you might not be aware. But jeer A and a flash in are actually Australian companies, which is great because you know I'm Australian, so I'm pretty proud because a flashing is just one of those huge success companies here in Australia. Up and worldwide. It's one of those unicorns is one of those companies that has done great things not only for Australia as a country, but for the world in the tech industry worldwide. And obviously they there now huge. They're a big company. They're no longer just here in Australia, but the offices across the world and their products are used especially in particular a lot of their parts areas worldwide, not just Europe. But Ghira is like, Seriously, it is like Is the Ferrari you know is it is the Mercedes Benz. It is the top of the line, the best brought on the most widely used product. Fragile project management and agile development. And that's why a lot of you, you know, it won't come to us a surprise when you see about Vera or that you've heard about Jiro before because it it is quite popular. It is the most widely used tool for managing adult projects. And like I said, it doesn't have to be just I t Like I said before this happened just I t projects. But it is more most commonly used for writing projects, obviously because agile s you'll know was born in the I t. Industry. But that doesn't mean, of course, that he can't apply adult to other industries are to other types of projects. Yes, you can. It's not just ideal is not just for ITV. And there was morning I t now this is using marketing. Hey, Ciara Finance pretty much any industry you can think off, and the same goes for Deressa product. It is used pretty much in any industry you can think off, and let's just go to the A flash in page on. I also want to take you to Wikipedia. Wikipedia thought orig. You know the world's encyclopedia. So if you go here to Jiro Software 2nd 1 you'll be able to see their reckoning. Wikipedia information about Vera and this is the you know, the Wikipedia Jiro Page on basically shows you a little bit off, you know, jurists history on. As you can see here, the initial release of Jiro was in 2002 so that's a that's a while ago, which means that gay rights are very much your product. It's a very robust, well structure product he was reading in Java. You know, for those air developers and I know a bit about technology about different technologies, Jiro is reading in Java is cross platform, meaning you can use Jiro, you know, on a Mac or a windows of eyes on the limits on anything you can use. Gerald. There's no no issues with these injera in any type of device that you're using on board, you know, the company. Like I said before, the company is a flash in the company that found it and just something that I thought was interesting when I when I was reading a bit about history off, you know, off Jiro ages ago is the product name Gojira, which is the, you know, the Japanese word for a good seal. You know, the mustered a dinosaur concealer. So in Japanese, the world, the word they used for Godzilla is Gojira. And then when you shorten that era, it's It's just how they gave the name to the software in this company. In a flashing like a set of flashing is is this Australian but the practice now used worldwide. And if we go to the flash in website just a flash in dot com, that's a T l a double s i a n dot com slash in a t l a double s I and dot com. You'll get this website and you can see a lot more about their products, you know, off abuse. Obviously the 1st 1 you see is Europe because, like I said, it is their most widely used on most popular product. And just so you know, a flashing is hugely successful. Like I said, as a company, they generally grow on 33 between 30 and 40% year on year, so their growth is huge. You know, they have hundreds of thousands of users worldwide on they make billions in revenue. The guy one of the guy that I co founded, a flash in, which is Mike Cannon Brookes. He's a bit like the Steve Jobs, the Australian Steve Jobs, you know, he's is this tech guy Entrepreneur came, you know, built here from nothing. And nowadays he's one of the richest man in Australia. Obviously, he's also one of the richest man in the world. And I think if I recall correctly just to give you some context on how Rich is, I think the house, I think in the house he bought his house, a house he lives in. Hey, paid about $100 million for it. It's a house here in Sydney, obviously a beautiful house to mention eighties, one of the most expensive, if not the most expensive property ever bought here in Australia. On that, just to tell you lied about his success I really like the guy with the way. He's a great guy. He's very conscious. He's always trying to help the country. He's very politically active as well. He's always comment, commenting on different things of the country's doing. How we can improve your in Australia on, you know, people look up to him in his company. He's very respected for the everybody that works for him, for the company respects respects him. He still has a very active role in the company he's still involved with. It also hasn't stepped, stepped away from a place oppression. He's still there on then, like I will see saying before they have different proximity. You can see here not just off course. Jiro Jiro service does, by the way, for anyone that's familiar. Where Service Now, which is also very popular and widely used for anyone that has seen, you know, support roles. And they have companies that are helping out people with tickets, etcetera. So that would be the acquittal of it equivalent from apply a clash in would be jury service disk, Um, and like I said here, they have a lot more information or 150 companies worldwide. here just on the companies they work with. And there's a ton of videos here on the look really good information on the pro eternal. Here, Resource says at the bottom, expanding. Learn a little bit more, and then you can read more about the company's history, etcetera. Or you could just go there if you do Wikipedia like I said, I'm just enter the name here. We're looking at a zero. But you could also assertion we could be here for a flash in. All right, here it is. It's a public traded company, turrets in an ass like in the US. Um, here is the guy that I was telling you about. Mike Cannon Brookes. He's a guy that but that that you know that house for over $100 million.400 million dollars , um, you know, was founded in Sydney here in Australia, on here. The products the revenue of the company last year was 1.21 billion. They have over 3000 in place. It's quite Biggs, really interesting, and you can see here a little bit more history with the company and positions, etcetera. They also own trailer, by the way, So if you are using Trillo dot com, which is also heavily used world life. So this is now on a flash in product. It wasn't actually created and by a flashing by the way, they bought that company a few years back, and now they own it. But yet so, just like I said, I wanted to give you just a week, you know, just a week bit of history around a flash in and around Ghira, another product on. Probably talk about this in a different course because of these courses about Jiro. But there's another really popular product from a flashing court called Confluence. So we search your cough lends. Um, if you want to guess Google, you know Google. Com. If that's what you wanted, Teoh and just search for confluence, so you probably get the so far, this is in that. So I'm going ignore that. But if I went hear complaints from a flash in right here, so I take it the conference pages a bit like a conference. Just so you know, I'm gonna just doing a bit of history. It's a little bit like and knowledge base or like a wiki. But created by a flashing for people to collaborate on projects on. I'm not gonna go into detail off that right now because it'll probably a separate course, but I wanted to give you, like I said before a little bit of history and a little bit of background on a flash in, which is a company that created Ghira on jeras will. And that's what we're hearing the Wikipedia page. And I'm not going to read this off course over. You can read it yourself, but I just want to show you that you can find this if you went to Wikipedia a little bit of information about a flash and on also more information about Europe. So this is is a good place for you to just get a bit of background. And, of course, in the website itself, on that attraction company website itself, you can really little bit more about them on about what they dio some really cool, cool stats. You know, offices in seven countries for 1000 flashes $132 million into community, 2.6 million community members you can see here on. Then you can see here a bit more of other history in this timeline, if you go here to the to the back about how it all started. And of course, there's more more information here about values off with flashing is a company and what they do anyway. Love, Really. There's a really cool company, you know? It's like it's like Google. Like Amazon. Like one of those really, Or like Apple is one of those really high tech companies on. Like I said before, it is one of them, one of the greatest companies that Australia has produced for the world. And anyway, like I said, I just wanted to give you a bit off background on here on a flashing. It's a company just a bit of history on. I'll see in the next one, guys. Cheers, Bye. 4. An Overview of Jira: Hey, guys. All right, So, like I said before, I'm gonna assume that you already went here on you Signed up for the free version of gear up. You just get started. Then you just enter. Or either you sign up with Google or you enter your email password. Obviously, it's a new password. They're sitting up for these fridge era, and so it's not you enter your email address, then you create your passwords. You got your passport for jeer? Uh uh, Your first name. Last thing we want. Sign up. They'll send you an email to confirm your registration. Once you confirm your registration, you'll get to this page. Let me just show you a moment. This is basically where you'll end up once you go to your email and they send you that confirmation even after you signed up. Which is pretty standard, of course, if you used so for approx before, if you're here, is any website before? Generally, when you sign up, they not always, but a little of times they send your confirmation link and then you just click. Verify your account and then you're set to go give your Jeron name. Give your It was like, OK, so there could start. Give your side of name shows something for me, Like your team or your company. Okay, so you just set this up again. We're using a free version. Doesn't really matter which name to use. You can use whatever. I'm just gonna put here gear up course and then, Okay, the name is taken, so I'm just gonna say Jerrod cores unique. All right? It's free. So it's a It's a little bit like, because this is a bit like, you know, when you're creating an email address or whatever that because it's free, somebody else might have already taken it. Don't worry too much about that. You know, this is just something you can just putting whatever name you want. 01 of putting its get continue. Then we'll continue with the process of setting this up again. This is a one off thing. You don't have to do this every time you log into gear. Uh, this is now because we're just kind of like Sarah setting up. Um are Jiro, you know, our Jiro for the first time. So if you already have team members that you wanted to include when you just entered the email address on and then they will just join, because I use my mauricio rubio dot com email address. So it was kind of like my company, right? So it basically allows I can I can allow anyone without Mauricio that rubio dot mauricio rubio dot com email address joined the Jiro. You can do the same if you are. You know, if you're working for a company you know, block at company that come, then you can take Leave this stick if you want anyone from your company to be able to use You're generous height if you don't want to. If you want to get private and just by invite than on tick ticks on Dick, this book's let's just on ticket. So this is, like, fully private. I'm not gonna have people right now because I'm just gonna show you. We'll show you an example later with people. I'm just gonna show you real quickly than usual set up and what it looks like. But, yes, you can invite people. Obviously, you can invite people later on if you don't want to do it at the beginning right now and you don't want to enter their email, you can do the later. So this. Just click Skip and then help us set up your Jiro. So you can say here I'm new. New to Jiro. My team is that's a new settlement authorities. We spend our time working on features of board operations, fixing bucks. Let's just say features again. Don't worry too much about this. Is it just something you really uses to kind of customize your experience a little bit, reorganize things in a way that might be more useful to you, seeming not to like Google and other companies do. But it doesn't really affect too much of you. Choose one of the eruptions, and you can always change it later on. If you wanted to. Of course, let's say features. We have a type, flexible scale. Let's say type generally when we're working on anything, is tied or again. Like I said before, you can skip that. You can skip this if you want to skip it, but let's just leave it like this next. All right. So choose a classic template, so they just basically set this up for you, depending on watch. You want to use on. Obviously they have a lot of information as well. Doesn't have to be sulphuric and be business. You can change this product management test tracking process, control, content management, recruitment document. But let's just assume that you're working on a project and an actual project. And like they say here, they're recommending something for you. Scrum So scram is generally how you manage your ideal projects. Not obviously, always. Of course, there are a lot of our agile methodologies, but the most popular and most widely used in the most known to most people it's crumb. So you're working on the actual product. Just big scrum on Teoh set up your you know, your Jiro site here in Europe page again. There's something you could change later on if you wanted to, so don't dwell too much and it just goes crumb. And in this course, I'm gonna focus on as if you were using an agile project because I know for a fact that most people use injera are working on agile projects. So I'm just gonna go on, make the assumption here that you are working on a national project and that you are using scrum again. Even if you were using another agile mythology, I'd still recommend that you choose this template or these Jiro set up with scrum doesn't mean you can be using the as the M or, you know, extreme programming or one of the agile methodologies If you wanted to with this scrum seven and it's just kind of like a template, it doesn't mean that you have to run the break in with scrum. It is just setting up the software for you in a way that is user friendly and in a way, the most people using the step of idle mythology would use it. So yeah, just go with scrum Select Create Project and Terra Project name Celeste is called Is Project Example. Okay, The key p What is a key? You click here on on the I for information. The product key is uses the prefix of the process. Eat your keys. E g Test 100. She was one day this creating I needed to prototype. All right, let's Z listers expert example Key P. It means anything that it's created Indira And here, by the way, talks about issues and I'll explain a little bit I little bit about that later. But issues can be pretty much where you define them to be, so they can be actual issues. So actual problems, actual bucks, or they could actually be user stories or epics on again in these scores, I'm gonna make the assumption that you know the terminology about agile I'm not gonna teach you about agile in discourse because this is a dear, of course, and agile cores. If you're in this course, you have zero knowledge about agile. I definitely recommend that you go through my agile course, the idol crash course and or one of my other agile courses. You get familiar with the terminology, but yeah, definitely. I'm gonna make the assumption that if you're in this course you already know about agile and we're just learning about Jiro because this is a year, of course. All right, so let's just go with this for the example automatically created the keep eat. Don't worry again about too much that you get too much about that. You could change this temple like I said before, if you wanted to, but let's just leave it with scrum. I recommend that you live with describe it's what they recommend it as you saw before in the the part before we wear or within the self here in injera. But if anyone asked me what I recommend how you set up your gear up, just use the scrum one. Okay, that's the one I recommend. Just go to create. It's just going to set up. Just let's give it a little bit. All right, here we go. Guys. Here we go. So this is what Gerald looks like. You know, this is a Jiro. I think this is a free version of Ghira. Like I said before, you can you can have more people if you wanted to have more people. Here is the left hand side menu and project. Example Suffer project. Okay, You could have more projects he created. More products of you were working on multiple project. So there's one of the really cool things about about jeras. Well, you don't have to stick to a single project, you can have multiple projects and you can see here we have the board to do go here to the board. You could create more boards were right now in the p predict example board. Right. So pretty example. Board to do in progress. Done. Um, the backlog. So this is where you would see all of your back? Look on, Let's say you have one. You can create one right now if you wanted to write. So let's just say example. User story, All right. And yes. Is this story is your story tasker bottom in just todays It's a story on gives you this little three buttons here because you can actually obviously have more details to it, right? You could also change it into an epic, right? So if you don't remember again, I like I said before, I'm not gonna go into all the agile terminology and all. What? You know what? Agile using this course because it's Ajira cost, of course, but just a quick reminder, if you remember where what an epic is so epic is basically a user story than you can't deliver or a single spring it means is a very big is her story. So when a user stories too big, bigger than something So it's big too big, it actually can be done in a single sprint. We call it in agile and epic and that's where they have here. Injera epic. The Work ethic You can also great, of course, tasks. Remember that in actual user stories are generally requirements. But a lot of times we also interchange liberty used tests or user stories in agile, so don't dwell too much on that, either. I generally would recommend that you classify you think that you're working on Indira US user stories or stories for short. They use the word story here to shorten user story a story. So it comes from the wording at the Tour teen Idol user story. So and then epic right? And here's an example. Examples. There's used her story on you could have more things. You can attach things to the to the story itself. You can create another one if you wanted to, or create this one updated configure fields. So this allows you to customize this. You can click here a custom, so there is one of the other things. What people love Gironde, whites or powerful, and it's because it allows you to customize a little things by the full bill, put things for use with they'll make it easy for you. But again, if you wanted to customize it, you could customise it as well. Where is my fields? If you're trying to find something, you can find the heavy search functionality here. I need a little allow you just start searching for something. That's a description. All right, I'll come up. So, like I said before, Jezeera is quite robust. It's quite it's quite powerful. It was launched in 2002 has been around for a while, and they're always doing things improved here, which is pretty cool. So I'm gonna figure Cancel. Okay? Yes, I want to cancel this right. Active sprints. So if you're running through your sprint this where your active Springwood were appear, then if you went to reports, there's one of the reasons. By the way, I'm just giving you a very quick overview off Jiro. This kind of like a quick tour off Jr will get into the details later in the course, But here you can see there's a bunch of agile reports that they have automatically created for you. And of course, you'll is well, because we'll actually make more sense to you when you have actual content when you've actually going through creating your user stories, your sprains when you have people to the project. But I just wanted to show you that this is included in the evening. The free version Algeria. And it is something that a lot of the I guess ideal software are agile. Project monitoring software up after they don't have a lot of this stuff by default, you actually have to. Creating an Excel or you have got by an Adam or you have to buy extra functionality is one of the reasons why actually so popular and so whether they use because a lot of these reports are automatically done for you so you don't have to use Excel. You don't have to use Adel's or you have to pay for extra functionality. It's included right there in your Ghira. The burned down chart, typical of vital projects, burn up saying the opposite spring report. Velocity charred, cumulative flow diagram. There's a bunch of different things and one of the really cool things I also like about gear, I said. They give you a little bit of a summary here, uh, what each report is, and then if you click on any of them, it's just kicking the Brendan chart or easy. Right now, nothing's gonna come up because I don't have any data yet because we're just sending these from scratch. But I just I just wanted to show you always see it's coming up with There are no available springs for this portal. What? They can't really show you any data. But if you actually added a project and you actually have your user stories and he actually had users, you could actually see reports here on. We'll get to that in the course. Don't worry. We'll get to that. Like I said, this is just a very quick ah, very quick, high level overview of Jiro for you. I'm like I said, You can collapses as well. The many here. Expand it on you conceive back to project. Let's just go back to project. So you have this. Is this kind of like your standard? Typical. Just gonna go to the keyboard. Let's go to the product example Board. This is kind of like your actual camp on board. Um right. It went to here to just a report, but we could just go here to stealing the reports. Let's go back to project Active sprints, right? So this is where we would be set conflict or actual camp on board or candor. Borer Scrum board. There's different worth of people used to describe these boards, but here and here they just called it. They just call it board. Thank you So before keyboard andan active Sprint, the Back look reports, releases, issues and filters pages, components at an item, project settings. All of these is, I think, pretty much self explanatory. But of course, you can explore all these in detail if you want it to the releases where you would have, you know, let's create a version and the version. So this is again coming from suffer development. You generally seen these, you know, Windows seven and Windows 10 right where you see so far, version 1.1 point 11.2. That's why that's what in the world we talk about versions and then releases so release would be released 1.1 released, 1.2. So it's kind of like that burgeoning that we're referring to in software development and in 19 issues on filters. So any time you have your issue, so if you remember all issues well, let's click here and create. Let's just create one real quickly. I think the other one. I didn't save it. That's why then created. But let's just break this test or example. Use her story again. You can attach things. I'm just gonna say they use her story. There's a lot of our things cannot hear. I didn't show you this before, but you can scroll down who reported this? Is this an issue you can assign to that's assigned to Mauricio where you wanna sign? Priority High, low lowest. You can also customize this way the way. So you're allows you to customize a little things Spring. We have a creator spring yet, but if he created this spring, if you cannot hear that which sprint, we're just creating the user story, right? So less is to create. Okay, so proud Example One so effectively, if I did refresh here, it should come up here under old issues. Here you go. You go, guys. So it wasn't coming out because I hadn't refreshed the page on rumor. The cloud versions When you change, you just need to refresh it or if you click on something and then click back again. He would he would have come up for you. So this is just a very big example. What I use your story would look like injera, and you can attach things. You can create sub tests you can link things on and let's just go back to project. We're here on issues on field tears. So remember that when you create something in Deraa like a user story, all of that the generic terminology and Yuri's issue. And there's just comes back from a bit of the history when we're talking about the history of Jiro. Initially, it started like a buck trucker, you know, high in sulphur development. Home bucks issues. So Jiro, when it started as a broad, initially, it was maybe for tracking bugs. But over time it became an agile software development and Antal project management tool. What Some people still use it to track bucks, and that's why our issues and that's why you can you can still create our by the full the terminology that they use issues. But it doesn't mean that he didn't his early is an issue. Of course, you can actually change that. The user story a task or an epic like we saw before on if you want to pages. So again, this is just If you wanted to a notes or requirements or retrospective, you can do all of these directly. Injera. Isn't there really cool like I did? Your retrospect is here directly in your project directly injuries again. One of those reasons why people really liked here because it has everything kind of like bundled together components. Eso components are subsections of a project using to root issues. We've been approaching into smaller parts. So I guess the best way to explain this component think Think of it as categories or streams of work. So sometimes we might have things were working on a pregnant, relate to marketing or them. I relate to procurement or they might relate to maintenance. Whatever it is, you know, those streams will work. You can use that by creating components in Europe, so they're kind of like categories or streams of work on. I'll show you later in the course a real world example of how we're using these in one of our projects at item so you can have a short cut, you know, a bit bucker. Give him repository pages already there. So this is just something like some extra things here. If you want to see in your gear up on the project sayings if you click your product sayings he's afraid that we created you know, before you can change your Al Atar that makes me here for you too. Oh, I'll sign your easier stories or your test to the project because I can remember they could have multiple projects of the avatar might just help you. This is useful when you have multiple projects and then you just want to recognize something with a picture instead of the name that That's why it would be helpful in that scenario and again here, you can see your left inside many Let's go back. I'm just gonna go back back to project. So they were just We were just in predicting So again, we've gone through, and this is a very quick, high level to really quick tour. And don't worry if I if you're feeling going too fast over all of these, will actually get into real world examples later in the course so you can see these in action But I just wanted to give you a very quick tour off the menu on one of the things where they look like what you see in general. When you go to Ghira and again here, you can see that there's a lot of our stuff here on these second, so they have kind of like to left hand side menus. So, dear software start in recent years, you click your start in recent, it will show you a recent things that you've done right or that you've start. It's just like a quick navigation things. Sarah to you wanted to search for something, create eso the plus sighing again. If you want to create a user story a task about Warren epic, you just kind of like a week, you know, we want to do that notifications again. Everybody used to seeing this little bell for identification. So if somebody created a user story, or is somebody updated something or they completed something? This is where you would get that notification. These older something that is pretty good, by the way, in jeer at you. When something does something or update something, you automatically get not just identification and Jiro themselves. But you also get an email automatic email sent to you. This is really helpful, of course, because you don't have to actually go to jeer a to see what's happening. You actually get that they're wrecking your email. And in the modern world, a lot of people spend a lot of time in their email and you know, they might not have time to go toe, You know, the Jiro side and actually look at where things are at. And they might just want to get a quick notification delivered to their email so that something that Jiro does automatically and you're experiencing using euro you'll see that in your in your in box and and switch to so again, if you wanted to try cough lands for one of the other products from a flash in these where you would go to help so they have a help page communication community. What's new about Vera? All of these are information that we saw before on the website is also right here injera when you actually look into it settings. So these kind of kind of like your dearest sayings that means that of saying systems, products products issues, etcetera. You can manage all of these directly here from this part of the menu again configured your issue type work for the screens, Custom fields on more so, dear it. Like I said, it is very flexible. It gives you a lot of options again. You can see here you can add another type of issues. So it doesn't have to be just this once that we're seeing before these were the standard ones that appear because this is what people use normally, you don't have to create anything else. I'm just showing you these to show you just how powerful giris on. Just so you know that you can actually customize things you can actually rename this, that the eye comes the name here, you can translate it. You can do a lot of things that you see here, that he should type of delight to another type of issue. So this is one of those really cool features and functionalities off here is a probably it's then you can actually rename customized things at things, remove things, move things around, create work flows, create different types of issues, different types off kindof convention names or things, how you are referring to things in the product. And that helps because, you know, there's generally all of things where there's no one size fits. All right. Each product, it's unique. Each team is unique. They might have their own criteria, their own jargon, their own things. And this is really cool in general, which it means you can actually customize it. But most products this the standard names will still apply especially, of course, if you're running an agile project on your profile. So if I went here on, you know, this is me, Marisa Rubio, um, settings profile. Let's just go to the profile So you guys gonna see what it looks like? I'm just go collapse this here. So it just shows that I'm working on this user story. My job title, my organization department. Here's how you can contact me my email address. Ask up Morrissey Ruby that come, I can create a team so it's kind of like, you know, like in anything else, like your Twitter profile, instagram profile or whatever. Most most suffered developing tools have your own kind of like your patri kind, your avatar etcetera, and we'll see a little bit more about this in the real world example. But like I said before, I just wanted to give you Ah, flip a beautiful taste for the different things in the menu. Remember, we have too many is here. One is collapsed. These ones here. Um, as you can see, the menu here also changes of big depending of your wrecking the project. So here it's kind of like a more high level. Imagine a treaty is idling the high level Many. But if I went here on projects and actually went into the specific project example that were seen before or if I click here below wherever. Doesn't matter. You can kick here, recent or here below. You can start things as well. Just get here. This many here will change. And now we'll show you the typical Ghira. Agile deer. A menu with sprains, your back low reports, releases, issues, pages, etcetera that we saw before. All right, guys, I hope you found this useful. And it's giving you a bit off on internal beautiful overview off era and how you can use Jezeera on, you know, just different menus available to hear the different taps. The different things that you can do in boats. In both men, you're still the one here and the one here as well. And a beautiful if labour for with the rays and how you can use it. But don't worry to match. If I if you felt I went too fast through these will actually go into a real world example that will apply. Follow these things for you. And in any case, of course, you can always go back and re watch this video. If you feel that you want to re watch it, uh, you can also change the speed of the video. You know that a lot of the tools now they sell us. That could change the speed videos we can pause on replay on. Of course I'm here. I'm here. If you have any questions, just let me know. Happy to answer any questions you might have. And I'll see you on the next one, guys. Cheers. Bye. 5. Components and How to Use Them in Jira: Hey, guys. So in this part of the course, we're gonna talk about components. And if you go to your Ghira on the left hand side, Manu, you're gonna notice that I'm actually here on the components tab or on the components section off the land, left hand side menu, All right. And before we go into the detail of these, let's just weekly talk about components. So components injera are pretty much categories right or what we would call in projects. Streams of work themes, right in stash. In particular, we have this dreams of work for the components that you can see here on screen archiving, audit requirements, data governance, Discovery portal publishing. Essential Mountain is researcher engagement and storage. These basically means that every single thing that we're doing in stash falls under one of these main categories, or streams of work or themes. Project themes, streams of work categories, whatever you want to call them injera. They call them components, right. And that's why you see that little icon off like, um, a piece of a puzzle piece. You know, a beautiful puzzle is because though all of this coming together when you put all of them together. It's what actually builds your product. It's what, actually, because your project, it's what, actually being whatever it is that you're doing, okay, in our case, every single thing that we're doing in stash for researchers these year and in this product falls in one of these components. Okay. And all the issues that you can see here that are having created injera are assigned to one of these components. Obviously, these are not the only issues that we have in this project. We have a ton more, but these are the ones that were actually taking the time toe assign to each of those components. So these are probably the top priority things that we're working on. And the truck top priority issues that remember the war talking about issues injera, they can actually mean tasks, sub tasks, user stories or epics, whatever it is that we actually assigned to each of these components, right? So if you wanted to know what's underneath each of them, remember, you can just write leak open, linking you tab, and it'll show you the details off each of these components. In this case, we're seeing the archiving component on. We can see here on the left hand side that this one is an epic. This one is a user story and so forth. Right? And we can see more details about each of these issues in gear. I've already explained to you guys what issues? Meaning, dearest, I'm gonna go over that in detail. But like I said before, just this is where you actually go and can see details of each of those issues. Indira. Okay. And I'm just gonna go back here to component again. You could easily create more here, you know, enter a name here and after you completed all of these details and your test and you got it here, component Lee, we're on a sign that say, and if you look at, you know, just basically at a new component. So I'm just gonna remote this test. It was just an example to show you is so here. Optional optional. It's where I left it without adding any anything to it on again. Obviously these little three I these little three dots. If you're used any sulfur product before it just kind of shows you that it the connection. If I clicked on this I click on edit, we're delete. It'll basically exactly can edit it. Allow me to edit these archiving component. So if I click on edit, it will show me more details about this component, which is basically not a lot of information, because that's how you create components is very basic and minimum and minimal information . But you could actually change this if you wanted to write. This is a place where you do it and with the full of the we left this unassigned because for us, it is actually not something that we're assigning to a particular person. But in our case, these themes are These categories are things that were working for the project as a whole together. So everyone in the team is working on these together. It's not just something that we would assigned to a particular person, but generally it's something that most, if not all, the team are working on together. It's just that there might be different people working on these components in different points in time. Andi does basically all you need to know about components. There's nothing more to it is very easy, very simple, and it is very good and very powerful. When you're doing this to manage huge project and you want to break the work down into categories going to things of work, this is the way you would do it injera by using the components functionality on didn't think of it as, like us of parents umbrella and then under that parent umbrella, you can add each of your user stories, epics, sub tasks, task, whatever it is, and that just allows you to. If you ever wanted to do reporting on them, you could do reporting on the things that you were working on in each of those components in each of those categories. If you wanted to see status and different things like that, you can see all of that in reporting, and we'll get into the reports in our part of the course. But in this components bid, I just wanted to really quickly show you how you manage your components, how you can edit them, how you can create them, how you can delete them, which we will raise off, click here, edit or delete on. And if you want to search for something right here in the components that say you have hundreds of them. Normally, you won't have a ton of them. Most predictions have a few categories or themes of work, but if you did have a ton of them, will you have the search from Shelly right here at the top? Andi, you will be very easy for you to search for those those things that you're trying to search for. And, of course, don't forget that there's also a button here. Managed components. If you click on that, it'll just show you different options like we saw before about editing the leading, adding stuff but directly here under project settings. Just kind of like a quick link to your project settings on going there. Referee two components like we saw before. So I'm just going to click again here. Two components who go back to that view and that's it. That's basically all you need to know about components. Injera. All right, guys, see in the next one. Tears by 6. The Jira Board: Hey, guys, in this part of the course, we're gonna go through a real world example office, crime board injera or what a lot of people referred to, as well as an agile board or ajira board, because it's here. Injera. All right, But before I get into the details off this example and what it is, I want to talk to you a little bit about the project. The project that is represented in what you're seeing on screen and we're gonna be covering in this real world. Example off how we're using Jura in one of her projects. All right, so I'm just gonna go here a second toe Microsoft whiteboard just to illustrate what this project is about. All right, so this project is called stash, okay? It doesn't stand for anything. Particular is just the name that we've given to the project and basically specifically to the product that we're gonna go through in this real world Example and stash all you need to know about stash. It's that is a software for researchers. So the user's off these system, right? The people that are using stash our research chairs. Okay, So they're researchers that worked for, Ah, University rights or there you knew university researchers. Okay, on basically the Ustashe to manage what we call research data management plans. Okay, We're are the m piece. All right. Obviously, this is not something that you need to learn from memory or that I expect you to learn from memory. I'm just giving you a bit of context to So you understand the product project that is covered in the real world? Example Aguirre. All right, So stash, like I said, is the name of the project. Right? So this is a project, right? And we are managing this project and everything. We're doing the product directly in Gironde. That's what I'm gonna talk to you about it because a really good example off how you manage rial world real life projects directly injera on. Of course, this is an ideal project and we're using Scrum to manage this project. Obviously, we also have a team of people running this. We have to developers working on this. So one business analyst, one b A. We have 1 p.m. And there's one manager working with us on these projects. Well, all right, so this is more a bit like the team, all right? And I'm talking about the core team here, of course, because there are more people working on these behind the scenes, and there's a lot of stakeholders involved as well. But I just wanted to give you a little bit of context. Before we get into the detail of the example and how it looks in Gironde, how we're running the project, it's hitter up. I just wanted you to know a little bit about the project, and I'm not gonna go into all the details off stash. But basically, like I said before, all you need to know is that it's a research that a management plan system that allows researchers to manage their rdm piece and why dio you know why the researchers need to manage their RD MPs will, basically, every time they're doing their research right, when there's a researcher doing any type of researcher, most if not all, of the times they're working with some type of data, right, and that could be images that can be numbers that can be audio, that can be pdf's were documents, interviews. It can be Agassi lian different things, depending on the type off research that they're doing. Whether it's in science is whether it's an engineering, whether it's biomedical, medical, you know, social sciences, humanity's it doesn't really matter, like, regardless of which feel they're doing the researching, they most likely most of the time, if not all of the time are gonna have some type in some form of data. And stash is the system that basically allows them to manage that data right? And that could be archiving it, publishing it, sharing it, storing it, etcetera. All right, so stash is a big system on. It's something that we've developed using different technologies. And now we're a stage where we're continuously improving and enhancing the product. Right. So stash here is not only a project, it is also a product. Or what a lot off you would know us software. Okay, so this is basically what Stashes, right? It's just a system, a product application that we used to manage rdm piece, and that researchers themselves used to manage their own rd in peace and share it with the world with colleagues with our people within the university. All right, so now that I've given you a little background on stashing. Like I said before, I don't want to go into a lot of details, but feel free to go, you know, message me on text me or send me a you know, a message if you have any questions about the project and the example that I'm giving. But like I said before, obviously this is a quite a complex and huge project within the university. And I'm not gonna go into all the details of that right now because I just wanted you to have a very high level overview of what it is that we're doing. Like I said before, basically, what we're doing is we're adding new features to this. So all the time we're adding new features, adding new features, right? We're doing integration with other systems and other applications or integrations. All right, and other things that we're doing are just general improvements and enhancements, All right, And that's basically what we're doing with this project. We're adding new features, So every time we talk to our researchers, they might give us ideas, you know, for new things that they want him added so they might give us ideas or suggestions, you know, just basically new things that they want basically meets needs that they have, that we need to meet with system. So that's why it ends up translating into us, adding new features over here. And obviously because there are other systems on other applications of researchers use, we also integrate with them to make their life easier. And obviously we're also making constantly improvement improvements and enhancements to the system because we want to make sure that they have the best product that can have to make their jive job easier so they can have an excellent research project. Research that a management plans are quite important for things that we refer to US research excellence. So research excellence, um, also data integrity gotta integrity on other things, such as ethics. All right, so these three things are quite important for people when they're working with research, right? They want to make sure that they have the best practices and principles when they're doing the research projects. We wanna have integrity off the data, so we want to make sure that the data is protected, that he stored properly, that it can be replicated etcetera, that is complying with a bunch of different things that needs to be. It needs to be complied with and then on the ethics aspect as well. If it's private and it's sensitive data, we want to make sure that we're managing that properly and appropriately. All right, so this is like I said, a very high level overview off stash as a product on what we're doing with this project. All right, so everything that we're doing with this project and in this real world example, we're basically managing the project with weekly, not weekly. Fortnightly. Sprint's right. So we're our sprints are two weeks prints, right for nightly, and every month we're doing demo sessions for the board, and we're showing different stakeholders or progress We're doing every fortnight. Also demos before the board, the monthly board meeting. So with our product owner, we're showing them our progress before we go to the board monthly board meeting and we're doing our daily stand ups were doing are, you know, fortnightly spring planning, fortnightly backlog, grooming and all that is reflected injera. Everything that I'm talking about in terms of what we're doing with the project and how we're running the product and what everybody in this team is working on is reflected injera . And that's why I chose his example, because it's ah, it's a huge project. It's quite complex, but we're actually making it very easy by managing these directly injera. All right, so I'm gonna go back, and I'm gonna jump back now to Ajira, to show you specifically what we're doing. And I don't want to get too much into the details of the what per se, because that's not probably super important. What I'm trying to show you is how we're using gear A to run the project, right? And for you to get a better understanding on how you can use Ghira in your own projects because this it doesn't matter that this is our unexamined off stash, regardless of which product or project you're running, the things that I'm going to show you here are the same type of things are you gonna be needing and doing when you're running your own project? All right, so right now, I just want to highlight here for you quickly that were on the active sprint tab on the left hand side menu and that basically is showing you your board your scrum board right on . As you will notice in this board, you can see at the top the sprint that we're in, right? So we're basically in spring three heats up. Like I said, it's to explain. So from February 18th to the 28th off February and below that, you can actually see the structure off your agile board or a scrum board, which typically has three columns to do in progress or doing undone. Okay, but Ghira, like I've said many times before it, is quite powerful. It's something that you can customize to your own needs You can so you can actually rename this If you want it to rename the title of the column, you could actually add more columns if you wanted to. On there's a bunch of other things that you can do so before I go through the different examples in these board. If you want it to configure or customize the board, you can go here to you see here at the top, right hand side corner. There's a board button. If you click on that and then you go to configure, it's going to show you here. The configuration menu. And here on the left hand side, you'll see the different options that you have for the configuration menu, such as the car colors, that car layout estimation, working days, etcetera. Right. And if you were doing here in the column, like I said before to do in progress undone, you could actually rename rename this if you wanted to. If you see this little pencil, it basically allows you to edit this if you wanted to, you could also move the columns around by dragging and dropping if you want it to a swell, and you could even delete them if you wanted to. So, like I said, Gee era! And this is, by the way, one of the reasons why people loved here on what Aguirre is so powerful because it is very customizable. It is very easy to change things injera or to reorganize them, or to rename them or to change the colors, and it just gives you a lot of flexibility. Okay, so I love This is very intuitive and self explanatory, and you could change it, do things with this yourself if you want to play with it in your own projects. But in this example. As you can see, we kept it simple, the ideal way. And we just kept to do in progress and done. And I'm just gonna go back to the board by clicking on this button back to the board. So we go back to the scrum board and then here you can see the columns, right? But if I scroll down, you're seeing here, Mike. So Michael Inches, one of the developers working on the project, and if we went down, you would see voices. Who is one of the other developers working on the project? So this is something that we actually set up in the board as well. We've actually set up if I go here again to the board and to configure if we went here to the swim lanes, which is basically the horizontal view off the border we're seeing, we've actually said, Show us the swim lanes by a signee, So show the swim lanes. But people that are working on stuff, right, this is the ASIC Knicks, right? But he could change that if you wanted to. As you can see, it gives you different options. Or you could even remove the stream lane. So you're not seeing the different user stories by developer or by person that's working on them. But you could just see all of them together without having that division that we were seeing before, where you saw Mike's name at the top. And then Moyes is his name at the bottom. All right, but let me just go back to that example Rial world example. Like I said on all of these things that you're seeing here in our board are obviously user stories and I know what you're thinking. You might be thinking right now. Why aren't the user stories in the, you know, in the structure or the traditional structure for user story, which is us a block I need to block sold that block right, which is Assad is basically the who I mean to block is the what? And so that block is the why, right? So generally a user story has that structure because we're trying to clearly state under state and defining the user story itself what it is that we're doing, who is doing it on why we're doing it. What's the value of doing it right? Because a lot of the agile teams are might be very mature with the agile methodology like these Project Team and the steamy Nicks. In this example. We're not using that long structure because it takes a lot longer to write, as I I need to so that for every single user story and in addition to that, it might look a bit redundant. So even though agile and scrum theory tell us that when we're writing a user store, we should be using that structure. What you're gonna see in practice is that most people and a lot of people don't actually use that structure, and they use their user stories mawr to represent the different things that they're working on, the task or the requirements. Right? So I guess if you were going to strictly by the book and strictly by the theory, user stories air basically representing requirements for your customer from your customers or your or your clients for your end users biting practice and impractical in practical application in the real world, you're gonna be seeing that in the scrum boards and in the agile board. Sending in these jeer aboard here that we're seeing right now, most people are gonna be using it to track there, use their stories. But when providing user stories, people are generally adding basic e tasks and requirements, right? So I just wanted to just make a little bit a little note about that. So you're aware of that and so that it doesn't come a surprise when you're seeing these on screen. Why doesn't have the traditional user story structure? But basically, if you look at this little, I can hear this green little I can hear next to the user story. It's basically telling you that it's a story that it's a user story, Indira. They use the name story just, I guess. An abbreviation of the longer name used her story, but when they say story injera, they're basically referring to a user story, which I just explained, and these little blue I can hear. He's a sub task that is part off this user story or this bigger task, right? So, Indira, you can also add sub tasks to each user story. Okay, And of course, you could also add tasks, not not cold and use their stories. If you didn't want to, you can actually call them tasks. If that's easier for you, we don't have. You don't want to use the user story, our story terminology, that's fine. I always say to people you know, do whatever works best for you, for your team and in your context because we got to keep in mind that even though there's a theory, you know, we need to be pragmatic and a lot of times practice very Subait from theory. Okay, so I guess don't get to, you know, don't get too concerned with that. And don't over think it what I would recommend if you generally use the stories and then stopped, ask if you need to add to them on. Like I said here, you can see very quickly at a glance. And this is the power off Ajira board right here. Right now. You can see what is the status of Mike and what he's working on in this particular spring. Let's go back on. Just remind ourselves over again in spring three. Okay, so we were already gone through spring one springtime. We're now in spring three. And as you can see Mike here, he has I finished all of the tasks all the user stories that are here on the right hand side. All of these are things that he already finished, which is a ton of work. So he's done a ton of work in the Sprint, and these are three things that he's currently working on. And these are things that he needs to work on because this is an are really cool thing. If you go here to the top, right hand side corner it zero days remaining, it means that we're pretty much run out of time in the spring. So Mike will probably not be able to finish Opie pretty much didn't finish by now. These three sub task and these user story that he has here. Okay, so that's the other thing. I want you to keep in mind with Vera. If you're ever unsure about what something means or you're not too sure about what something represents a Nikon a link name or something. Just remember that you can hold her over it, and he will generally give you some information. You know, for example, here this little red arrow if I hold her over it, it means is that should So it's a user story that with Marcus, I should on for those that are not too familiar with this. I'm not gonna go into a little detail right now, But one of the ways in you in which you can prioritise user stories is but using what we call Moscow. All right, so let me just very quickly go through that concept for you guys that have never perhaps herto Moscow. Okay, So if I go here, let me just go back to these example that we're seeing before on. Actually, I might just go here at Let's just leave it like that. I maybe if I scroll here So for those aren't familiar with Moscow, So muss co is just a way in which we prioritizing Gironde. The am stuns stands for must, though here doesn't stand for anything. So forget about it. It's just because they wanted to give you a cool name. The S stands for shoots. So must shoots Kouds the old here this instant for anything on the w stands for won't have . All right, So these are the top priority things. These are the essential things. The things that we can't live without. These are the things that we just have to do is not optional, because if we don't do them, the system breaks or you were doing something that is illegal or were breaking the law or were not mean compliance standards. It's just something that is essential and needs to get done. It needs to get done. All right, there's there's no option of doing it. You have to, all right. It's kind of your commitment on. And then we have the shoots right, which are important, but not essential. Right? So is the next ranking priorities on then the goods Less important. Okay, on again, they're not essential, right? So they're less important than the chutes. But if we did them great, you know, it's like a nice to have. So this is a bit like a nice to happen, all right? And then the 1/2 they are just things that we're not doing. So we're not doing them not doing them, all right. So, basically things that we've declared our outside of the scope and this is just a concept and something that we use in agile to prioritize user stories. So I'm just gonna jump back to the example I just wanted to come back real quickly here just to show this to you, Andi, to explain a little bit, you know, the must have the month, the Moscow concept, in case you ever you hear about it. So this is what it stands for. Moscow is for must shoot scoots and one house, All right. And that's something that we're using in this project. And that's why I want to quickly explain it. If I go back here, we've actually added to our user stories that category, whether it's a shoot, this one, for example, is a sub task. And that's why it says your minor. But if we go here, it's a must. So these red arrow indicates, should this other red arrow, which is a little bit different in the case of indicates a must. So, like I said before, if you're ever in doubt about what something means injera just just hover the mouse over it without clicking on it. I know he will tell you this thing here is just a you know, the unique i d that Gerald gives to the user story. So Esty is on abbreviation for this project. S T stands for a short for stash, which is the name of the project on then 552 is the unique I D off these user story. So it's used her story Esteve Dash 552 or 5555 to whatever you wanna call it, all right. And then here, for example, below Mike's picture, you can see it says one hour and 30 minutes, so that's basically his estimate for doing this particular user story. That's what he estimated it would take him okay on. That's why you see these one that says to, you know, 2.32 hours and 1/2 it basically means, he estimated, for the sub task that it would take him 2.2 point three hours. Some of the user stories don't have time, or some of the sub test or user story don't have time because he might not have had a chance to actually estimate them. And he just started working on them where he finished him before he even had a chance to estimate them. And obviously this is also something that is very typical. I wanted to show you this example because it's such a great examples. Real world. What happens in the real world in real world applications, ideally in agile. If you went by the theory, you would have estimated the time he would take you to execute all the different user stories on generally actually, in an agile and scrum. We don't normally typically estimating in time in hours. But most of the time we estimate in story points in our case, in our project in particular, we're actually not using story points. But as a team, we decided that we wanted to estimate in hours Okay, just because it makes it easier for us to manage the time, the workload and the resource allocation. But you don't have to. You can actually do your estimation in story points if that is easier for you and for your team. Like I said, this is just an example. Okay, so I just wanted to show you here also that in the real world, a lot of times people don't actually estimate the time that or don't actually assign the story points or the time it will take him to completely use their story before they actually get started with the work. Ideally, they would that it's part of what we call spring planning. But in the real world, sometimes we're busy. Sometimes we have a ton of things going on in this example might. Actually he's not only working on this project, he actually works in the operation as well. So I'm sure he didn't get a chance to actually add his estimation toe all of these other user stories. And as you can see, he actually had a bunch of them as well to work on a bunch of stuff tests as well. So he added the time where he could Okay, uh, these other legal color here that you're seeing. He's basically what what it's representing is that these user story is part off an epic that we called only M V P for research office. So only is basically one of the things that we're working on this project and is one of our big deliverables on our epics, as we call them in, agile or in scrum, and in particular, I guess I'm not gonna go into all the details of what it means, but in essence is basically like a portal, like a data portal that we built for the research office that allows him to see successful grants in that website in that portal. Okay, so that's what one of the things that Mike has been working on in the sprint on if I scroll down more and more and more to see Moises, Moises was also helping out with this epic. And that's why he has that, you know, user story, that it's part of only as well and BP for research office and in case you don't remember. And we p stands for minimum viable product, which is one off the agile concept we use. And then if you look at the things that he finished, there is also another epic that he was working on, which is system operating system patching. Right? So stashed Merrill. Good lap. So three things that he was patching us part of the sprint. Now, obviously, if you want Teoh open any of these user stories to see what we did specifically, you can just click on them and or you can just click right click and then open open Lincoln in Utah, and it'll take you specifically to the user story we can see here. The user story that type. It's that use their story studies. It's done. It's pretty minor components. He didn't have any component assigned. No labels. But you can check again. You can change all of these injera. Remember, you can edit it. You can comment is very flexible. What you're seeing is basically what we have assigned. So in this case, it's a spring to spring three. Because it's something that we were carrying over from the previous Sprint. So Mike started to work in the index. They're full text search, but he actually wasn't able to complete in spring two. And that's why carried over for spring teat, Spring three. That's where we actually carried it over for the sprint. And these are the tasks that he complete the work part of these user story, as you can see. And then here on the right hand side, you can say you can see what he estimated the remaining amount of time and how much time he actually logged onto these specific user story that he was working on. Okay. And you can see here below the activity of these air story. So comments we went toe all basically show you when it was created changes like all the history that these user story has on gold the history that went through. And that's also something that I really like about Jiro, which is pretty cool, which is basically keeps a love off any changes you make to a user story and the activity here because he all or you can just specifically look at comments if there are any work log history activity on just quickly there. There were no comments in these user story work log. So people here, Naomi works, you know, spend some time on these. She's on our team member and Mike. He spent two hours. So these were This is the work that they loved. This user story history shows a bit of the history. So what was the original value and what was the new value of the user story on it? We went to activity. It'll just show you the whole activity with the day to kind of like a, I guess is showing you a chronology. You know, like a time line a time frame off when things happening, that activity and here in the rights of bunch more. If information like people dates time tracking development fragile. You know, the springs via on board and Chet's. Okay, so I'm just gonna go back. I'm just gonna close this, and I'm just gonna go back here. Like I said, you can open any user story by just simply right clicking and then opened linking you tab. You can also click it if you would just click it with with your You know, if you just click it with the left hands with the left button on your mouse, it just gonna open it here on the right hand side. Kind of like I can minimize the view of it. Right? But if you can also close that or like I said before, you can right click on open this and it'll just show you all the details. In case you wanted to go into the details of that user story, same goes for any of them. Okay, so this is a really good example on if you can see here quick filters, it basically shows you different filters that we've added here at the top on. But like I said before, all of this is stuff that you can configure if you go to the configure. You can hide details if you want to. You can expand. You can collapse hide epic labels. So if I did Alexis get here just to show you, remember that this thing here only is an epic. If I clicked on it, you would hide them so you wouldn't see the epics. You would just see the user stories. But if we wanted to see it again, would just keep Kirsch Olympic labels. And it'll shows that shows the the epics for each of the user stories. Remember that sub task? It's part of a user story, which is why you're not seeing on Epic. Assigned to It is because this is a user story on this kind of like the if you were thinking off a tree, this is like a branch of this bigger trip. Andi. That's why it's a sub task of these user story. And that's why the epic said the higher level, which is the user story. Okay, so in this part of the course with, we've covered a real world example of what a scrum board and agile war Ajira board, if you want to call it that looks like and like I said we had in these three typical columns that you would see, which is it to do in progress and done. But you could. Like I said before, you could actually change these if you wanted to. Okay, If you click this, you can actually hide the heather as well. If you wanted to expand this view, let me just show you real quickly If I click, this is just gonna hide that many of the top and make this bigger, Which might be good if it might be good. If you're actually in a presentation showing this to someone and again, you can actually minimize this again if you just click this And this is a really good example off an agile board here, injera. And we cover basically what we're working on in spring three. So this shows you at a glance everything that we did in Sprint three and in this case in this particular project, by the way, we're just adding the user stories that developers are working on. We're not adding in our in our board, the work that everyone else in the team is doing. But specifically we're focusing on the development side of things. So these are all the things that these two guys have been working on in the Sprint, which is pretty much completing and finishing today because, as you can see here, it's zero days remaining. But like I said before in this project, we're doing four times the sprints. If there were, for example, three days left than here, you would see three days left. But because today is kind of like the last day, it's actually saying Syria, there's remaining meaning that we're actually finishing on dropping of the spring. One of the things injury is that even though we might have actually completed this sprint, it doesn't automatically complete for you. You actually manually complete market complete. And it just that's just pretty good. Also, like I said, in terms of flexibility, Indira, it just gives the power on the scrum to the scrum master or to the team itself to actually decide when they actually mark that complete. Okay, Andi, that's just something that you know you can manage on. Ideally, you're gonna close on the day. Of course, Like in this case, we we should be closing today. But it is up to you if you wanted to close hit a lot of different date. It really gives you that flexibility to manage that. Alright, guys, I hope you've enjoyed these real world example. And if you have any questions, don't hesitate to reach out. This is what you know, Agile board looks like engineer or a scrum board Looks like Indira. And this is one of the things that we're referring to as a team all the time in our standups, when we're looking at our progress and when you're working on things yourself, these one of the things you're actually going back to and just seeing where Europe with things, What you're gonna work on next because remember that even though we might have a bag look and we'll look at the back, look, in our part of the course, even though we have might have been a backlog with another additional bunch of things that we're working on, we're obviously in this scenario, we're not gonna go. We're just gonna show in the spring the things that were working in this particular spring in this particular fortnight. So you're not going to see, because it can become quite distracting when you have a problem and it's a big project and have a bunch off hundreds or over thousands of tests that you need to complete to finish the project. Actually, when you're this is one of the powerful things about agile gives you the part of focus on a short time frame on the very specific things that you're gonna be doing on the very specific things that you're gonna be delivering in that spring, which is what you're seeing here on screen. So Mike delivered a bunch of stuff in the spring, so I'm sure everyone's going to be really happy. As you can see, he actually complete a lot of things that he was working on in the Sprint. And Moist is the same, you know. He also completed 1234566 Use their stories and you can see here, By the way, just us a little note next to the name, the number off user stories you're seeing here that the word has a word. Issues again. Don't worry too much about that. That's just the convention on the conventional name that Jiro uses for users. You know when when they're when they create something in the system that you know. They're generally referring to it as an issue initially, but it doesn't mean that it's a problem. It actually just means it can be a user story. It can be, ah, different. You know, it could be a user story. Could be a sub task. You can be pretty much anything that I see you name it. Are you categorize it, um, again. Like I said, don't worry too much about that. You'll get the handle fetus, as you're working with. It is just a convention because and this goes back. And that's why I wanted to talk to you before when I talked about the, you know, history of Deraa. Like I said, Jerry initially was born to track issues to truck bugs in software. But it's evolved, and it's nowadays used for agile product management. But some of the things our legacy, and they're still you know, some of them names that you see in the system. Indira's the system are still legacy, so they still use a lot the word issues, but not always. They're actually referring to any super say that makes sense. I'm sure you're gonna, you know, you're gonna get the handoff it as you were working with it. Like I said, don't worry too much about that just real quickly to to elaborate on that. And I'm not to, you know, to make sure you're not confused by it. If you actually opened this user story, SD 55 200 is going to right click open linking your tab just to go into the details of that user story. Do you see here that there's a type? Do you remember how I explain these little Aiken shows? Represents? At least use your story, our story? If actually click here on edit and I clicked on the drop down here, I could actually changes to a task, a bug or an epic. So, like I said before, that's why I was saying to you, don't worry too much about these these names Jezeera. He's very flexible, and you can change him and you can rename it if you wanted to. So in generous terms, when they're talking about issues, they're referring to any of these three things it could be or any of these four things. It could be a story, a task, a bug or an epic is just how the system was built. So don't get confused by that. Like I said, is just how they when they build Ghira. Initially, they just called it issues. And that's why every time you create something, when you click here on create, he just basically creates a new issue. As you can see here, they call it issue, but it's not really an issue. As you can see in the drop them below, you can actually convert that into a story about a net pick or a task. Writing unnecessarily an issue per se issue is just the name they gave it in the system. I'm pretty sure at some point in the future, a glass in my decide to rename that from issue to something else create whatever, but for now, they just kept the, you know, the legacy, how they used always called it in the system, which is issue because that's how the system was when he was born. They were always referring to things as issues when they were creating something in the system, and that's just, I guess, the legacy in the history of Jiro so product, because it originally started as ah, but trucking and, you know, an issue tracking application. But nowadays, issues brought up things way beyond that. I like I said before, Even though you're seeing year tasks, story bugs and epics you could add genera actually allows you to configure this stuff and change it so you can actually go here to configure. Um, you could actually changes in the you know, you could actually changes in the configuration settings of Jiro if you wanted to change this, but most of the time, it'll be fine. You most of time. I don't think you'll actually need to create anything or confused is differently. The full things that the Jiro gives you are pre 7. What Reports Look Like in Jira: the jury has a bunch of things here on the left hand side, there are the menu. It's these. The menu item from the era. One of the really cool things are the reports. So if I click here on reports, it's gonna take me to the reports page off Ghira and you can see here there agile reports like the Burn Down Chart, Spring Report, the Velocity Chart, Community of Flow diagram and so forth. And one of the things I really like about the rights that it does automatically all of this for you. In a lot of the other other tools, they don't actually have this functionality. You have to actually do it manually yourself. Or you have to buy something extra to get or on Adam or something else. Jerad. That's part of the practice, part of what they want. They You know what you can see here directly, injera. And if you wanted to see, for example, this burned down chart, one of the most popular charts in agile, you're going to see here, this is what our sprint looked like. And you can see here the convention of that gruff here on the right what it means. And if I did here, let's say our previous brand spring to so you can change. And you can see how we did on the previous sprint as well. The green represents time spent, remain values on again. These things you can also kind of like antics. So if I want to take up the red one, um, you can actually remove it as well. You can configure this if you wanted to. So, yeah, like I was saying before you can actually change his graph and customize it if you click here on this drop down menu, for example, if you want just to see the original time estimate Okay, so this is the burned down chart on the gray line is kind of like the theoretical way of that burned down going down if you actually gone us ideally, yes, it If everything had gone in the perfect world, that's how you would have looked. But the orange one or the red one here that you're seeing is showing you the rial actual burned down graph, how it actually went. Okay. And as you can see, we started here and we did, and with lesser known for me work gays, your wandering. Why? Something's a gruff went up. It means we actually added user stories to that sprint, which is something you shouldn't be doing ideally, But in practice, it does happen. Something practice. You actually need to, uh, use your stories, your sprint. So again, the practice. Very something's versus theory. And so we added the user stories when we needed to in the sprint. And that's why at the another at the end of spring, we actually had ah, little remaining work. Also, because we added to many in this case is basically just showcases that we have too many user stories in that spring. So probably a lot more work that way could actually take on Okay, I'm just gonna go back remaining time estimate. All right. And yep. This is just like an example of the burned down chart, and I'm just gonna go back here to reports I'm gonna switch report. Let's just go to the spring report. Okay? So I showing you real quickly here a beautiful summary, and if you scroll down completed issues, issues not completed. So this is showing us spring to I can actually change this to spin one or three. It's just joining us three sprints because he's the number of springs that we've done so far in this project. If I went to spring three, he hasn't actually been marked complete yet, but it's pretty much complete because there's no time remaining on the Sprint. So the completed issues or user stories or blocks air here and below are the ones that we didn't complete. And it just shows you, you know, like I said it. This is just a spring report, and this is what a Sprint report looks like. And that's what you would be discussing with your team in your retrospective on when you're looking at how you guys did in that sprint, all right, and this is really cool. Like I said before, just keep in mind that injera they refer to I use their story of baga task in an epic pretty much anything that you're creating in the system as an issue on the reason why, in case you're wondering why Jiro does, that is because originally when they created Jiro, it was actually a software for trucking, tracking and managing issues, bugs in software, but then over time, it became an agile software, you know, an agile project management tool. But they've actually kept some of the terminology, So that's why they're still used, that you know, the name issue. But it's not really that when you're seeing here is actually an issue. That's why they have here the issue type. These green ones are user stories on these books. Are actual bucks actually problems? Or they would actually be, Let's hear a really issue in this scenario, but that's just like I said, not something for you to worry about. I just want to very quickly show you that you have a bunch of reports that you can. If I go here back to our sprint, are can been bored. I could actually go back again to report real quickly on like it's like we saw before. There's a bunch of reports here in in the click here on all reports Injera. It's going to show you all the different reports, and in case you don't remember what it report means or what they stand for, etcetera, Jiro makes it super easy for you and puts like a little summary below the name of each report which helps you room remind yourself what it's about. And, of course, Like I said, they have a time on a lot of information in, you know, help guides and the help center and knowledge based articles. And they also have a community. So you're not gonna you know, you're not gonna not find information about something if you have a question about it on. Anyway, I hope you found these. Useful is just a real world example of an adult combine board injera and real world examples off what reports look like injera. We discover two of the many reports we covered the you know, the burned down chart on the sprint report. And we could also have a look real quickly and the velocity chart just so you can see what the velocity chart looks like. Here it is. This is what the velocity chart looks like. Comedian and completed. And once we complete spring three, spring three would appear here on the right, but just real quickly, because this is a project that is just starting up. It is a great example to show you something that typically happens with agile teams when they're just starting to work together on their projects. It is very, very common to see agile teams that are just starting up with their products toe, overcome it and to plan to do way more than what they can actually do in a single sprint. And that's what happened to us in spring one. As you can see here, the gray one represents the commitment. So what we planned to dio and the green one represents what we actually did, what we actually completed when we finish this two week sprint. As you can see, there's a massive gap right we thought were going to do all of this. But we actually were able to only do this little bit here. That's very common when you're starting up in your agile projects on then spring to we said , Okay, let's get more realistic. So we plan for less work than what we're planning. Sprint one less. But we also had an efficiency as a team because we started to work better together. We started to understand better and get any inertia learning curve. Although things that happened when yours working through Sprint's, this is very typical again, very normal and where you're going to see here is that we actually need way more than that . We commit it, which is right. That's awesome. Right? But ideally, you want these two bars, Toby, at the same height on the same level you want basically to complete what you plan to complete, right? But if you did more, that's okay. If you did last well, it's a lesson learned for you. It's something that you need to reflect on. And what you're gonna see over time in this graph in a velocity chart is that it starts to go from small to less the war, and then it plateaus, you know? Then it becomes a bit it stabilizes because then you become better at your estimating as you're going through your different sprints, your team is going to start improving, improving, improving, and you're gonna get better, are planning on executing at the same time, which means that you're gonna reach as status. And you know your A level as a team in which this to ground in these two bars are pretty much at the same level on also, you're going to start seeing the velocity which initially is low on it starts to become higher and higher at some point it plateaus and it becomes, you know, it becomes kind of like a stable line. Yes, trade, horizontal, stable line. Which shows you that the team has reached a level off maturity. All right, guys, I hope that these, um bit here off the right is something that you can take advantage off. Like I said before, if you want to learn a lot more about Jiro, just search for my Jiro course and or just, you know, go to YouTube or read or whatever you want to dio or just enrolling Jiro, you know, just goto Jezeera and create a free accountants or playing with it. But this is just to give you I guess I guess a bit of a taste for Ghira. And so you You know what? What's included there on guy? Just show you a little bit of Jura. Jura has a ton of things more than what I just showed you, but I probably show you some of the really key things on. Like I said, I just wanted to give you a real world example of a real product that we're working on and he saw right there. A natural camp on board on a few of the reports that you could see if I go here about two active sprints this I can hear with the board. It takes me to our agile Come on war, which we saw before. All right, guys, I hope you enjoy this part of the course. This is a real world example of a real project, a research project that I'm working on right now. And I just showed you what it looks like. Injera. And I'm sure you're gonna get a little value out of these lecturing the course and I'll see you in the next one. Cheers. Bye. 8. The Backlogv2: Hey, guys. So in this part of the course, we're gonna talk about the product backlog or the bag look injera. Okay, So as you can see on the left hand side menu, I'm already on the bag. Look, Tab. And if you recall, you can also collapse this left hand side manual sidebar by clicking here the bottom or you can again click there and explained the sidebar again. So if you have it collapse, you'll just see the icons here. And if you expand it, you'll see the icons and the name. Okay, So just real quickly. Like I said before, we are on the product backlog or back. Look, you also see the name here at the toughest well, backlog. All right, So what do we generally have in the product? Back? Look. So in the product back, look, we have basically all the issues that we created in our gear A project, right? And if you recall issues don't necessarily mean problems, but that is actually just the GE era convention or the Ajira name that he provides for the different things that we create. Injera. Right? So kind of like the name type for every time when we're creating a user story on epic Ah, bog a task in general like we talked before. We call them issues, right? And you see that here, the many on the top. Also, when you click on the create button, like I said before, you're gonna basically start creating an issue. Right? And remember that here, just when you create select in the top, the project gives you the option to what issue type it is. So what category does this issue belonged to? Easy to task. You see the story, use their stories it above received an epic. Okay. And just remember that these fields are also configurable. So you could actually add more of these different types of issue types if you wanted to in the settings off Ajira. Okay, so I'm just gonna cancel these justice. I just wanted to show you real quickly, but like I said before in the back lot, we have pretty much every single issue we've created, Indira. So you'll probably notice that at the top of the back. Look, we have the current active sprint in our case. This is spring for and that's from the third of March until the 13th and it has 22 issues for 22 things that we're working on in this particular sprint on, you can see everything that is part all the issues that are part of the Sprint are here, below the title of the Sprint. And if I actually collapse this, I'll see here the backlog itself on all the issues that are part of the bat. Look, as you can see on this project, we have a pretty big backlog. We have 241 issues that we need to work on to complete the project or to complete the product. Keep in mind that the backlog is not a static thing. It's something that generally can be increased over time. Or it could actually be even reduced in your backlog grooming sessions. When you're working with your agile team or your scrum team, you might actually decide to reduce the battle for increasing depending on what you're trying to achieve. OK, but in this case, with the information we have at this date, we currently have 241 issues loved injera in our back look, and this is basically what we use when we're doing our spring planning and planning what we're gonna be working on next, Right? Our next sprint, we look at our back, look, and then we take some substance off a subset of the user stories or tasks or epics that we have there, and we add them into our spring back look, or the next print that we're gonna be working on. Right? So you see here that in the back Look, Tab off course. Where this whole section of the course we're talking about the backlog or the bank. Look top right here. You can see here. There's a button at the top, right hand side corner. That's his create sprint. So if I actually clicked on these, you would allow me to dragon drop here different types off issues that are in the back up to create the next sprint. Okay. But I'm just gonna delete this because it was just something quickly that I wanted to show you related? Yep. Confirmed. Okay, so that's basically all you do when you're planning injera your next sprint, the next you know, four diet or the next. Whatever you designed, the length of your sprint does. Remember that, Tom agile teams work with one week sprints. Other teams work with two weeks friends, others with three and others with four. It doesn't really matter, because it Gerald gives you the flexibility to define the length of your spring right here in the system right here, injera. And you can put the range whatever arrange your team is using to work on their actual project. In our case, we're doing fortnightly sprints. That means every two weeks we're creating a new sprint on nodding a bunch off issues from our backlog into the Sprint. So, like I said before, if you were going to create a new spring, you just click on, create Sprint on. Then you can rename this right now. It's just put Spring four, but I could actually easily change it to the sexually Spring five on. It's gonna be a from march because these one finish on the 13th so this could be March 14th and so forth and then, you know, count two weeks after that, okay, and then you basically create your next sprint. Let's say this is gonna be two weeks. Let's say this is the 28th. I'm just, you know, just give you a quick example of how you would do this off course. I can also really remove this Number two. And I can just just set of parentheses here on Dan. You could just start dragging and dropping. As you can see here, you can actually drag and drop from the back. Look, you could actually drug and dropped from the backlog issues into your next sprint, right? You could just easily drag and drop them and put them back. All right, That's all you would do when you were doing your next spring planning. OK, so that's what I wanted to show you in this part of the course just how to create a sprint . You just so high how you did it. I'm just gonna debate this because it was just a test. The explained confirm OK. And I could also, like I said before, expand this spring to see what? Which is our This is showing us a current active sprint, the spring we're working on at the moment and just a quick recap. Remember that these little icons indicated that type of issue injera. So in this case, the green ones Little green icon misses a user story. The red one means it's a bug on. We don't have any any epics here. But as you can see, these user story is part of the only epic this this pink color here only M v p represents an epic on this other thing. Here only version 1.1 point 0.0. It's the version, right, which is the release. And we're talking a little bit about releases injera. But basically you can actually attack your easier stories with a particular release so that you know, when you're working on software projects, generally, when you release overturning circulation 1.1, or returns to point to one or whatever it is, and this is how you could actually manage their release, you don't necessarily have to use numbers. Of course, you've seen Google call them KitKat or, you know, Google, Oreo or whatever, so you don't necessarily have to use numbers for your releases. You could actually just give him a name like Google does when they're working on their projects and they call him Oreo or whatever. And I gave us again. I know I'm talking about specific in this case, I'm talking about a project that relates to on you research project a research for up research. That I'll management plans is a system that's called Stash, that researchers use. But it doesn't necessarily mean, of course, that you can only use Jiro for I t projects or technology projects. You definitely can use Jiro for any other type of project. And let's say, if these were marketing campaign that you were working on, you could call this. You know, depending on the different releases you could you could you could call launch one Ah, a particular name and then assigning their stories to that attack user stories. That's part of that release and will cover releases in another subsection on our part of the course. But I just wanted to show you quickly here what this stuff is about. The back look. Like I said, it's basically what you have everything that you were working on in your project, and you can see our whole back along here. If I scroll down, you're going to see everything that we have in our but low, and this just gives you, ah, view off what you were planning to work on your product as a whole. And you can see here some quick filters in our cases off course filters that we've created . And you could actually change this if you needed to. And if you search here, of course, is gonna give you the option to search again for, you know, whatever it is that you're searching for, there's a legal here, a legal kind of like sidebar as well. You can see the versions and the epic. So if I click Conversions is gonna show us the different versions that we're working on at the moment, and you can see these stash version version 3.2 point zero. And it gives you an indication on a visually visual indication of where you're at in terms of completion of these version on have actually hold my mouse over. And I just left it there. It says 21% off. Estimated work done. So we've completed 21% and then you can see the remaining amount here on the right hand side and great. Same goes for this one. If I over my mouth over it, it'll say 66%. It's already completed. That's why you see This blue line is beyond the half of the off the line as a whole because it's more than 50%. So in this case, it's 66% meaning there's, ah, big remaining right. We're talking about 34% remaining in this scenario, and this is another version I can. You know, if you click on these three thoughts, you can edit the name if you wanted to of this version of it, or you could have more. If, of course, number. Hide this panel. And if I click here on Epix show, the epics panel is gonna show me all the epics that are part of this project. If I scroll down, I can see all the epics that we've added to his project on Ben. The ones that don't have any coloring. The line means we haven't even started to work on them on the ones that have blue means. We're working through those issues that are part of those epics, right? In this case, that could be used or stories or box etcetera, right? Remember that issues like I said before is just how G rock calls pretty much anything that you create. Indira. So when you create something Indira in the system, do you recall student an issue, but it doesn't necessarily mean that it's an issue. Like I said before in the cores, he just means a type of issue, a category of something that you're creating Indira like, I kind of think like a ticket so you could actually convert that or categorize that'sa in terms of the issue type that we saw before. When you're creating the different issues, you can categorize it as a task as the story of Sabah Barisan epic and again you can customize it. But generally you probably won't use anything beyond what it's actually already there. It's pretty standard, pretty common when you're working on projects and this is you. Just enter the information off your issue, Indira and then you created, and every time you create a new one of these issues, it'll automatically go into your battle because remember that the backlog has everything that is part of the project's all the issues that were part of it, and that's why you saw these big number here when we're looking at the back look 241 issues and like I said, you can filter these. It gives you the option here to see all is showing us the You know, in this case, we're seeing the 1st 100 issues effect material. Show me the next. The first fight 1st 100 issues. If I click here, Tirol shows the 1st 500 If I could hear all issues going to show us all the issues that are part of the team product, project or service that you're working on. Okay, so that's pretty much it guys. Like I said, also, you can, as always, click everything in general. You can either hold or your mouth your mouth, all right? And I'll give you more details like you're seeing right now. He wanted hovering my mouth or these icons you can click on the Remember that the S T six year old five is just like a unique I d. The ajira automatically gives every time you create a I use her story or or an issue in Europe. In this case, it's given this random number. SD six year old five. It's just a unique identify. RST is just the summarized things stands for stash, which is the name of the project in this case, eso defending. Every time you create a new project, Indira, it'll automatically create conflict and name convention for you. Like we saw earlier in the course on again. You can right, right. Click on this link or hyperlink and then open the Lincoln and you tell I don't just show you hear the details of that particular issue in this case, the issue types of stories or these a user story that we're working on the parties it should on here is the epic that it's part of. And here we can see more information like we talked before about who is working on it. The dates time tracking, etcetera. Right, and then hear this up test that are part of these each injuries in your user story in this case and so forth. If I went back to the board, I'm just gonna close to stop now. Remember that you can also either right click on it like I showed you. Or you can just click on it simply and it open it here on the right hand side for you will be like, in a bit of a summarized view. Okay. And then you see here you have. Ah, bar. You can scroll up and down off course. This is for the backlog over here. But there's also a little Bauer right on the right hand side as well here for just this little summary view that he hoped that particular issue in dear again, this is not showing you anything different to what we saw here. When we when we click, right, clicked on it and then opening opening a new tab is the same information. Just that you can see it here in detail by right clicking on it. Or you can simply see it by not right clicking, but just clicking on it on the issue. And it will show you this little summarized view of fate on the right hand side, right next to the back look. So it really gives you a lot of flexibility on how you want to look at things. And that's one of those things that is typical of Ghira. That's one of the reasons why people loved us so much as well. It's because it gives you a lot of different ways to look at things and a lot of flexibility. Okay, guys, So Well, we pretty much covered everything that you need to know about the backlog. And like I said before, every time you create an issue, it'll automatically go on the back. Look for you on based on the back. Look, you can actually start creating your sprint's like I showed you earlier in this part of the course. Okay, guys will see in the next one. Cheers, bite. 9. Roadmapping in Jira: Hey guys. So in these part of the course, I want to show you a real-world example of a product roadmap, JIRA. And as you can see here, we have the whole year from January until December, and we've divided that into product roadmap by quarters, which is typically something you would do when you're developing a product roadmap. So you have here Q1, Q2, Q3, and Q4. That stands for quarter one of the year, quarter two of the year, quarter three of the year, and quarter four. So the whole year divided in groups of three months, right? So the first group is January to March, second April to June, July to September, and the fourth quarter, October till December, right? So vertically, you have here the quarters of the year, right? And horizontally you have different groupings or categories, which in this case are basically streams will work, right? So this is something we've created specifically for this, right? Obviously that the groupings in the categories could vary depending on the type of product that you're developing, right? But you can see here we have archiving, audit requirements, data governance, discovery portal, publishing, and essential maintenance. In this particular case, doors as those are the streams of work for this product that we're building. And that's why we've called them with those names. And that's why we regroup the different work that we're doing in those different big streams of work. Now because we're working through these using Agile development process, you can see here that we have the different sprint, sprint one, spring to spring three, spring four, et cetera, up until spring 15, which is our core and Sprint. Now, these roadmapping functionality in JIRA allows you to add this label here so you can see from which day till date is the sprint, right? And what you're seeing here as well below are the different epics that are part of these product of what we are building, right? And you can't fully read the name of all of these because it's something's shortens it. And that's just something because of space constraints in the tool itself. But if you couldn't read the whole name, if you just hover your mouse over it, like, like so, you'll be able to see the full name, all CFL, outer index and clean up. And this one, for example, says solution these, and then you can't read them. But if you hover your mouse over the solution, the signing unprocessed documentation Part one. Alright. So the different colors here that you're seeing just basically indicates different types of epics. And then, like I mentioned before, because of the grouping that you have horizontally, this is just categories of the work that you're doing. So everything that is underneath, underneath archiving, even though it might have a different color or a different name, relates to the archiving stream of work. So these are basically all different epics. So different chunks of work that we need to get done so that we can actually. Develop the archiving functionality in this product. Okay, so all of these epics that are here will allow me to actually get done the archiving functionality that I need to complete, okay? Now, if I actually opened up any of these, for example, this one only and VP for Research Office. Let me just right-click that and open that in a new tab. So we're opening up these epic here, only, MVP for research. And when I open it, you can see here all the user stories below it that are part of these epic, right? So as you know, JIRA colSums goals m issues, but this is just a system terminology, but there are actually user stories, okay? And if you hover your mouse over this, your mouse over this icon here, these green icon you can see it's a story, it's a story. This red one here is a bug. Okay, so it's a bug. So all of these actually, all of these different user stories are part of these. Only MVP for research epic, right? As you can see here, that's why it's called here. And epic. And archiving is the stream of work, which in Gira we referred to it as component. Okay. So you are seeing here the product roadmap for the whole year. So one of the reasons why product roadmaps are so important, so valuable and so great for stakeholders is because at a glance, look at these in a single page, in a single view, you can see everything that's going to get done throughout the year. What specific Eatly is gonna get done when it's gonna get completed? And how is the workload distributed across the different months of the year when things are going live as well. Alright, so that's really cool. So you can see here, for example, if we went down here to the discovered plural publishing, we are, we have here two epics related to the data portal outbreak. Okay, you can see them down here. I'm going to make this a little bit bigger so you can see it better. Now in these examples that you're seeing on screen where using the roadmapping functionality by EC agile. So this is part of the G ROM marketplace. And I'm just gonna right-click on that here. Open linking tab so you can see it. So JIRA, a classroom, that company that created JIRA, they have Alito marketplace, which basically allows you to add extra functionality, an extra things into JIRA. So to make it more powerful, more robust, right? So a little bit similar to what Salesforce docx or many other platforms like our pork products such as microsoft Teams, et cetera, which allow you to add extra functionality. So JIRA does the same thing, right? So these company here, easy agile has developed a few products to enhance that functionality and that's what we're using here in case you're wondering why you're seeing. So this is one of those things that he's not out of the bucks. So JIRA does have a roadmapping functionality out of the bucks. But we've actually enhanced it a little bit with this atom that is by easy agile in the company and that we're working and actually added that extra functionality to make g route and the roadmapping functionality of JIRA leader with more robust. Why? Because we wanted to see epics. Markers, a couple of other things. Okay. But again, with JIRA does have an out of the, out of the box default roadmapping functionality which you can use, which is very similar to these unacceptably like these, but very similar to these. Alright. Now, the markers here, these colors here that you're seeing vertically are the markers. If I click on these markers, button is going to show you here. And that basically allows you to see these markers, okay? And you can create epics here as well by using this button. Okay. I'm just going to cancel that. Okay. But that's just to show you, like I said, an example of that product roadmap here in JIRA. And the key thing for me that I want you to take away in these, less on anybody's part of the course. Is that the product roadmap allows you to distribute unplanned award that you're going to get done in the foreseeable future, right? It doesn't necessarily have to be one year, like it could be to some people do rote maps up to five years in advance, right? But in this particular scenario, we're looking at a one-year view of these development on these build. And you can see how we've distributed. And this is something that you would do as a team, of course you wouldn't do this yourself. But generally product managers own the product roadmap. And they're the ones that actually see how this is built and how this is constructed. But the team is part of it and the whole team participating how this is developed, how the workload is distributed, et cetera, right? Because obviously not a single person can make such an important decision without taking into account the input for everyone that he's working on these, we need the input of everyone that he's working on these. Alright? So you can see here the first quarter and the work on the second quarter, et cetera. So as a team, we try to distribute how when you're looking at how to distribute the work that you are going to be doing your product roadmap. You're gonna think, of course about your resources. So how many people you have working on this? You've got to think about the workload, that complexity of the different things that you're doing. And then how much you can actually realistically get done, right? And then you start mapping it out and you start putting the different word, spreading the different work across the different quarters and of course the different months on across the different streams. So it works in vertically as well. Alright? So like we talked before, these big things and the colors here that you're seeing are epics. So big deliverables that you are seeing on screen are epics. And then inside each of those epics, like we saw before, in these only MVP, there are a bunch of user stories need to get done. So you can actually take this one complete. Ok. So once all of these gets done, we'll be able to actually mark this one, these big epic, complete. Meaning after I need all of these automatically this gets done because all of this, he's actually like a child and this is like the parent, right? So the epic is like the bigger thing because it's so big it can't do it in a single sprint. And all the user stories that you are getting NO3 are sprints will want you can, once you complete this user stars that are part of these epic will then automatically, the epic is then done. It's considered complete. Alright? And so you can see here we've gone through multiple sprints. And some of these work is steel. You know, it's still ongoing, right? Because there are still other user stories that still need to, need to be completed. But over time, as you are completing the whole user stories and you'll be completing the spring, the, the epic as well. And then that way you can continue to move on to the next one. Alright? But like I said, basically this is really good because he'd allows you to see when things are going live, when things are gonna get completed. And obviously a product roadmap is not static. It's something also that moves according to the pace, the velocity of the team, right? So sometimes you might need to shift things around. And another thing that you would consider, of course, as you're building your product roadmaps are dependencies. So sometimes you would say, OK, I'm not going to start this solution design, for example here until I've actually completed the only MVP for research office first, right? And that's why this is seeing afterwards. And after you've actually have these epics. Okay? So that's an example, alright, in the essential maintenance bid here at the button you can see we have system operating system patching, et cetera, et cetera, every single quarter because that's something that we're doing regularly regardless of what's happening in above, in the scenario we still into the patching a reporter. And that's why it's looking like this. Alright? Okay guys, so this is basically what I wanted to show you in this example of product roadmapping in JIRA. And like I said, building this is very easy. You just create the epics, create the themes. And you can filter here if you need to filter. Just to mosques, just the shoots that could see were worse hearing everything right now because we haven't actually applied a filter. But this is really a good way of you developing or it's a really good tool for you to develop a product roadmap in JIRA, Like I said, which basically allows you to see what's going to be developed over time and when things are gonna get completed. And you can continue to track progress, of course, by drawing your sprints using the marker functionality here. Okay. Alright guys, so that's what I wanted to show you on this lecture of the course. I'll see you on the next one. Cheers, bye.