Alright, so guys let's begin.

So, I was talking about agile and we people started

These are all the user stories you have you. So I am storeing here the user stories
and not only user stories, the product backlog will be used in the companies to
even store the bugs. Imagine these are all the user stories and these are all the
bugs defense. Ok, these are all what defense correct this is what I explain now
adding the users stories in your product backlog will be done by a product owner.
This will not be done by developers, this will not be done by testers.

1 who is adding the users stories here is a product owner. So we will have a role
called as product owner. Let's keep making a note of the roles in 1 place. So I
have a role here, which basically what? Product, product what ओणम, product what इज
the next step from your हां हां ए true या होकर planning activity और डूइंग but
happens इन which place what इज the call dance ए big lock ए ग्रूमिंग talk about back
long रूबी will start from your father नो सोफ़ा जो product owner एंड बिजनेस channel
इस त्यौहार एंड test are also but what इज the thing too understand subscribe टो ए
big boss if you don't define how कांप्लेक्स user stories are यू don't define how
परिसर यूज़ stories are आई will नॉट बे एबल टो arrive अट थे depression of it ok if यू
want थे depression of ok how मच time it will take टो build ए user story we will
definitely require ok to give complexity points which is called us user story
points.

Ok, so will have to give here something called us a user story points. Now what
does story points are being give me सो give the user story points company will use
a technique called us planning पोकर activity. Got it, they will use a technique
called us what planning पोकर activity in the conference call or a meeting, right? A
virtual meeting on Microsoft teams or any other online meeting software the product
owner is now going and telling look, This is the user story and this user story is
about let's say developing a login feature. This user story is about developing a
login feature and this all feature should be present.

Now while the product owner is telling all of these things, there are so many
developers, there are so many developers, there are so many developers, there are
listening to the product owner and at the same time you will also see there are so
many testers, they are also listening to the product owner and trying to understand
the user story. They are trying to understand what the user story. Ok? नौ after
listening to these user stories behalf developer, we will have here the project
manager, the project manager will be there in the meeting right there will be some
fellow called us team lead team lead will talk about स्क्रैप master in a while this
all people are listening तू product owner my new project has started all यूजर्स
story has been kept ए product backlog some 500 user stories are kept नौ after दिस
user story are kept नौ दिस user story इस वैन by वैन pick pick up by डी product
owner एंड डी product owner reach out दिस user story टेलिंग date दिस दिस feature
development नीड्स तू be दान All the people on the conference call the listing
developers, testers, project manager, team leader all listening to it.

And at the end after the explanation is done, the product owner will ask. Anybody
do have any confusion about this feature? Firstly tell me that. Right this teacher
to be develop, you have any confusion if any confusions other people will have वन
called as question mark. They will raise that particular card and now he will
unmute them and ask them ok please tell me that what question you ask.

So you tell ok in this side did not understand this part of requirement can you
explain that a bit? Right? Anyone else do you have confusion? No, everybody clear
about the user story? Yes.

So नो product owner is asking if you have understood a user story, you tell me how
much points will you give to this user story based on complexity. So, we will use
something called as a planning poker card. Right, you will see here a planning
poker cards, agile. Right, Agie यू will सी योर नो the planning पोकर card will look
like right यू सी दिस year दिस are the planning पोकर card are going तू be like right
लेट me copy दिस image एंड लेट me पुट दिस image on डी एस पे India और हर ok नो सी
date दिस हो यू are planning पोकर card will look like एवरी person एवरी डेवलपर एवरी
टेस्टर will have दिस card नौ what दिस card डी नंबरिंग इस being जिवन based on डी
विपनो के series ok इसे note स्टैंडर्ड practice but डी best practice डी विपनो के
series दे will be फॉलोइंग और डी card numbers are being जिवन इन which देवर इस वन
card question mark question mark it मेंस नौ ok तेल going का head एंड picking up दिस
पार्टिकुलर card एंड टेलिंग आई have अन question about दिस पार्टिकुलर user story यू
can आज डी question product owner हु इस डी स्पेशलिस्ट इन डी domain right it इस डी
banking domain he knows everything almost everything about the banking domain you
can ask him question he will clarify your doubt because without understanding the
requirement you cannot build the software.

After the clarity of required user stories with done, clarity has been given. Now
people will pick this card. So, how this card is being picked let's say this
particular card is been pick now, ok by the developer 1. The developer 1 year fixed
this card. What card is picking up?

