The Jira Dashboard and Tools
Intro to Agile
Jira and Agile
Jira Dashboard and Tools
Conclusion and Q&A
The course is part of these learning paths
This course is designed for users who are already able to create, update and search for issues in Jira but now want to understand how to use Jira to control, manage, and maximize the effectiveness of their agile projects. We will look at using Jira in Scrum and Kanban projects and how Jira can be a powerful aid in the pursuit of empirical process control.
If you have any feedback relating to this course, feel free to contact us at email@example.com.
- Review Agile, Scrum, and Kanban practices and how Jira can be used in conjunction with them
- Understand how Jira can be used to capture Epics, Stories, Tasks, and Acceptance Criteria
- Understand how to use Jira to manage Scrum and Kanban projects
- Learn how to use the Jira dashboard and tools
Anyone looking to improve the way they use Jira to manage their workflows and projects, through the use of agile practices.
To get those most out of this course, you should have a basic understanding of agile and Jira.
Now the other thing I would say about Jira is that Jira allows you to create your own dashboards. And so we go to, if I went to dashboards here, and I said, view system dashboard, and then what I can do is I can create my own dashboard. So this three-dotted button, I can say, create dashboard. I can give a dashboard a name. And then once you've created your own dashboard, you can add lots of different gadgets. There's a little load all gadgets tab, tag, and there's lots of little kind of reports and graphs and charts and filter results, and many, many other things that you can add in to your own dashboards, and you can create multiple dashboards. But the nice thing about a dashboard over a report is that it's pre-configured and you can have multiple gadgets or multiple graphs on the same screen. So I would definitely recommend you try and create your own dashboard.
So go to dashboards, manage dashboards, my dashboard, and then click on the three-dotted button, go to the system dashboard to begin with. You can click on that three-dotted button and then create dashboard. And then you can create your own kind of pre-configured report windows with lots of little kind of graphs and analyses and Scrum boards and Kanban boards, and whatever you like all ready to go. And it means that you're not having to create, go to the reports tab all the time and generate new reports, you can literally just go to a dashboard and it's available.
Okay, so some useful reports there, I'm just going slightly over, but I just, I just want to finish off by talking about enhancing Jira, and then we are done. And so the culmination of all of this is talking about and making sure we're increasing transparency and maybe even working across projects.
Anyone remember the three pillars of empirical process control? It's a question for a Scrum exam if ever there was one. I'll give you a clue, the first one is transparency. Come on, guys, come on. Transparency. In? It's getting late in the day, isn't it? So transparency, inspection, and then adaptation. Adaptation, absolutely. And well, I've just talked about some of those features, haven't I? What would you say Jira isn't good at? I know what lots of people say here.
Replacing communication. Replacing communication, that's true. But also, Jira isn't really that great at time tracking. I think, you know, at least one of you is kind of asked a question about that. It doesn't really, I mean, it does do time tracking, but out of the box, it's not great at it. There are time tracking add-ons that you can add in to Jira. So yeah, so that does things, so there it is, empirical process control, transparency, inspection, and adaptation.
There are a few other transparency tools. There's a tool called Confluence and Confluence is like a document management tool that allows you to create kind of web page type documents, but it also integrates into Jira. So you can, in Confluence you can include links into Jira Issues and Jira Epics, and so you can create documentation that allow people to link across into Jira.
So a lot of people use Confluence documents as a way of providing the wider business with information about the projects. And so it's an Atlassian tool and it's definitely one that I would recommend you checking out because rather than saying for the business, if you want to know, look in Jira, it's sometimes a nicer idea to give the business a link to your Confluence project page, and then it's a much nicer interface, it's a web page interface where you might post the latest information about the project and from there they can get to Jira reports and then if they want to they can go into Jira from Confluence. And it's a much nicer transparency tool.
So like it says, many teams create Confluence pages to demonstrate this. We looked at reports for the adaption phase and how important they are. So that's key. And then I also showed you the dashboards. And I would say creating some of your own dashboards, I would definitely encourage you to do that. So if you've got some time just finishing off today just to create a dashboard of your own.
The other thing about Jira is that the dashboard, you can create multiple dashboards, those dashboards can be presented as full screen wallboards and you can actually project them or show them on big screens. And lots of teams do that, lots of teams show the Scrum board or the burn down charts, and maybe other reports on big screens so the business members can just walk around the different teams and they can look at the current state of play, which is the ultimate in transparency.
So you're not hiding anything. If anybody wants to know where the project is, they can literally look at the big screen and it's there, you don't even have to have a Jira license. So the dashboards can help you really kind of widen that transparency. And there's an example of a dashboard, but it's not, I mean, you can make your wallboard look much nicer than the that, it can have a dark background and look really cool on a big LCD or a projector.
Agile Projects are created with a default board, but you can also create your own boards in Jira. So instead of just having a Scrum board or a Kanban board, you can create a board from an existing project. So you create a new board, and then you can display issues from multiple projects if you want. So you can have a board of boards. And we often call these rollup boards. And you can see it asks you which projects do you want including on this.
So if you want to report across projects, then this kind of board would be ideal. If projects don't contain the same statuses when you're creating a rollup board, you sometimes have mapping in your columns, which is fine. But, but yeah, I mean, it's possible to sort of bring multiple projects together in one board if you want. And that's something an admin would do, but it's something to remember is possible. And then you could also configure your rollup board to have multiple swimlanes.
Now I mentioned that Jira Cloud has a little kind of roadmap that you can use with Epics, which gives you a sort of almost Gantt chart-like view. If you need to manage multiple projects, or the managements of multiple teams, so in other words, to manage a portfolio of products, then there's a tool which is now called Advanced Roadmaps. It used to be called Portfolio. On your PDF it may still be called Portfolio, the slide may say portfolio. But it's an add-on into Jira, and that will give you much better cross-project and cross-team analysis and management. But certainly out of the box Jira is very much a project tool rather than a cross-project tool.
QA is the UK's biggest training provider of virtual and online classes in technology, project management and leadership.