Business Analysis Full Course 2026 [FREE] | Business Analytics Tutorial For Beginnners | Simplilearn

Key Takeaways

Hey everyone, welcome to this course on business analysis. Now today, organizations do not just need ideas. They need the right people who can identify business needs, work with stakeholders, define requirements clearly and recommend solutions that create real value. And that is exactly why business analysis has become so important skill. And for professionals who want to grow in this field, CBAP is one of the most recognized certification that shows strong knowledge of business analysis practices and frameworks. So in this course, you will be learning the key concepts of business analysis based on the Babok guide V3 framework where we will be covering the core knowledge areas, important techniques, exam related concept and practical applications used by business analyst in real projects. So whether you are preparing for the CBA exam or simply want to strengthen your business analysis understanding, this course will give you a solid foundation. Let's look at the agenda. First, we'll understand the CBAP certification including the exam structure, eligibility, application process, and course requirements. Next, we'll be exploring the fundamentals of business analysis, including the BACCM model, the six Babok knowledge areas. Next we'll move into key areas like planning, monitoring, elicitation, collaboration, strategy analysis and requirements. After that we will cover important business analysis techniques like brainstorming, interview, SWAT analysis, root cause analysis and many more. And finally we will look at real world case studies and project work that will help you apply these concepts in a very practical way. Also, if you are interested in boosting your career in business analysis, do not forget to check out our AI powered business analyst course. Now, this course is perfect for professionals who are looking to enhance their skills with the latest tools like PowerBI, Excel, SQL, all while gaining hands-on experience with real world projects. Also, you'll be learning how to leverage generative AI for smarter, faster decision-m. Our program is IBA babok V3 aligned and it will help you prepare for certifications like CBA CCBA where you will engage with 10 plus industry projects, 40 plus practical activities and benefit from live online sessions led by experts. Plus with simply learns job assist you will be getting the support you need to land your next big role. So what are you waiting for? Hurry up and enroll now. The courseing is mentioned below. So before we get started here's a quick quiz question. Which of the following is one of the six core concepts in the BACCM model? Your options are budget, context, coding or marketing. Let me know your answers in the comment section below. >> So let's start with the first topic for the day. Let's discuss what is business analysis. You all can see here 71% of the failed software projects are traced to poor requirements globally. What do you all think is the main major reason behind this huge percentage? Just look at this percentage. Only 29% is a success rate. just 29%. The main reason is assumptions, emotions and other aspects those should not be part of your analysis work. Analysis should be purely based on the factual evidences. Analysis should be based on your research, exploration, investigation and there's no scope of assumption when we are doing our analysis. Imagine imagine if I ask this question that why 45y old woman sati says I have done the historical analysis. I know that this woman is a CEO of this company. She has got ample of experience. This boy is still in school. So my preference is this woman. But was that information given in the case study? No. So here you should all should have asked this question that we need more information more information with regard to what exactly is the benefit why we have to explain this more information regarding their educational qualification their background what they are doing currently. So meaning to say it's an important thing to understand the business needs get a stronghold over the existing behavior. Understand the context that is what context we're trying to bring about the change. understand the existing behavior, functionalities, processes, infrastructure and all such things would then help you come up with the solution. Most of you were coming up with the solution based on assumptions with no factual evidences to support your argument. And that's the first thing that we need to inculcate. We need to start working in or we may say start to accept that it's an important thing for us to collect the factual evidences first. Second point you all can see here on your screen everyone 40% of the effort in an average software project is in fixing errors. Why do you think why do you all think we have errors in any project? What's the main root cause of the errors in any project? What's the main reason of issues or defects in any project? Assumptions, incomplete analysis. Yes. You don't understand the business needs. Yes. You you have not gathered all the required information and you jump to the solution. No proper testing is blaming testers and saying BA is the perfect person but testers are causing the problems. Yes. But testers are dependent on you for the requirements. If your requirements are not cleared then you cannot blame the testers. Yes. So don't blame testers. put the blame on the VA first and then the testers. Yes. Okay. Requirement is half cooked. Improper testing and documentation leads to all such things. Yes. And you all can see here requirements defects and is saying that sometimes change in the business requirements is also a reason. So in a way you try to blame the business users for this thing. It is one of the factor. Yes. But you you would agree with me Ariola and others. This is something beyond our control to to make uh those those things like like if business keeps on changing the things there's something that we can restrict but some few things are beyond our control. But the thing that's in our control is to do proper detailed analysis, gain proper understanding of the requirements, understand the business needs, maybe then your business users will not come up with um additional requirements more frequently. Maybe you'll be able to win their trust. Yes. So if you're more organized, if you're more structured in your analysis, if you're able to win the trust of your business users, you may find even the improvement at their end as well. That happens. I've seen this thing. I've experienced this in my projects that if you are not organized, they're also not organized. They mean the business users. But if you are coming with more structured approach, even they're also more structured accordingly. Yes. So in our live sessions everyone we will talk about some standard set of practices. We will talk about few important tools and technologies. Few important techniques. Those may help you improve on business analysis capabilities. Those will help you provide a complete solution in accordance with the given set of business requirements. Doing the analysis such a manner that you're able to provide an end toend solution end to end solution would help you solve the business problems make them realize benefits and the solution would be regarded as a valuable solution a sustainable solution usable for the purpose. So all such things we'll discuss in detail in our live session. Business analysis body of knowledge we'll discuss in detail from chapter number 10 till the last chapter. 50 techniques, 30 important tasks, six knowledge areas, six underlying competencies. These all would help us come up with a very organized approach. Use some standardized templates, sort of important modeling notations. those will help us come up with a better solution a complete solution for the year business problems. So this is the first thing to start with everyone and this was about having these W's on your screen. W's means you are asking questions to gain more clarity, gain more and more information. you are able to draw out, explore, identify the information that is relevant to the change and that's the purpose of having these W's here. But if you observe here, there is one very important W missing here. This is known as five WH criteria. But one W is missing. Which W is missing everyone? Who and who represents? who represents your stakeholders. So we will talk about the stakeholders. Yes, not only the business users. Business users are part of the stakeholder group. The stakeholders can also include your technical experts, your quality experts and others. Okay. So we will talk about the stakeholders as who in detail. how to capture the stakeholder requirements and how stakeholder requirements act as a strong bridge in between the business requirements and the solution requirements. So this was about everyone the five five WH criteria. The next thing on your screen everyone is you all can see here one maroon color or you can say red color lens on your screen. What do you all think is a use of this lens when you're doing your analysis? Why at all we have this lens here? Derra is saying get into the groove of the things deep dive. Okay, I'll take you all back to your eighth standard physics or science subject. Eight standard science. If I talk about any lens, what are the two important characteristics or properties of any lens? Some of you will be thinking, are we in an analysis session or science session? Yes. No. No. I'm asking about the two characteristics. One is one is the magnification magnifier. Another name for it is magnifier. zoom in and zoom out. Another thing is focus. What you are mentioning here is something linked with magnification to dwell deeper to bring in more transparency. Nobody's talking about this another feature that is focus. Focus on what? Focus. Everyone should be purely 100% on the requirements with no with no implementation biasness. Everyone no implementation biasness simply means you are into a lasting role. Yes, you are focusing as Malik is mentioning on the solution and the needs and you are not influenced you're not influenced by a particular stakeholder group. You are a neutral observer bridging the gap amongst all the stakeholders. You're focusing on the solution. You are trying to come up with a complete solution in accordance with business needs with no implementation biasedness. Sometimes what happens is generally BAS come from the technology background or technofunctional background. So they are more inclined. We have to cons I'm not saying that we don't have to consider it. You have to talk to them. You have to understand the ambiguities and their challenges. But at the same time that won't be a compromise with the system or solution quality. I'm not saying that you won't consider their request. You you will turn a def to what they are saying. The only thing is their suggestions, their recommendations should not cause any compromise with the solution quality. Okay. Their solution should make your solution align with the technology but not any compromise with the solution or the you may say components of the solutions discuss very important thing to start with and that is 5W and this processcentric lens I'll summarize what we have discussed so far so we have started with a discussion wherein I mentioned that for any BA it's an important thing to perform research exploration investigation apply 5W analysis with with minimal scope of assumption no assumption your business analysis go that she is she is old so she has experience somebody is new so he won't be able to do the things. No, it's all about your analysis results, your evidences. Those help you take a better decision. Second thing is this processcentric lens. This lens would help you dig deeper into the given problem. Break down the complex requirement of smaller fragments. Do the analysis more atomic level. And when you're doing your detailed analysis, you have to talk to different people and you have to focus on the objectives when you talk to them and not get influenced by them. If you get influenced by them, if you are inclined towards some stakeholder group that may lead to a solution that is implementation biased or business users biased unbiasedness may lead to several errors or issues. So this was about the five WH. So so W is missing here. The the purposes to make you all think and ask such questions. Okay everyone, I hope everybody's with me till this point. 5W and the processcentric lens. Shall we move on and talk about defining needs everyone? Next thing is everyone defining needs. Now when we talk about needs everyone needs can be in the form of problems to be solved or needs can also be in the form of opportunities to grow. So it's about doing your detailed analysis to a processcentric lens defining needs recommending solutions that enables change and this change helps in continuous improvement. Let's take one example everyone to understand what are the enablers and why enablers are so important how they help you bring about the change law and others. For example, if I say the current state or the as state is I'm talking about the uni liver project one example from the univer project current state is that the uni liver employees they're going to the cafeteria to have lunch or to have food. This is the current state and the future state or the change is that you have your mobile phone, you have your cell phone, your smartphone and you're having one app there as canteen ordering system and you're ordering a meal online. Imagine law if you are a BA imagine a business analyst and you have to ensure that nobody is going to the cafeteria and everybody is using this canteen ordering system app to order the food. How you'll enable this change? What are the necessary steps? Those may help you ensure that people accept this change. Employees are ordering the food online and nobody is going to the cafeteria to have food. How you'll enable this change everyone? One of my learner in one of my morning batch in the hours had to say that shut down the cafeteria and they have no other option than to go and order the food online. Is this enabler to shut down the cafeteria? Are we in the Hitler's era? Yes. No, we're not in the Hitler era. We not in 1930s and 40s. um by giving discounts offers and you all would agree with me. This may also include proper training. You have to train your employees how to use it. Yes, training, mentoring, use uh usability aspects a good application to use and offers discounts. Yes. And and lawyer very good point that take a tally of those that prefer eating in canteen and come up with certain important offers for them so that it it it it encourages them to use the new app. Yes. So enablers everyone are all those important transition requirements is saying is admin allowed to eat food at the workplace. So that may be part of the policy you may come up with certain important policies. Yes. So that may be the details around your solution requirements loyalty promotions. So in a way everyone I can understand now that you all are very very clear with this topic here. Enablers enablers are all those important transition requirements those may help you those may help your organization transition to a new future state without any glitch. It's a hassle-free and a smooth transition to a new future state. We all need more examples to understand this thing. Let's take one more example or two more examples. We all have witnessed the coid9 crisis. Yes. If I talk about the coid9 example, everyone most of us were working from office. Yes. But during the coid9 crisis, what happened? Was that possible to work from office? No. So there was a change and the change was work from home. This became very popular all across the world. Yes. Since they learned from different geographies, this happened everywhere. Work from home. What was the biggest enabler here everyone? What was the biggest enabler that helped us transition to this new future state project and others? What was the biggest enabler? The biggest enabler was the internet. The biggest enabler was the assets like laptops allocated to everyone. Yes. And even few companies I don't know about others but in my company they provide a reimbursement to purchase the table chair and everything even even for the pen and copy that we use for everything we got the reimbursement I don't know how many of you got the reimbursement for tables and chairs yes so table chair yes they are giving us some bottles and everything to laptop and everything so what are these important things bills Yes. And this is part of everyone business continuity plan. Yes. Business continuity plan. You can see here this was the business continuity plan. Everyone and before the covid-19 crisis when we used to have business continuity plan training sessions people used to laugh. People had never imagined that this these things may happen but disaster recovery is a very important thing. So you can see here this is one enabler. Enabler is all those important things those may help you have a successful hassle-free transition to the new future state. I'll take one more example of the enabler so that it makes so what we have discussed here everyone that business analysis is about research exploration investigation with the help of 5W analysis. This research should be deep detailed. You have to dig deeper into the given problem. Get into the groove of the problem with the help of a process ccentric lens. Processcentric lens signifies here that we are going to focus on the business objectives without any implementation biasedness without having inclination towards any solution delivery team. We are having a discussion. We are acting as a strong bridge in between the business users and the technology experts. This will then help us define needs. Needs are needs are the form of problems or the opportunities to be solved. This will then help us once we understand the needs we can then recommend the solution based upon different types of analysis like feasibility gap, risk, impact, financial and other types of analysis. Once we arrive at a solution, the solution would help us then bring about a change with the help of enablers. Enablers are all those transition requirements. Those may help us have a hasslefree and a smooth transition to a new future state. And this change when we are bringing in this change will help us in continuous improvements with minimal number of defects since we have applied a structured and organized approach. So this is what we have discussed first topic everyone. Now we have to start with the next topic that is who is a business analyst. Let me share with you all one very important link and I get this thing from people here that when I search something on Google, Google says something else. So if you have any doubt everyone or if you have any difficult to understand don't search on Google search on bat times.com don't know how many of you know about this web application bat times.com especially people who are new to the analysis world I request everyone to please click on this link and confirm is everybody able to access this link batypes.com please check can confirm you can give me a thumbs up if you're able to access this link. B times.com everyone is a very good and a reliable resource for any business analyst. You all can see here there are a lot of articles for you all to read. There are a lot of templates that you all can use in your projects. There a lot of events, webinar, conferences, communities, booktore. You may find a book from your trainer in few months. I'm pushing them to add my book as well resources. Now next time if you have certain questions or if you're not clear with something just search it here. The reason why I'm asking you all not to search on Google is because Google is fetching information from reliable as well as some resources those are not at all reliable. I can tell you this thing even this thing happens with chat GPT as well. people search something on chart GPD and they said in charge GP I found this thing and this is contradicting towards in the Babok guide. So it's an important thing that you look at the reliable sources, the relevant sources, the valuable sources and don't pick in the garbage from the internet. So I request you all and especially everyone people who are new to the analysis world if you all can take out some time from watching those irrelevant reals just spend 15 to 20 minutes daily going through this application. Yes spend 20 25 minutes 15 minutes going through this the way you read newspapers. This is a newspaper for a VA and I can tell you within two to three months you'll analyze you'll realize that you know so many things in the business analysis world you have so many things to talk about in the business analysis world. So make an effective use of this thing. If you find something difficult to understand you can search it here and you'll find so many good articles from so many good people all across the globe. Yes. So this is straight from the horse's mouth. This is something that IABA acknowledges and IABA recommends even I'm recommending this thing as a senior trainer. So make an effective use of ba times.com who is a business analyst. Now here you all can see here different color bubbles here. We'll focus on this third one first and we'll talk about the most important thing that is requirements. Elicitation elicits the needs from the key stakeholders performs the elicitation. Now let's talk about requirements solicitation in detail. Let's see what is requirements elicitation how it is carried out what's the practical significance behind it and I'll share with you all one story now that story is something very much linked with your requirements recitation so let's listen to this story and see how many of you are able to tell me the moral of this story is now everyone before I share that story with you all we are talking about the who is a business analyst and there is some very basic thing that I want to start with and discuss with you all before we before I narrate that story to you all the topic is the important discussion item is very basic thing one thing is responsibility another thing is accountability very popular in any project. Responsible stakeholders, accountable stakeholders. What do you all think? Especially people who are new to the analysis world is a major difference between a responsible person and an accountable person or do you all think it is one and the same thing. So the first topic is we are talking about who is a business analyst and here it's an important thing for us to know the responsibility and how it is different from accountability. So let's talk about the responsibility versus accountability. Everyone as for the Babok guide responsibility can be defined as a sole ownership that is a responsible stakeholder will perform the assigned task directly. It means owning the task, working on it and ensuring the completeness of the given task. Responsible person is regarded as carrying some as somebody who's carrying the cross on his shoulders. That is you are doing the execution, you are the owner and directly working on the task. Like BA is responsible to perform requirements gathering. BA is responsible to perform 5W. Accountability can be defined as it is about the peripheral involvement. What is peripheral involvement everyone? You are not doing the things but you ensure that the things are done in appropriate manner. You are tracking, monitoring and performing the evaluation. Accountability also includes providing a better environment wherein responsible stakeholders can work effectively and come up with required outputs. But ideally it will be a good practice if somebody else is accountable so that you can cross check verify and come up with better quality deliverables. That's the difference between everyone responsibility versus accountability. So in simple terms somebody is doing the things he is responsible for those things. Somebody is tracking monitoring evaluating providing better environment. At the end he or she is answerable for those things that may seem accountable. Now let's talk about since we're clear with responsibility versus accountability. Now let's focus on this topic everyone and that is who is a business analyst. And here we'll talk about the responsibilities of the business analyst. We'll talk about the responsibility and one of the major responsibility what I think Shivangi you are mentioning few minutes back gathering the requirements doing the analysis and that is something linked with requirements elicitation let's see what is requirements elicitation how it is carried out with the help of one example and this example is from a very popular book I don't know how many of you have read this book how If you have heard of this book, I was fan of this book. I used to read this book a lot during my school days. And the name of this book is Arabian Nights. Yes. People from the Gulf countries from the oil rich nations can easily relate with this book Arabian Nights. Yes. And the good thing with this book is there are lots of stories. Those may inspire you. Yes. to work efficiently as a business analyst. So in this book there was one story there was one story that can be that can be easily linked with requirements elicitation. So let me narrate that story to you all and then I'll ask you all the moral of this story. Yes everyone. So in those days in that part of the road I'm talking about the Arabian road. There used to be one Khalifa. I'll just use the common terminology as king. Although king is not equivalent to Khalifa but one king I'll say okay there was one king and he had three detectives. Three detectives their names were Arabic but I'll just make it simple for you all as D1, D2 and D3. These detectives can be considered as a modernday business analyst and these detectives were gathering requirements for this king. They were having some very good experience. They were providing some very valuable information to the king. This helped this Khalifa this king to run his kingdom in a very proper manner understanding the concerns of people of his country and all such things. One fine day, D1 and D2 got to know through some sources that D3 is getting much higher salary, much better compensation and above all they realized that he's getting huge respect in the eyes of the king. Now D1 and D2 were not happy with this thing because they had similar work experience similar ways of working 24 + 7 for the king. So D1 tried to express his anguish. He wanted to clarify these things with the king. So he tried to reach out to the king and he was about to ask these questions. But king was a very smart person. He knew that Diva is going to come up with such questions. So King said before you ask your questions, I have one important task for you. Would you be able to accomplish this task? Would you be able to complete this activity that I'm going to assign to you? Now this time prestige issue that whatever task he's going to assign it to me, I'll come up with the best possible result. So king shares with him a scenario. King says that as you know D1 that we are kingdom K1 surrounded by kingdom K2 and K3. He said yes definitely yes. He said we got to know that few vagabonds have entered into our kingdom from K2 side. There are few vagabonds here. I wanted you to do some analysis. I want you to help me know who are these vagabonds, why they in our kingdom and come up with all the details around these vagabonds. D1 that I'll do this thing right away. I'll share with you the information in a minimal time. D1 went to that place tried to locate and identify the vagabonds within few hours he was able to locate them. He then had discussion with those vagabonds tried to get more information that why they are entering into this kingdom. what they are doing here. He also discussion with people around and he also tried to understand whether people know more about them or not. So Dan had a discussion with the vagabonds. He had also discussion with people around the citizens of the country and he came back with some information. King said, "Do you have the information?" He says, "Yes, king. These are few vagabonds passing by our kingdom and they're going to kingdom K3. He said why they going to kingdom K3? He said because they're going to they're going to attend one marriage ceremony. So king said that how much time do you think they'll require to come back? They said within one month within one week they'll come back and they'll go back to their original country K2. King said how many men, how many women are they carrying any instrument at my house? D said I never inquired up to that level. I just know that these are the bags. They're going to attend somebody and come back within one one week's time. So king asked D1 to stand behind the cords. Then D2 came in. D2 also had same set of questions for the king and king assigned the same task to D2 as well. Now D2 went to that place had discussion with these vagabonds had discussion with people around and D2 came up with a lot of information as compared to D1. Kim was asking several questions. D1 D2 was answering all of them. D2 said yes these are few vagabonds passing by our kingdom. They are very jolly nature. They are singing songs. People loving their company. These many men, these many women, they don't have any instrument at Mahamas. They're going to go to kingdom K3 come back and all such details in a very detailed manner. He was sharing with the king and king was also so happy to gain these many details from D2. But then all of a sudden D3 comes in. D3 was not looking comfortable. D3 had a fearsome face. D3 was in a hurry to share something with king. So D3 D3 said please stop that and they don't share this and bull stories with the king. This is not going to help us. I have some very urgent thing to share with king. Now king was not happy with this attitude because king and d2 were having very good discussion. So king said is that really very urgent. D3 says yes that's why I'm stopped in middle. My apologies for that. But I need a very quick discussion with you, a very urgent discussion with you. King asked D2 to stop for a while and say since he had a huge respect for D3, he said, "Yes, please. You may go ahead. I'll share the detail." King when he was having a discussion with D3, D3 comes up with very surprising statements. D3 says that King I was listening to what D2 was mentioning. These are not Vega bonds. And this surprised everyone. D1 as well as D2 as well. Then king said then then who are these people? D3 said these are enemies disguised as vagabonds. They are around 15 to 28 at present. But thousands of them as per my analysis as per my experiments hidden trials I know there are thousands of them hiding behind the bushes in the countryside here. These people are locating our important army positions. These people are trying to understand the different things that they're doing here. creating and defining some strategy and these people waiting for this instruction from these people and they may attack our kingdom at any point of time. So instead of listening to this and bull stories it's an important thing for us to alert our army catch hold of these vagabonds and then come up with a strategy to win the war against these people here. King listens to D3. He comes up the proper strategy and eventually they are able to win the war and then again come up the stabilized kingdom and story goes on from there. My question to you all is what do you all think was a difference between the analysis that D3 has performed as compared to D1 and D2. law is saying D1 and D2 are getting less salary. Less salary means less work. Yes, that's not a right thing to say. I think it's a writer note. But my question to you all is what is the moral of the story law? Why do you think D3 was able to come up with a better solution? How D3 was able to say that these are enemies and why D2 were not able to predict this thing? Understand the problem. If you see here everyone, you are missing one very important thing. You're missing one very important thing that I have discussed in this story here. Maybe you are like mesmerized by the Arabian Knights. Let me make it very clear. D1 and D2 their analysis was focused completely was dependent. Everyone if you all agree with me in the story we just listened to just that we have discussed D1 and D2 their analysis were completely dependent upon the information that they have gathered from Vega bonds and people around can you depend 100% on your stakeholders for the information the stakeholders may not know about the information. Yes or no? They are own they're your own people but they don't know whether these are vagabonds or enemies disguised as vagabonds. But if you look at D3, D3 is performing requirements elicitation. He is talking to people but along with that he's also doing his own research. He's also performing certain experiments. So moral of the story is it's an important thing. It's an important thing for a business analyst to perform requirements elicitation with the help of these three important pillars. Let's discuss the moral of the story now with the help of what they answer is everyone. Among the stories to draw out, explore and identify the information that is relevant to the change. Business analyst should focus upon three things. collaboration that DA and D2 did. They both collaborated with people around in Vega bonds. But along with that, we also have to do our own research. Look at the historically available information. Look at the existing information. Try to do some data analysis. Try to do some exploration. and also perform experiments like hidden trials, prototyping when we are doing all these three things then it is requirements elicitation and this will help you gain clarity around the requirements and then you'll be able to come up with a better solution. So moral of the story is that every BA must cry. Raf next time you get the requirement start crying and then if your manager says why you are crying then tell him that in the CBA certification program the trainer was telling us to cry when you get the requirements. Crime means collaboration, research and experiments would help you perform requirements elicitation in a very organized manner. For example, let's take one more example. Let us suppose I say Vijendra we have with us. We have Rafael with us. Rafael and Vijendra maintain 100% attendance in the live session. Is this good enough for them to become a certified analyst? Is this just enough if you collaborate with me? No, you have to go through the Baba guide. You have to go through the class notes. You have to spend some time going through bat times.com. This is all your research. Go through the bat times.com. Read the articles. Go through the Babok guide. Do not completely rely on what you're getting from the trainer. Complete reliance may bring you to the same level as D1 and D2. But if you want to become a certified analyst like D3, you have to dig deeper into the Babok guide. Go through the class notes, work on your projects on your own, not copy the projects. Those are already there in your drive link. Yes. So requirement solicitation depends on three pillars. That was the moral of the story here. Collaboration, research and experiment. Now experiments we'll discuss in detail with the help of some tools. We'll install and we'll we'll talk about some important tools that may help us create prototypes and also perform internals. Moral of the story is every BA must cry. Okay. When you just focus on collaboration, you are gathering the requirements. Sometimes they ask you this question in your job interviews that what's the difference between requirements gathering and requirements elicitation. Would you be able to answer such question if they ask you in the job interviews that what's the difference between requirements gathering and requirements elicitation? Requirements gathering primarily focuses upon a detailed discussion and engagement with your key stakeholders. But requirement solicitation encourage BA to not only collaborate but also do your own research and perform experiments to arrive at a better set of requirements and their corresponding solution. That's the moral of the story everyone. Are you able to understand now what is requirement solicitation? Yes. So this is the moral of the story. You all have to remember C R E collaborate, research and perform experiments. Okay. So we have discussed about the requirements elicitation everyone. What we have discussed today as part of elicitation is just as just the uh basic discussion. We have a separate knowledge area chapter number four is specific very very specific to this what we discussed today. So how to cry loud we'll discuss here we'll cry here loudly here we'll cry here the very detailed manner. So here you'll find all about crying in detail. Yes. So it's better to say that BA should perform requirement solicitation. Yes. requirements. So let me add a red heart to this. So shi is given a very good point. So I'll not say it's better to say it's better to practice requirement solicitation. Yes, if you'll just say it won't help. You have to practice this thing as a BA. Requirements gathering alone won't help you gather the requirements. It's good. Gathering the information is good thing. I'm not saying I'm not I'm not against you having a discussion the stakeholders you talk to them. is good but 100% dependency reliance on what you get from the stakeholders is not a good thing. Cross validate do the research perform experiments yes because you cannot assume that what they are getting from the stakeholders is 100% accurate. So so that's the moral of the story the requirements of the key stakeholders. The next thing is everyone discover, synthesize, analyze the information, investigate and clarify stakeholders desires, determine issues and their causes. Last point here one is last point is performs the tasks defined in the web guide. Our next topic, we won't be able to finish this topic today, but yes, we'll start with this topic today. The topic is stakeholders. The stakeholders as we had discussed today in the first half on high level stakeholders can be defined as an individual or a group that is directly or indirectly impacted by the need change or the solution. BA is going to talk to them, interact with them directly, indirectly. And you all can see here everyone. There are few blue faces, happy faces. There are few orange or you may say pale yellow faces, lethargic, tired faces. These all are the stakeholders. Yes, perfect. This is a good answer. Thank you. These are external. These are the external ones. The blue faces are the external ones. These are the internal ones. But my next question to you all is when we say internal or external, these are the relative terms. My question is external to what? Internal to what? The correct answer is solution delivery. People who are directly involved in developing a solution, people who are directly involved in creating a product. These all are these tired faces. That's why these are tired faces because they are working day and night. They are the ones who are developing a solution. And why these are happy faces? Because these are the beneficiaries. They are the ones who are going to realize benefit. They are the ones who are going to use the solution. They are the ones who are external to it. they are the ones who are not involved in directly developing this product. So these are the internal these are these are the external these are the internal and the reference point is the solution delivery. Why not organization? organization would be the correct answer if you're just focusing upon the IT service industry. But don't you all think nowadays so many companies have their own capital units. It may be that you are working on some in-house product. It's not always that your IT team is your service provider. IT team may also be part of your organization as well. Yes or no? That's why I said organization is not the point of difference. The reference point is the solution delivery not the organization. Okay everyone with me on this thing? Yes. Let's start with our discussion now and let's discuss about these important stakeholders. First a very popular one very common question that I get from the learners is that what's the difference between the customer and the end user or these are one and the same thing. Let's discuss this thing with the help of few examples to understand the difference between the two. Who is a customer? Who is the end user for the internal team and what's the major difference between the two? Okay. So let me take you all your projects. Project number one it is canteen ordering system for unilo. Ahmed and everyone else in this project can order system for uni liver who is the customer for the solution delivery team and who is the end user. Uni liver as an organization is paying for it. They have the legal rights. They are the ones who are owning this product. So, Uni Leo is the customer. Whilst these 1500 employees till the time they are part of Uni Leo, they're able to access this application. They're using it. They're using it. They're operating it. So, they are their users. Similarly, if I talk about MARI and others library management system for the Stanford University, library management system for the Stanford. Here Stanford University as an organization as an as educational institution is acting as the customer for the development team because Stanford University has the legal rights has the moral rights they have purchased or they are paying for this product but who is using it students alumni faculty or staff these all are the end users. If I talk about WhatsApp pay, WhatsApp pay is owned by the company Meta or the Facebook. But who is the end user? You and me who are using this WhatsApp pay are the end users. Hospital management system for Mayo Clinic. Here the Mayo Clinic is the customer having all those legal rights whilst the medical staff, the patients, the doctors, the nurses and everyone else those all would be the end users. So this was the main difference between the two. Now one of our learner is coming up with a very good question here that in some cases customer may also act as the end user. When customer himself or herself start using the product then he or she becomes the end user. For example, for example, I'll take a very simple example. Let us suppose there's one company Ford. Yes, Ford. And can anybody help me know what was the main business model Ford? Why Ford as a company became so popular in US first? What was their business model? Business model was to come up with cheap cars. Cheap in the sense with very low prices. Yes. the the the cars with low prices as compared to companies like you may say BMW or Mercedes and others they came up with the business model to produce and manufacture the cars with lesser rates so that it's easily affordable to a common person that's why it became so popular in US first and then different parts of the world so food if I talk about food as a company and if I say Today I Isa or Pavi they pay for this car and they become the owner for it. Yes. Isa and Pavi are sitting on the back seat and there's one driver driving it. Then Issha and Pavi are the customer for Ford and this driver is the end user. But there's no driver in this car and Issha and Pavi are themselves driving this car then Issha is customer as well as the end user for food. Are you able to understand this example when in which all cases customers also acting as end user? So somebody's paying for it and they're also using it. Then in such cases customer is uh customer is equivalent to the end user but in most of the case it happens that end customer is purchasing it while somebody else is using it. Yes. So that's about the customer and the end user. Everybody with me on this thing or loving this thing? Yes. Now, now let's talk about let's talk about the last topic for the day and one last story to share with you all and that's related to regulators. Since there are so many learners here joining from the North American region, so many people here from USA and Canada here. So I'll share one story from 20 years back. I'll take you all back to the year 200 7 and 8. 2007 and 8 everyone or I can include nine as well. These three years are considered to be bad for the business all across the globe. This was a period of great recession. Yes, great recession. And can anybody help me know what happened in US in 2008 and 9 that was the major reason for the recession. Yes, it's also known as the subprime crisis. The subprime crisis or as Vijend is mentioning here the Lehman brothers collapse. What was the main reason everyone behind the layman brothers collapse especially people are joining here from US. I was part of one of the Europe European bank then and we had a very strong relationship with this financial institution. Yes. How's the market bubble somebody's talking about? Yes. What is this housing market bubble everyone? What happened everyone? I'll just make it very short since we're into last 50 minutes. layman in those days in that part of the world I'm talking about the North American world real estate business was at its peak most of the people all across the world were planning to settle in US was considered to be a heaven for people to live and there was a mad race to leave their native nation and go to US and settle And what happened because of this and and and also US government opened the doors for everyone that you all can come here invest and live here especially the skilled people. As a result of that there was a huge you may say exponential rise the real estate market and layman bidor thought of making a lot of investments in the real estate business and they had huge investment in the real estate business due to some reasons due to their some of their bad decisions you may say or some market speculations they started to like lose the trust of their investor tors people were not only people but the corporates the companies started to withdraw their investments from this financial institution even in my bank wherein I was working as an operational you may say somebody is into business operations as a very you may say new person in the corporate world we witnessed that all of the people were like all the banks were willing to withdraw the investment from this lemon brothers As a result, what happened was they were short of you may say funds and I'll use one term from the banking word liquidity. Liquidity was causing problems. They never had cash or cash equivalents to return to their investors. As a result, what happened was they started to sell their properties, their investments in real estate business. And then what happened when they started to sell the things there was a subsequent haircut in the real estate business. What is a haircut? What's the meaning of haircut in the real estate business everyone? Haircut simply means when there is a significant drop in the prices of the real estate properties because somebody is selling it on a massive scale. Now what happened was they were selling the things they not getting the actual price of what they had invested as a result they were not able to clear the depths and then eventually they were declared bankrupt they their their bankruptcy led to the hu huge recession all across the globe and then there's a place in Switzerland yes the name is Basil some people say basel in India Here there was one committee that was established and the name of the committee was BCBS Basel Committee for Banking Supervision and they came up with some important principles and it was made mandatory for all the European banks. It was made mandatory for all the North American banks to follow those norms. There were clear instruction that if you don't follow these norms, your license will be revoked. And here in India as well, we all follow. Now the Reserve Bank of India has accepted these norms. Here in India as well, we follow all these norms. So what is the importance everyone? What is the important significance of regulators? Regulators are going to come up with all those important policies, rules, regulations. Those are going to help you avoid the uncertaintities in the business. those are going to have they're going to help you ensure that your solution is within the given limitations and it's it's aligned with the policies of the organization the country and other parameters for example if I say I'm talking about capital market here in India people joining from India what is the name of the governing body the regulatory body that governs the capital market here in India India CB yes security exchange board of India CB if I talk about the banks nationalized or the private banks then what what's the name of the uh the regulatory body it's the RBI yes similarly in UK and US as well we have different bodies monitoring the activities of different people like in is anyone joining here from UK in UK I work with the HMRC her majesty Queen Elizabeth department HMRC now it's the name of the king after the death of the uh queen so HMRC is about the tax collections in UK and they come up with all those norms for the tax collections so meaning to say regulatory bodies play a very important role when they talk about policies rules compliances and other things. And here we had discussed about the very first thing the very basic topic to start with. We have discussed about responsibility versus accountability. Responsibility is more about the ownerships working on the given task directly. You own the things you work on it complete it. But there's some other person, some other group who is tracking, monitoring, evaluating what you are doing. Also providing better environment facilities. Those may help you work efficiently and that group is the accountable group or people who are accountable for what you are doing as a responsible person. So accountability we had discussed more about the answerability while responsibility is more about the ownership. And then everyone we had discussed about requirements elicitation yesterday. Requirements elicitation is to draw out explore and identify the information that is relevant to need change or the solution. And yesterday everyone we had discussed about three important pillars to requirement solicitation. Pillar number one, pillar number two, pillar number three. Whenever you get some requirements to analyze, you start crying. When you are crying, it means you are collaborating with your key stakeholders to gain more and more information. The stakeholders may not know about the full information with the project and others maybe that the stakeholders are also new to this project. So it's also very important that along with collaboration gathering the requirements you also do your own research. Now for research in our sessions to come we'll talk about the historical data analysis using data mining data modeling data flow diagrams how to look at the existing stories in the shareepoint and Jira and other tools. So research is more about analyzing, discovering the information, synthesizing the information, looking at historically available information, getting some insights from the existing data. Those all things would be part of the research. Research can also be in the form of document analysis. Let us suppose I say I share one topic with you all and Kitika and Projecta sharing this or like Kitika and Project search this thing on bat times.com. Don't you all think if Paka and Pritika are looking for the information on bat times.com this is also kind of a secondary research when you look for something Yes. on Google or some other external source. Yes. So if you're doing your research as I mentioned yesterday do not directly search on Google because it may come up with some contradictory information that's not the right information. So if you're doing your research after the live session prefer bat times.com okay that's the best way to do your own research. Don't go over chat GPT and one more thing yesterday somebody was asking me this question that what's the role of AI in the business analysis world if you search something on chat GPT or any other AI tool once you get the answer you should also ask them what is the source from where you have picked this information and always cross check the source before you accept accept what is the answer from Chad GPT. Okay, I can tell you my experience. We were using chat GPT in our project for some very important projects but we found around 60% of the information was not correct. Yes. So, so be very careful, be cautious when you are like searching something on chat, Jupiter or any other AI tool you think it. So, so AI is good but blindly following what AI is doing is not the right thing to do. Ask AI from where you got this information. Okay. So, so that's why it's an important thing that when you do your research, you search for a reliable source. And then the last thing is experiments. In the experiments yesterday, we had discussed about that we'll discuss in our sessions to come. How to create the PC's, prototypes, uh the MVP. Yes. So everyone we had discussed about the requirement solicitation the three important pillars to it. Then we also discussed about the structure of the Babok guide the business analysis body of knowledge and here we are discussed about few important things dash many knowledge areas dash number of tasks dash number of techniques and dash number of underlined competencies. So let's talk about the BACSM model. Now, now before we start with this topic, I'm coming up with one statement and you all have to my statement is backup model the BACCM model is considered to be an icebreaking step, a trigger to understand the highle requirements those can be then transformed into the low-level requirements. My question to you all is what are the highlevel requirements and how these requirements are different from the low-level requirements. Backup model is going to help you gain clarity around the highle requirements. What are the highle requirements and how these are different from the low-level requirements? What are the highle requirements and how these are different from the low-level requirements? Now is saying highle requirements describe what the business needs are. Okay, perfect. His guy is saying highle requirements are ones which has maximum reach and has severe impact on business. Okay. High level requirements where multiple stakeholders required to involve high level requirements usually or combination of many low requirements. Yes. So high level requirements everyone is considered to be the top view sorry top view or the bird's view when the requirements are mentioned the form of an overview or summary. This is termed as a highlevel requirement. Highle requirements can be categorized as bird's view or a top view. Any BA needs to break it down and capture the details in more granular, decomposed or fragment form. This granular form of requirement represents the low-level requirements. For example, let us suppose let's take one example to understand this thing. Yesterday I given you all one homework to select any two projects of your own choice. How many of you are going for the last one HMS? You all can just give me a thumbs up. learners will prefer to go for this last one. HMS from healthcare in healthcare one project number four. Yes, Gonima Lord you all are going for HMS and HMS is a very good project I must say. So you have made a very good choice. HMS is one of my favorite project and it's good for people who are new to the analysis world to select this one HMS. It's one of the better projects. So let us suppose I see everyone the example is that you have to develop the hospital management system. When we say we have to develop when we have to u create this product HMS this is the high level requirement for us just the summary that we need to develop an advanced solution HMS law comes up with the detailed analysis and says that for HMS the very important thing is the patient's registration Patients registration would include the name of the patient, their medical history, their contact details, their residential address and other scan copy of the existing tests or existing consultation with other hospitals. Once they submit these details, one patient ID would be created, one unique ID. This unique ID would help them get the appointment with doctors. Consultation with doctors. For consultation with the doctors, they have to come up with the time slots. They have to pay that fees. They have to visit the OPD and other things. Then after appointment with doctors, what else can be part of it? lab tests, laboratories, yes, blood test and all such things, radiology and all such things. Then medicines, then something else. When you are decomposing this summary or highle requirements into smaller fragments, these all represent your lowlevel requirements. So I am more interested in payments. That's why payments I had mentioned here itself before we go to the medicine part. Okay. So payment is first in sense itself. Yes. So so payments is a very important thing that you are mentioning here. Yes. So HMS we are trying to come up with someone is mentioning about the companies like Tokyo. Yes. Uh and other companies. So uh the insurance reimbursements and all such things may also be part of it. So meaning to say and these are the details. So when we are dwelling deeper into the details in a way we are focusing we are trying to define the low-level requirements. Highle requirements simply means a summary overview or just a top view. But low-level means you are doing your detailed analysis. You're breaking it down into smaller fragments. Okay. Now I would also like to share with you all everyone one very important tool that may help you create the low-level requirements. So let me share give me a second. Let me open one good diagram and then I'll share with you all. Just allow me one more minute. Just let me open the good one. Yes. So this is what one thing I want to share with you all here everyone and this is a very good yes kind of a use case you can say this is one very good tool everyone and the name of the tool is create now create tool everyone this helps you not only create some good visuals but they also share with you all some sample or some examples Those may help you understand how to use a given template. Like if I click on this one, if you see here, let me increase the size here. You can see here, let us suppose I say you have to create a website like the canteen ordering system. Now you all can see here that for this website you have to create one homepage header sidebar logos header should include logos navigation. So you can see a breakout. This is the main topic. This is the main topic. This is the subtopic. subtopic into further subtopics and that way we are able to come up with low-level requirement. Creation of a website is kind of a highle requirement for us and with the help of creately tool we were able to functionally decompose and come up with the smaller granules in the form of low-level requirements. Yes, everyone. So if and and this is very important for you all to know how to do such thing because now in the agile world they want this is the expectation from a BA to create something on these lines to represent high level and lowle requirements. So creately tool you all can try as a basic tool to start with and you all can see here everyone on top you have the option to edit this template. So you can also edit this template and customize it as per your requirements. So there is one task everyone in each and every project and the task is if you all look at your LMS the task is write down the main feature that needs to be developed. If you'll edit this one, double click and edit and you can create your own feature list here. So you you just simply need to click on edit and you can edit the text here and make it as your own template. So for create need to work you can any you can open any template click on edit and then double click and change whatever you want to like you can make it as canteen ordering system yes shank and others you can make it as HMS okay so whatever you want to you can you can play with this if you want to add few things just C and Ctrl + V and you'll find that there'll be uh more icons here. So, you can play with this tool. Yes. Don't don't pay for it. Just use the U trial version for it. Yes. Don't pay for it. And you'll also find some videos. Those may help you understand this tool better. You have so much that you can do. I just mentioned one. But Creately, you can see here. I'll just open the Creatly tool. There are more than 120 plus templates here. So I show you the Ply tool even see Visio is that I was using 20 years back till date V is used. So Visio is the pioneer tool I must say but since Visio is the traditional tool there's so many companies who are like planning to transition from V to some new tools with better uh visualization. So vis is the best one I must say but but you can use other tools. Yes, because these are getting more popular nowadays. So you can see here Lucid is also a very good one. Yes, Lucid. We'll discuss Lucid. We'll talk about Lucid as well. So I have Lucid in my list. So we will talk about Lucid as well. So Lucid chart is also a very good one. BPMN we'll discuss using delucid draw io as well if you see here draw is already there on my screen so we will talk about all these tools so you have to hold your horses we'll talk about all such tools yes this is drawio this is your list one that we'll discuss this is the creately so one by one step by step we'll cover all these tools so for today just the very small homework the very simple thing is that using the mind mapping templ template create the feature list. Is that simple for you all? Yes. Just use this template and create the list of features. And you can see here that I just show you one of them. If you think that if you think that you you want to use some other other uh template, you can go to this WBS and you can use some other template as well. So as when you open hand whichever one you think is good one like if you want this the curved one you can use this curved one this is also good one if you see here this curved one project title 4.1 4.2 to this is also but the important thing is important thing is for you to know how to decompose the things okay now there can be different types of maps that's for you to explore and do the research the concept is the main thing is that you know the high level requirement and using different types of map you're able to decompose it okay getting it but We but do we give the input to this tool and generate the template with the generated? Yes, definitely yes you can do that. You can give your inputs but it will not generate it will just you can simply edit or if you find this tool a bit complex you can I I'll share with you all the very basic one app diagram the draw.io Here you can create your own. You'll not have any sample one to edit. I've shared with you all this one because here you'll get some sample templates to refer. So you can explore creately. If you find this good, you can use this one. Else I'll share with you all five to eight more tools. Those may help you come up with some better revenge. Okay everyone? So is everybody clear with the difference between the high level versus low-level requirements? If somebody asks you this question in your job interviews, especially people who are new to the analysis world, would you be able to answer such questions? Highle requirements versus low-level requirements. Yes. So that was about everyone the high level versus lowle. Now let's drill deeper into these core concepts here and let's talk about these six core concepts. First one is everyone the needs. Yesterday everyone we had discussed about the needs and those are all in the form of problems that we had identified in the uni liver project. Yes. Today we'll discuss another project wherein you'll find that there is no problem as such but there is an opportunity to grow. So let's discuss the second project now and see what are the opportunities and what is their business model. Okay. And let's talk about project number three in the list WhatsApp pay. And let me increase the font size before we start discussing this thing. WhatsApp is a messaging voice over IP service owned by Facebook. Now when we had created this case study 6 years back the name was Facebook. Now the name has been changed to Meta. Yes, Meta is the parent company now and Facebook and others are the subsidiaries. It allows users to send text and voice messages, make voice and video calls and share images, documents and other media. WhatsApp runs on mobile devices but is also accessible from desktop computers. WhatsApp has over 2 billion users worldwide as of today and it has become the primary means of electronic communication in multiple countries across multiple continents including Latin America, the Indian subcontinent and large parts of Europe and Africa. Today the global the the the globe uh today cause the globe people are moving to digital payment services such as Google pay, PayPal and others. Mobile wallets are in massive demand. The transaction value of global mobile payment market is around this much USD in billions in 2019 and expected to reach 12,000 plus billions by 2025 registering the compound annual growth rate of 23.8. Now what is CAGR? This also we'll discuss in as part of finia analysis and will solve some medical problems. WhatsApp being one of the leading mobile messaging apps wants to get a slice of this growing digital payment market. Now everyone when we read this thing together in this case study when we look at the high level requirement law share and everyone else do you find any problem or challenge with this company meta or do you think they are looking for some good opportunity to expand the universe of their business. So here are the business needs in the form of problems or the opportunities to grow. Yes, there is an opportunity for them to to take a plunge into the digital payment market. Yes. Now I have one looking for the opportunities to expand their business. Nikita Malik. Yes. But I have one question for you all. Think logically and answer my question is when they entered into the market for them the benchmarks were Google pay yes I'm coming to that point only there was a competition or they had the benchmarks like Google paypal and others but they had a different strategy everyone if I talk about Google pay. This Google Pay is one app that is 100% dedicated or 100% full focus on payments. PayPal full focus on the transactions and payments. But but never followed their business model. What WhatsApp did everyone? What WhatsApp what they did instead of creating a new product they simply made enhancements to their existing app and they added one button or icon as the fund transfer. Now my question to you all is Mark Zuckerberg the Facebook is one of the richest person on the planet earth. He has no scarcity of budget on budget. They are coming up with the new product. They could have launched new app. Why do you all think they never came up with a separate dedicated app for payments? Why they integrated and made their existing app more complex? Why there was enhancement? Why there was a not why why there wasn't a new product being launched? What was the main reason? Radika is saying they wanted to exploit their huge customer base. But okay when when when this case study we had created it was in the year 2018 I believe or 19 when we had documented this thing. Now we are in 2026 8 years. 8 years back we had documented this thing. After 8 years, do you all think it was a good strategy to to uh add one feature to the existing one and not create a separate product? Do you think this WhatsApp WhatsApp pay business is more successful as compared to Google Pay and PayPal? Is there anyone who has any sort of statistics to compare which which payment which payment related company is earning better revenues? Which which payment app is more successful? Everyone can anybody help us know? Google Pay is more successful. UPI, Google Pay are more successful and and they are not able to compete with these people. Why? What's the reason? Reason is reason is Apple Pay, Google Pay, these all are more successful. The very important thing that sometimes we miss when we coming up with the solution is the value. Value everyone is usefulness to the stakeholders within a given context. If you are just trying to exploit the huge customer base that you have and not providing a usable product to your customer, eventually you'll find that there will be a significant dip in your revenues. I'll take you all back. I'll take you all back to the year 2006 7 again and I'll just talk about one very popular company then and the name was Nokia and if I talk about 2023 onwards it is there in the market but it has hardly any presence. What happened with the Nokia business? What do you think if there was sudden collapse of complete demolition of such a huge empire? If I talk about 2000, 2002 3 here in India and Indian subcontinent, you all would agree with me Nokia was the undisputed leader. But what happened with Nokia? The main thing was the adaptability was Akash is mentioning here in those days. In those days there was one company becoming very popular and the name was Google. Google came up with two very popular products then. What was those two popular products launched by Google in this era? One was Chrome and another was Android. Yes, this chrome was like accepted by everyone. People loved this and this was coming as a very good replacement to traditional Internet Explorer and even the Mozilla Firefox and similarly Android Samsung accepted it and they had better revenues and what they did they had a collaboration with company Microsoft. Yes. And they came up with the product Lumia and that was a disaster. So meaning to say the usability aspect giving value to your customer is also very important thing to consider when you are analyzing and and law says that even Apple had a very significant role to play once they came up with those smartphones. So there are several factors. I'm not saying there one factor but there are several factors to it. And in the same era I mean there are a lot of things that happened in this era. If I talk about here in India not just India if I talk about globally 2007 and 8 or I can include nine as well. Seventh richest person in the world. richest person in the world. His name Mr. Anil Amani from India. Seventh richest person. His brother was third richest person. Then seventh richest person 2007 8 and 9 this era. Now in 2023 he was declared bankrupt. What happened with this business? What happened with Mr. Armani and why? What was the main reason for the collapse of his business? The main reason was again the adaptability. The main reason was everyone that in those days there was one technology that they were using and that was CDMMA. Then the new technology came in as GSM then 3G then 4G and all and it took time for the company to take a decision to transition to the new technology adapt to the new world and that was a major reason for the collapse of their business. So what you try to understand everyone here is the very important factor as part of the BCC model that is value along with the opportunities that you have as law is mentioning here instead of show off instead of just promotions it's also very important that you think about the value usefulness to a stakeholder within a given context. test. Customer value and business value are two important components to it. Customer value is about how well you're able to come up with a better quality product. Product that is usable for the purpose, sustainable, usable. If people have some feedback or comments, you're able to make certain adjustments. So customer value is very important like you all must have observed this thing that even in our live session during the break we request you all to participate in the polling activity and after the live session we ask you all to share your valuable feedback. What exactly is the reason why we are having those two activities? Yes. So creating demands is something very important. Yes. But it's an important thing that you also consider the value parameter. You can promote your product. You can you can do a lot of things to increase the demand. But but if you're not giving value to your key stakeholders, are those promotions are those tactics to increase the demand work in the long run? No. So the important thing is that you focus on both customer and the business value. So let's read few things from the map guide to understand what is this value parameter and why it is so important. Yes, I'm coming to context as well in few minutes. Let's first talk about the value one everyone. Let's finish this value first first and then we'll talk about the context as well. So value everyone if I take you all to session two notes topic number one value parameter value everyone is the usefulness to the stakeholders within a given context. Next usefulness can be defined with the help of two important elements everyone. Business value and the customer value. Business value everyone it is associated with cost structure and revenue streams. Now in our sessions to come possibly in our next Sunday session we'll talk about how to calculate ROI, payback period, present value, net present value, internal rate of return. These all capital budgeting techniques everyone are going to help us estimate and calculate the profitability and gain margins. This is one important thing to consider as part of business vending. Another important thing is everyone the customer value customer value everyone is about something linked with the quality of the product. The product or solution features must drive customer satisfaction and and I can see that so many people talked about the usability. Let's see who talked about it. Loyalty you talked about it and somebody else also talked about usability. I remember somebody talked about it in the chat. I can yes e easy to access as kl mentioned madi talked about trust and somebody had mentioned about usability as well. So you can see here Akash is saying it's more about marketing and not just need. Yes. So it's a very important thing that we combine all those things together so that the customer value is achieved. It is associated with the quality of the product. Product or the solution features must drive customer satisfaction and the solution must be usable for the purpose. hair house of quality akash and everyone else the voice of customer are the two important things to consider. Now what is VOC everyone? VOC is very common activity in most of the projects. What is VOC? VC is about the feedback, the reviews, what else, those important comments that you get from your key stakeholders. So review comments and the feedbacks. House of quality is going to be like all those important functionalities, features those may drive customer satisfaction. And this house of quality leads to minimum valuable product. Now what is MVP? I've given you all this as homework to read. So MVP is something that you'll be able to come up with if you're able to come up with proper customer values. So value everyone and to summarize value can be considered as a combination of business value and customer value. Business value is more about generating profits. Customer value is about maintaining the voice of customer and also the house of quality. Yes. So this is a nutshell the value parameter. I'll take a pause here wait for your questions before we move to one question I'm going to share with you all. So please read this everyone. Ard is saying that customer value like that's that's okay let me let me ask this question to everyone when companies like Jio come up with free internet is that the customer value or the marketing strategy this is not something as you can say it's related to customer value but it's more about it's more about it's more about marketing ing your product. It it is something linked with customer value for sure but it's not about bringing in value. It's more about increasing the demand. Okay. So it's about increasing the demand but but the important thing would be that you provide the better quality internet. When you come up with a better quality internet, better services, that's something that contributes to customer value. Okay, getting it. So, so sometimes it's a mix of the marketing strategy and the customer value. Sometimes we think it's a customer value but it turns out to be the cheap tactics. Yes, that fails later. So some in in few cases marketing strategy is disguised as the customer win. So we have to be very smart to to check and differentiate between the marketing strategy and the customer value. Okay. It comes under business value. Okay. Context everyone is a very important thing. circumstances that influence or are influenced by and provide understanding of the change. Context is about everyone yesterday if you all remember. So what is the context everyone? Context is going to help you understand the background, the existing behavior, what exactly is happening in the current behavior that may help you come up with a proper definition of business needs. Context is something that will help you understand what are the existing functionalities, how organization operates at present, what are their strengths, what are their weaknesses. That way you'll be able to understand what are the important business drivers for the change. Is everybody with me on this thing? So context is a very important thing to analyze first. When you analyze the current state, it will help you then define the context. Context is going to help you understand the business objectives, the business drivers. Yes. So that's why context is important thing when you are analyzing the highle requirements. Is everybody clear with this thing? Vijendra I think you had this question on context are you fine with the answer now? Yes, everyone. So, this is your BCM model with six core concepts. One more example. Okay, let's talk about let's talk about the WhatsApp pay in WhatsApp pay Vendra and others. What is the context for the change? Why Meta as a company is planning to launch a new app or planning to launch a new product? What's what's the context? Context is anybody help me know what's the context? Har has a very good point digital payment. But why at all the digital payment? why why at all they're bringing about a change or why at all they they think that this is going to be a good business for them. There are several things if you see here. First important thing is that globally people are transitioning to the digital payment process. Nobody is now willing to pay the cash from their pocket. Simply they can scan the code and they can pay for it. So it's easy. The people are switching to digital payment. So it's in demand. So that's why they're going for it. And they also have a huge customer base. So they think this will be a profitable business for them. Yes. But ultimately that was not the good business for them after 6 years or 8 years. Okay. But still they are earning good revenues from it. So context is going to help you understand why a change has been initiated. What were the key business drivers behind it? Okay. So so that's about the context. Har is saying that send money to family friends while chatting and while watching ress yes I'll add one more thing at the same time. Yes. become a very integral part of everybody's life. So, so yes, perfect. Yes. So, you can see here that that context is going to help you understand the background and this will help you understand what are the key business drivers and that way you'll be able to then define a proper solution. So, that's why context is so important. It will help you in simple way in in simple terms context is going to help you understand the existing behavior the current behavior the asis state the background and then you can easily come up with the complete definition of need and then the corresponding solution okay getting it vijend I can give you a few more examples if you're not clear with this thing. I have few more things more few more examples if you want to understand context better. Yes. No. Okay. Perfect. So we we are done with this topic now. BCCM model learners who are preparing for the CCB and CBA examination. You all can create one short form to learn this thing as N CS and CVs. N CS and CVS are the six core concepts need change solution context value and the key stakeholders NCS and CVS. Yes, everyone with me. NCS and CVS. Okay, the next topic is relatively more important everyone and that is the requirements classification. Here Vij and others will discuss about context one more time with the help of one BD template. So you'll understand context better once we'll talk about BRD in detail. Okay. So we'll revisit context one more time. Requirements classification schema is our next topic. And you all can see here everyone four different types of requirements, business requirements, stakeholder requirements, solution requirements and then the transition requirements. Yesterday we had discussed about the transition requirements in the form of enablers. So today we are going to focus upon these three that is business stakeholders and solution requirements. Business requirements everyone and the stakeholder requirements these are combined together and they're documented in one standardized template and can anyone of you guess what's the name of the template the business analysis standardized template that captures both business and the stakeholder requirements yes absolutely wonderful answer Dennis and Ahmed answer is B R D BRD is one standardized template wherein you'll find a complete description of the business requirements and the stakeholder requirements. Business requirements and stakeholder requirements. These are also known as the highlevel requirements. Here you'll find some summary, some short descriptions and then when you perform your detailed analysis, when you apply several important techniques, it will then help you break down this BRD into smaller fragments. And this fragment level information is your low-level requirement. And this is defined as the solution requirement. Everyone solution requirement. This is a very good question that you are asking me and I'll come up with the answer in few minutes. Solution requirements. Solution requirements everyone is nothing but the low-level details. How well you are able to break down the summary the overview into smaller granules. How well you're able to come up with the details around the BRD and solution requirements include functional and the nonfunctional requirements. So, Pritika will take one example. We'll now discuss on sample BD. So this will help you understand a very better manner of what exactly the BD represents and what exactly business requirements represent. So let's discuss one sample B now and then you'll also get the answer to your question law that who is documenting once we'll discuss the B components you'll get to know that whether your business users are writing it or the BA is doing it. Okay. So let's discuss on sample B now and with the help of BR let's see what are the important components to it who is writing it why we are writing it and what's the practical significance behind it all can see here project summary objectives background and then at last you'll find the Business drivers objectives should describe how this should describe the overall goal in developing a project. Highlevel description just the highle description not the details. highlevel descriptions of what the product will do, how they're aligned to business objectives and the requirement for interaction with other system. This is also very important thing. Second thing is everyone the give background. Background everyone is about if you look at this explanation here provide a brief history of how the project came to be proposed and initiated including business issues problems identified and expected benefits of implementing the project and developing department and last thing is business drivers. List the business drivers that make development of this product important. This can be financial, operational, market or environmental. And Vij you had this question on context. These three things you'll be able to define if you know this core concept context. Yes, Vij with me on this thing. So context if you know it will help you define the objectives that what product is going to do how they're aligned to the business objectives and how the requirements are going to interact with other system the linked systems. What are the financial benefits? What are the monetary benefits? Operational benefits, market conditions, environmental conditions. All such things can be easily defined if you know the context. Yes. Law is saying what's the difference between the objectives and the drivers? Yes. So what are the drivers of the one? Let us suppose I say let's try to understand this thing with the help of one example. If I say canteen ordering system, financial driver is you all would agree with me. Office productivity. Yes or no? Financial driver is the office productivity. Once you'll come up with this app, this will help you outlift the office productivity. Operational benefit is that it will drive employee satisfaction. Now Law and Weber are not going to stand in long cues waiting for the tables to be vacant. This will help uplift their business operations. Market and the environmental conditions are now that now you're providing better services, no more food wastage, no more wastage of time, proper time management and all such things. And that way you may also then you may also attract people and people are now now willing to work with unilo instead of filing for job instead of requesting for job with other companies they're now preferring unilo because it has got better facilities employee centric better products better services. So these are the drivers. Now look at the objective. What are the objectives? Objectives tell you that what product is going to do. Product is going to help you uh request uh food food delivered to your uh work location and what are the interaction with other systems? Okay, if I ask all one question law and others can ordering system what are the important interactions? One interaction is the order from the employee. Yes. Employees going to order. Second is order received by cafeteria management team. Yes. Delivery boys getting the details of the order and also customer providing the feedback. Yes or no? These all would be part of the objectives. Yesterday somebody was talking about having having a small area. I don't know. I'm not able to remember the name. Uh I think Nikita or somebody else pantry. Yes, somebody talked about Yes. P you talked about it. Pantry. So that can also be part of the objectives. Is everybody with me following this thing? So what we are doing here is as part of the BRD we are first coming up the very important thing as project summary. Project summary is something that defines your business requirements. If they ask you this question in your job interviews that what are the essential components to any given business requirements? What are the important sections to define? So you can tell them that objectives, backgrounds and drivers are the key components as part of project summary and this helps us define the business requirements. Next thing is everyone next important thing is project scope. Now project scope is something that can be linked with stakeholder requirements. It says describe what work is in scope for the project and specifically what work is out of scope. Now this is very important beyond the current budget resource and timelines as approved by the project stakeholders. Now my question to you all is ideally you should just focus on something that lies within the boundaries in scope things but in the beyond it in the beard it is mentioned everyone sorry in the beard it is mentioned that not only focus on what lies within the scope but also define what what lies outside the scope out of the scope. Can anybody help me know what's the purpose? What's the intent behind defining both incope as well as the out of scope requirements? What's the purpose? Why at all you're focusing on both the things the main purpose is everyone to prevent scope creep. Dennis, you're coming up with the right answer. I hope you have not copied it from the third line here. It's your own logical thinking that you have come up with this answer. Yes. So, it's a brilliant answer. Yes. If we are not defining the out of scope requirements then the chances are unintentionally or due to some assumptions these are absorbed in your solution. Let's try to understand this thing with the help of one example. Let us suppose I say I'm talking about food order law and others. You all can see here that only 1,500 employees may order food. Here a login page to validate the users must be created. It will help in authorization and authentication. No other person or employee outside your deliver is authorized to order food. Now this way if you're capturing the inoscope and out of scope requirements it will help our technicians or technology experts understand how to come up with thick and strong boundaries for our solution. Now if I ask you how you will ensure that it's just the deliver employee and no other person ordering how you'll ensure that this thing happens what you'll do then you'll simply you'll simply try to come up with certain authentication as Issha is mentioning here a very good point that you can only login if you have the official email ID and uh and and one time password shared over your ID if you if you if you're able yes so ID password integrated with employee ID which is this is a very good point yes employee ID can be one of the very important authentication nowadays we have this SSO feature in most of the companies yes single sign on that's also very good authentication feature how many of you using it it's a very good feature nowadays the SSO wherein you just need to enter your employee ID and based on certain authentications at their end they'll take you to the next page if yes so seller authentications may help like order timing employees may order food during the weekdays only not on weekends and between 12 to 2 p.m. only. It's not like if you have uh uh like you enter into the office at 9 9:00 a.m. in the morning and you feel hungry and you're ordering food. Yes, it's just about 12 to 2 p.m. that you'll be able to order the food. So that way if you are able to come up with certain important restrictions boundaries, you are able to define the project scope. Yes. SSO may cause problems. Yes, it has some shortcomings as well. So what I'm trying to explain you all here is the project scope that should include both in scope as well as the out of scope requirements. Out of scope requirements would help you ensure that you prevent scope creep. Okay. So if they ask and this is one job interview question they may ask you this question people who are new to the analysis world how do we prevent scope creep in any project how do we ensure that the project scope is very clearly defined you can see that by defining both incope and out of scope functionalities we can pass on the clear message to our technicians This will help them create thick and strong boundaries considering that what lies within a scope, what lies outside the scope and this way we'll be able to prevent scope creep condition. This way we'll be able to prevent any redundant, duplicate or unwanted component in the solution. Is everybody clear with the scope creep or do you need some examples to understand the scope creep better? Do you need some examples to understand the scope creep better? I can give you all one more example. Yes, let's take one more example. Yes, let's take one example. Let us suppose I say I'm talking about hospital management system and in hospital management system we have one form as patients registration. During the patient registration, let us suppose I say we have Maduri with us and Maduri is filling this patient registration form. She has mentioned the name, the date of birth, the medical history and then there's an option to select the doctor from the list of doctor. This is a list of doctors based on their specialization and this is one combo box a list box wherein they're all names displayed. Maduri is selecting doctor XYZ books an appointment with this doctor. The appointment is scheduled scheduled timings is also mentioned and when Maduri is going to the hospital she's there in the OPD and she shares the details of the appointment. She's surprised to know that this doctor is no longer imparted with Mayo Clinic. This doctor left the organization, the hospital one month back. Maduri is not happy with this thing. She has traveled 15 kilometers to consult this doctor and now hospital is saying that he's no longer impended. This appointment is getting cancelled. What is the flaw in the business model here everyone? What is the challenge and how you'll remove this law? If you are the business analyst, if you are the business analyst, what you'll do is you'll come up with one very important step that if any doctor is getting impendled, his name, his details should be removed the same day to avoid any cures and confusion. His name appearing in this list is causing scope creep. This is scope creep is causing problems for Maduri. It may cause problems for others as well. So this list of doctors should only include the active doctors. Active in the sense those are impanled with Mayo Clinic. People who come from database development background. Simply in our database table, we may add one flag as active or inactive and only active names are displayed. Inactive ones are the creep and these should be removed. Yes, more than everyone else are able to understand how to prevent the scope creep condition. So scope creep is about your solution your solution having some redundant duplicate or unwanted components. Those are causing unnecessary noise. This may also result into some employee dissatisfaction, employee complaints and sometimes very severe issues. Okay. So that's about the scope creep and how do we remove this. Now let's discuss one case study wherein you all have to first identify the business requirements and then you have to come up with a corresponding solution. What do you all think can be a good solution for the given set of requirements. So let me share one case study with you all now. Requirements classification schema case study. Yes. So this is basically for my project. This is the real time case study from what we did few year back. So there is one application everyone the website that is primarily designed for those employees who are on the verge of retirement or simply resigning from the company. This application helps them raise a few tickets and request for reimbursement and helps them raise requests for pension and private fund withdrawal. During the COVID 19 crisis, this happened in my project. We started getting complaints that this application was causing some problems. Performance was very low sometimes and sometimes it was not responsive and on few occasions it goes down completely. So now since this was causing problems and there were lots of complaints from different business users. So this was assigned to me to like discuss and resolve this problem. So I then discussed this problem with my production support manager and he shared some valuable inputs. You mentioned that this application was designed 10 years back and the scalability was marked as 20. So when we say the scalability was marked as 20 this simply means there can be 20 concurrent users to this application not more than that. If there are more than that, yes, users has at a time as Kita is mentioning here. So 20 concurrent users. If the more than 20, it may start to create some problems. Now during this COVID crisis, you all would agree with me, government came up with government in different countries came up with a lot of relaxations to withdraw your savings, to withdraw your funds. So now what happened like there was you may say huge traffic and the traffic increased many folds and sometimes there are more than 300 plus users logging into the application. Now this was the problem. This is your case study on your screen. Now Aayush Ritika and everyone else imagine if you are a BA like me facing such problem in the project Shabbaz another Akshai Isha and others what do you think can be a possible solution for such given business requirements? What do you all think can be the best approach to resolve customer queries to ensure that people are not facing this problem? What can be a good solution for this case study? Everyone questions open for you all to answer. Jagan is saying that very simple thing is increase the bandwidth of the database in the cloud in infrastructure. So similar suggestion I had for similar sation I had from the production support I said why don't we increase the scalability I never came up with such a good answer like Jagen but I said like very simple very simple terms that please increase the scalability up to 500 and so that everybody can use it but Jagen when I said this thing the production support manager had a smile on face. He said if it was that simple we would have already done this thing. The challenge is it's our own dedicated servo. The old technology 10 years back we had developed this thing and if we'll try our level best we can increase the scalability up to 50. Then I said 50 is not going to solve the purpose. We need something that's more than 300. Now what Pavi and Kuml are suggesting that was my next suggestion and I said why don't we get a new application then he said that why you're telling me this thing if you want to give application get approvals on the budget get approvals on the stakeholders get the approvals on the resources and then you can come back to me and then we can do it it's not my job to uh give you suggestions on the new uh product to be created. Now, now if you realize here, look at the situation. People don't create a new one. Do you think um Rome was built in a day? Do you think we can create an application within a day or two? No. upgradation or a new application, transitioning to a cloud platform. This will take time and do you think people during the coid9 crisis are going to wait for a new application to be launched? Are they going to use that application heaven or hell? No. They need an immediate solution first. So, so that was a very challenging thing. Now I'll share with you all as saying I would first find out the trends of the Now I very good answers. Let me read few more answers before I come up with my solution. Aim is saying I would first find out how the trend of the visitor had changed during the co postcoid and I'll find out the daily number of visitors. So this information already given to you daily number of visitors is crossing 300. Lo is saying that short-term fix is performing tuning infrastructure scaling. Absolutely wonderful answer. Thank you. Common is saying advise them to root the requirement from the alternate source. Okay. So if there's alternate source then we can do that but in our case there was no alternate source available. Pney is saying investigate collect data how many how many are going to retire and resign. It's not about how many people are going to retire and resign. It's about people who are logging in because now even if you're not retiring or resigning since government has come up with the relaxations everybody is interested to withdraw the amount. Yes. Because government had given the option that you can mention that you are going through COVID crisis and you need money and you can easily get that money from your funds. So this was the problem. So not only people who are resigning even people who are part of the job yes just to go out with friends and family and enjoy some time in the hilly region they're taking out the money in the name of covid-19 crisis people misusing the government relaxation increase the scalability dedicated email to raise request so that someone can raise request on behalf of them that's can be one thing yes but Let's look at the solution that we came up with. I'm not saying that the solution that I have come up with is the best solution in the world. No. But this solution all the business users agreed to all the stakeholders authorized to provide signoffs. They approved it and everybody was agreeing to this solution. So let's see what was the solution that we came up with and how we were able to cater to these business requirements. So everyone this is the solution on your screen solution is everyone on your screen I just rearrange few things it's clearly visible to everyone solution everyone was divided into two parts one is the strategic solution. Point number one is strategic solution and point number two is the practical solution. My question to you all is what is the difference between the strategic solution and the tactical solution? A strategic solution everyone is a structured organized and welldefined solution that's going to fetch goodness in long run. A solution from long-term perspective, a solution with minimal defects, a solution with all those capabilities, those may drive customer satisfaction. That's the strategic solution. So as most of you were saying Jagun and everyone else we raised one request to create a new application with the scalability marked as 1,000 everything on the cloud platform the advanced application based on the AI capabilities and this request was approved and our team the development team our technicians came up with the estimate that it may take around 7 months to deliver the new application with new capabilities. For these 7 months there was a workar around that we came up with. First thing that we did was as per the suggestion from the production support manager the scalability was increased from 20 to 50. This was the maximum value. This is the now the maximum scalability on the main login page. One functionality as a counter was introduced. This recorded the number of logged in users. When the record count reaches to 50, the 51st user is redirected to the maintenance page with a popup error message. And what is the pop-up error message? That now the maximum scalability has been reached. You can wait here or try again later. There's a scheduleuler that monitors the ideal time for the logged in users. If the ideal time crosses 15 minutes, then users are automatically logged out and the users in the queue get the opportunity to log in. Now that way we were able to come up with a solution for this problem everyone. So you all can see here that we had a tactical solution in the form of a workar around and we had a strategic solution from the long-term perspective. Now in this solution everyone we have few functional aspects functional solution or you may say functional set of requirements and there are few nonfunctional requirements as well functional requirements saying can that solution be already obsolete on the AI agent error. That's also something a good question, a debatable topic that we can discuss here. But let's keep this topic for the Q&A time. We can discuss this thing. So let me first complete this thing. Now if you see everyone in this in this in this solution here we are talking about certain important features to be developed certain important functionalities are introduced and we're also talking about certain nonfunctional requirements. What are the nonfunctional requirements of the word? Nonfunctional requirements are the requirements those you cannot see but you can feel kind of an abstract now like the better performance better usability maintenance availability scalability. So these are all the environmental conditions those help those support the proper working of the functional requirements. Now let's look at few examples of non-functional requirements and then we'll come back to this topic again and we'll talk about functional requirements as well. in your drive link in your above guide everyone if I take you all to chapter number 10 the technique section here you'll find page number 303 categories of nonfunctional requirements please check and confirm everyone please I request everyone to please check and confirm is Everybody able to find locate the 15 NFRs in the above guide? Please check and confirm. Categories of nonfunctional requirements. This includes availability, compatibility, maintainability, formal efficiency, portability, reliability, scalability, security aspects, usability, ease of use, certifications, compliances, localizations, even the service level agreements, extensibilities, these all are considered to be the nonfunctional requirements. Nonfunctional requirements are the supporting conditions. Environmental conditions those may help, those may support. functional requirements to work efficiently. The more popular ones nowadays everyone they may ask you such questions in your job interview that what are the commonly used or commonly you may say defined efforts in any project. The answer is security. Answer is performance efficiency. Answer is usability, system availability, maintainability. These all are few you may say important NFS to consider. All 15 are important but these are the more popular ones. Usability, security, performance, efficiency, maintainability and availability. Okay. So now we have discussed the theorical part. We've discussed about these four different types of requirements a very interesting tool and that is Jira. Jira is the very popular tool in the agile projects nowadays and Jira helps us capture all these four types of requirements. TFS is also a good one. Now the name for TFS is changed. TFS is now known as Azure DevOps. Yes. Average for TFS. Now it is Azure DevOps. Even I'm using TFS. That's why no. Yes. TFS is also a very good one I must say. But we'll talk about Jira first. The reason is for TFS trial version Microsoft asked for the credit card details and most of us are reluctant to share the data although they won't deduct any payment but they ask for the details and that's why people find it difficult to or reluctant to install this. So we will talk about Jera first and then we'll also talk about TFS. So let's start with this topic now. Jira Jira V1 is one tool a document collaboration and project management tool. This is owned by one Australian company Atlacian and this tool helps us create some important BA deliverables document the high level versus high level as well as the low-level requirements and Jira tool in a way reduces the dependency on Microsoft products like word, ppt and others. And Jira also acts as a document repository. So let's see what is this Jira tool all about, how to create your own credentials, how to use this tool to write the different or capture different business analysis deliverables. You simply need to click on this link or you can copy this and then you can find here the Jira page. For me it says continue because I already have access to this one. But for you all, you all have to start a new site. For new site, you have to first mention your personal email ID. Never mention your official address because it may create some problems because they'll they may come up with certain advertisements and other over your email official email. So mention your personal email address. Once you mention your personal email address, it will automatically create your own site and then you can click on continue. Once you click on continue, it will then take you to the next page and it will ask you to select one of the three options. It's taking few seconds to load the next page and then we'll see what we have in the next page. You all can see here there are three important templates here. Canbun, web design and scrum. Now canon is for the short duration projects for defect fixing for production support. Canon will not focus at present. Web designing is not for us. It's for the technicians. We'll focus on scrum agile approach to plan, prioritize and schedule sprints using the scrum framework. So we'll select scrum. Then we'll click on continue. And then you have to name your space. So let us suppose I say I have I see Shazad name on my screen. So, Shazadab sample project SH Shazad CBA sample project and I click on get started. So tasks assets and click on next and again click on next. Then it says Jira better than when used together but I'll do it later. And this takes me to Kenman will discuss. Kenman will discuss sharpness. Kman is basically one of the agile approach that is generally used for the production support for maintenance and for the short duration projects. So canon is less popular approach as compared to scrum. Iscrum is more prevalent. Iscrum is more popular. Is scrum helps to handle the software development projects better. So that that's why we discussing scrum first. We'll also talk about canban. What is canban? Can is one of the agile approach to handle and manage the small duration or the production support related projects. Okay, getting it? You may get a different view for sure. There may be several views like I if I show you here I have one more view and this is kind of bluish or greenish. So you may get different views views is not the problem. The important thing is are you able to see the name of the space and also are you able to see the button like create and others are you able to find Jira on top everyone yes or no Karishma Shanoga and others is everybody able to reach till this page or do you all have any issues now the next thing Everyone click on this plus. Is everybody able to find spaces in the left hand section? A space with a Saturn icon. Yes, a space. Click on this plus. And then once you click on this plus, you'll find here even if you build Canv toggle to scrum. So you can go to the spaces and from there you can simply yes. So people who had selected canburn or any other um template you can simply click on a space and then you can easily change the template. Okay. So you can simply go to software development and from here you can again select the scrum. Okay. So let me repeat the steps everyone. Let me repeat the steps. First important thing is for you to click on this link and then you have to mention your personal email address. When you'll mention your personal email address, then it will automatically create your own site. Yes. Once your site is created and there's a green tick, then you can click on continue and then select the scrum template. Once you select the scrum template, it will ask you to create your own space and there you have to mention something as a title to create your own space. Then click on continue and the job is done. It will take you to the main Jiraa dashboard. On main Jira dashboard, let me repeat this is the main Jiraa dashboard. You have to click on this space, this plus button, this plus icon here in the software develop. Now you all can see one more thing here that Jira has a diversified use. It's used in sales, analytics, operations, designing, finance, human resources, marketing. Yes, last week I was into the HR analytics course and we created some dashboards for the HR team. So, it's not just confined to software development. It's also used for analytics. It's used for HR analytics. It's also used for marketing, product management, work management. We are going to focus on software development. I'm going to select scrum here. Use this template team managed. And then you can mention the name of your space like I can mention here tbling project team managed short acronym is created here. Scrum project. Click on next. And this takes me to in few seconds to the I'll do this thing later. I think somebody had this question today. Bring your team along. So just click on I'll do this later. And this will take you to your Jira main dashboard. Main dashboard. Yes, everyone. Now you all can see here I have Shazad as one project another as Rafaelio. Now everyone let's establish this relationship in Jira by performing some basic steps. Let's do this thing in Jira. to everyone on the top of this page the top ribbon if you'll move towards right after this search you'll find one blue button with plus icon here is everybody able to find this blue button on top and then you can see here you'll find here work type as user story now here. Now here just make it a bigger screen and instead of story first select epic. So, epic I have selected and then the summary I have mentioned here as canteen ordering system description we're not discussing today description we'll discuss in the next session or next next session we'll talk about how to write this for now you can leave this blank and then just click on create when you'll click on create everyone you'll You find one message that changes are saved and you have this epic created as RCSP something like this and this is the epic created here now. Now everyone let's try to create. Yes. Yes. You are getting SCSP because you're using your name Shabbaz. I think it is Shabbaz C. I'm not sure why C but SP means scrum project. Okay. Like for me it is Rafael. So RCSP. Okay. Perfect. So now we have one epic. Now let's create one user story. For user story again we'll click on this blue button work type we'll select as the story and the story will create one login page epic you'll find as I mentioned few minutes back let me repeat this on the top section here top ribbon this blue button click on this blue button and here in this work type drop-down you'll find one of the option as epic okay now don't anything right now don't select parent or anything as of now just write create this story okay so just work type as story and summary you can mention here as login page as part or if you only have task in epic it means it's not the um okay so if you if you're not able to find the story in this list you can add the work type in story are you able to find this option add work type. You can add a work type as a user story. That's a work around. Okay, perfect. So, summary is login page as part of team ordering system summary and then you can simply click on create button. When you click on create button again you'll get a pop-up message that your story is now created. Click on this link everyone and on top you'll find here an option to add the epic. When you create your story and when you open that link, you'll find it on top. It says add epic. This simply means it's asking you to add the parent to this child. So what you'll do? Simply click on this pencil icon. You can add a parent or you can do it like this. So I'm just showing you how to do it uh in a very simplified man. You can also add a parent to it. That's also fine. So you can simply add the epic like this. Yes. And then click on this link one more time. Click on this link two times and everyone. Then you'll find here that there is one epic as canteen ordering system and child work items include the story that you have created. Now you can add several stories here like you can add here. Second thing is another story here and you can mention here the food menu. This is your next story food menu. Another story can be your payment gateway. This can be another story here. You can also add food delivery. So now we are able to establish what we discussed theoretically that one epic this highlevel requirement may have several low-level requirements in the form of user stories. So the first topic for the day everyone is a and others business analysis planning and monitoring Rafael and others. This is the icebreaking you may say knowledge area or a very important one to start with your analysis and the name of the knowledge area is business analysis planning as well as monitoring popularly known as BAPM business analysis planning and monitoring. And this knowledge area has five important task everyone. I'll use different ink here. Plan business analysis approach. Plan stakeholder engagement. Plan business analysis governance. Plan business analysis information management. And at last identifying business analysis performance improvements and people who are preparing for the CBAP examination for them it's an important thing to create some short form like this A S G I P. Yes A is your approach. Today we'll discuss about the approach. It can be predictive. It can be adaptive a waterfall of the agile methodology. We'll discuss in detail today. A is your approach. S everyone is about the stakeholder engagement. Here we'll talk about how to identify the stakeholders, their characteristics, how to perform stakeholder analysis. Those all things are part of stakeholder engagement. G stands for governance. I stands for information management and P stands for performance improvements. So let's talk about everyone 3.1 plan business analysis approach and let's see what we have as part of this task here. Plan business analysis approach everyone the first one plan business analysis approach. So you all can see on your screen here everyone it says everyone define overall method to conduct business analysis activities. Now method everyone swam a nad this can be a traditional method this can be the modern day method the new method and now it can be a old method it can be a method when I was new to the analysis word it can be a method when you all are new to the analysis word yes so method can be everyone the old one or you may say Old is not a good word to use. So I'll use the word traditional. Yes, method can be traditional. Method can be the legacy method or simply in bracket old one. Yes. Like the train and method can be the modern method, the new method. Yes. the traditional method. This is popularly known as the predictive method. And we'll discuss why it is known as predictive in few minutes. And the new methodology is known as can anybody guess what is the name given to the new methodology? The new ways of working that word is accepted. The new method is adaptive. Yes, adaptive is the new methodology. The adaptive, the advanced one, the adaptive one. Predictive everyone. If I talk about predictive examples can be waterfall, V model, the spiral model. These all were like very important and very popular when I was the college pass out. When I was looking for a job in those days, these methodologies were like you may say religiously followed in the IT world. But now after around 20 years or so, there's a drastic shift. These are considered to be the old school. These are considered to be outdated and these have all been replaced with adaptive methodology. And this includes agile and devops. So everyone we have discussed here about the methods. These can be of two types. Traditional or the modern. Traditional methodology. It is known as predictive methodology and the modern methodology it is known as adaptive methodology. Adaptive in the sense adaptive in the sense it is more flexible. Flexible in terms of delivery in terms of documentation in terms of communication in terms of release plan as well. So that's why it is adaptive and this is predictive. Please make a note of this everyone and then we'll discuss the differences between the two predictive versus adaptive. So everyone let's talk about the differences this table that talks about the difference between predictive and adaptive approach predictive versus the adaptive. Now you all can see everyone there are four important differences people who are new to the analysis or learners who are preparing for the job interviews. This table is very very important for you all. You all can bookmark somewhere. You all can write it somewhere that it's an important thing for you all to know the four differences between the predictive and the adaptive methodology. Yes. First one everyone is solution definition. Let's focus here. It says defined before implementation to maximize control and minimize risk. This used to happen when I was new to the analysis world when we used to create FSD and SRD. Today you all had questions around it. FSD SRD. So this used to happen when we used to write FSD and SRDS. But now what is happening? If you look at this keyword here, define in iterations to arrive at the best solution or improve an existing solution. Now this is a very important thing for us to understand. Let's try to understand this thing with the help of one example. The very first point solution definition. So let's try to understand this thing now. So let me create some data here some example here. So we are talking about everyone the approach and let's first talk about the predictive one. The predictive approach in the predictive approach every one there was one terminal SDNC that was very popular. Can anybody help me know what are the important steps that we follow in the SDLC the software development life cycle. people from the engineering background, people who have been into analysis or development for some time. What is the SDLC software development life cycle? Let me write it here. The steps include requirements gathering. You have gathered the requirements and you come up with corresponding solution. Yes, this is a complete solution. Then once you have the solution, then you'll ask your development team to develop the code or code implementation. I'm just covering the basic steps, not all the steps. Then what will happen is developers are going to develop the code and then once the implementation is done code implementation complete I'm using the word complete here again and again complete implementation include deployment On this is done then there'll be testing quality analysis quality assurance I must use the word quality assurance for the complete solution. complete solution. Then what will happen after the testing? What's the next thing? The user acceptance. Yes. After user acceptance, what you'll do? You'll go live or you'll push the change to production. Yes. Yes. So user acceptance is about this sign off and then you deploy to the live environment. Yes. And then if there is some issue then you will maintain the things. Yes, these are the important steps everyone. Now everyone this is what we used to do in the predictive world and let's see let's try to understand what is happening in the new agile world in the predictive approach. The release plan is equal to sometimes 3 months. It can be 6 months or in even few projects or even one year. Yes, everyone. And I hope everybody understand the meaning of release plan. Yeah, release plan simply means you analyze, you develop, you test and then finally deliver a solution within a given time frame. That's a release plan. Now what is happening everyone in the adaptive world? In the adaptive approach, there is a slight twist in the tail. There's a slight difference. release plan that is supposed to 3 months. But what we are doing is there is a concept of partial release or you may say incremental delivery. So what is happening is instead of sharing the complete product at the end of 3 months we are sharing the partial solution after certain time period. Let us suppose I say we coming up with a partial release that after every 2 weeks we'll deliver for RN requirements solution as one. Yes. Now everyone if two week is cycle number one how many such short cycles we'll have in 3 months very simple basic mathematics release plan is of 3 months and we are planning to deliver some part of the solution some part of the requirements after every two weeks. So we have total six times we'll deliver it. T1, C2, C3, T4, T5 and C6. Is everybody clear with this thing that why six? Yes, because our release is divided into smaller short cycles of 2 weeks duration. Now what is happening in what is happening here is in C1 you deliver S1 in C2 you deliver for R2 S2 and in C3 what you're doing is R3 and for this one S3 and similarly similarly for C6 you have R six and you as six other solution. So what is happening here everyone instead of delivering the complete solution instead of doing the complete analysis up front what we're doing is we are coming up with the incremental delivery concept the actual release concept and these two weeks are the iterations the repetition that we have within this 3 months cycle. Now my question to you all is which approach do you all think is more flexible? Which all approach do you all think is better? The second one adaptive or the first one predictive in terms of solution delivery. The second one is more productive. everyone. The reason is the main reason is if something goes wrong in the first cycle, you have the ability, you have the flexibility to make corrections in the upcoming cycles. It brings in more visibility. Now you all can see here after every two week if I'm sharing something with Anurag, Anurag has more visibility. Anur is not waiting for 3 months to get over to look at what what's the product, what it looks like. Every two weeks he's getting some flavor of the solution. Every two weeks he's getting something to test and analyze. He can come up with his continuous feedback. He may come up with his comments. He may come up with sort of plan to make certain improvements. That way it helps us come up with a rapid delivery, a quality delivery and more you may say ability to negotiate, ability to adapt and this way it helps us come up with a better quality solution. Now everyone this two week cycle if it is consistent throughout the release plan there is name given to it. What is the name given to fifth iteration everyone? This fifth iteration that we're talking about what's the name given to it? Fifth iteration. A sprint is the right answer. A sprint is the right answer. everyone these fixed iterations of 2 weeks this is your sprint now I'm not saying that it's always two weeks you may customize it in your project and make it one and a half weeks or something like that so let's see how it is created so in your Jira in your Jira everyone you all can see I have this backlog here and in my backlog you all can see here that I just remove this and start from the scratch. If you see if I delete this, I have an option of button to create the sprint and it says add dates. Now sprint number one duration if I make it as two weeks and update you all can see here that two week cycle we have here and then if I create another sprint so this will be another sprint it should reflect the dates let me make it as 2 weeks the starting date today and update okay it should reflect the date not sure why it's not but it should reflect the date here. So you can see a sprints are created with a given dates here. So this concept of the sprint everyone helps us divide the release into smaller short iterations. Yes is and this is a very good thing that Vishi is asking. Bish is saying that is adaptive something different from the predictive in terms of the SDLC? No. The same thing is followed. It's a release within a release which is the same thing is followed in agile as well. But the only thing is the main important difference is the requirements gathering that we're talking about is not gathering the complete requirement. Adaptive comes up this concept of partial breaking down into smaller fragments iterations. So cycle is going to remain the same but the only difference is it's not the complete requirement. You are going to gather the requirements for sure. You are going to talk to the stakeholders but not on the complete thing but on the partial things that makes this approach flexible. Okay. And then one very important thing is that BA is not going to analyze the things in the sprint. A sprint is for the technology and testers to work. Your analysis must be ready before the start of the sprint. So, BA never works in a sprint. BA always works in the release cycle. Okay. Pages and others I making sense to you all. So, BA is not working in sprints. A sprint is not for BA to work. BA should be ready with his or her solution before the start of the sprint. BA is analyzing the things concerning the whole release plan and then it's for the team to divide to smaller chunks and prioritize it. So if I go take you all back to your first point, it will make more sense to you all. If you look at first point especially than everyone else solution definition defined before implementation to maximize control and minimize risk but here solution is not the complete solution. It's a partial solution define iterations to arrive at a best solution or improve an existing solution. Is everybody now able to understand point number one? Yes. Is everybody able to understand this thing? Example as I mentioned example can be let us suppose I say you are developing canteen ordering system. Yes you're developing canine ordering system and it has several requirement components to create a login page. Food menu payment gateway. Yes, food delivery feedback. If you are in the predictive world, all these requirements, those are prioritized for the release must be closed first. You should come up with the solution, get the sign off and then you'll start with implementation. But but in the agile world even if you have got this sign off on the login page feature you may start with your development getting my point with another. So difference is here even the partial sign off may help you start with your development but in the previous one the complete approval and sign off was required to start to start with your to start with your implementation. So it's defined before implementation is solution. But here it's not about defining the complete solution. It's about some part of the solution discussed and agreed and you may start with your are you with me vij and others. So the important thing here is that the important thing is that let me talk about the risk as well. The important thing here is this is a very rigid approach. rigid in the sense let me let me take your back vision you have a very good question let me answer this so software development life cycle was religiously followed in the waterfall methodology why the name waterfall everyone and here the name is agile can anybody anybody guess why the name was defined is waterfall for the predictive approach. Waterfall because what? How water falls? What what's the flow? Water falls from the high altitude to low altitude. Yes. It will go with gravity. Yes. High to low. And it has so many steps. Imagine. Imagine Anurag and Kitika are the two business users and Vijayra was the BA gathering the requirements from them and they provide some sign off here. They say okay we give you a sign off start with the development. Anurag and Isha. Isha are the human beings. They are not robots. And it may be that Anra has given this sign off. But then later he thinks that he wants to add few more things. It may happen. Yes, Anurag and Isa. It may happen that Anurag and Isa change their mind and they want few more things or they want to exclude few things. They have given the sign off but that sign off doesn't mean that it's the end of the road that you cannot make changes. It may be that want something new or want to delete something and there problem starts to happen. There was no scope hardly any scope of making changes to the already ex you may say agreed upon requirements of the corresponding solution. changes was not welcomed here. If there were changes, yes, you cannot change things in between. If there were changes, you are requested to create one change request and this used to be prioritized after 3 months. Imagine, imagine if an has missed something during a sign off as a business user, he has to wait for 6 months to get this thing and a 6 months time in the modern day agile. Do you think anybody is going to wait for 6 months? No. No client, no team. In 6 months there's a lot of change. Yes, you may find in 6 months the complete development team has switched to another company. You won't find the same developer that was there 6 months before. Yes, if you if you look at the trend earlier people used to spend 15 years 20 in the same company but if now if you talk to people the young blood they'll say in last four years I said 11 companies but that never used to happen 20 years back yes what is happening everyone the thing is we are in the adaptive world yes it's about the rapid delivery of the software the quality delivery and that's why the traditional approach traditionally yes constant change and and the ability to handle that change that makes this approach more fruitful more you may say acceptable to everyone yes Vend are you getting the answer to your question are you able to understand this thing with the help of example that I shared with you all so the example is if you come up with a complete solution first and then try to implement it it's the predictive approach but if you're able to that the partial sign off on even some part of the solution and if you're able to start with your implementation it's you are working in the iterations the small cycles the small parties within a given release second point everyone is the very important one and that is level of formality everyone now today I remember somebody was mentioning that we talk about FSD SRD SRS and I said no the reason is if you look at the second point you'll get the answer some I'm not able to recolct the name was that you p somebody else who talked about FSDS today so you can see here formal information is captured the standardized template in the old word example FSD, SRD, SRS, even the BRD. I add BRD to this list as well. But now in the agile world, they're using this new terminology and that is the light weight documentation. I remember when I was new to the analysis world I'm talking about 2008 or 9 in those days when we used to create the FSDs this used to take more than 2500 pages use case documents more than four to five pages long and nobody's reading it everybody is scared to see such a heavy textual document but just for the sake of SOPs we were doing it but now those FSDs, SRDs, SRS have all been replaced with the lightweight documentation using tools like Jira, Azure DevOps. Even some of you would be using Rally as well, Trello. These all two helps us create some short crisp and you may say lightweight documents like epic features stories. So now it's more informal approach in the agile world. Okay, is everybody with me? That why we discussed about these stories and why we never talked about it because this is considered to be comprehensive document heavy textual documents and in the agile world this is not required some of my learners asked me this question that are you in favor of this thing do you think it's a good practice I don't think so I feel that these documents should still be created completed but the problem is you don't have that much of time in the agile world to write those comprehensive documents. These document used to help us in knowledge transfer, understand the things better, know all the important protocols. But now since we in the agile world, everybody is demand to develop a better software rapidly of the software. So these dos are no longer significant. It's all about creating some short crisp documents using the tools like Jira, Azure DevOps and others. Yes. Everyone is everybody clear this the second point level of formality. So in simple terms the protocols the SOPs the standardized templates are getting replaced with lightweight documentation. Comprehensive documents are getting replaced with some small short crisp documentation documentation. Any question from anyone? Is everybody clear with this thing? So that's why it's an important thing for BAS to know how to use the tools like Jira, Azure DevOps and web. In our first session, we have discussed about this thing on high level. In our sessions to come, we'll talk more about Jira. How to create the Jira dashboards, how to write your stories, how to link them with features and all such things. We'll discuss how to manage the backlog, how to prioritize it. All such thing we discuss using Gen tool. Third point everyone is about the activities. Very similar to solution definition. Same thing goes with activities as well. Activities required to complete deliverables are identified first. Very similar to solution. All the activities have to be defined. But here it's not important to define all the activities. Activities are again divided into small iterations with deliverables first and then associated task are identified. So even activities are not completely defined here. activities also in the short iterations based upon the solution that we have. So that's about the activities and the last thing is here past or perform specific phases. Phase can be of 3 months, 6 months, even one year. But here we have iterations. those babies from one week to four weeks something in between. Ideally in most of the projects you follow 2 week situation. Okay. So this is a complete you must say set of uh differences on your screen. I request you all to read through all the uh four differences and let me know if you all have any question. Third point. Okay. Let us suppose I say let us suppose I say is we are talking about one activity and one activity is let us suppose I say I'll make very simple for you all if I say your solution is can order system this is what you have to create activity is to come up with the more simplified solution and here in the predictive approach what you'll do is you'll come up with WBS work breakdown structure and decompose everything login page email address user ID password one time password, department and other details. First breakdown. Second breakdown of the food menu, all the food items. Third about your payment gateway, all the options. Fourth about your food delivery, all the options. This is how you come up with the you may see here activities required to complete deliverables are identified first. This is how you'll come up with the things in the waterfall board. You define all the activities here and then you start with the development. But in the adaptive world, this is not required to have everything. Let us suppose you're prioritizing login page in the scrum sprint one. You just need these details to start with. In the second sprint, you'll need these details. So, it's not required to have everything before you start with the development. Whatever you prioritize as a solution, for that thing, you'll need the set of activities. Are you with me everyone? You don't need the full activities. You don't need the complete list of activities. You only need the activities those are pertaining to those are linked with the partial solution that you're going to implement. Okay, are you with me everyone? So activities are also you may say partially prioritized not the full set of activities. That's how we work in the agile mode. In simple terms, it's about partial delivery concept wherein you break down the requirements into smaller chunks and work in an incremental delivery. Incremental means step by step, one by one, not everything in one go. Okay. So that's about the activities divided into small iterations with deliverables first and then associated tasks like you all must have seen this thing that now in the agile mode in the user stories we have an option to add the subtasks. How many of you are doing it? Subtasks are nothing but the activities those are within the given solution. Yes, getting it. And I saying in planning are we not going to break down and then prioritize? Yes, you are going to break down. But in the predictive thing, full breakdown. There's a difference here. It's a full breakdown and here it is partial breakdown. Partial breakdown everyone helps you prioritize a smaller things a small little things in the first few weeks. It's not about the full breakdown full solution and then implementation. No, you are coming up with an incremental delivery and and others. So breakdown is not the full breakdown. It's about the partial breakdown based upon the solution partial solution that you have prioritized and accordingly you work. Yes, you're working in bits and pieces. That's the you may say the good thing with adaptive work. Getting my point? Yes. So it's not about like I'll give you one more example in in when I used to be uh like if I take you all back to the year 2012 when I started as a trainer in those days what used to happen that when we used to start with the live session sorry I used to tell my learners that today we'll discuss these topics and we'll target to closed in today itself and this chat box was not there. We used to have the traditional Cisco application Webex if you all have heard of. In WebEx, we have an option to of Q&A and what used to happen I used to continuously speak for 2 hours and after 2 hours I used to open that Q&A when all the questions were listed and then I used to go through those questions one by one. But now you see the change I haven't mentioned that which all topics I covered. I just mentioned this is the topic for today's discussion and then you all are coming up with your questions parally. What is happening? This is the agile training as well. Yes, we're not focusing on the whole thing. We are just focusing on one thing at a time. People gaining agreements. We are resolving conflicts, building consensus and then moving forward. That's a good thing with agile everyone. Yes. So it may be difficult to decide on the timelines. No, let me make it very clear planning. When we talk about the adaptive war, it's part of your planning that you decide before the start of the cycle what is going to be the duration. Like for example, if I say release one and we decide together as part of the management team that for this release we'll have 2 weeks iteration. This is going to be fixed throughout the three month cycle. If you're not able to deliver something within a sprint, it may be like pushed to the next sprint. So we have this flexibility. It's not like if you promise that we'll deliver something and we're not able to then there will be penalties. No, you have come up with certain estimates you'll try to complete it. If not that's push to the next next sprint. Yes. So it's not difficult. It's very planned approach. It totally depends upon how management decides how to size these prints. Usually you'll find 2 weeks duration but in few projects it may extend to 3 weeks 2 and a half weeks based upon what management decides. Yes. But what agile community suggests the ideal duration is of 2 weeks duration. Okay. Yes. Anna, Isha, Shuangi, Pabney and others are you all with me? like we have SDLC of predictive what do we have as it's the same thing it's not something different you have to first you have to if you look at the differences in SDLC also what you were doing you first gathering the requirements then development the same thing happening agile mode as well but the only difference is that it's not the complete solution it's the partial solution Same thing is there in agile as well. It's a release within a release but the only difference is the only difference is the the partial release part of the solution not the complete solution. Okay. Yes. More details we'll discuss today. But the first thing is Shivang and others are you all clear with this table that you all see on your screen. Is everybody clear? If they ask you this question that what are the activities, what is the timing, what is the level of formality, would you be able to answer such questions? Yes Shang and everyone else. So this was about everyone. The first thing the first thing as part of PL business analysis approach is yes value saying solution updates then development also updates definitely yes. So as as you come up with the new solution the development is also going to increase and by the end of the release you'll have the complete solution ready and the complete you may say development being done. So that's how it works in agile the partial release concept the iterations and the incremental delivery. Yes, everyone. Now, yes, correct. Now, everyone, I have one question for you all, Shivangi and everyone else. Let's dig deeper into this thing. And my question to you all is in your slides theory elements Aki Pi and everyone else based on a discussion IBA should have mentioned that planning methods are of two types predictive and adaptive. But to my surprise but to your surprise they have mentioned falls between Aki, Pagni, Shivangi, Gajula, Isha, Yusha, what do you all think? Hannah, Rafael, what do you all think is the significance, the importance of these two words falls between? They should have simply mentioned that planning methods are of two types predictive or adaptive. Why they are saying planning methods fall between predictive or adaptive? Any guess any idea? It's a very simple question to answer. won't fall between signify anyone not the requirement something else lawyer saying we typing we know the answer it's a basic one yes is coming up is a very good answer this simply means it's not something in black and white. There may be few things in gray as well. Yes, not simultaneously, but there can be a mix of the two. Law, you are still typing. Okay. So, so the answer is answer is This is the hybrid methodology. Like if I tell you about my project, we have fully transitioned to agile ways of working. But since I am the product owner, I come from a traditional background. So I always ask my team to create the BRDs. My BS tell me that in the next team and other team people are not creating it. I think they're not creating it but we'll definitely create it because this always helps. So what we doing here? We are into the agile methodology but we're also accepting some good practices from the old world. And this is a mixed bag and this makes it the hybrid methodology. Some of my learners told me I don't know about you all but some of my learners told me that in their project they still create the use cases and based on the use cases they then create the user stories or location use case is not at all required in the agile world but they are doing it because there may be few people like me in the other projects as well who are from traditional background and they and and they prefer this thing. Yes. So this simply means Shivangi and others very basic thing that it can be in any project that you're following the traditional ways of doing the things. It can be that you have completely switched to the new ways of doing the things and it may be that in your projects you have somebody like me, somebody like more as well than me and they are not able to forget. They're not able to absorb and accept all the new changes and they still going with some old traditional ways of doing the things that makes your planning methods hybrid. Yes. Law is saying you old people are not able to adopt the new things. Yes. It's it's not about accepting the new things. It's about recognizing there was good things in the old world. Yes. You cannot simply say this is a old blood and replace it with young fellow like Issha. Yes. All people have some good things as well. At least they're good in philosophy. Good in giving you some good lectures. Yes. So, so meaning to say planning methods can be of two types predictive adaptive. It may also be a mixed bag with a combination of good practices from both the methodology. And third methodology is known as hybrid. Yes, Shivangi is everyone else you all are with me following the significance and meaning of false between. So false between is is a combination of the two best practices from both the words combined together. Now second thing everyone is everyone on your screen formality and level of details of BA deliverables are based on the planning approach. >> Oh sorry. So we discussed this thing few minutes back that in the predictive world we had the comprehensive documents as part of BA deliverables and these are the form of BRDs, FRDS, FRS, SRS, release notes, user manuals, user guides and all such documents. But now in the agile world we have a new concept a new terminology being used and that is lightweight documentation using tools like Jira Azure DevOps and others. Yes, the AEX the stories and others. Yes. So you have a very good point here. element simply means all the important constituents or components within a given task. So if task is one then elements are like t11 plus t1 2 + t13. is is something like one task may have several elements and all these elements combined together tell you about what are you going to do as part of a particular task. Okay. So these elements help you understand what are the important activities to be performed by a be within a given task. Okay. So you in simple words kit can kind of elements are the subtask within a given task. Okay everyone now the third point everyone let's discuss this thing. Third point is and this for you all to answer it can everyone else. Let us suppose any activity is assigned to you. You all had this question few minutes back that what exactly is the activity? Any activity let us suppose I say to functionally break down the requirement is one activity. Another activity is to manage the resources in your project. Another activity is to define all the non-functional requirements. Babok guide says that if any activity is assigned to you break it down into smaller fragments into smaller task. Why do you all think it's an important thing for Kitika and others to break down the activities into smaller tasks when they plan for business analysis approach? How is that going to help you? If any activities assigned to you, if I mentioned few points, let's see if you all agree with this thing or do you all differ and you have some questions for me. We are talking about everyone the work breakdown structure breaking down the activities into smaller tasks and it has a few advantages as listed below. First thing is everyone it promotes granularity that is analysis at the more fragment or atomic level and what exactly happens every one when we're able to when we're able to decompose the things into smaller fragments we're able to gain more information more detailed view that makes the things simple to understand and then your team is going to make less number of assumptions. Did we talk about the creatively tool in our live session about did we discuss about this tool? Let me show you that tool once more. Did we ever talk about this tool in the live session? Yes. So if you see here the WBS template let me share this link in the chat box with everyone. So let me ask you to create some WBS. So you can see here there's a lot of WBS templates. So let me open one of them. So what exactly happens is like everyone when we create a work breakdown structure this would help us come up with more fragment level information that's the first thing if we have some fragment level information it will help us in task allocation that Suppose I say is a lead BA of the product owner and she's getting some requirements to analyze. She's creating some smaller features and those features can be distributed among several BS and they all are working on those features. So it also helps in task allocation and in a way makes tracking, monitoring and tracing easier and in turn this helps in delivering better quality product to their users. Third point everyone is a very important one. Let's read the third point. Third point say one analysis at the granular level helps to ensure that solution aligns with the stated requirements and this helps to avoid the scope creep condition. What happens is if you're able to come up with more simplified information, more detailed information, clear information, precise information, this helps everyone develop a clear understanding and then chances to absorb creep. Creep is any redundant, duplicate or unwanted component can be minimized. So they will ask you this question that why at all we should do this thing. This will always help us come up with more simplified solution, more detailed view of the solution, more granularities, more fragmentation and that helps to avoid any creep any redundant or any duplicate components in our solution. And fourth point is about continuing with point number three. It also helps you define the scope. This helps to get clarity on the important requirement components and in a way it will help you define the scope for the given set of requirements. Fifth point is summary of all the four points above. It says WBS promotes autoomicity. Autoomicity is all about regularity, fragment level information, low-level information. So this is how point number three helps you in coming up with more accurate solution without a redundant or duplicate components. So I request you all to please read all these five points on your screen. I'll take a pause here if I have any question we can discuss else we'll move to the next point number six is about three important techniques we'll discuss in the sessions to come like functional deco composition requirements disability mind mapping these all are going to help us perform WBS in a very organized manner after each sprint it will go to development not all if it is all then it is your waterfall if it is each it is your agile okay gajula so that's a good thing with agile that After each any one you're done with sprint number one you you're done with your development you'll go to the next one. So every sprint you'll find the development as well as testing to come up with a partial solution not wait for all the sprints to be done. A sprints are meant for development and testing. The scope clip we had discussed the previous session as well. Let's discuss this in one more time. Whenever you find everyone whenever you find and you have a good question and the answer is it's not documented it's visualized and you can see here all these templates Anna here so WBS is generally visualized and you can see all these templates let me share this link once more so WBS is generally in the form of a block diagram a chain diagram kind of an organizational model sometimes. So it is generally visualized not docu you can document it for sure but the better approach will be you create some block diagram like this. Yes, Anna coming to your question projector here. A scope grief simply means when your solution has certain redundant or duplicate components. For example, let's take one example. In your hospital management system, you have one important feature. Book an appointment with doctors. Projector is filling this form and she is getting an option to select the doctors from the list of doctors. Here you select one doctor book an appointment but when you reach to the OPD when you reach to the hospital you find that this doctor is no longer impended. He resigned from this organization from this Mayo Clinic two months back. Now Rajetta is frustrated. She is not happy. She is saying that I have traveled 15 kilometers to consult this doctor and he is no longer impended. Why you have not shared this information with me before? So Raja imagine if you are a B how you would correct this problem? What you'll do then as a BA you'll ask your development team that in the database add one flag as active or passive and only active doctor should be displayed on the screen yes or no if somebody has left the flag should be P for him if somebody is active is the flag should be A and that way you'll be able to ensure that there's no scope creep and why the scope creep is happening. This scope creep is happening because you have not come up with the detailed information. Update the list. Yes, update the list so that you have the active doctors in the list available here and there's no one who is no longer impendent appearing in this list. So a scope level one is when unintentionally or intentionally you find there are few things added to this solution and that's causing noise that's causing chaos and confusion that's not required but it's part of your solution. Yes. Why send notices when a doctor leaves to re they should do? Yes. And hide those things is mentioning. Yes. Hide those things. If somebody is passive is her name should not be populated. It's a very simple. If you have to write this code in Python or in C# it's very simple. If an else statement you have to write and this helps you come up with this refined set of list. Is everybody clear with what is scope creep? So scope creep is everyone I have written the definition here. Let's read this. A scope creep is when solution grows larger in size and accommodates a few unwanted duplicate and components. This cause components outside the solution boundaries to penetrate and become part of scope requirements. Examples of a scope creep everyone in HMS a list of doctors at Mayo Clinic include some doctors those are not impendent this is redundant information scope keep in ordering system yes Vina very good answer here Vina is saying that scope creep to prevent scope creep Yes, I'll add just prevent to prevent scope creep is about avoiding any redundant duplicate or un unwanted information or any unwanted component. Yes, it's all about wrong, unwanted. Sometimes information is correct but it's not valuable. then as a winner we have to remove those things. So it's all about the requirements that add value to your solution. Yes, sometimes what happens is we add a lot of things and those are not adding any value. Those are also redundant. Those are not wrong but redundant in nature out of scope requirements. Yes. In canteen ordering system, employees of nearby offices ordering food is again the scope creep. Okay, is everybody clear with the scope creep? When I when ask questiona are you clear with what is scope creep and how to avoid a scope creep? You'll be able to avoid a scope creep if you're coming up with more detailed analysis. You've done your proper research. you have factual evidences to you may say um support your arguments. So this is about everyone the WBS very important thing you all can use uh this these templates to come up with the WBS. Now I have one homework for you all. I hope you all have got access to the project LMS ordering system library management WhatsApp pen HMS. Yes. Now and others the homework for everyone is in your projects there's one task here. Write down the main feature that needs to be developed. Please check and confirm everyone. Is everybody able to find this task in your projects? Write down the main features that needs to be developed. Now you all have to use the WBS template something like this. You can use any tool of your own choice and then come up with a functional decomposition and in tomorrow's session during Q&A you all can share with me how you have worked on this task and if you have any question we can discuss. You just simply need to let us suppose I say I'm talking about the HMS. So for the HMS this is the first level. Next level de composition can be patient registration, appointment with doctors. What else? Lab tests, medicines. What else? Your billing. and then decompose this one. So this way you all have to create one WBS for the task that you have in your projects. Is everybody fine with the homework? Any questions on the homework? Write down main feature that needs to be developed. And it's a common thing in each and every project everyone in WhatsApp page you'll find it as task number seven. In HMS you'll find it as task number five. Okay. So work on this thing and then you can share your findings, your analysis whatever you have documented in the tomorrow's session. That's the homework for you all. Next thing everyone is the timing for the business analysis task to be performed. So timing as we have discussed in that table that timing is in the form of phases, this can be of 3 months, this can be of 6 months. Yes. And timing in the agile world is in the form of iterations. Now everyone let me make it very clear to you all one more thing here. Sometimes they ask you this question in job interviews. They ask you is iteration equivalent to sprint? Answer is no. If let me explain this thing. If iteration is of fixed duration, let us suppose I say in this 3 months cycle I divide this into two week cycles or 3 week cycles or four week cycle. If I have four week cycle then I'll have just three sprints. If it is two then it will be around six sprints. If this remains constant throughout the cycle this fixed iteration is known as a sprint. But let us suppose I say my iteration one is of 2 weeks duration. Iteration two is of just 5 days or you can say simply one week. 1 week is equal to five working days. Then 1 and 1/2 weeks then 3 days then 2 days. This is not fixed and when it is not fixed these variable iterations are not sprints here we come up with the terminology as wip work in progress and when we have such iterations everyone in any agile project such agile project is known as canburn And this one is known as scrum. And that's why if you all remember when we were creating the credentials on Jira, I requested you all to select scrum and ignore canban. The reason is canban is more for defect fixing production support and short duration projects. Is scrum is more popular agile approach. The reason is it helps in coming up with very organ structured development since we have fixed iterations in the form of sprints. So that's about the timing for the business analysis task to be performed. The next one next important thing is the techniques. Now elements we have discussed now how to accomplish the things how to work on those elements we have few important techniques here today we're going to talk about one very important technique very popular technique and a very important one and that is process modeling first we'll talk about brainstorming as well but first We'll talk about the very important one and that is process modeling. for process modeling. Everyone nowadays we have some very popular notations that we use a very popular way of creating a process model and that is using the BPMN. My question to you all is what BPMN stands for sorry and what exactly BPMN signify everyone? This question only for those who are using BPMN in their projects to create a process model. What BPMN stands for? First question for everyone to answer. PP MN BPMN is if I say this PM is process model then what is B? What is N? Yes, PM here is process modeling. and B stands for business. N stands for notation. So business, process, modeling, notations, all those important symbols, images, icons and all those important things those may help us create one advanced flow diagram. Process modeling is about how well we are able to identify all the important process components from the inception till the completion and how well we are able to arrange them organize them in a sequence that makes complete sense. So let's look at one standard process model. Let's look at the BPMN diagram and that is your sim lane diagram. First we'll look at the sim lane diagram from the bop guide and then we'll try to draw this using some BPM notation every so let's see what is a symbol diagram and why it is so popular. So I'll take you all to your web guide technique section starting with P process modeling and let's look at the sim lane diagram. This is the sim lane diagram on your screen everyone. I hope it's clearly visible to everyone. Sim lane role one sim lane ro two. Is that clearly visible to everyone? Let's first try to understand why the name simil and then we'll try to decode what's mentioned in this diagram. Okay. Let's first try to understand why the name simil. I'll make it very simple for you all to understand this thing. Let us suppose I say this is one swimming pool. This is our swimming pool and these are the three lanes in this swimming pool. Lane one we have web the trainer law as one of the learner and we have web is swimming in this lane. L is swimming in this lane and Kika is swimming in this lane. Weber finds that law is very proactive. Law is swimming at a very swift and very high pace and law is swimming very swiftly and he'll eventually win the race if he's swimming at the same pace and velocity. Vab is the old fellow. What he does is he is crossing the lane obstructing his path confusing law here and reaching the destination first. This is confusing law this is also confusing critical and eventually webber is reaching destination first. If I go with the normal the general rules in any swimming competition, if there is one referee or if there's somebody who is watching this game, do you all think Weber would be declared a winner in this case? No. Why? So why do you think Weber is not the winner? Weber would be declared a winner. He is doing cheating. He is violating certain rules. If I talk in terms of process, if vab is process number one and law is process number two and kita is process number three. VAB is bringing about a change. He's switching from this position P1 that is suppose X1 to X2 but at the same time is causing certain adverse impact to parallelly running processes that's why he is rejected or disqualified. So what exactly every what is the purpose of simulant diagram everyone law and others the purpose is yes purpose is that when you are coming up with the solution for any given set of requirements you have to also think that your system or your process is not autonomous or independent. Your system may have certain important integrations. Your system in most of the cases is linked to other systems like Rita is talking about cross system crossunctional and there may be several things linked with your system. So it's an important thing that you do proper impact analysis and ensure that when you're bringing about the change it's not causing any negative impact adverse impact to the parallelly running processes or the subprocesses that's the intent that's the importance of simulant diagram everyone is everybody able to understand this thing or do you need some more examples I can give you all some practical examples. Yes, definitely. Yes, we have the lifeguards uh in the in the in the Yes. Let's let's let's just talk about those uh let's talk about what law is saying that do you have the life guards here or do you have certain important restrictions to do this thing? Yes, let's talk about those things now. searching the doors. Let's let's take one very simple example from my project and see if that makes sense to you all. I'll give a simple example. So in my project, we have one registration form that we generally ask our users to fill. And in this form we have like details like a username, the address, the age, the educational qualification and we also have like the comment section where you can provide some comments and then we have submit and also we have reset button. This is one very basic form that we have in none of our application and if I count there are 1 2 3 4 and five important fields for user entry. I was having a discussion with my business users and they said web in our application we also need one more feature and they said like we we want uh that there is one upload feature added here and when I asked them the reason why do you need this upload feature what's the context they said like we are getting some details from the users but we also need to validate Like if Sachin says his full name is Sachin Rahui. So he should upload some document then we can actually validate whether it's a full name or not. Yes. So so is that some scan copy of the documents people can upload so that we can verify at our end. So this seems logical to us. I said okay we'll implement this thing. So they said how much time do you think it will require for you all to implement this thing? So I said it depends. let me talk to our development team and then I'll answer this. When I had discussion with my development team with my uh technology manager, they said um the it it may take around 3 to 4 days to uh for us to implement this thing. So after 4 days they shared this thing with me and they said this is done you can test it and you can pass on to the testers if you think it's good and then you can share this with our users for the demo. So I was testing this upload feature every one and I tried to upload few PDFs, few images and everything and I found that performance was good. Within few seconds it was loaded and form was getting successively submitted. I was about to say that this is working fine. But then I realized one thing everyone let's focus on this point here. Then I realized that this upload button is there. But before the implementation we had the last field as comments and this is missing here. Now the actual number of fields here is four + one this upload feature I agree it should be 5 + 1. One field is missing. So I asked my developers that uh why this comment is missing? It was a very important feature for us to gain the feedback from the users. So why you have uh removed comments? So they said Baba we have not removed comments. What we are doing is we had section width defined. We have not increase the section width. We have just added one more field. As a result of that the comments is now hidden. So I said why it's hidden? It should be appearing on the screen else user will not be able to provide comments. They said this is something a mis from our end and we have to come up with the solution for it. Now the solution is either we can add one scroll bar here so that all these fields are visible or we can increase the section width. Increase a section width would make it un unstructured or make it like u a screen that's different from other screens. So I suggested them to add this call bar here. Don't you all think this should have been analyzed at there and itself or this detail should have been provided by a BA himself because due to this error due to this error everyone yes and a very good point here that who is giving a solution here solution that I'm providing here is something in collaboration with technology team a solution that I'm providing they are agreeing to it if they're not agreeing then we have to then we have to come up with another solution. Answer is not solution architect. Answer is you as a BA you are going to provide a solution and solution architect should agree with it. Architect should not provide a solution. So that's something happening most of the pro that they provide a solution and at the end they they'll blame BA that BA was not providing that's why I did this thing and BA like somebody is going to be blamed at the end. So you have to provide a solution not rely on solution architect they should just agree to what you are saying if they're not agreeing you should come up with another solution option. Now what we'll learn from this story everyone here is that when we are bringing about the change we have to ensure that existing functionalities remain intact and imagine imagine if I would have passed this thing as a product owner and testers would have found this issue. This is one important type of testing that we perform in any project. What is this testing known as everyone? When you find that a new requirement is a compromise with the existing requirement. If new requirement causes some issues with the existing requirement, what is this type of testing known as? This is a regression testing. So to avoid any regression error to avoid any bug BPMN is like a prevention better than cure you are going to find bugs you are going to fix it that will back and forth discussions to avoid all such things it's an important thing that you create a swim lane diagram sim diagram will help you understand what are the subprocesses, what are the existing functionalities and accordingly you're going to come up with the solution that's going to help you come up with the change. That's a continuous improvement not the series of bugs. Is everybody able to understand the importance of it? If theoretical part is clear, we can go ahead and draw this. Once we'll draw this, we'll gain more clarity of the work. Shall we move ahead and draw this diagram using one tool that is going to help us develop better understanding around it? Yes, Vij and everyone else. Yes. So, let's draw this one everyone now using one tool. So, today we're going to talk about the very basic tool. Very basic tool. We're going to talk about it. What is the difference between the two? We can discuss but let's first discuss about creation of it. In our live session and others will talk about seven different types of testing. Sanity, regression, integration, functional and everything there you'll get the answer to this question. But let's first create one diagram using this tool. And you all can parally draw this thing. Let me share the link. Please click on this link and I saying so lane one current functionality will be reflected and lane two will having additional yes provided provided your requirement is linked with several other systems there. Sim lane is very important to create. This will help you understand whether the new thing that you're coming up with is causing any adverse impact to the existing functionalities or even the new functionalities. Okay. So let's draw this. We once we draw this and others we'll gain more clarity. Okay. So please check and confirm you can give me a thumbs up on this link. Is everybody able to access this link? appd diagrams.net. I'm starting with a very simple tool, a free version that you all can use. Yes, especially now here everyone you all can bookmark this link a very useful tool. Why I'm saying useful? Because this can be easily linked with your Jira as well. So this can also be linked with your Jira. So that's very good tool. Now here everyone if you all just expand this advanced section advanced section 1 2 3 4 5 6th row and fourth column you'll find here horizontal swim lane like this. Please check and confirm. Just click on that link and you'll be able to drag and drop horizontal sibling on your main screen. The main widget that you see here. Yes. Let me repeat. Advanced section. 1 2 3 4 5 6 1 2 3 4. Is everybody with me or do you all want me to repeat this thing? I can repeat. If you're not able to do this thing everyone says yes, how about others? Shall we move ahead? Yes. Let's move ahead now and let's try to draw this. Not seeing advanced section. You'll see just below the miscellaneous one. General, miscellaneous and then advanced. Raf is able to see this thing. Give me a thumbs up. How about Anna? Now just general miscellaneous just below these two sections you'll find it now with me or you can share your screen with me once we are into our Q&A time. Okay, got it now. Perfect. Now you can mouse over everyone after advanc within advance 1 2 3 4 5 6th row and fourth column you just need to click here and you'll find one pool on your main screen on your main grid the way it's appearing for me. Okay. So app diagram then advance advanc group four. Yes. How to change it? You have all these options. You can plug and play with this and change it. Okay. Let's draw one thing. Let's draw one diagram here for pool. You can mention here. Double click and you can change it like today I'm doing it in ordering system lane one is about the registration lane one is registration registration lane two is about let us suppose Close the menu and then about the payment gateway registration or login simply you can say login. These are three important links. Now we have to create one BPM diagram symbol diagram. So it's an important thing for us to know what are the important BPM symbols and notations. So for that thing I'm sharing with you all one link you all can give me a thumbs up if you're able to access this link payment symbols exchange. I'm sharing this link in the chat box. Please click on this link and confirm is everybody able to access this link that I just shared with you all. Yes. Now you all can see here everyone that here it's mentioned you all can go through these videos as well. I'll just summarize. You can see here to create a BPM diagram for messaging you have to use this message symbol timers escalations conditions links errors and activities for task you have to use the rectangle for task for subprocess the dotted one transactions call symbol these all are three important BPM symbols and notations sequential flow message flow associations swim lanes start and these all are mentioned here. Groupings, data, data storage. So the homework for you all is that you all have to read through this and if you have any question you can discuss with me. Now using these symbols let's draw one diagram. So what we'll do is we'll simply go to general section and we'll use this circle because as per the BPM notations we use circle to start the process. So you can use this circle and start with login. You start first then you can use this connector with start and then you can add one rectangle like this. And here you can mention enter username. Then after username, next thing can be enter your enter password. Then the one time password. And if all this information is correct, then what we'll do is we'll add one decision box here. And here we'll mention that is info valid. If it is yes, we'll go to the next lane. And here user can view this board menu. Now you can see here I think law you had this question that do we have any checks or validation. So you can see here that before moving to food menu we are validating whether the information is correct or not to avoid any user who is not part of uni liver he or she should not be able to. What we are doing is to nullify the impact to ensure that only valid users are able to order food. We are having this important security check here. If information is valid, you're going to the next lane. And if information is not valid, what will happen is you have to enter the details again. And three times you enter details incorrectly, your access is logged. So if the information is not true, if it is no, then you're going back. If it is yes, you are then allowed to order food. And then you may add few colors to it to make it look more attractive. You can add colors and other things. Color should not be the priority. No, this is not a sequence diagram. Sequence diagram is based on UML principles that we'll discuss later as part of design. Sequence is for solution design. So we'll talk about design aspects as well. In sequence we'll talk about synchronous calls. Asynchronous calls that's completely different thing. Okay. But yes in sequence you're focusing on synchronous calls. It may look very similar to this one. But this is not a sequence one. Okay. Now everyone we have created one basic process model here. Basic simulant diagram using some some basic uh BP notations. I can show you all some sample projects. Ben learners have created some very good very attractive and some very good people diagrams. I'll just show you all a few of them if I can show you some of them here. Like if I talk about HMS hospital management system Shia story and let's see what she has done. She has created some such a brilliant one. If you see here such a good symbol diagram patients, hospitals, hospital building and look at this such a beautiful diagram on the screen. Yes, some of you would be thinking that he himself is g such a bad diagram and he's showing us some good diagrams. Yes. So it's for you all to draw, not for me. Even here you can see such a good diagram. There's no color, there's no cosmetic but such a good diagram. Yes, Shang. Everyone else, you all have to work on this thing in your your projects. There is one task when you all have to let me see if we have a flow diagram here as well. Yes, look at this one. Such a good diagram here. Admin, user, system, and how well she has structured and documented everything here. So in your projects everyone there is one task here that talks about create a future process map. Please check and confirm is everybody able to find this task in their LMS. Create future process map. Here you all have to create one sim lane diagram. So apply the same logic that we have discussed here. You can create some attractive visuals. Work on this thing as a homework and then in our next session in during the Q&A time if you're interested you can share your screen with me or everyone else and together we can discuss on your questions if you have any around this diagrams. Learners who are planning to switch to transition to BS profile. People are looking forward to become a certified analyst. For them learning this technique is very very important to know the BPMN standards and to know how to create this simulant diagram. And also one more thing everyone once you are familiar with this thing once you know how to create this you can also add this thing to your resume that you know how to create swim lanes process models based on the BPM and conventions it is going to attract the recruiters for sure everyone companies are looking for the analyst who are knows how to work on these process models it's an important Okay. So for now you all can focus on this tool that we have discussed diagram. In our tomorrow session we can talk about the lucid chart or other other important tools where you can easily create certain attractive sim diagram. So there are few more software that we can talk about like lucid one. Let's see if I have the access of now. I can show you all few lucid diagrams as well. Let me show you if it's there. So, Lucid also very good tool lucid chart. So, you can create the Lucid um online flowchart maker. It's a very good one. So Lucid can also mean we'll talk about it how to create simulance using Lucid as well. But first try this one app diagram and create some visuals. Simple ones everyone are let's talk about one and interesting ones brainstorming and workshops. Now I'm 100% sure that each and every learner present here all of you who have been part of brainstorming sessions and also the workshop sessions. Now everyone my question to you all is what's the difference between brainstorming and a workshop or do you all think it is one and the same thing? Those questions are open for you all to answer. Very simple technique. Brainstorming and workshop. What's the major difference between the two or do you all think it's one and the same thing? Not same. Sometime not same. If it was same then you won't be asking this question to us that much. We know now. But let us think brainstorming is about a number of ideas. Shi has a very good point. Brainstorming and you you're saying that is not an enabler is analyzing analyzing what not same and I saying workshop is demanding is demoing. Okay. Yes. demoing the things. Yes, absolutely wonderful enough. Thank you for your answer. Let me explain this. Let me explain this with help of very simple basic example and you all have to accept few things. So you have to accept that this is the brain not the pair of kidneys or lungs. Yes. So imagine if this is your brain. Difficult to believe but you have to believe that this is your brain not your brain anyone's brain. Not the lungs or your kidneys brain and this is the right side of the brain. This is the left side of the brain everyone. So what is the role everyone of the left side of the brain and how different from the right side of the brain? Why do we have this right side of the brain? What's the main function? People who are interested in biology before they became the analyst. What's the role of the right side of the brain? Right of the brain is about everyone. Anybody give an example? Right side is about the images. When I say I don't know about right, but I know about left. Left is about the analytics, maths, logic, reasoning and this is all your creativity. Yes, winner. So everything is coming from left side. What is your right side is doing? Right side is looking at the images. Colors. Yes. Images, colors. And now it is a very important thing that we cannot live with without which we'll we'll die. Natural death. Real. Yes. So images, colors, reals, what else, cosmetics, these all are part of your right side. So emotions. Yes. Emotions. So if this this this part is not functional it's fine with me. Yes Shivangi after 3 and a half hours if this side is not functioning well I'm fine with it. Need not to worry on this part. But this part should be fully awakened. This part should be fully active. And what is brainstorming everyone? Brainstorming is about generating ideas from the key stakeholders with the help of their lateral thinking and cognitive mind. It's the initial step to start with your business analysis work. I remember som you talked about crying today. Yes. So collaborate, talk to talk to the different stakeholders, have a discussion with them, generate ideas and those ideas may help you. Start with the analysis work. This is a starting point. Generate ideas, ask people to share their experience and all such things will be part of brainstorming and it is considered to be unstructured in most of the cases. unstructured, questions, ideas, discussion, all those things happening and the intent is to get more ideas. But here it's completely opposite. Here it's not about initializing the things. Here it's about finalization. Here it's about closure. and closure by training people by mentoring them by resolving conflicts and build consensus by accepting the feedback the review comments and making changes and then closing it. So workshop is more about the enabler. Workshop is more about finalization or a closure to move to the next thing. The workshop is more about gaining consensus. Workshop is more about the trainings, mentoring and all such activities to resolve conflicts and build consensus. And that's completely opposite to brainstorming. So that was about everyone the brainstorming versus the workshop. Last topic for the day. The last thing to discuss here is everyone lessons learned. Less law everyone is very similar to one of the agile ceremony. Gajing workshop is like generating quantity by following agenda. Not exactly generating but it's about the quantity or a quality that everybody agrees to. Workshop is more about bringing everyone to the common platform. Workshop is more about making everybody agree and gain consensus on sort of important agenda that you have already discussed with them. Okay. So workshop is more about enabler. Workshop is more about gaining consensus by providing certain training or certain important detail around the given topic. That's the workshop. Okay. Najul and others. Now the next thing everyone lessons learned lessons learned everyone is very similar to or I should say synonym to One of the agile ceremony that we are using nowadays in most of the projects. Which agile ceremony can be equated with lessons learned technique? Everyone which agile ceremony are you talking about? one of the agile ceremony that can be associated with lessons learned technique. And what are the four agile ceremonies? Everyone in agile we have the daily standups. Then we have a sprint planning and the grooming sessions. Then we have review or you may say demos. And what is the last one everyone before we close the sprint? What's the last agile ceremony everyone? This should be a simple answer for everyone. What's the last ceremony? So may just can you clearly see my screen or is it not visible feedback but feedback is given in which agile ceremony answer is retrospective. You're talking about the retrospective meetings. Yes. So lessons learned every one is about the retrospection successes, opportunities for improvement, failures, recommendations for improvement. I can easily remember since that last 30 minutes, let me share one story with you all here. When I was new to the corporate world, my very first job working as a software developer then with understanding of net Microsoft technology. So as a group we all were hired more than 15 plus developers and we used to make a lot of mistakes in our coding and programming. So our managers used to come up with some philosophical statements like if you're doing a mistake it's fine everybody is doing it it's something wrong and everybody is committing mistakes but if you repeat on your mistakes it's no longer a mistake it's a crime and you'll be punished for that. But if you still not learn from your crimes and you keep on committing it, it's no longer a crime. It becomes sin in the go eyes of God. Now if you commit a sin, we won't be punishing you. God is going to punish you. So don't go to that level. Commit mistake, it's fine. But do not repeat on your mistakes. Yes. So we look at depth of this statement. So nobody dare to commit a sin. Everybody is committing the mistake and nobody's going to the third level. So lessons learned everyone is about how we learn from it mistakes successful. What are the success we had in the current sprint or the current release, opportunities for improvement, failures and recommendations for improvement. Now everyone in your Jira in your Jira you'll find one lessons learned template so let's look at this one I hope you all have your Jira page open on top everyone on top you'll find here the Jira icon and just before that four small squares if you have your Jira page open You just need to click on this one and here you'll find one another Jira product that is confidence just before the Jira icon four four small dots or squares if you click on that it will help you toggle to confidence if you click on confidence here it will take you to the conference and here you can create a new page So if you click on click uh create can create a new page and here on a new page in conflence you'll find here three horizontal dots. Click on this one and then you'll find your templates and imports and here you'll find one lessons log template as four L's of retrospective. We can see here this template that's very popular in most of the projects. So four L of retrospective milestones loved longed for lo and learned. List what you loved about your work. List what you wished you had while working. List what you didn't like about the work. List list what you learned and these L's four L's everyone if you're able to capture then it will help you come up with a proper action plan so that you not repeat on the mistakes you're coming up with continuous improvements and you keep a track of all those unsuccessful events successful events and then come up with a strate strategy accordingly. So this 4L retrospective template they can ask you this question in your job interviews that if you have to uh organize on retrospective meeting although it's a job of a scrum master but if you are if you are if you have to organize such meeting what are the important things that you'll focus upon. So we can talk about four LS of retrospective. Okay. Navigation everyone is let me repeat to navigate to this page. Let me start from the beginning. So this is your main Jira dashboard that we created. If you're not able to find sushil under the four dots, you can go under apps. Go under apps, explore more apps and here you'll find confluence. So if at all you're not able to find it there, you can find it here under more apps. Okay. And very simple thing is you can click on these four dots and then conference here. Click on conference. Yes. Then click on create button. new page and within a new page everyone these three dots. Click on these three dots and then templates and import and then you can search here for 4 else retrospective. Yes. And also you'll find here one more template that's the lessons learned. So I'll just show you all the lessons learned as well. If we have here one more template, let me check. Just search it here like lesson. So there is no just four else we'll find it here. Four retrospective. Yes. in the top banner beside Jira four dots. Let's start with this topic now everyone. The topic is plan stakeholder engagement plan and approach for establishing and maintaining effective working relationship with the stakeholders and how you'll do that. Yes. Yes. You can come with your question and how you'll do that by identifying the stakeholders and analyzing their characteristics. When you identify the stakeholder when you try to identify the stakeholders and analyze the characteristics this combine together this combine together is known as something is known as stakeholder analysis in question for us is stakeholder register is what to use to get. Yes, you can maintain a stakeholder register. You may also if you all recollect if you recolct in the BRD that we had discussed last week. If you all let me share the link once more with you all in the BD that we had discussed last week. You all can click on this link and confirm if you're able to access same B that we discussed last week. You all can see here even in the BRD we come up with one important section as approvals. So what exactly this means? You have to maintain some somewhere the details who is authorized to provide the sign whether you need the approvals from project sponsor, business owner, project manager, system architect, development lead, user experience lead, quality lead or the content lead. So you have to list down all the key stakeholders and then see who all are required which all the stakeholders are going to provide the sign off. Yes. So and today we'll talk about it how to create the AC matrix the stakeholder matrix the Nian diagram those all things would help you understand how to perform a stakeholder analysis how to identify the key stakeholders and then and then come up with the plan to define the decision making authority law and others in our Babai Just after the stakeholder engagement, the next task in the list is governance. To your question law, the answer lies in the governance model of the project. We'll see here while planning the governance approach. You can see here who has the responsibility for analyzing the change request. Who has the authority to approve the changes and how changes will be documented and communicated. These all things are done as part of the governance approach. Yes. So you can even say this thing that who is providing the sign off this depends upon the business analysis governance. In the governance you'll get to understand that who has the authority to approve the changes. Not everybody in the team can provide the approvals. Not every business user is authorized to provide it. Yes. change board what Anna is mentioning here is the right answer you can get this information from the change board or even register that law is talking about so the moral of the story Anna law and other says you have to identify and define the authority who has the authority to provide the sign off that's an important thing if you are clear with this thing we can move ahead. If you need some more examples, I can give you all a few more examples to understand this thing better. Is everybody clear with this thing? If they ask you such question, how you are going to answer them? Yes. So the answer is the moral of the story is don't do not name anyone like PM is going to approve it or sponsors. come up with more organized algorithm that will check who are authorized to provide the sign off which all the stakeholders are part of decision making authority and accordingly we'll reach out to them for the approval. Yes. Yes. A very good point here that who will decide and how will how will come up with the business analysis governance. Yesterday we had discussed this thing. If you look at the governance 3.3.7 is the stakeholders. So in order to come up with business analysis, governance model, you will have a discussion with the domain subject matter expert, project managers, regulators and the sponsors. These all stakeholders are going to help you come up with the business analysis governance. Yes. So those the list of approvals, the level of approvals, the plan for approvals, those all details you'll get from business analysis governance model. Okay, getting my point? So that's part of the business analysis governance. Our next topic once you're done part stakeholder engagement. Yes. So and that's a good discussion that we having at present. Thank you everyone for your participation. So it can it encourages me to cover the things in detail here. So projects you're coming up some very good questions here. The answer is the proper governance would always help you understand which all stakeholders are part of decision making authority which all stakeholders are authorized to provide the sign off and then accordingly you may reach out to them to gain consensus approval sign off and then you may start with the implementation. So what is the next topic? Then we'll talk about these things in detail. Yes. So coming back to our topic here everyone we're talking about stakeholder analysis and the stakeholder analysis everyone includes identifying the roles the attitude. attitude is about your behavior or your responsibility responsibility or your behavior decision making authority level of power or influence of the key stakeholders sometimes I get this question from the learners that what's the difference between power and decision making authority can anybody answer this If let us suppose project and and vijendra are powerful and influential stakeholders in any company and vijendra and are the decision makers. What's the difference between the two? What's the difference between a powerful or influential stakeholder as compared to a decision maker or or do you all think it's one and the same thing? Anna is saying power can change the decisions being made. It's a very good answer. Thank you. And now Vij is saying he can influence the decision making but has no authority to do it officially. Absolutely wonderful vision. Yes. There is a wonderful art source. I don't need to explain more now but let me make it very simple for people who are new to the analysis world. Let us suppose I say I'm talking about company ABC and handling the project XYZ ABC company CEO CFO board of director or chairman these all are powerful and influential stakeholders. But if I say in XYZ we have one product owner or a project manager providing the approvals of the requirements. These are the decision makers here. They are the decision makers. But what Anna is mentioning here powerful means that they can turn their decision. They have this power but most of the time they not get involved in these activities. So that's the difference between the two. Everyone decision maker is somebody who having the authority to provide the approvals of the signs. Yes, everybody with me on this thing. So when you perform a stakeholder analysis we have to identify the decision making authority level of power and influence of the key stakeholders role and attitude. >> You all can make a note of this thing mark with the nastics learners who are preparing for j