It he says I will give complexity 8 to it. Now the other developer also picks up
the card complexity 8 but the developer who is here now ok, the fourth developer,
he picks up the point, आज ok, 5. He picks up the card and he will not tell that
this particular complexity here seems to be 5 more. Now bigger the number more
complex. Lesser the number less complex.

More complex, more time. Less complex to build less time. It's understood. Right,
bigger the number more complex. Highest complexity point, hundred.

Lowest complexity 0 and in between we have the numbering that we have given
following some technique like bipnac C series. Now the product owner looks at that.
Testers are also doing that. तो tester are estimating the time taken to test that
and that telling the complexity but the major role here developers will play more
than testers correct? So now the developers some of them have given 8 a day and the
course the developers giving 5.

So, the product owner will now ask, can you justify why the complexity point should
be 5 and not 8? Why should be 5 and why the complexity point should not be 8? Can
you please justify this to me? For what reason the complexity point should be 5?
Sir to build this login feature, we already have the built in features.

To build this particular, ok you know stuff basically we already have the built in
library like split security. So this is not going to take much time. Right, so we
are using spring security, if you are using this built in libraries, if you are
using this building concepts, for this I don't think so, that is going to be
complex. It is going to be what? Basically complex.

Are you understanding what I am telling you? Yes everyone. So now the developer for
what is he telling now? If other developers are even, hold on. कौन minute hold ना?

Observe here now, when we are talking about, ok, the developer core, what is he
telling? Other developer agreed to that because developer 1 and 2 are juniors right
they did not had much experience but this developer code is highly experience and
yes more clarity about the development. So now the product owner will ask ok अन
डेवलपर वैन एंड तू are यू clear with date सो दे my agree और दे my दिस agree right सो
if दे agree दे से या या आई agree तू date date point did नॉट कम तू my mind प्रोबेबली
if take date पार्टिकुलर approach सी can make it more highly secured and development
can be done easily we did not worry about ok you know the authentication part more
because of printing free works are providing good security otherwise there is lot
of time we will have to put to test the login feature for which we will have to
invite again a penetration testing team. Right? And from there again more loop
holes will be coming into project.

Right? That I am able to break डी login page by some doing you know SQL injection I
am able to do this, I am able to do that, some ethical hacking, मैंने depression
testing means ethical hacking. Are you understanding now security testing, that's
another name for it and that all we need to take care of it. But if I use building
library my job of worrying about these things is not there. Everybody agree.

Now because everybody agreed now, I will go here quickly ok to my product backlog.
I will go here quickly too my product back lock एंड इन the product back lock आई
will एंड up गिविंग year now आई will एंड up गिविंग year फॉर the first user story
point एस file like दिस यू will notice ए planning पोकर activity will have ए where
अलसो ए copy break point यू go something what will हैपन now when planning पोकर
activity happening आई एम अलसो लेट से experience डेवलपर दादर fellow इस अलसो
experience डेवलपर एंड when सी are talking about it there is a clash that has
happened between us now. Our thought process is not magic. There is properly and I
am totally disagree with them and I am getting irritated. I am totally getting
irritated because whatever is telling, I cannot agree to that and whatever I am
telling, must be, please irritated, we cannot agree to that.

So we have an option in planning focus activity. Directly pick the coffee card and
tell, I want a break, you can go out. Right, ok. So this this a kind of and
informal meeting हर everybody has got the right तू speak are you understanding
everybody opinion in डी team I am taking it that is what is happening in your
बैकलॉग ग्रूमिंग in your बैकलॉग ग्रूमिंग the first activity that I am doing is
planning focus activity are you understanding now? Yes then now we have your other
user story points that will be given right and that's how basically the user story
points will be given.

Are you understanding guys now everybody clear with this now ok नौ वंस सी पीपल have
वेट अहेड एंड ईस्टर्न फॉर ऑल over user story वंस सी have ड़न अन ऐस्टीमेशन फॉर ऑल
user story date दे date से डी ऐस्टीमेशन फॉर दिस इस 3 यू can सी डी planning पोकर
activity card हर right डी नंबरिंग हर इस 1 दें 3 दें 5 एंड दें 8 9 इस नॉट date 13
इसे date 20 इसे date 40 इसे date 100 इसे date right सो आई एम going तू give यू are
डी user story points based on date So 3 then 8 then I am giving 13 and that goes
on, ok? Then again for this work I am giving it as 3 like this firstly sort out the
user stories based on how much complexity The meaning of dynamic here is now the
back lock user stories can keep on getting added up as it when the customer comes
with new requirement Got it? The difference will keep on getting added up as it
when the test of the fight effect. Are you understanding now? Everyone how the
planning vocal activities are done and how the user story points are given.

