In this lecture, we're going to talk about scrum boards.
You're probably already familiar as a user with Scrum Boards, so we are just going to go through a
few settings that you need to be aware of.
As a juror admin, if you have no idea of what Scrum Boards would come on board these again, I would
recommend you to go and take my basic chair course where you can learn all the basics.
So before we go in, start creating our scrum boards.
We need to have filter and I'm going to use this filter that we have created in the previous section.
But before we go, I like to show it to you another issue that I have encountered with team managed
projects, and I hope you remember that I did not recommend to or use to manage projects in general.
We have this book project, right?
A book project and I have a link to it to our super epic as well, because I wanted to show you how
we can combine in one board projects and issues from a number of different projects.
So here we get clearly an arrow because I'm using the same filter I did before.
And normally what we should get as a result, we should get all our peaks which are linked to our soporific
cover.
Could be 25, right?
And we do get epic book four, which is linked to maybe 25 and two more epics from from the PBE project.
So this is working fine, but we also need to get all the issues linked to those three epics right because
we say epic link, link, this should be 25.
So what do we see here?
We have issues flowing from our two epics from PB project, but we don't get issues from the book project,
right?
And we need to get them because we have internal for children issues.
So this is clearly an issue.
This is a bug, I believe, and I think this is happening because those two managed projects are relatively
new.
So a lot of things are still being tested.
Might not really work well by the time you're watching this course, it might be fixed in my side working
already.
But just be aware that whenever a new functionality is introduced in JIRA, it might not always work
as expected.
So make sure that you double check your filters.
Try with something really simple at first so that you can look at the results of your filter and compare
with what you are supposed to be getting as a result.
Okay, so we'll leave that as is.
Maybe it will be refreshed later and we'll get our issues here.
But for now, let's do it as it is.
We have our base filter and now let's go and create the board.
So to create a board, usually there is only one place you can do it.
So you go to your projects, you go to either project, it doesn't really matter and you'll be taken
to a board, any board properly springboard or come on board, whatever.
Well, it doesn't really matter.
So what you need here is clicking on those three dots and clicking on create the board.
It doesn't matter again, doesn't matter at all.
Where you started from can be any project, any board.
We are going to change our settings anyway.
So create a board and we need to trust from on board.
This can't be changed.
So we need to decide at the beginning what we are going to use.
And remember that you can create as many boards as possible so you can have one scrum, one combined
board.
And it's not a very critical choice to make here.
If something goes wrong, Scrum doesn't work, you can always great to come on board.
We are going to talk about come on board in the next lecture.
So here we are going to focus on Scrum Board and here this is very critical step.
If you create new boards, usually by default, you already would have bought per project when you create
a new project.
So board from an existing project doesn't really make any sense because you already have well, you
have a strong board for some project you might want to create a common.
Bond board on top of that.
But usually it's not.
So what you need to board with a new software project will also create a new software project, and
you don't necessarily need it in many cases.
So in 99% of the time, we are going to go for existing sales filter.
So that tells you that you need to have a filter first.
Okay, let's click on next.
And we are going to call it probably book cover.
So we are basing our board on book cover, saved filter.
So let's start with this filter and location.
Will tells us it will tell us which project it will be under or it can be also for location so I can
create a board in my personal space.
And what it will do, it will create a board just for me, which I will be able to share with other
people.
But when we go to project in one the appearance here on the left hand side.
So in most cases, you probably will want to create it under a project which is the most relevant.
So here, publish a book on concrete board.
And let's wait for a second.
So here we get our board again.
This is very, very confusing because this issue, the behavior is not what I expect.
Normally when we have epics in our filter, they will go automatically into this epic panel.
So we do have it here, but it doesn't work as a proper epic filter.
Right.
And at the same time, it also appears here.
So this is not how it should behave.
I hope that by the time you're watching this, they have already fixed it and team managed projects
work just fine.
But for now, actually, let me just go and remove this link so that we don't clutter our board with
this weird, weird thing.
But normally you just need to remember that you can have as many issues from as many projects as you
want on your board.
Okay, so let's refresh.
And here we should have a clear board with just two epics now.
Okay.
So a few things that you need to know about the Scrum Board as a group.
And again, we are not going to go into all the details of how it works.
But as an idea, when you set up a board or when people come to you with some issues, complain that
something doesn't work or ask you to help them to optimize the board too, and they have no clue how
to work with it.
First of all, the most important feature of the Scrum Board is that we need to be able to prioritize
issues but just drag and dropping.
And this is why this is why we absolutely need to make sure that our filter, the base filter of this
board has water by rank ascending in the filter.
How do we check this?
We go to boards things and on the main page and the general page, we can check our board settings so
we can see we can change our board name, we can see who is the admin, we can have more people and
we can see the query.
So we have the name of our filter, we have the shares, we have the edit rights and we can check the
query.
So we can't edit it right here, but we can click on this is such a query and go to the keyword beach
and edit the there.
So here we can see all of our rank ascending.
Then it works fine and ranking would be using rank.
This appears automatically, so projects in board would sometimes give you certain areas as well.
If you specify the specific projects in the fall to query.
So like I said, in a way that as long as an issue is linked to an epic, which is internal link to
the speech point of that issue, it will appear regardless of the project.
But sometimes you would want to limit your filter to a number of projects, and in that case you will
get a list of projects on this board here.
Okay.
So the most important thing, again, is that we can order by rank actually doesn't really matter if
it's ascending or descending because you will be prioritizing on the board anyway.
But if you make it descending, all the other filters, all the other boards that you use also should
be set to descending because otherwise if you have ascending on one board, descending on one board,
on another board, that would put this issue at the top, on one board, at the bottom on the other,
and all the order will be complicit, right?
So make sure you stay consistent and then it doesn't matter which one you stick to.
Most people said ascending.
Okay, then as I said, you need to make sure that you include epics in your filter.
So we discussed it in the previous lecture.
Make sure to check the query to have your ethics here, otherwise it won't appear you will have a blank
epic panel.
Now, when it comes to board settings, what are the common problems?
What are the common issues that teams are facing and that we need to fix?
First of all, is that certain issues don't show up.
This is always happening to teams.
Oh, I created an issue and it's not on the board.
What should it or I.
A smooth transition.
It has disappeared.
A few things to check.
To check.
First of all, you need to see which issue they are talking about.
So get their issue from them.
Then we go to board settings and first thing we do is check that the issue is filtered properly by our
filter query.
You should be able to read the filter querying the way that you can tell whether an issue will be an
issue that you can check or be will be shown in the results or not.
If you are in doubt, you can also go to filter query, double check the query, check the list of the
issues it filters out and then start from there.
All right.
See if you can find your issue here.
If it's here, then the query is all right and something might be wrong with that board itself.
So what else can go wrong?
The next thing we check is columns.
So right now, here we have a basic set of columns, a basic set set of issues, basic set of statuses.
Right.
So we have to do in progress done.
And we can add more columns and we can we can remove columns.
So let's say we add editing column.
And we put this status to editing and then we decided to just remove this and progress column.
So we only have three columns now and we think that for our purposes we can go straight from To-Do to
editing and then to them.
So right now we have 12 issues in our board and they are all in open status to do right.
So now let's go to our board and see what happens if we change the status for, let's say, this Picasso
design issue.
So from open to start progress, we need to switch to writing.
Okay?
We need to fill out some fields.
Okay, so now it's in writing.
Now let's refresh our board.
And all of a sudden we don't have this issue here anymore.
Right.
So it has disappeared.
And what happened?
It disappeared because the status is no longer on the board.
Yes.
The status the columns are related to active space.
And these boards is currently not active because there are no active springs.
Right.
You need to start a script.
But if something doesn't show up here, it also won't show up on your backlog.
So this is very important.
In our board settings, we need to make sure that there are no maps, statuses, or at least there are
no issues which are in a mapped statuses.
Okay, so let's put it into progress as it was and drag the statuses back here.
So based on the team's demand, you can create more columns, you can remove certain columns and remap
the statuses and just make sure if something disappears from your board, chances are high that it's
because something is wrong with your columns.
Same thing happens quite often when you change your.
So a lot of people, when they change workflow for the project, they forget to come here and update
the statuses.
So make sure you do that.
Otherwise things might just disappear.
Okay.
The rest is not as critical.
So we have a lot of settings here.
We can see in column management we can set the constraints to issue count.
For example, if you are doing more combine, like if you have encumbered like processes and you want
to set up working progress, minimum and maximum number can do minimum maximum.
So this is just for our active springboard.
So let's put it to NUM for now.
We can set up swim lanes and this is for our sprints and this is most mostly visible on the active sprint
board.
So we are going to talk in the next lecture.
We are going to talk about come Kanban and come one is almost identical to this active springboard.
So we are going to talk a little bit more about settings in the combined section.
Quick filters would allow you to have those quick filters at the top of the board so they appear here.
Finally, we have only my issues and all updated and they are shared across back all connectors things.
So you can't separate and have one set of filters here in different set on active scripts.
So on top of the default, once only my issues are resolved updated and you can add you can add a new
filter and it would be based on the check cloud.
So we can see, for example, labels equal what we have for labels, let's say urgent and we can call
it urgent, can send descriptions not necessary and edit.
And now we have this, this urgent flowchart before refresh for the board.
Okay.
Now, if we click on our channel, it will filter out only issues which have that urgent label on them.
So this might be helpful if you have very large or very large backlog with lots of issues and you need
to help the team to sort out things.
Yeah.
So urgent if you like.
We get back to all issues.
Okay.
We can change the card colors.
I would not recommend you to do it so you can basically show the issue cards and different colors.
So let's say based on the size so we can decide who has which color and if we do this.
So let me go again to our backlog and see if it changes here.
Right.
So you see those colors here based on assign is a different assigning should get different colors.
I would not recommend to do it too because it slows things down.
So only do it if you have small board, if you don't have a lot of pictures, otherwise it will be taken
forever to load.
Okay, so usually I would say now you can change your card layout.
So what you see on on the cards and here we split between backlog connective space.
So on backlog, for example, we can say that we want to see labels and we click on labels, we click
on ADD.
And now if we go to our backlog and we are fresh, we would have an.
I feel it when I go back home.
Issues, you see?
Tests Urgent.
Urgent.
So this makes the backlog looks much longer.
It adds one extra line to every issue.
So there are pros and cons.
Some people like it.
Some people dislike it.
So ask the team what they need and said from there.
Next we have estimation usually normally would just points.
So based on that, all the statistics get calculated for the reports and we are going to talk about
reports later.
So if you are not doing start points for whatever reason, you can also use Thomas to meet or you should
count.
So just counting the number of issues.
But I would highly, highly recommend you to explore story points and trust points.
Usually that work really well for different sorts of teams and not only in software.
So learn about start points, trying them out and they work really, really well on your points.
Then we have working days, so this tells us the time zone, the working days, and this helps us to
to figure out our statistics for for our reports later so it can change your region, your working days.
Then we have it should tell you so this is what you get on the right when you click on the nation.
This is what you get here.
So we can select what we want to see here in the main section, the tail section, and in more fields
section, right?
So we can add different fields.
This is different from our scoring schemes because spy schemes tell us what are the fields that we have
in general and this tells us which fields we show here on this specific board.
And because we don't show something, it doesn't mean that it doesn't exist.
Okay.
So this is basically built on top of our existence camps.
And finally, we have the road map, which basically allows you to enable or disable road map.
And we are going to talk about that a little bit later.
So those are the main things that you need to know about the board.
But please keep in mind that the Scrum Board also sort of includes a combined board in it as well as
Kanban board sort of includes the Scrum Board and they will see how.
So on a Scrum board, you still have a mini camp on board which is your active space.
And everything that we are going to discuss in the next lecture when we talk about coming on board is
going to be applicable to this one too.
So please pay attention to the next lecture as well, even if you only are planning to use Scrum Points.
So this is all first Scrum Board and I will see you in the next like.