Until I was working at a company that followed an agile methodology, I thought it was a course where we had to do a proper study, and then we could apply it in a company, but I was also surprised when I joined a company where the agile methodology is followed. At that time, I realized that this is not a course where we need to learn something separately. Rather, it is a set of instructions or exercises on how to do daily work in a particular company.
Now, when you go to work in the morning, how are tickets assigned to you? And how you update them and get feedback for them, all these things come under agile methodology, which has nothing to do with any courses, but there are many terms used that you should be aware of. Whenever an interviewer asks if you have any idea about agile methodology, they expect you to know many terms because they think you must have heard about these terms.
What is agile methodology?
So it is just a process or a set of practices that explains how software is developed. Suppose you are developing purely customer-centric software. Where you are giving them regular updates and getting feedback from them and according to the feedback you are making necessary changes, when you follow such a process it is called an agile methodology. Where the requirement is not constant, it can change at any stage, hence it is called agile methodology. But if you just give such a short answer to the interviewer, then it is not enough; you should be aware of the terminology, about what you use in agile methodology.
Sprint
A sprint is just a cycle, or you can say a time interval, which is the amount of work that needs to be done in a particular time. The time interval to complete the amount of work is known as a sprint. Usually, in most companies sprint is of two weeks, which is equal to one sprint. But according to the company or according to the project, these things keep varying. Sometimes it goes up to 3 weeks, but in most companies, two weeks is equal to one sprint.
Sprint planning meeting
So, as I told you about the sprint, which is of 2 or 3 weeks, to discuss the necessary work to be done in that time frame, a meeting is scheduled, which is called the sprint planning meeting, where you explain all the things, like what will be done in that sprint, and all such things are decided.
PI planning
Which means planning the program increment now, if I compare it to a sprint, then the bigger version of a sprint can be called PI. A sprint is of 2 weeks, while a PI is of a quarter, which is 1 quarter of a year. 1 PI will be counted, and the second quarter will be counted as the second PI. So, this way, you can make a PI plan. About all the things that need to be delivered in a particular quarter, and according to that, you can divide your project parts. This way, you can make PI planning. Now consider there are generally four PIs in a year, with 6 springs under it. But this thing can vary according to the company. This is the main difference between PI planning and sprint planning. PI planning is done across all teams, whereas sprint planning is done among team members, which you should know about.
Daily stand-up meeting
So, in this meeting, ng you basically need to share what you did yesterday and what you are going to do today. All the updates related to your work need to be shared in this meeting. And a scrum master is created separately to lead this meeting. And apart from that, hat all the developers and producers or leads all join to get the updates. This meeting is usually held in the morning so that everyone can get all the updates. And apart from that, if you have any doubts, then you can discuss them in this meeting. But in some companies, es this meeting is also held in the evening.
Sprint retrospective meeting
Which is done at the end, when your sprint is over? This meeting is held where you have to tell what good things you did in the period, or what bad things you did. Usually, in this meeting, all the points need to be discussed. So that you can improve them in the future.
Story points
The main purpose of story points is to define the time required for a particular task.
That is, consider whether you have a task that will require one story or two stories for it. Now a story point can be in terms of a day or hours. This depends on the company you are working for. In many places,s one story is counted as a day, ay and in many places,ces two stories are counted as a day.
Epic
Now, if I compare Epic to a story,y then Epic is a big part of stories.
Which cannot be completed spring sas aske we have watched it is very big, which cannot be closed in a particular sprint, so such work is divided into specific stories so that we can start working on it.
Scrum master
Therefore, the person who is taking the lead in any particular sprint or sprint planning is called the Scrum Master. He has the proper responsibility to monitor the stories of each individual and take appropriate updates from them, and if anyone is facing any difficulty them accordingly.
Zero sprints
This is a term that can be used before the first sprint. This is all the time before the first sprint to do any kind of pre-planning. Such a special interval is called sprint zero.
Spike
Spike is a term used when you don’t have a clear definition of the requirement. Due to which you can’t give them a proper deadline, either you can’t estimate the time required to complete a task, or you create separate stories,s which are called spikes. Which is used for your purposes. This is when you need to do some research, ch and it takes some time, and even after that, hat you can’t decide whether you will get to the end or not. So when you don’t have a proper definition for a task, then separate carecreated,eated which are called spikes.
Velocity
So the main purpose of velocity is to measure the amount of work done by a particular team in a sprint. So it is used to measure the speed of this thing. So these are the terms used in agile methodology. So whenever an interviewer asks you about agile methodology. Then they expect you to be familiar with all these terms.