Now some companies they go with, ok, instead of user story points they go with you
know t shirt sizing, extra small, small, large, extra large. पीस date related
साइजिंग आई have बेसिकली note work on date इन me company आई have उसे planning पोकर
activity card which वाज अन स्टैंडर्ड procedure इस दिस clear everyone नौ सो date
part वज never उसे by me नौ once basically the user story points is being given.
Product packlog is now ready with all the user stories. Now you define based on the
user stories the duration it will take to build that user story. Now this duration
is not again fixed every company the duration might vary some fellow might tell ok
for 3 user story point I will give you 0.5 days.

Some company will tell user story 3 point I will give you what day. Which means if
I pick this user story with 3 points, 1 day time is given for you to build. If I
pick the user story with 5 point, I will give you 2 days. You pick the user story
with 8 points, I will give you 4 days. Like this again they will calculate the
timing based on complexity.

Because जितना ज़्यादा complex होगा उतना ज़्यादा time लगेगा और जितना कम complex होगा
उतना कम time लगेगा. First maintain your product backlog like this, give the product
backlog, define the user story points after defineing the user story points now
page on the user stories. We can also arrive at what the estimate estimated type,
estimated type ok based on what User story points. Is this clear? Now once this is
done, the next thing comes in a child.

See, अजय is like microman, ok? It's not like basically you are managing all the
peoples together. Ajaile is a micromang. Business of managing 200 people at once,
it is better we will manage, we will manage small small teams and we will make them
all work on this project. So, what this agile further does if there is let's say 20
people working in your project.

I have a 20 people working in your project. So, a ji will split this team into a
size of size between 6 to 9, so first team size is 6, I cannot make it 5. Ok, as
per अजय I cannot make it 5, I cannot make it 10. अजय cannot have a deep size as per
10 that is a rule book of अजय. Again कम मेंस sometimes where दे don't have मच
proper आइडिया about it गलतियां करेंगे वो बोलेंगे एक में इसमें 10 लोग the 15 लोग the
ऐसा नहीं हो सकता है ए जाए purpose it self इस smaller team बटोर management ok डी
बिगर team डी management will go for doss I will not be able to track my employees I
will not be able to track the people correct?

So you can giving 6 people 14 people are remaining. So now further this 6 people
that I am talking about they are not just developer. 1 tester and there is 1 scrab
master, there is 1 Scrab master. Are you understanding now? Sir यह Scrab master कौन
है?

यह अचानक से कहां से आ गया? It's simple, Scrum masters are nothing but team lead.
Are you understanding now? जो team lead था, उसको sccrumaster बना दिया. तो team lead
who are working in a traditional way.

Sccrumasters are more working like facilitators. Team leads like authoritative.
Sccrumaster, facilitators. Sir, यह difference क्या है sir? देखो, authority means
see outside.

Ok? अब दिन हो रहा है. सूरज दिख रहा है? हां बोलना पड़ेगा. Because I am
authoritative.

मैं आपका team lead हूं. मैं जो बोलूंगा वहां बोलना पड़ेगा. Yes or no? Like पुष्पा
movie 2. अगर पीला shirt पहना हुआ है, तो पीला shirt पहना हुआ है.

ऐसा or no? सबको हां बोलना पड़ेगा authoritative. तो पुष्पा, अल्लू अर्जुन is
authoritative. Whatever is it that only has to happen. He is super authoritative
music team lead.

But facilitators, facilitators like I will do that work which will make my team
work easy. If somebody requires something I will provide that to them. If somebody
requires some help I will provide that help. Right? I have a point of contact to
help my team members do their work.

