© Distribution of this video is restricted by its owner
Transcript ×
Auto highlight
Font-size
00:01 And this video will cover sprints. features, user stories, spells and

00:06 using edge reports after you've made your and set up your repos head over

00:11 settings, team configuration, check ethics backlog navigation levels. Once you've done

00:22 , go over to the boards, sprint. So three sprints have been

00:32 made for you. Your first 2nd and 3rd to set a

00:37 You just click here. You can the name to like whatever you

00:43 You can set the date and the date. Just a heads up.

00:48 github, you can't back date in ops. So just be cautious,

00:53 when you set up a date, cancel, ok? I click on

01:08 set this Epics. Now according to documentation, Epics are used to group

01:13 under larger scenarios. So let's create . So click on new work

01:19 So an Epic would be something like entire front end. Pretend at the

01:28 right there. You you have your topic. Now let's say another Epic

01:32 be like your database and let's have more. We'll call it back end

01:45 P I O. Alright. So an API comes the features. So

01:55 way to create a feature would be . So for front end, you

01:59 come here, click on the plus , let's create a new feature.

02:06 let's name it, sign up page, we can assign it.

02:13 let's assign it to me comments you have like your state here,

02:20 These are both. Yeah, you have a description, you can have

02:24 discussion, you can have your you risk like how, how great

02:33 risk is business value, time start and target date. Risk is

02:46 self explanatory effort is in terms of . So let's say like a sign

02:50 page might take like uh like 15 maybe. All right. So you

02:56 , it automatically assumes it's our. you don't have to write hours if

02:59 do that. Give an error. For this guy, I do

03:04 I believe you don't have to worry starting target for individual features. Same

03:09 the business value and time criticality. that we have our epic our feature

03:18 your story, let's add a task would be like log in component with

03:27 react, save it for your your planning discussion description, priority effort

03:33 terms of like hours. So save close and let's add a bug,

03:40 bug. Let's say the login button working. All right. How would

03:50 reproduce the steps just like fill in user name, click log in same

03:56 before. All of the same, clothes. Now, let's say if

04:02 don't let me open all of them , you can like open through the

04:09 your features and your. So let's if you don't finish something in this

04:15 , you can come over here side to the planning side. Now,

04:21 say if you want to like, you don't complete the sign up page

04:25 iteration one, you can drag and to the second one or same with

04:30 others. Now, we've seen how and backlogs work. So if you

04:38 on work items, just shows you like all your bugs, your

04:43 your Epics. If you want to filter type, you can just look

04:47 your Epics or Feature Epics who they're to. So, I mean,

04:58 you can add more stuff. All . Now let's take a look at

05:07 board. So like here it shows all your Epics through like the

05:12 If you look at your features, stories, let's go back graphics.

05:22 let's create a column for blocked, ? So settings board columns, I

05:32 to create a new column. So column blocked, you can leave all

05:41 as is. So I want to it towards after active, you can

05:48 position these saving clothes. Now we it blocked colum. So all of

05:57 are easy. It's easy as we're drag and drop as you go along

06:04 the status changes as you as you . Now, we've created an epic

06:13 . Now let's create a user Now, user stories are developments of

06:18 often expressed as a persona plus a plus a purpose. It's like as

06:24 as a person I want or actually a user, I want this to

06:28 that. So let's see here. , so as a new user,

06:34 want a register like register page, want to see a register page,

06:38 that allows me to enter a user and password. Uh Again, same

06:44 with like as it was with you can like assign somebody. Oh

06:49 , probably uh description, discussion, points. Now what the documentation about

06:55 points is say are story points or , estimate the amount of work required

07:01 complete a user story using any numeric of measurement your team prefers. So

07:09 say like uh 10, like it's this, it's pretty high priority.

07:16 believe four is the highest. Don't me on that. Maybe it might

07:20 one. So I'll assume let's say super, it's really high classification.

07:25 You don't have to worry about Plus let's look at queries. So

07:33 are just like a a combination of few logics which are applied on work

07:37 . They can be used to see tasks are assigned to who, who's

07:41 on what the deadlines and stuff like . So click on new query,

07:48 two roles will be created by So this field for a field you

07:53 go and see which uh what you to work with. You're operator.

07:58 are quite a few. So let's if I want to make a query

08:03 finding all the bugs that are assigned me. So I got a value

08:08 look for bug. This is then the next row, what else do

08:14 want? So also I want to assigned to so bugs that are assigned

08:21 equals me, me and I'm gonna the query. So this is one

08:28 that has been assigned to me. say if I just want to see

08:30 stuff that has been assigned to So these are all the things that

08:35 been assigned to

-
+