So what I'll do is.
Just because it's the beginning of the cause, I will prefer doing everything from ground up.
So go to Dev your dot com, slash your organization.
Now, if you're already logged in, fine, it will automatically take you to the toilet, but if you
are not logged in, you'll have to log in.
So understand, it's only a dickens of dot com, which is my organization account.
I'm having access to this particular.
Organization, Dan 20-20, Dev Ops here, for the sake of few people, you probably want to create a
new organization and work with that.
Absolutely no problem.
Who can create as many organizations as you want?
Something.
And once you get into the organization.
Very quickly, you have to create a project, the starting point is always going to be a project creation.
So I create my demo project, we can keep it private, so only those people whom I am going to send
invitation would be able to have access to the project.
So right now, there is only one member that is myself.
I can invite other members, but before we invite other members, I think we should do is go to the
organization, what organization settings and under users who are users whom you want to send invitation.
So right now.
I'll add.
This user and I want to probably give access to the project also.
But e-mail invite is going to be sent to that particular user.
So this user has long been known to do something wrong.
I did so I should delete it.
I do not think that means it is not even doing a verification, actually.
So I'll type No.
Outlook dot com, and I'm giving access to this project and also I'm living the access level basic.
But he has not signed and unless he has signed and I will not be able to use this user for assigning
any task.
So what I'll do now?
Koutou in Private Windle.
And I will login with that particular.
I'll see an email there.
That I've been sent that invitation.
You have been invited.
Click on Join now.
Provide your username and password.
So now this particular user identity was given us around Ranneberger.
I invited him by email and he has joined and now you see this particular account also has access to
the same.
Company, same organization.
So I have two windows now.
This is the private window where I'm logged in as a hologram.
This is my actual window where I'm logged in.
Sandeep's on it and both are having access to the same organization.
How I actually invited that user to refresh this page.
And you'll notice that last access date has come, which is touristed.
Because I have visual studio enterprise subscription and getting the access level as that, but otherwise
it is basically the only difference I told you before between these two is in visual studio enterprise.
If you already have a license, you do not need a separate license for the box.
But for basic users, we need licenses beyond five users.
In one organization.
In one organization, up to five users are absolutely free.
So I'm actually not interested in this window.
I just wanted to show you that one more user can be added close and maybe that particular user who whom
I have added in this particular organization, I would prefer making it as an administrator.
Always it is recommended to have at least two administrators.
So go to permissions and you see project collection administrator right now.
It's Sundeep Sony and.
Project collection, service account that is not a user and also you see there the a warning, there
is only one project collection administrator by chance.
If the project collects collection administrator account is lost.
This whole company would be lost and that would be a dangerous situation.
So it is always recommended to have another project collection administrator, so I will add that second
user here.
So like this, we can have multiple users and for every user, you can have a certain role.
So now this particular rule is given to all and most of us are having the same privilege.
In this particular organization.
Though I am the owner, the other control is only going to be a member, but still Rühle also will have
almost the same permission as a project administrator.
Application can perform all operations on a team project collection, everything he can do as much as
I can do him, and he can also do the same things.
Everything is along, you see, everything is lot and you don't have to change it.
You can't it.
So like this, an organization has been created and under the organization, a project is created.
You can go to the project.
And from project, also, if you want, you can send invitation to users.
This is project settings.
So here also you can go to.
Beams and actually create multiple teams.
So right now in this particular team, there is only one one user.
You may want to add one more user.
So the default team, which is created is by name of your project.
Under that, the creator is the only member.
So I'm adding now one more member, which is.
So in my team, there are two members, maybe you can actually create multiple teams if needed.
So right now, we have got one thing we can add a new team, we can call that as a Web development team,
a testing team, a design team like that, we can add multiple teams for, let's say this is our development
team.
And here we are again, private members are in for now.
I don't have many users, so I'm adding some users as development team and the default team also.
And of course, after you create a new team, you may want to make this as the default team and delete
the old one.
You can do that.
So a new team is created.
And any time new members can be added.
The administrator of this team is Sandeep's on it because I only created the team who can provide an
image, all of the basic things.
Now, once the team is created, you will be actually doing.
As your both and whenever you are doing a board.
Remember, you have to first choose a team.
Always will have to choose a team for which team are you going to manage a board?
So let's say I go for a default, I'm only.
Every time Lloyd will ask me for a team for the project, which is created right now is a basic project.
That is why we are getting basic process project.
That is why we are getting to do doing done.
Now, you may want to change this basic project from.
So you want to change the process from basic to agile, so go to organization settings.
And here the board has a process called the process right now, default basic was used.
And here you will find the project, and that is where you may want to change it.
I'm changing the target process to now, as I say, it is doing, but that's fine with us because we
did not add any work items.
So nothing will be broken for us.
I did a column to state mapping.
Existing work items, blah, blah, blah, story, no, go back to the project.
My demo project, and here, if you go to both.
The configuration is not correct this now.
Because of the taint of this is going to become tedious, we'll have to change all these names now to
match the ADILE.
So what I'll do is to avoid this problem.
You do that practice and simply create a new project.
I want to concentrate more on Agile, so I'll create a new project, my agile demo project here.
I'll have to change it.
That's it, not in this right now.
Again, only one member.
I cannot simply add the use of that or.
Now, what about.
This is the cannonball right now, there are no work items, so we'll take one at a time.
No, let's start with the first on the board boards category work item.
You can add different types of work items in Agile.
They can be bux Ebix.
They're sorted in alphabetical order, but at the highest level we always have is an epic.
Now, for demo purposes, I do not want to cause confusion, I'll simply give a simple naming convention
a big one.
That's it.
I'm not worried about other details, I just created an epic one I go to back like they are, multiple
ways of adding you can actually click here and from here also, you can add an epic.
A big deal.
It's even.
This is quick, this is always going to be there, so in your time, you are you can just go here and
new work item, an addict under a big always is a feature.
So you may come here at a veto, let's say a feature.
I want one one which is under EPIK.
So I'm using some naming convention feature one one should be a child of a big one.
As of now, it is not a time they're all at the same level, how to make them as children.
We will see like that.
I know.
One more feature.
I call this as feature one two.
This is the second title of that same epic.
I know one more Fito.
I'll say this is Fito.
To one, this will be the first title of second epic.
But is there any relationship between them who can actually go to Borders and in both teams to if you're
not able to tend to it because the default setting for the canvassing board is you can only view backblocks
at the level of features and stories.
But if you want to view at the level of.
Epic also, which actually is not recommended, but by chance, if you want to see iPIX features and
stories, all the three levels, if you want to see here by any chance, you go to the two options,
actually.
You can go to simple shortcut would be here.
Go to settings of the gang member and in this.
It's not showing up here straight.
So first, let us go to.
The Project Sitting's.
Not doing projects that should be at the organization level.
Backlog levels, this is Read-Only here.
We want one more, actually.
Sorry, it's in projected team configuration here, we'll have to put a checkmark.
And the Project Sitting's team configuration Polytechnique.
That's it, no.
Go back to.
Both you can now see the level of.
Apicultural.
It's in backlog's the same option, you have to go to both sorry, not both, actually backlog in backlog.
Also select your team.
And under backlog's also, you have the same option you can to kill.
So at what level backblocks must be shown that you can control?
Not recommended, I would not want to have this Ebix.
But for the purpose, let us keep it here, so now I have a big one, a big one has
two features, a big two, a big two has only one feature, not that hierarchy, if you want to see
if you can actually go to backlots.
No, I did not make them as parents, so let's do parent child relationship, not now to the parent
child relationship.
No, I'll go to a particular epik and here we will have Link.
I don't think.
I want to create a new item or I want to use an existing item, I already have a feature, so I'll go
to this is a big two.
I want to add up.
Cling tape, you see this bullet?
I want to add a link to it for this.
Fito.
To one.
So this is Bill and this is tell me if I changed, I can also do this.
I've saved it.
Now I go to both.
Let's go to work item and then go to feature, I want this feature to be a title of this story, this
whole idea that would feature and this time the link which you are going to create.
Would be parent, I want to decide a parent see this I can't right now.
It was the moment I attended parent.
It is fact, and now Al provided the link of a.
So feature one two is a big one.
That's how the relationship.
Save this.
You may want to have.
Back to work item.
A big one.
I add one more feature and only one feature right now, I want to I want to add one more also.
So here, I should note, in the 210.
Pheto one one.
So for a big one, we have two children.
Let's see the hierarchy.
Viewers backlog.
And you can expand.
And not only that, from here itself, you can add new features.
And you work, I don't, but I want to change it to feature first.
A new work item, and from here itself, we are able to add that Fifita to.
At the local.
But this is not yet a tail.
If you really wanted a child of a two, then what we should have done is change this to a big one right
now.
This is not a feature to do in order if you directly wanted to add feature to do as a child of a pig
to use this.
It's adding a user story.
Sorry, it's not adding a feature, it's going to use a story directly.
But we want your the story to be told of.
Fito.
So we can go here and we can see.
A user story, one, one, one.
Are you the story
on one to.
And it goes on.
So you're able to see the complete hierarchy, a big one feature, one user story under the story,
you can add a task.
A task one.
No further task.
You may want to give a lot of properties.
You can give a link to your report right now, we do not have.
So don't worry about it.
You can link it to a user story.
It's already getting linked.
Parent will be the story one one one, because from there, I navigated.
So I'm just leaving it out, or we can give that one one, one, one.
I'm just creating a hierarchy.
I can add one more task.
So if you have all your items ready in Excel or maybe in some documentation very quickly, you can add
all of them over here, various ways of doing it.
So good.
Both now in both.
First, let's finish it off with work items, not invoke items we have got.
The first dropped recently updated so you can expand and they recently completed, if at all, anything
is in complete state.
We don't have anything in complete state and recently created.
So this will be in order.
You see, it is actually the order in which they are created.
And the idea is not.
Following the sequence for each type of work, it's a common sequence used for all type of work.
You don't really need to worry about it, but many times we would want to refer to a particular work
item by item.
When an email isn't about the work item to somebody, it will be put up in that email.
That is unique.
It is always unique, but you don't have to set it anywhere and you can't even edit it.
So you recently created know there are certain work items where you can actually do following, like
I am more interested in something like feature one or two so I can go to feature one, too, and I'll
say I want to follow this feature.
Any kind of activity on this feature I would like to follow.
And this also you can further customize it.
Only received notification from this work item when you have been mentioned.
That means.
We will be mentioned somewhere in the discussion, it will be mentioned in the description, it will
be mentioned then only we are going to get.
The notification, but even if you are not mentioned and if the state of that work item changes, you
will want to get the notification, then you have to use this.
And of course, you can do a custom whenever a state changes are then to changes and it's a tradition
in print.
Didrikson Tinder's.
Then you may want to get a notification.
So here following is important.
So now once I have some items followed, you can actually go to.
Queries.
And there will be a built in Querrey.
Not that so.
They are still able to all under the belt carry followed work items, you can just click kill and all
the work items which are following will be listed here.
Quick references to Paris.
Go back towards.
So they go back to work items so like that, the ideal to always keep is recently updated.
So, you know, the latest which are updated or on top, then you have all the work items which are
assigned to me, which I'm following.
You can actually filter it from your.
Well, I just mentioned.
My activities.
So right now, I'll just leave this default recently updated, this is two different types of work items.
Open inquiry, you can actually see the whole result actually can filter here, you can see, say,
work item I want is only tasks and features.
I'm not interested in everything.
You can filter it and see the job assigned to me.
You can specify based on state right now, all new only, so it is not displaying either state, but
if there are items with other state, they will be listed here and we can filter them for whatever we
do here.
With all this.
When we say open filtered view inquiries, it will take me to Kooris.
A new query has been created.
You can see that, Ed.
This is the result.
And if you decide to save this query, you can do that.
Give me my.
Frequent something.
There are two types.
One is called El Microarrays, another is called I'll come to that later.
I'm just saving it in my query folder right now so you can go to queries on the queries.
My queries.
We have got my frequent.
Spelling mistake is that.
So you can rename it.
Avrin ended.
Back to work items.
We have options right now.
You're seeing some columns you can add or remove columns.
You can add a new column and you can choose from the list.
So you may want to probably see the priority.
The priority is to for all of them, you want to remove some columns, you can do that also all these
things can be.
Important if you have a CFP file in the format, right format, you can just import them all into the
work items list.
You can do that.
Yes, any item deleted will automatically go to the.
Recycle bin, for example, I would like to delete.
Let's say this task, I would like to believe that test.
One, one, one, two, I would like to delete it.
So just Google delete.
It's deleted, but you can always go to recycle Bill, but that also takes you again to Querrey.
Carrageenan, Chris.
And from here, you can decide and restore it.
You can either permanently deleted or restored it.
And restoring it.
So back in my work items, that item will be there.
Yes, I protest, I can edit.
Anytime.
So with this.
We have got all the options which have didn't work, I tell you, we want to filter down to remove all
the filter.
OK.
You can just click.
All the items are flipped, otherwise filtered or just deleted any time you can get the filter back.
Completed work items you may want to hate because this list will keep growing.
Then we have got board, these boards are referred to as kanban boards.