Are you understanding? I will not basically work in an authority way but I will
work as a facilitat about them. Did you understand? अगर facilitator होगा तभी तो
मज़ा आएगा ना? It's or not authoritative रहेगा तो?
Definitely मज़ा नहीं आएगा, facilitator यार तो किसी developer को कुछ problem है
definitely हम resolve करेंगे. So sccruma masters are coming with ए new rules और
देखो बोलने में सब ठीक है but actual में क्या होगा जो होना है वही होगा right समझे
क्या जो senior है senior की तरह ही behave करता है जो junior है junior की तरह ही
behave करेगा बोलने के लिए सब है but actually the rule book of एजेल दिस पार्टिकुलर
thing date डी scrab master are फैसिलिटेट ors and drnut ok like team reach वर
authority ok it is clear नो दिस line date आई एम speaking directly comes from डी
author of ajail जो मैंने almost बहुत सालों पहले पढ़ा था और जिसको हमने implement
करके फिर project में काम किया था but ultimately live environment में क्या होता है
मालूम है team lead आखिर team lead का रवैया दिखाई देगा. समझे गया? काम नहीं कर रहे
हो, holiday ले रहे हो तो directly बोलेगा भाई holiday नहीं मिलने वाली है. Sir मेरी
शादी है, नहीं मालूम.

Right? नहीं तो नहीं that's it. आपको काम करना पड़ेगा. Ok, अगर आप काम नहीं करोगे,
आपकी शादी हो जाएगी, मेरी टूट जाएगी. मेरी job चली जाएगी.

I mean to say this is clear everyone now? तो real environment different रहेगा भाई
but whatever in books is there is 1 part, but real environment में काफी सारी चीज़ें
mistakes करना चालू कर देते हैं. So now I I pop 1 team. What is the size of this
team now? 6 people, same way I will now build another team.

वैसे this is my club team 2. Now the club team 2 that I am talking about now, it
might have let's say 7 members, right? 7 members, 13. Like this 1 more scrum team I
will have, which will have another 7 members. So 7 plus 07:14, 14 plus the 6.

Now probably Ok? This is called ascrum team 2. Ok? Like this you might have
multiplescrum teams working in your project. You not have once club team,
multiplescrup teams.

यहां तक clear है? Everybody, तो अभी तक हमने क्या किया product बैकलॉग ready किया
product बैकलॉग में हमने कंपलेक्सिटी points दे दिया कंपलेक्सिटी points देने के लिए
हमने planning पोकर activity कर ली planning पोकर activity में डेवलपर्स test कर सकते
वहां पे कंपलेक्सिटी points decide कर दिया अब कंपलेक्सिटी points के base पर आपने
क्या किया? Estimated time आपने generate कर दिया. अब अपना product backlog ready हो
गया. अब हमें team form करना है जो product backlog से user stories को pick करेगा और
यहां से अजय process शुरू होता है.

समझे क्या? Which means instead of making 20 developers work together at once. I
will now build small small club teams and every scrum will come we have 1 head
master. समझे क्या यह head master कौन है यहां पर? Sccruma master, scrubma master को
सब संभालना है?

छह लोगों को, second scrubmaster को संभालना है, सात लोगों को. अब जब सात ही लोग हैं
और एक clubmaster है, सामने सामने दिख रहा है कौन क्या काम कर रहा है. Yes or no, कोई
छुट्टी भी लेगा तो immediately पता चल जाएगा. दो साल दो सौ लोग में कौन beach case में
भाग गया पता भी नहीं चलेगा, right? Login किया, logout किया चला भी गया.

अब मेरे को क्या तो पता चलेगा कि दो सौ लोग में कौन है कोई नहीं? Yes or no? Correct
but यहां पर जब छह ही लोग रहेंगे, immediately मैं catch कर लूंगा कि इसमें से कौन
आया, कौन नहीं आया? दिमाग में कम information रखना है, आसान है. Yes or no?

Agreed with this? Everyone online students, ok? So, देखो actually theory classes ना
बहुत ज़्यादा carefully आपको लेना है, Right? Because coding में कैसे हम करके समझा
सकते हैं but theory classes में क्या होता है कि यहां पर बहुत ज़्यादा complexity
build हो जाता है and अगर if you are process related things are not clear आप
scenario based questions में फंस जाओगे. There is clear?

Because यही चीज़ में होने वाला है. There will be backlog, there will be sprint
backlog, there will be sprint, there will be sprint, there will be a board which is
called as a कनपन charter earlier. On here they have prepared it as a board and in
the board you see the progress of the user stories. अगर यह सारा link करना है पहले
process समझना है कि यह features आपको जीरा में क्यों दिया गया? और जीरा में bug कैसे
report करते हैं?

Ok.