Business Analyst Training Full course (Step by Step Guide ) ( 100 % free course )in 10 hours

Summary

Highlights

• Pradeepa kicks off a comprehensive guide on business analysis for all aspiring analysts. 🌟
• Explore various methodologies: waterfall vs agile, understanding each one's unique applications. 🔍
• Delve into the daily responsibilities of a business analyst, emphasizing both technical and non-technical skills. 🛠️
• Learn how to effectively gather requirements and manage stakeholder expectations. 📋
• Practical case study: Developing open EMR software for healthcare, from requirements to user testing. 🏥

Key Takeaways

• Master the basics of business analysis with Pradeepa's free course. 🚀
• Understand the role differences between IT and non-IT business analysts. 🧑‍💻
• Learn how to create user stories and test cases efficiently. 📄
• Explore the business analyst's role in both waterfall and agile frameworks. 💧
• Gain insights from real-world projects like open EMR to boost your resume. 📈

Overview

Chapters

• 00:00 - 01:30: Introduction and Greeting The chapter titled 'Introduction and Greeting' begins with a morning greeting and confirmation of the participants' ability to hear the speaker. The speaker, Pipa, thanks everyone for joining the session. She announces that the day's learning will cover the basics of business analysis and mentions that the course will span over ten days.
• 01:30 - 03:30: Course Overview The chapter provides an overview of the course, introducing Pradipa, a senior business analyst with 16 years of experience in a Fortune 500 company. Pradipa's goal is to guide individuals aspiring to become business analysts. The course schedule includes daily sessions from 7 to 7:45 a.m. USD time. The introduction sets the foundation for what students can expect to learn from Pradipa's guidance based on her extensive industry experience.
• 03:30 - 06:00: Business Analyst Roles and Responsibilities This chapter introduces the role and responsibilities of a Business Analyst, starting with addressing common questions around the motivation for choosing this career path. It discusses whether individuals from various backgrounds, including non-IT, can pursue a career as a Business Analyst. The chapter aims to clarify the initial steps and considerations for those aspiring to enter the field.
• 06:00 - 12:00: Understanding IT and Non-IT Backgrounds in Business Analysis The chapter discusses the global opportunities for becoming a business analyst (BA), regardless of geographical location, such as the US, UK, Australia, New Zealand, India, or Bangladesh. It highlights how both service-based and product-based companies hire business analysts and the presence of BAs in various domains like healthcare, banking, and retail. It also touches on how individuals from non-IT backgrounds can transition into business analysis roles and succeed in the field.
• 12:00 - 19:30: Business Analyst Job Market and Industry Insights The chapter delves into the Business Analyst job market, focusing on industry-specific roles such as Pega, Salesforce, and Guidewire Business Analysts. It emphasizes the importance of becoming an expert in these technologies, which are likened to advanced Java languages. The discussion covers the foundational skills required to step into the Business Analyst role and illustrates paths for scaling expertise in these specific platforms.
• 19:30 - 26:30: Service-Based vs. Product-Based Companies The chapter discusses the journey of becoming a lead or senior business analyst over a period of five to six years. It emphasizes the importance of self-assessment, noting that individuals may start at various levels of expertise. Some may be beginners, while others may possess domain knowledge but lack proficiency in certain areas like language, coding, or business analysis skills. The focus is on understanding one's current position and the skills needed to advance in the field.
• 26:30 - 30:00: Domains in Business Analysis The chapter "Domains in Business Analysis" discusses the various career paths and roles one can undertake in the field of business analysis. It highlights different positions such as IT professionals, testers, developers, engineers, product owners, and scrum roles, emphasizing business analysis as a viable career option. The focus is on understanding the reasons for pursuing a career as a business analyst and the skills necessary to succeed and progress in this domain.
• 30:00 - 35:00: Resume Writing and Skills Enhancement The chapter discusses various career paths in the field of Information Technology (IT), emphasizing that one can choose to specialize in different areas such as becoming a project manager, a developer, or delving into testing roles. It highlights the options within testing, where one can either focus on manual testing or pursue automation testing. The key message is the diversity of career options available in IT, allowing individuals to tailor their career paths according to their interests and skills.
• 35:00 - 51:00: Difference Between Pega, Salesforce, and Guidewire Business Analysis The chapter delves into the various career paths available for engineers, highlighting options such as becoming a Java engineer, a .NET engineer, a Pega engineer, or a Salesforce engineer. These roles are essentially different types of coding professions.
• 51:00 - 70:00: Business Analysis Techniques - SWAT Analysis The chapter titled 'Business Analysis Techniques - SWAT Analysis' discusses the primary responsibility of a Business Analyst (BA) which is gathering requirements. It emphasizes the creation of Business Requirements Documents (BRDs), Functional Design Specifications (FDS), and System Requirement Specification (SRS) documents. This approach is termed as 'pure vanilla' business analysis, which focuses solely on requirements gathering and documentation, without involving in testing or extensive IT work.
• 70:00 - 88:00: Business Analysis Techniques - BPM and Process Models The chapter discusses two levels of business analysis: the first level, which involves gathering requirements and writing in an AEL environment, and the second level, which includes writing user stories and end-to-end documentation such as data flow diagrams. It emphasizes the technical knowledge required to understand how applications interact with each other and the overall data flow between them.
• 88:00 - 114:00: Business Analysis Techniques - MosCoW, Use Case Modeling This chapter discusses the various roles and responsibilities associated with business analysis techniques. It highlights the collaborative nature of the role, focusing on tasks like drawing up specifications and conducting testing such as UAT (User Acceptance Testing) and SIT (System Integration Testing). In cases where there is no dedicated testing team, the business analyst may take on additional roles, effectively functioning as a system analyst to aid in the testing processes. This integration of roles ensures that business objectives and user requirements are thoroughly met and validated.
• 114:00 - 123:00: Business Analysis Techniques - PESTEL and CATWOE Analysis The chapter discusses different types of business analysts, particularly focusing on the pure vanilla business analyst and the system analyst. The pure vanilla business analyst is primarily responsible for gathering and documenting requirements without involvement in testing. In contrast, system analysts engage in gathering requirements and writing user stories, especially in an agile environment. The chapter highlights the separation of roles and responsibilities within business analysis.
• 123:00 - 138:30: Agile Methodology and Documentation The chapter 'Agile Methodology and Documentation' focuses on the various aspects of Agile processes, particularly in relation to documentation. It discusses the role of documenting through diagrams, test templates, and test plans. The chapter highlights the importance of assistance during different testing phases such as system acceptance testing (SAT) and user acceptance testing (UAT). It emphasizes a holistic approach to business analysis, detailing how one should not only gather requirements but also understand the entire application workflow, and define user stories effectively in an Agile environment.
• 138:30 - 160:00: Case Study: Open EMR Project Overview The chapter provides an overview of the key skills and processes required in business analysis and project management within the context of the Open EMR Project. It emphasizes the importance of clear communication between requirements and implementation, guiding the developer to understand and build the requirements effectively. It covers the creation of data flow diagrams, developing and executing test plans, and conducting testing in both System Acceptance Testing (SAT) and User Acceptance Testing (UAT) environments. Furthermore, it discusses obtaining the necessary approvals before deploying to a live production environment. The chapter is likened to a senior business analysis course that can also prepare individuals for roles such as product owner.
• 160:00 - 186:00: Case Study: User Stories and Process Diagrams for Open EMR The chapter discusses the qualifications and experience necessary to become a Scrum Master or Project Manager in the US. It emphasizes the importance of having a Master's degree from a reputable university and highlights that direct entry as a project manager is typically possible with this educational background. Alternatively, professional experience of around 10 years in roles such as developer, tester, or business analyst, coupled with team management skills, can also lead to becoming a project manager.
• 186:00 - 201:30: Case Study: Testing and QA in Business Analysis The chapter discusses two career paths to becoming a project manager in the field of business analysis and IT. One path involves acquiring an advanced degree (such as a Master's) from a reputable university, which can lead directly to a managerial position. The alternative path requires gaining extensive experience over 10 to 12 years in roles like tester, developer, or business analyst, until reaching a senior level where one can then transition to a project manager role.
• 201:30 - 258:00: Interview Preparation for Business Analysts The chapter discusses career paths in agile project management, specifically focusing on roles such as Product Owner and Scrum Master. It explains that these roles are primarily applicable within teams that follow agile methodology, as opposed to hybrid or waterfall methodologies. The narrator mentions having additional resources for learning about becoming a Scrum Master.
• 258:00 - 275:00: Agile Principles and Scrum Framework This chapter explores the Agile principles and the Scrum framework. It begins by discussing the role of a business analyst, specifically differentiating between non-IT and IT backgrounds. An emphasis is placed on individuals with IT backgrounds, such as a Bachelor of Engineering in Computer Science or Information Technology, noting that they likely have foundational knowledge from their education. The chapter aims to elaborate on how these individuals can apply their IT skills within the Agile and Scrum methodologies, and the potential career paths available in these frameworks.
• 275:00 - 290:30: Tools and Techniques for Business Analysts The chapter discusses the systems and applications relevant to business analysts and how these systems interact with one another. It delves into databases, queries, and introduces some coding languages such as C++, basic Java, or JavaScript, essential for IT professionals. For non-IT professionals, like those in electrical, biomedical, or bioinformatics engineering, the chapter underscores the crossover skills needed for business analysis.
• 290:30 - 324:30: Business Analysis Metrics and KPIs In this chapter, the author outlines the diverse academic backgrounds from which individuals can transition into business analysis. They highlight that irrespective of one's field of study, whether it be different branches of engineering, commerce, physics, or biological sciences, anyone can become a business analyst. The author draws on personal experience to assert that a varied educational background could be beneficial in the discipline of business analysis.

Business Analyst Training Full course (Step by Step Guide ) ( 100 % free course )in 10 hours Transcription

• 00:00 - 00:30 hi everyone good morning can you hear me yeah hi pipa good morning hi so let's get started it's already 7 so um everyone thanks for joining today we are going to learn about um the basics of business analysis and I'm going to like this will be a 10 days course so
• 00:30 - 01:00 every day morning like uh 7 to 7:45 a.m. uh USD timing okay so I am pradipa um I'm currently working as uh business analyst u a senior okay in one of the fortune founded companies in us so I've been with the industry like about like 16 years now so I just want to uh guide people on like how to become a business analyst because like there are many people who want to become a
• 01:00 - 01:30 business analyst but they don't know how to do it so um that is why like uh I have started this course okay so today we are going to learn about like why do you want to become a business analyst like there are many um different jobs available in the market but like why do you want to become a business analyst and then like you you are from non it or it or from any like different kind of background can I become a business analyst if I'm a non it person or or um
• 01:30 - 02:00 if I'm from a different country okay if I'm not in the US and I'm like in the UK or I'm in Australia or in New Zealand or in India or anywhere Bangladesh anywhere can I become a big business analyst and what are the different companies okay so we have whether it's service based companies or whether product based companies what are the different companies that hire business analyst and um what are the different domains available so um whether it's Healthcare or banking or retail what are the different domains and how to become an
• 02:00 - 02:30 expert in a particular domain also we have different platforms like Pega Salesforce guideware so these are like um languages so Pega is nothing but an advanced Java okay so how to become an expert in one of the languages like if you want to become a PGA business analyst or a Salesforce business analyst or a guide web business analyst how to become one and then I'm going to talk about like what are the very basic skills to become a business analyst and then how can you scale up okay how can you become an expert and how can you
• 02:30 - 03:00 become a lead or a senior business analyst going forward in five to 6 years so the last one is self assessment right now you can be anywhere you can be like a beginner or you can be like you know some of the domain knowledge but you don't know it or you know it but you don't know like um domain knowledge or language or coding language or you don't know about business analysis skills so you can be anywhere so I will I'm going to talk about how to do that self assess
• 03:00 - 03:30 M and how to scale up your skills okay so let's talk about first why do you want to become business analyst so you can become in it rate you can become a tester you can become a developer or an engineer or you can also become a uh business analyst you can become a product owner okay we can become a scrum
• 03:30 - 04:00 master or you can become a project manager okay you can become any of these things right in it but uh you can choose any of any of these okay you can become a tester so in testing you can you can become a manual tester or you can become an automation tester okay so Developers you know about
• 04:00 - 04:30 engineers you can become a Java engineer or you can become a net engineer or you can become a Pega engineer okay or uh you can become a Salesforce engineer so these are different kind of coding languages so you can become any of that okay uh so in business anal analyst so you can become like you have like three three different levels of business analysis so first is like primary the vanilla ba vanilla ba in the sense that person will be like only requiring ga I
• 04:30 - 05:00 mean Gathering the requirements but will not do any other stuff okay just U Gathering the requirements creating brds fds SRS document okay system requirement specification document and that's all this is like we call it as a pure venilla ba they won't be doing any kind of testing or they won't be um doing like so much it work okay so basically like Gathering requirements and doing documentation
• 05:00 - 05:30 so that is first level and the second level of business analysis someone like who will be able to gather the requirements and uh who will be able to write like in an AEL environment okay they'll be able to write user stories they will be able to write all the um uh I mean documentation in the S end to end okay data flow diagrams they'll be able to like technically they know how one application works or interacts with different application so the overall data flow diagrams they'll
• 05:30 - 06:00 be able to draw okay and then they will also be able to like do some level of testing so for example uat testing in sat also in system integration testing also to some level they can help the testers actually if if there is no testing team in the particular um for that particular team then business analyst will also become called a system analyst and they will be helping with the
• 06:00 - 06:30 um Developers for all this sit testing also uid testing getting approval and all so there are two different types of business analyst here so one is the pure vanilla business analyst who will not get into testing at all okay they'll gather the requirements they will just document the requirements that's all but when it comes to system analyst they are the ones who be like in the agile environment they are the ones who will be like Gathering the requirements writing all the user stor
• 06:30 - 07:00 and also doing all the documentation uh diagrams also like basically like creating all the test templates test plans and in sat also they will help and during uat also the final U right user acceptance testing for that also U these people will help so I'm going to teach you that advanced level of business analysis where you should be able to not only gather the requirements also end to end you need to know like how an application works how to like uh Define user stories how to make sure that
• 07:00 - 07:30 whatever requirement that you're writing the developer is able to understand it and create that particular requirement how to like create data flow diagrams and how to like make sure you create test plan documents how to test in sat environment uat environment and finally how to get uh approval before we go live into production so that's what that is what I am going to teach okay something like senior business analysis course and you can also become like a product owner
• 07:30 - 08:00 scrum master and project manager for project manager of course you need uh in US you need an MS in U certain field you need to have like from uh I would say like from a standard very nice University okay only then they're you can directly become a project manager here otherwise you require some amount of experience uh you can be a developer you can be a tester you can be business analyst but you need that um team management skills or you need some kind of experience at least like 10 years of
• 08:00 - 08:30 something one or the other and then once you reach like a seniority level only then you'll be offered a project manager so that is the second route there are two routes becoming a project manager one is you can get a standard U you can get a very good Ms degree from a very good University and directly become like in staff PVP level or in manager at least in manager level otherwise you can you have to like get all the experiences in it basically like a tester developer or a business analyst and then maybe after 10 to 12 years you'll be like
• 08:30 - 09:00 promoted to becoming a project manager so there are two ways to becoming a project manager so product owner and scrum Master is like for mostly like for agile methodology if the IT team is agile they are not hybrid or they are not waterfall so they having agile methodology only then these two positions are will be available okay so I have made different videos on how to become scrum master and also if you have uh if you want to become a scrum Master you can take take a look at it but right
• 09:00 - 09:30 now I'm going to focus only on business analyst so the next slide is like non it versus it so many people may have an IT background or like example like Bachelor of Engineering in computer science or uh Bachelor of engineering and information technology something like some kind of IT background they have they would have done their in 12th right they were major disciplin have in computer science and all that so they have like basically an idea of like
• 09:30 - 10:00 systems and applications and how one system interacts with another system what is database and like what is query and all that so basically some kind of coding language experiences like cc++ basic of Java or JavaScript something like that that is totally it if it is non it people then basically like they are from someone you know right who have done their Engineering in electrical or electrical engineering biomedical engineering uh bio informatics or
• 10:00 - 10:30 something like chemical engineering fashion engineering something like different so we have lots of lot I mean different types of engineering now so maybe that background maybe a different engineering background or they can be like student of like Commerce or or maybe like some different kind of Science Background to um BC like different physics biology microbiology like that okay whatever said and done anybody can become a business business analyst in my experience I'm working in
• 10:30 - 11:00 one of the fortune 400 companies and I can really say that only the non it people Excel I'm not uh I'm not um degrading it from it from it people but I have specifically seen the best of the the best the cream of the cream are are definitely non it people because they think out of the box they don't like maybe we can always say that ID people have some kind of like limitations on their thinking because they basically programmed like they know
• 11:00 - 11:30 what are the basics of it right so this one application interacts with another application what are the uh positives and negatives of their interaction what kind of bug um can happen during testing or they have some kind of idea so it's kind of boxed they know Basics then they kind of boxed whereas non it they will think from a user perspective because they don't know how an application works so basically their thinking testing level basically it will be from a users perspective
• 11:30 - 12:00 okay this application requires login this application requires registration how will a user from an user perspective they will be thinking instead of from um an engineer or application expert perspective that's why these people are very good at testing they can easily find out defects because somewhere in their mind they are not programmed to that they are not like uh no this will never be a defect like that they will never like program their mind so I always seen like um the best of managers
• 12:00 - 12:30 too are from non IT background and they may be like from a very um different Science Background okay so Engineering in um bioinformatics or engineering biotechnology and all even I am a uh non it person I have a degree in biomed engineering so like that's totally different but these people are the ones who really want to uh because it's very competitive okay once you get a job you will know that it um industry is very
• 12:30 - 13:00 competitive first of all getting the interview itself is going to be very hard for you because it's a highly paid job right so highly paid industry standards compared to any other industry IT industry is going to pay you like huge compared to any other industry so it's since it is highly paid uh people are going to be very competitive because they want this job and you also have work from home okay you can work from home also so your bonuses are going to
• 13:00 - 13:30 be very high okay so you're going to have yearly bonus are going to be have you're going to have at least like um you're going to have paid holidays if you're full-time employee you're going to have paid holidays you're going to have stock options so all these will be given to you you don't want to leave this that's why like people always like Grudge about this it industry like they'll be like this is too much pressure I don't want to do this but they will still be there because they have some of the benefits right so people always say that oh I don't want
• 13:30 - 14:00 to do it I want to go to my passion I want to do some business I want to do that but they will never leave because they're so much used to like all these benefits they don't want to leave somehow they are stuck in this so but I'm not telling you to think like that for me I I'm very one of the major decisions in my life that I did was like transitioning from non it to it because when I basically did my engineering degree I was thinking like I'm going to go to the US I'm going to do my research I'm going to do my PhD in biomedical
• 14:00 - 14:30 engineering I'm going to like go to one of the uh biomedical companies right for example you have cd scans or MRI production companies I'm going to become a lead engineer there but the reality is to do your Ms to do your PhD to invest so much of time in doing your Masters and the pay is very less compared to it okay you do all you invest so much money in your Ms you invest so much money in your PhD and then you have to wait for like about uh like 8 years of totally doing all your degree and everything and
• 14:30 - 15:00 then when you get into your biomedical field the the training fee or basically The Beginner's salary rate that is way less than the traine salary of an IT industry so that was like it was bothering me a lot so why this industry is so much paid why this is so much hype in the US why Americans are not able to get into this why is there so much demand for Indians and Chinese to get into this industry what is that so fascinating about me I should definitely
• 15:00 - 15:30 get into this one because I deserve to pay hide and I deserve to be like one of the experts and I really want to get paid High okay that time like 15 years back my ambition was like I'm in the US I have huge opportunity I know I'm from non it but somehow I have to crack and get into this industry because I deserve that pay I deserve a holiday I I deserve that working work from home option I don't want to go into some industry like work from 9 to five what about if I have
• 15:30 - 16:00 kids and I am not able to take care of them so there like since being a woman there is like so much dilemma in your mind like whether I can have the work life balance or whether if I'm having kids how am I going to manage or if I'm going to like a production based company and I'm going to like uh stay there from 9: to 5 like what will happen to my work life balance who will take care of my children I am in a country where I have no help so all this was going in my mind and finally I decided that okay I'm going to try into it I know I'm from a
• 16:00 - 16:30 non IT background I don't have anything like Basics about it industry but I have to like give my 100% of effort and learn from the basics and then I have to get into this industry so when I in the US right so it is very very difficult because you here you know the competition is going to be huge um people know that there are a lot of Indians here and they going to fake their experiences so those they the interview is going to be very very very
• 16:30 - 17:00 difficult I'm sure in India or in other countries too people have this image of like the fake resume so because like lot of people they they fake their resume right because you don't have experience in it but you want to get into it and you are like helpless and clueless here you have some knowledge you have something in your resume but you never know what type of questions they're going to ask and what kind of background check is going to be there or uh what kind of like
• 17:00 - 17:30 um uh whether I'll be able to crack this interview what happens if they reject me like how many rejections can I take so people have so much um self-doubts about themselves about their skills and about like what kind of how to actually learn that is also there right whether watching YouTube videos is enough or someone has to guide me whether I have to go through a training is that training enough to crack an interview um so I had so much self-doubts in us it is
• 17:30 - 18:00 very difficult because you have too much competition uh in India I think you have like fairly less competition I think but in us it's very very difficult to uh even though if you have a green card even though if you are a citizen or you have work permit it is very difficult to crack an job in IT industry because our people right Indians there is so much competition here the pay is very high here so everyone wants to get into this so I'm sure it's the same in other countries too also if you if you see
• 18:00 - 18:30 about like what is service based and product based company service based is something like CTS TCS or um you have vusa like these are some of the service based companies and product based we can say like Microsoft Amazon Google so I'm going to show like for example in TCS you can you
• 18:30 - 19:00 can see here business analyst business analyst you have you have openings in carry you have openings in uh Phoenix you have opening in Pittsburgh so you have openings all around so these are like service based companies whereas in Amazon also you have senior business analyst Amazon Amazon Logistics production planning business analyst AWS Amazon web services business analyst Amazon Fresh stores so even in product based companies also you have openings and service based companies also you
• 19:00 - 19:30 have openings so now you need to decide which one you want to go and definitely in product based for example you you get hired in Amazon um the pay is going to be like 200% more than the service based companies for example in service based companies you get like like 100k okay 100K whereas in Amazon you're going to get at least 150k or 160k plus bonus plus stock and so plus this joining bonus like something called 100K
• 19:30 - 20:00 you have to be with them for 3 years they're going to give you another 100K so the pay for service based and um product based is going to be very different also but the work experience also will be different in service based like TCS or CTS so what usually they will do is they you are not working for them you'll be working for a client right so you'll be working for some um CV s you're working for some Walgreens
• 20:00 - 20:30 you're working for Walmart you're working for some kind of insurance you're working for Bank of America you're working for a client so basically they have to get your billing from them and they're going to give you only half of it half of that they're going to have as a profit whereas for product based companies you are actually you can be a contractor or you can also be a full-time but if you are full-time with the product based company the pay is going to be very huge but I'll also say that the work hours are going to be very extreme like from morning 6:00 to
• 20:30 - 21:00 evening 6:00 from morning 6:00 to evening 8: the work hours are going to be like you can imagine the work hours they're going to give you in Facebook also it's like that so morning 6: to night 6 or morning 6: to night 10: they're going to have such kind of shifts and um but the pay of course if you are Bachelor and if you really want to get into one of the product based companies and you definitely want to earn something more in a short amount of time or you are having that mind of like creating new products creating new ideas
• 21:00 - 21:30 Then I then I would always recommend you to go for product based because in service based it's more of like the interview is going to be very generic kind of interview so what did you do tell me about business analysis or like tell me about your previous companies that you work what is like how do you handle stakeholders so that's kind of basic questions they're going to ask you because and also like they have multiple clients as well right if you if you get fired from one com one client they can always place you in a different client
• 21:30 - 22:00 okay so here it's going to be very easy compared to product based companies service based companies for you it is going to be like the pressure is going to be less also but the pay is also going to be less okay almost 50% your pay is going to be less whereas in uh companies like Microsoft okay and companies like Google and companies like Amazon your pay is going to be like about 200% more than what you're going to expect from TCS or CTS but the
• 22:00 - 22:30 timings is going to be insane also the expectation from you like what is it that you're going to give it to the team and what you're going to be like if they pay you so much High the expectation is also high right so they want to be on toes and they want to like uh you to deliver um everything on time and they expect you a lot from you but if you're very ambitious and if you want to get into this product base you can always try Okay interview also there'll be like three to four levels of interviews here come compared to TCS or CTS the
• 22:30 - 23:00 interview will be very different and in TCS of course there are like um two to three levels of interviews so first is like the primary like the domain test or something and then in second level they're going to ask about oneon-one it can be um a zoom call or it can be um in person and then they have one client round so that client round depends upon um I don't know it can sometimes the client R will be there sometimes it's only TCS managers is going to take the inter okay
• 23:00 - 23:30 so so these are the different service based and product based companies I have told you the pros and cons of both the companies if you want to enter into Microsoft if you want to enter Google even if you are non it that's fine they don't care if you you can enter into Tesla too but always remember the work pressure is going to be very very very high the timings are going to be insane they don't care whether you eat or not and uh Google have their own um like you can always like take your clothes stay in Google's office and you can always stay there you can eat there they're
• 23:30 - 24:00 going to give you everything for free food or coffee or everything that's going to be free for you but they want you to stay and they want to you to deliver everything on time okay then the next is what are the different domains in business analysis so we have Healthcare we have banking we have retail and um
• 24:00 - 24:30 okay these are some of the domains uh you can become an expert in one or you if you want to like add few domains to your resume so maybe one Healthcare project or maybe One banking project you can always do that too especially if you want to get into service based companies like TCS or uh uh TCS or CTS they have like different kind of clients they can have one Pharmacy client or they may have one health insurance client or they may have like something called AIG or AIG is
• 24:30 - 25:00 nothing but um it's not a health insurance right it's a commercial different type of insurance so if you they may expect you to have maybe one knowledge in one or more domains but um I would recommend you to learn at least two domains have basics of uh you should know at least Healthcare or banking you should know basics of healthcare and banking so that it's easy for you to get into the um interview at least HR is going to pick up your resume if you're resume is going to be very plain very
• 25:00 - 25:30 plain like you're going to say I have I know business analysis I know like documentation I know how to do word Microsoft Word and PowerPoint and all it's very very hard for the h to for the HR to pick up that resume because they want some kind of speciality in the resume right there are like 100 people applying and they want they going to pick only like five of them so they really look for even if it's truth or not they don't care about it what what they look is the words so the words in
• 25:30 - 26:00 the resume are going to be that is like gold for you so you may know 100 things but the HR is not going to know that right because before you they even see you before they even they call you what they looking at is a document that word document or that resume okay so the words in the resume are going to be golden for you
• 26:00 - 26:30 because uh I have heard this multiple times so many people emailing me that um I I'm like applying for interviews for 3 months six months I'm not even getting one call that's basically because you don't know how to write your resume okay that's a skill to write your resume you might have added 100 things in your resume but that's not what the HR is expecting right the HR is expecting something is the hiring manager is giving him very specific
• 26:30 - 27:00 keywords okay they don't want to waste the time of the hiring manager okay the hiring manager may have only like three half an hour slots or maybe he may have only like two days in two days like uh maybe he is having like only four slots so they cannot be like calling 100 people for this five positions so even 100 people applies they're going to select only like top 20 people or maybe top 10 people and how they're going to do that selection is based upon these keywords so so it's very important for
• 27:00 - 27:30 you to uh to know how to write a good resume okay what are the skills I need to add and uh like how to highlight each word because the HR remember HR is a non it person okay he doesn't know anything he will have requirements to hire 10 testers he will have requirements to hire 10 business analyst so he will have no idea whether you have some knowledge or not okay all his is like seeing your resume and then he'll be like looking
• 27:30 - 28:00 for the keywords okay this person knows agile for example they're looking for some agile business analyst okay and you know agile you know the difference between what is waterfall agile all agile techniques you know but you have not entered in your resume maybe a 10 times maybe youve entered like one or two times what this HR is going to do is do contr F give agile and then going to click on enter and then he's going to find out how much agile words are there in the resume and then he's going to like decide whether to call this person
• 28:00 - 28:30 or not but you will be like no I added agile in my resume but like how many times have you added did you add one time or two time or did you add it like did you enhance that did you make it bold did you add it in your summary did you add it in in all your projects so it's very it's a very very important skill to write your resume otherwise your resume is is never going to get picked up you're going to apply still wait for the phone call and that that is never going to happen so even
• 28:30 - 29:00 learning the skills that is one thing but writing learning to write your resume and learning how to like approach the interviewer or approach the HR learning how to like apply at the right time for each company you you should know when TCS will be hiring when there will be a vacancy when CDs will be hiring what is the prime months they're going to hire when there will be a vacancy you should never apply when they are going to like fire all the people when there is like a year end in December you apply you're not going to
• 29:00 - 29:30 get you're not going to get any responses so you should know for that you should have a nice uh Social Circle of people working in that companies okay so you should have referrals very crucial okay to get a job you should know people inside the industry you should know people inside the companies try to find out some like some kind of some setting will be there you need to know friends inside so otherwise with referrals very easy to get even if you don't have knowledge with referrals you
• 29:30 - 30:00 can definitely get in okay so I would recommend you to learn business analysis that's good but also simultaneously you should also know how to write your resume you should enhance your Social Circles within the company and you need to try to get contacts 90% of the jobs is filled by contacts inside the company either they know someone or someone is referring because they're getting that hiring bonus or someone managers knows this person like that's how most of the jobs are getting filled okay if you're get if
• 30:00 - 30:30 you're going as a trainee that's different so you're fresh out of college and there going to be a mass hiring in the college or some campus interview something is happening there get your name and you enter into training and you go that is totally different but I'm talking about people who are in their 30s I'm talking about people who have a huge gap I'm talking about people who are married and they having a huge gap or someone who want to transition from one Department to another department someone is working in different sector and want to get into it no you definitely you need to have that social
• 30:30 - 31:00 group or circles or friends and the next one is like what is the difference between Pega business analyst Salesforce business analyst and guideware business analyst so Pega is nothing but it's a language so it's an advanced Java and this is a licensed uh software okay so this is not free if you see here I'm going to go into their website so Pega has their um Academy and all and
• 31:00 - 31:30 there are so many people teaching Pega I also have done like two to three videos on like how to become a Pega business analyst so this is like nothing but Advanced Joba so if you want to become a business analyst but the company is hiring Pega business analyst for example all the bank mostly 90% of the banks in US is their their coding is based upon this language okay so Bank of America and then you have wells foro there are many um banking companies here who use this
• 31:30 - 32:00 language as a core language because they feel that paa is more easier to code if you're going to go for something like open source like Java it's going to be very difficult but Pega means they have some additional security features and all so people like to buy this purchase and um they want to uh become I mean they want to develop their product using this Pega language so so when these can I I think someone okay so when people want to when uh the
• 32:00 - 32:30 company like Bank of America they want to develop their product in Pega they're looking for some people who knows about this language right so they want developers who knows Pega they want business analyst who knows Pega and they also want testers who knows peega so basically you need to learn all the basic skills okay requirement Gathering skills requirement Gathering skills also
• 32:30 - 33:00 documentation skills you need to have that documentation you need to how know how to draw so data float diagrams how to like use PowerPoint or how to use um like for example glyphy diagrams how to use Confluence how to use jir all that you need to know okay on top of that you you also need to know banking
• 33:00 - 33:30 domain on top of that you also know to know a little bit of Pega okay what is Pega what are the basics rules uh rule sets of Pega how to test something in Pega so basic of that also you need to know this will make you a complete business analyst so the skills whatever I'm talking right you need to know Basics how to uh gather a requirement how to do documentation uh you need to know how to work in both waterfall methodology as well as agile methodology G and also how to like uh draw all the um diagrams okay
• 33:30 - 34:00 uml diagrams flowchart data flow diagrams all the different kind of diagrams so I'm going to teach you on like some of the diagrams I will teach you how to draw also and on top of that you need to know one coding language not like entire not like a developer but you need to know what is Salesforce what is Pega or what is guide wire so at least one specialization in one of the coding languages also like at least one or two domains so it can be in banking or it
• 34:00 - 34:30 can be in healthcare okay so I'm in healthcare for all the 15 years I'm in healthare so um I me working in one of the leading us insurance companies so Healthcare has always has good Market but if you don't want to do Healthcare you can always go for banking retail or different whatever is your interest okay you can become you can learn one of the domaines and also one of these languages so it's very crucial for you to put all this in your resume for example here uh
• 34:30 - 35:00 in Salesforce so this is Salesforce so Salesforce also they have it is also a product like Pega but it's different okay so they have like lot of tools artificial intelligence they have so many tools and products here but you can also learn so learning if you go to learning they're going to like um so you can learn about Salesforce ERM Salesforce Cloud basic service so you can learn something basically what is
• 35:00 - 35:30 Salesforce and how people are using Salesforce how to test in Salesforce like all these basic things you can always like learn so that in the interview even if you don't know what is sales force at least you you can at least can match up right like saying that I know business analysis I know like how to test and everything also in Salesforce I know the basics like that you can test you can tell them okay instead of knowing nothing at least you know the basics of how a sales will product is working and what are the
• 35:30 - 36:00 different customers for example human is using it Priority Health is using it there are so many companies who use the Salesforce products and even in healthcare banking like in so many um so many people in in us right I can say that some of the major companies are using the Salesforce product so you'll have a good opening if you are in the US so um you need to know one of these products and also you need to know the domain knowledge too so who's going going to use it whether it's any Healthcare company that Healthcare
• 36:00 - 36:30 domain knowledge to you need to know so yeah the next is so I've talked about skills so in skills I've already told you need all the skills next is self assessment so self assessment right you now you want to become a business andless good now you have to do like assessment on yourself okay what is my level of learning now whether I'm a beginner or I know some of the domain skills I know some of the coding skills
• 36:30 - 37:00 but I don't know business analyst skills or I know business analysis skills but I don't have domain skills or I don't have this uh Pega knowledge or Salesforce knowledge or any coding language or I know everything bits and pieces but I'm not becoming an expert I already undergrown training with some of different company but I'm not getting interview calls or I'm already working in some company I don't have enough time to learn so you may be stuck somewhere you need to definitely like like write
• 37:00 - 37:30 take a note write down in and points like right now what is my communication skill okay can I communicate can I communicate properly with everybody through email through documentation okay okay and also during calls with the clients if I have a call with the clients with different stakeholders can
• 37:30 - 38:00 I lead that call or U can I talk to anybody like with an expert with no fear or do I have that presentation skills do I have that drawing skills or do I have like interview skills for example even if I don't know something how would I tell the interviewer I know that or I do I know how to handle the interview properly or whether I'm going to get frustrated again and again I'm going to lose hope and then end up not getting a job so where am I standing now and even so this takes a time okay don't think in
• 38:00 - 38:30 overnight in one night you can become an expert it definitely takes about 30 to 45 days and I can guarantee you in like in 45 days um every day if you take like one um 1 hour or like maybe 45 minutes every day and if you are thoroughly enhancing on something if you want to like um develop on documentation skills you don't know how to write a BRD you don't know how to write an F or you don't know how to like um write any particular document now I'm
• 38:30 - 39:00 going to learn how to write a document right you take the videos or in YouTube you have ample number of videos in Google you have ample number of documents so you take that and you are going to like practice it takes time because you don't have background and you also you don't you cannot like you are not going to college right you're not doing Ms in business analysis or something so this is like self- learning if you're doing self- learning it's going to be very hard on you because you have to try to motivate yourself and then learn all the
• 39:00 - 39:30 basics by yourself and that's what I did in like 15 or 16 years back that's what I did because there was that time there was not YouTub like nobody was like putting videos in YouTube too you have to do everything by yourself and like it was very hard that time to get guidance from anybody at least now we have ample number of videos in YouTube everybody is like teaching you what to do but in those times like nothing was available everything you have to learn you have to search and Learn by yourself and and uh
• 39:30 - 40:00 and you have to enhance your skills by yourself you will get lucky that I will tell you if you are putting your effort and um at least for 45 days or two months if you're learning every day you will definitely get lucky and you will get a call because if that effort is not there nobody the universe is not going to give you anything and so you from your from your stand you have to give that effort that 45 days that two months of every day one hour learning you have to do you have to enance all your skills and when you have reached that 2 months
• 40:00 - 40:30 timeline definitely I'm telling you once you are like confident on yourself now I can attend an interview or now I can apply for CDs or TCS now I know the basics now I can handle any kind of tough questions I don't have any fear for the interview if I fail that's fine that is an experience and then now you like uh try to apply for a job even if you fail in the first interview I'm sure you will get in the second or the third interview because you now like you're not not afraid of the failures you're not afraid of any of the questions
• 40:30 - 41:00 they're going to ask and you know the basics and you have learned enough right so definitely it's enough to get a like that first level of interview that's fine once you get an uh job then of course you will have that passion to get learn inside the job and then from there your career will take off so my uh recommendation is you have to do the self assessment without doing the self assessment you'll become blind and uh you will you'll have no vision on what to do and you will have no vision on like how to get a job and you'll be struck in that environment and you will
• 41:00 - 41:30 never progress in your career okay so um I think we have some more time like do you guys have any other questions yeah hi hi uh I am following your
• 41:30 - 42:00 hi everyone thanks for joining so today we are going to learn about uh today's day two we are going to learn about some of the uh business analysis techniques and like how to like um implement this techniques practically in your case studies and how to answer in the interview okay regarding this business analysis techniques so um
• 42:00 - 42:30 before we start on the techniques I just want to like tell about like how a project will be and um in real time right when you enter into a project what are the things you have to do so if if you from non it you need to understand that there are about like three to four environments in IT industry okay so one is Dev and uh second one is q a then you have uat then you have production okay
• 42:30 - 43:00 there are like three to four environments Dev means this is where the developer develops the code okay so de in Dev environment the developer will develop the code and in QA environment the tester will be testing and in the uat environment that that is where the end to end testing u means user acceptance testing that's where the endu testing will happen and uh production means that is life so the public can
• 43:00 - 43:30 access the application okay so any application in software um development so I can say that in software development okay if if you are hired by an IT company they expect you to know all these environments okay you cannot say that I don't know what is U I don't know what is QA and all so anybody even if you if you're non um I mean um you are in the non-technical role you need to understand that there are like four
• 43:30 - 44:00 different types of environments one is Dev Dev is where the engineers or the developers right they do their coding it can be any language it can be in Java it can be net or Pega Salesforce whatever it is they will be doing their coding in the dev envirment and then they will move the code to the QA environment in QA only testers will be testing they will be doing all the testing and again it will be moved to the uat environment for the business you in U right that's where the business people business owners will be
• 44:00 - 44:30 testing okay so once in the uh U environment the business owners they do all their testing they confirm like everything is working fine only then the code will be moved to the production environment so in production right that's where the real members like the public right they will be able to access the application it can be any kind of application it can be a web portal or it can be a mobile application it can be any kind of application the public will be able to access the end
• 44:30 - 45:00 product okay of the software development this you need to know before even you start a project or before even like uh you enter into industry this is these are the basics okay now what you do is you are getting a project let's say you are being hired by a TCS company and uh they are asking you to go for a client okay let's say the client is Bank of America and uh they say that okay this will be your new client this is your new project we you want we want you to become a be a lead analyst and gather
• 45:00 - 45:30 the requirements now before you start the very first requirement Gathering call okay you need to prepare that preparation is very important please do not schedule call without you knowing the basics without you you understanding anything about the uh environment whatever currently is working on whether it's a new project or whether it's an enhancement project enhance enhancement means already the uh
• 45:30 - 46:00 application is there they have an existing application but they want to add new features okay that is enhancement project new means completely from scratch they are developing a application okay so uh you need to like that that's the first thing you need to ask them whether this is going to be completely new or whether this is going to be like an enhancement project or uh what is what is that we are going to do so even before you schedule a call with
• 46:00 - 46:30 a business owners now you have to make sure that you have enough knowledge at least the basic knowledge you need to like coordinate with your colleagues so you need to like maybe ask your senior business ba or if you have put some fake experience and you added some 10 years of experience in your res now you will be the senior B so but still you have to like um ask all your um colleagues not that uh asking like end to endend process at at least like I want to know what is this whether it's
• 46:30 - 47:00 a a new project or it's an enhancement project who has worked earlier on this uh do you have any documents can you share some links like this without bugging them like in a very professional manner you need to get gather some information once you have a basic idea of okay this is going to be an enhancement project and these are the business owners and uh they are working from uh this time zone because time zones are very crucial for you to um skip a call please if they are in C right now in California it's going to be
• 47:00 - 47:30 like morning 5:00 or something so we don't you have to like when you schedule a call you need to be like well aware of their time zones and then like whether they'll be able to attend so all this is basic sense right so you have to like analyze from where this business owners is working which country or if it's going to be internal like what is the time zone how when when when they'll be available to attend the call and all because business owners can be very hard for you to um like they are non- technical people
• 47:30 - 48:00 they don't know exactly how to give you requirements they only know the functionalities and the expectation from them is like I want this to work like this I need an application where the members has to log in they have to like view everything they can only give you and from an user perspective but technically they will not know anything okay so you are you will be a lion between uh you'll be a lien between this uh completely non-technical people from an inducer perspective you have to
• 48:00 - 48:30 gather the requirements and you have to break down that requirements and you have to make that as a technical requirement so that is your that is your role so what is the role of a business analyst you will be acting as a lizin okay liin between stakeholders or business owners and you'll be making sure that you gather all the requirements business requirements from them and then you have to make sure that you convert them into functional and non-functional
• 48:30 - 49:00 requirements okay that will be your role okay so this will be your role if they ask you what is your role tell me your role this is what you say so in my in my current project or in my previous project my as a senior uh lead ba my my
• 49:00 - 49:30 role was to gather the requirements business requirements from my various business stakeholders and convert them into a functional requirement or a non-functional requirement and making sure that it is documented that will be your role okay that is your role and responsibility as a be now okay you brand new to the project you don't know anything about uh that project but still with with the help of your colleagues you able to like get some information but uh you don't know
• 49:30 - 50:00 about like how Bank of America application works okay let's say that in Bank of America application they going to do something like uh a new feature so already they have their web portal and everything everything is fine but now they want to add some new functionality okay so give me a second
• 50:00 - 50:30 okay so they want to you they want to enhance some new feature you know only that much you don't know like how many markets they are going to do whether for example there are 50 states in us right
• 50:30 - 51:00 okay so there are 50 states in um USA so they will not know business owners you have to understand that if you a US project especially they will not roll out in all the 50 states in like in one time they will never do that what they will do is they'll roll out in one state for example they are rolling out in New York Okay so the one specific Market they will roll out this functionality they will get
• 51:00 - 51:30 feedback from the users like how is it whether it's very user friendly or what is the feedback only then they are going to like um roll out in other states one by one okay so that information also you need to ask okay so whether we are doing this um going live and we are going to like making sure this is available in all the states or we are going to do Market by market okay so whether it's New York first and then California or then Virginia or then Florida however it is
• 51:30 - 52:00 okay so you get um you do some document analysis you're getting a few basic idea but still like you want to get all the require requirements from them now you get names of all the business owners okay all the stakeholders business owners or stakeholders there'll be a principal architect okay so business owners will be there there will be a definitely there will be
• 52:00 - 52:30 a principal architect who will be coming whom you have to like make sure joining the call and if that if it's a very huge project then and multiple teams are interacting definitely there will be a project manager project manager means technical project manager not your project manager okay he's called as a technical project manager whom whom who is a project manager who only like guiding or creating guiding you or maybe like if you want to interact with multiple
• 52:30 - 53:00 systems they will schedule calls with all the different uh teams so they'll be acting project manager only for that particular project once that project is over they will go for a new project okay so those are technical project managers but these people be only only for huge projects not for like these enhan enhancements projects or like very small functionality changes and all these people will not come you will be directly the lead for all this so you get all the names okay business owners names architect names and also project managers and other people other teams
• 53:00 - 53:30 like developers names testing team name okay who is the testers development um scrum Master names all other teams names you are getting and you're going to schedule the very first call okay the very first call you have to be thoroughly prepared on what is going to be the agenda so without agenda like don't schedule and like talk in a random way okay so you have to be very professional what is the
• 53:30 - 54:00 agent of the call in the email itself while you're scheduling scheduling the invite okay the invite itself you have to like make sure that what is the purpose of the call what is the agenda of the call so for example how you have to make sure this is a this will be a quick 30 minute discussion um regarding our new features on this particular functionality for Bank of America whatever it is whether it's a web portal application or whatever um whatever is a functionality you're going to to write and then you're going to write down this will be the agenda this is what we want
• 54:00 - 54:30 we want representatives from each team and uh if if I'm missing someone please forward the invite and feel free to forward the invite like that you have to like make sure during sending the email itself because most people what I see like um this junior BS what they do is they schedule the call there is no um agenda okay just in the heading they put like they are adding the names like this is a requirement Gathering call that's all so who has to join whether I need to join or not whether the who will be why
• 54:30 - 55:00 should I join because most you remember the business owners can be very tough on you they'll be like why are you wasting my time why why should I join even though it's their project they'll be very hesitant to join the calls because they are like having lot of calls from morning to night okay so you have to like very be very professional in writing emails so that's a first skill you need to develop okay while writing emails while replying with for all the emails and for
• 55:00 - 55:30 for all the followup emails okay so then the agenda needs to be very clear why you guys have to attend my call this is the purpose and I want this basic information from you okay so if you are a business owner tell me about the existing current data flow so that and all you need to like very properly you have to write and then you will send the email once you um have that call scheduled now like every everyone is joining the calls from my
• 55:30 - 56:00 experience the business owners will have no idea technically they will be telling like currently um member will log in and uh member will member can see all the documents for example if it's a Bank of America member portal they'll be like Oh yeah member can log in using the username and password they'll be able to see all the documents and if they want to uh if some sometimes if they want the design we have something called design
• 56:00 - 56:30 right for example I am the primary member from Bank of America account I have a design my design also can see all the documents and I am giving access to my design also okay so they will be telling like this which is like we don't know whether we have to check with the compliance whether that is legally that is allowed or not we don't know so they will be describing some functionality very blankly they have no idea whether this is compliance issue you or whether this is like can can that be done in that particular State whether state law is allowing that
• 56:30 - 57:00 okay and whether like for example there are some privacy documents whether that can be sent through email so every um there will be a email notification right like for example you do something in the member portal the something like you're adding some documents or maybe like there is a in healthcare let's say that there is a claim you submitted okay the claim is in progress or whether it is going to be approved or if it is approved or denied the member has to get a email
• 57:00 - 57:30 notification that is a particular feature but to what level they can get a member notification they can only say that your claim has been processed please log in to the member portal and see the status you should never be in a to a uh to a member's private email you should never send the status of a claim like approved or denied or in progress that status should never be there that's a liance issue in healthcare I'm talking about same way in Bank of America also
• 57:30 - 58:00 you will be even in banking sector also there will be like you can never show the amount how much the member is having in his actual amount that should never be shown in an email so this is your pending amount status or this is what you withdrawn I mean that can come to their text actually but in in email notification this is what is your balance like this they can never send it depends upon like which Market you're working what is the compliance issue the functionality will change okay from Market to Market but basically you need
• 58:00 - 58:30 to understand like what is the domain concepts for this particular functionality and compliance issue that can come with that particular functionality uh I'm again and again saying that business owners will never know about compliance issues they'll be like I don't know that and you will gather the requirements accordingly the developer will develop that functionality and that can go get into production and that can be a huge legal issue also in future so that has happened in Healthcare a lot of times where for this particular state for New York we are not supposed to show about
• 58:30 - 59:00 the claim status in an email notification we are not supposed to show any Min details of a minor child details right for example they are having some uh fever or HIV or something like that minor okay under 18 you are not supposed to show that sensitive diagnosis in an private email that's like a state compliance issue and the member can sue the whole organization so uh all this like details maybe in the very first call you may not know but I'm telling you from an experience like you need to
• 59:00 - 59:30 know how to write emails you need to follow you need to know how to follow up that email properly in a professional way and when you're Gathering requirements with the business owners you have to be very kind enough the first call is going to be like very generic call of course you're telling that this is what we got new intake request so our team we got new intake request for this project do are you aware of this and I'm trying to gather requirements and I want to your help so this calls these calls can take about like a week or two or something and I'm
• 59:30 - 60:00 going to schedule the calls are you okay with the timelines do you want any other um business owners to be involved in this process uh please let us know and I'm going to invite my Engineers I'm going to invite the other team engineers and testers as well for the future calls please let me know if you have any concerns and when they're starting to give the requirements you should always record the calls for your uh good for everybody's good so you have to ask them like can I record these calls because uh
• 60:00 - 60:30 I cannot have everything in remembered right so can I please record these calls take a confirmation from them and record the calls okay that will help you if they have some so now they give you something okay they give you a requirement and in future they say I don't want this you'll always have proof that okay on that particular day on that particular time you have told me that this is the requirement now you want to change during development you want to change that requirement okay we can do but that is only through change request I'm not
• 60:30 - 61:00 going to change anything now after you provide the sign off right okay so make sure as a ba like um you have to be always alert than other people make sure like um you're very kind and professional to the business owners also the other stakeholders and also make sure in writing you have everything in writing okay so you send an email after the call you send a follow-up email or the status email like you write whatever is record you're able to write everything in notes and you're going to say uh send them because
• 61:00 - 61:30 tomorrow that is like documentation is everything okay so even though you record the calls documentation is everything your project manager will not be in the call okay so whatever you tell the team whatever you are going to tell your um uh developers developers also right they will not be they'll be like this is not my work my work is to code my work is like to do coding and send the code to QA then it is T responsibility I don't want to be involved in all these calls this can take like lot of time this is your
• 61:30 - 62:00 responsibility this is the B responsibility to gather all the requirements so usually developers will be like this is not my my my work right this is your work you have to do it if you have some technical questions you can pull me in the call otherwise like Gathering all the business requirements that is BS responsibility I can help you even the architect the principal architect will be helping you on the data flow and everything but how how I'm going to get the business requirements line by line and how am I going to
• 62:00 - 62:30 convert that into functional non-functional requirements that is so that is completely your responsibility okay so you need to like handle everything in a professional manner and if even some people they can be very harsh they can be very rude um so they can they will never attend so I'm telling you some of the negative stakeholders attitude some they will ignore you some they will never attend the calls some even if they attend the calls they will not give you proper requirements even if they give you requirements they will be saying saying
• 62:30 - 63:00 the thing again and again they will not correctly tell you what they want so for that only we are going to use some business analysis techniques just by scheduling calls and like having like a random one-on-one conversation you will never be able to like gather proper requirements so um just like asking them throwing them questions like what do you think about this feature can you tell me the data flow what is this okay the member is logging and what is the first thing the member has to see in the web portal they
• 63:00 - 63:30 will not be able to answer it's not that they not capable of answering but they from non it and from Us's perspective they will not know the back end what is happening how this like one system web portal is how it is interacting with the database or web portal how it is interacting with a different pricing team or if it's a healthcare web portal how it is interacting with the claims application how it is interacting with the back end I'm talking about how it is interacting with the pricing application how it is interacting with the authorization application or how is
• 63:30 - 64:00 interacting with customer calls they will never know all they know use this is one website whether I'm clicking it's able to enter But at the back end there can be hundreds and thousands of applications in the back end that is interacting with one system to another system so they may not know that you may not know that but you have to know that so that's what I'm talking you may enter into an IT industry like a non-technical person but day by day with your experience you have to like make sure you at least like
• 64:00 - 64:30 50% you need to know in the back end even though you don't know coding you have to know that behind this application how many teams are working okay how the data is interacting from one team to another team if if my developer sends a file in XML file how is getting processed in the back end or if Json file is sent how is getting processed in the back end so this those kind of like small small technical uh questions um or maybe data flows you will need to understand but that will
• 64:30 - 65:00 come from experience only these are like Theory based business analysis techniques so um we will learn about this one by one the first one is SWAT analysis so SWAT analysis nothing but strength weakness opportunities and threats so what is let's talk about in one of the case studies okay so I'm going to teach you everything in case studies that is easier to understand and answer in the interview so so first is SWAT analysis nothing but it's a situation analysis means you're going to
• 65:00 - 65:30 take a situation and you're going to in that situation right you're going to like analyze what is that strength what is the weakness what is opportunities and you're going to what is threat okay so um let's take an example so here they say that internal factors like are called strength and weakness and external factors are called opportunities and threats so let's take take a case study of Amazon okay so case study number one
• 65:30 - 66:00 is Amazon so what we are going to say is there is a brand called Amazon for this Amazon what is the strength of Amazon what is the weakness of Amazon and opportunity for Amazon and threat for Amazon okay so what is the strength of an um strength of Amazon Amazon is nothing but it is an online sales service okay
• 66:00 - 66:30 basically focused on improving customer satisfaction and it is like basically undoubtedly the leader in online retail okay and uh they have um they have like operated mostly on like we can they don't have like a building or something like Walmart or maybe like um Target they don't have like buildings right so most everything is online so that is their strength okay so what is their weakness weakness is like basically they have a very thin
• 66:30 - 67:00 profit margin because they have to like ship everything Al although we can find many products in Amazon right from paper to whatever like whatever commercially you're finding in Target our Walmart will be definitely found here also but always in if you see on Amazon the prices are going to be a little bit higher right so yes vun I'm sorry to interrupt so this SWAT analysis will this work on SAS products as well yeah you can take any
• 67:00 - 67:30 situation any like any feature I have worked in one of the client and uh the features what the client is providing for its external Cas is everything is same so the difference is only about the modules that using mhm okay I not get an opportunity so example is there are four companies which are towards
• 67:30 - 68:00 into broker accounts all four of them will be dealing with the broker accounts purchases trading etc etc but only few of them will give the opportunity for their uh employees to participate in gifts and entertainments okay so other two clients doesn't need that feature and they're not interested in that and they're not willing to do it so how do we identify this opportunity here to
• 68:00 - 68:30 understand them how they can use this particular feature for this particular feature like um so your feature is like for for certain uh people like you are able to give gifts right based upon what criteria uh based upon the threshold uh an employee can uh gift an another employee depending on their uh performance trting or their contribution towards the work okay so you're you
• 68:30 - 69:00 basically creating a feature which can be used by four different companies I mean all four of them can use it they don't have to use it it is their choice okay but when I had a client I had the opportunity I mean I want to tell them that they can use this particular feature as well in case if they're willing to use it but this will come at a cost cost so the client State rejected that yeah so um if the business
• 69:00 - 69:30 doesn't want it then we cannot like force them right so what from your perspective like you already you having the feature from an application perspective we already have the feature we have couple of clients who are doing it and so for you you are like basically saving like um of course from next time for example if a new client wants the same feature you know the basics you know how to test it you know how to like get data for that particular test you know all that functionality right so from your perspective you already have something like you have a basic
• 69:30 - 70:00 foundation and depending upon the new client you maybe the test data will differ for like for if an additional company wants to like want this particular product now you have to test with them of course so you have to test with them then you have to make sure like they provide sign up and all but you cannot take that budget constraint on your team of course there will be some testing cost or something so for from from an IT perspective we already have a basic feature that can be used for multiple clients so I can use like if two people are willing to use that's
• 70:00 - 70:30 fine if I cannot compel the other two clients to use this okay I cannot so yeah so that is also one thing like for example when you're doing on multiple markets right for example I've told you here you can go with like one one business owner for example a New York business owner is TR to accept this functionality but the other business owners are like no no no in Florida this cannot happen in um um uh in Virginia this cannot happen we we don't want this change because our users are so much used to the old
• 70:30 - 71:00 functionality we don't want that new change so they'll keep on rejecting even if you like there are multiple times in it where the product will go up to uat but it will not go to production because the business owners don't want okay they don't want even they have funded us okay they have funded us we have developed we have tested it is in u8 everybody is finished testing but they don't want to go live because they afraid of new changes they don't because they have a million people who using maybe two million people using the older
• 71:00 - 71:30 web portal right if they want to change something they're afraid of the new change because even like think about us right if something for us is changing in the member pter or something we don't like that new one we always go like the old product we don't want to the member doesn't want to change immediately in one day but but there will be a time that they will have to change something will happen the organization has to enforce the leader leadership will say you have to change this application is
• 71:30 - 72:00 old our competitors are having like they have advanced their applications they have something like now called like think about Alexa think about this um robots who's like um who can you can type and get answers so competitors are advancing in Ai and something you are having the old uh this VB script application or very old like application we have to change this sometimes I'm telling you the leadership is okay to change but the business owners won't agree the staff VP level they are like
• 72:00 - 72:30 they want to do changes for example in our organization also we want to implement AI products in our web portal in our customer care cold everything we want to apply AI products but the business owners are not okay with that change because when we integrate AI with the web portal lot of customer can lose their job right because we automate something but I'm going to healthare application I want if I want just entering my member ID I'm able to get
• 72:30 - 73:00 the status of the claim or whether I'm I'm able to submit authorization then there will be like 50 people that needs to be fired from customer care right okay understood yeah understood yes got it so maybe like one functionality um when always in it that's a problem when you want to automate more a few people will lose their jobs and that's when business owners will will be very like hesitant on like going that functional to production because they may also lose their jobs if we want to like automate
• 73:00 - 73:30 most of the things so you will have that problem and all with the business owners but we cannot do we are an IT support so all our work is like how much of Maximum we have to like you want budget you have to automate um if 50 people are losing their jobs in customer care we cannot do anything about it because ID has to be evolving it will always evolve you will always automate new things but um business owners may be very like reluctant to like applying this new application but it's a part and part of
• 73:30 - 74:00 the job right if they say they want to do it we cannot do anything but we have the application they can use it that's what you can say okay then then can we share this SWAT analysis document with the client to explain them the strengths weaknesses will they get offended about this I mean you can always uh tell them I I don't know some people can be really rude and harsh and they'll be like I don't want to see the doc literally tell you that I don't want to see anything but um but
• 74:00 - 74:30 like I want to know like why you want them to do this what is the gain from your side I would like to understand their inputs as well because they are the ones who will be knowing about themselves so they can input their strengths they can put their weaknesses uh I'm not sure if we can suggest these threats and weaknesses to them so they might get easily offended and they think that we are downgrading them when we are comparing some of the features with the
• 74:30 - 75:00 with their competitors right yeah that is also that's a very thin line right we cannot like we can always say that we have something okay so better than what we we have something if you want to take a look I can show you but I we cannot force anything on that okay thank you yeah so um so maybe like it it depends upon you can be for a company or it can be for a situation to for example you are creating a feature okay for example you automating something I'll give you
• 75:00 - 75:30 an example of automation so when we um customer wants to like um let's take this um status okay this claim submission status okay so customer wants to like go to web portal they want to like so let's say this one a data flow right workflow okay customer wants
• 75:30 - 76:00 to or the member okay with the proper member ID is going to the web portal okay and then they're clicking on live chat support option and they are able to give their member IDs now the like like the chat option right in an automated message it is saying like um I'm here like maybe I'm like I am Melissa how can I help
• 76:00 - 76:30 you okay and then it is asking then you are typing like I want to check the status of my CL okay okay now it is going to ask give me the member ID and you are giving the member ID okay give me the claim number and now you're giving the claim
• 76:30 - 77:00 ID also okay now it is just saying that the claim is in in progress okay or maybe it is approved or denied okay this is the status it is is showing you okay I'm just saying this is an workflow now right now they we don't have this feature what people can do is they can they can call the customer can and they can um connect with the customer care and then they say they can give the member ID and then uh some
• 77:00 - 77:30 human being is going to like check put the member ID validate that member ID and then make sure this is uh um valid member ID first name last name date of birth address it is we going to do all the Hippa validation now the member is also mean the customer care person is also going to go check all the previous claims and they're going to ask like uh do you have a particular claim number you have the claim number they're going to add the claim number search claim number and going to give you the status or if you don't have the CLA number you can say like this is like I submitted last month or maybe in month of February
• 77:30 - 78:00 or March or something and then depending upon that they're going to like track your past previous uh claims and everything and they're going to give you a status and if it's in progress maybe they SLA is like two weeks or three weeks they'll say that we still have time for this claim maybe the SLA is only 3 weeks so we have to wait or if it is approved means then the customer can member will say this claim is approved so you're all good now if it's denied means the person is going to say it's denied please reprocess the claim and please resubmit again this particular
• 78:00 - 78:30 time or you can like appeal as well so uh this is like right now we don't have this live chat support okay our web application doesn't have this live chat support now the business owners wants to automate this this is the workflow that they want to automate and they want to like reduce the customer care costs because there is a huge call that people are in que customer is not feeling good about like having being in the calls for like about 30 minutes to just check the status of a claim right so they want to
• 78:30 - 79:00 just log in they're going to submit the request and get the response immediately this is the automation that they expecting us to do so as an IT team what we have to do is if you are a ba for this project now you have to do the SWAT analysis and think about for this particular situation okay what is the strength of this automation what is the strength of automating this feature okay checking the status online okay what is the strength of it and what is the weakness of it weakness is I would say that if
• 79:00 - 79:30 you don't have a claim number okay of course you give the claim number it's going to give you the it is very direct right request and response is going to be very direct in progress appr Deni weakness is if you don't have the claim number and you are just asking that live bought or I mean that robot to tell me tell me the status of my claim number claim number it will not able to pull the data because you're not giving the proper request so it's going to give you another like standard answer like
• 79:30 - 80:00 can you please provide the claim number can you please provide the claim number can you please provide he's going to throw you the same question again and again and again because it is not getting a specific or it will ask it will tell you like invalid option invalid option and then please try later something like that it is going to it's going to literally Panic the member if you don't have the correct claim number but if it's a manual uh in a customer care right is going to be easier for the person because we are humans we are able to interpret like okay in may like how many claims were submitted in June how
• 80:00 - 80:30 many claims are submitted in February how many claims are submitted and we are going to able to get the data for the member but that robot will not do that will not be able to identify that unless if it's a or something like more it is having more intelligence then it is able to pull the data but if you don't have that functionality that is going to be a weakness in this particular situation right also opportunities of course you can enhance this not only checking the claim status number you can submit the claims okay I want to submit the claims
• 80:30 - 81:00 through just this uh using the member portal or I want to like so every 30 minute you're going to drop and you have to rejoin so yeah are we talking about SWAT analysis and I was giving you a situation so you can take any feature okay any functionality that the uh business wants to owners they want to automate and then what you can do is you can apply this what analysis okay what when uh like how are we going to do what when you when
• 81:00 - 81:30 you like automate a particular workflow currently it is everything done manually but we going to do automate we going to automate this and some part of that will be like that will be very standard questions will be there and then that's how our system has to respond now what is the strength of this weakness of this opportunities and threats you can like Define that and tell it to the business owner if you want to choose this particular route this is the Str this is the weakness this is the opportunity and this will be a threat do we have any compliance issue
• 81:30 - 82:00 do we have have any cyber security issue you giving the member ID will anybody will hack the member ID and definitely SSN should not be provided during the chat so there are few things that chat should never ask the member right it should never ask about SSN details it should never ask about like any Bank um there are few things uh the this application should not ask because that can have some cyber security issues so if somebody hacks the application
• 82:00 - 82:30 then they're going to get all the and details they there is going to be data leakage and all that that that is all this threat you have to definitely tell to the business owner I cannot ask this detail it's a compliance issue and that that will be causing a cyber security threat in healthcare we should not ask these questions in e-commerce we are not supposed to ask these questions so all this will be a threat and you have to tell to the uh business owners okay so you can take take any situation and you can apply this uh strength weakness and opportunity and threat but you may ask
• 82:30 - 83:00 like pradipa like uh will I take every like in every call should I do this analysis no this is not like um you're taking every call you're not doing swart analysis in every call no there is a brand new project and in the very like very first call you are just doing this smart uh doing this analysis and you're giving the report to them accordingly they may change their requirements if they want and if they will a of all the threats and weaknesses if they still go with that process or automation then it's well and good from an IT
• 83:00 - 83:30 perspective we have submitted our analysis right and also this will be very helpful in the interview okay so if in the interview if they're going to ask you that okay you are a business analyst tell me what you have done in your project you just simply say that I'm gathering requirements I'm like documenting requirements I know how to write user stories I know how to do everything in Confluence and J so you're nobody is going to get impressed right because there are 10 people who are attending the interview your answers
• 83:30 - 84:00 should be like something like mind-blowing your answers should be like okay this person knows something both theor both theoretically and also practically so your answers should always be in such way right so these are all these can be theories all these analysis can be like SWAT analysis what is most analysis so let's go to that most analysis so most analysis nothing but we have um we have Mission objective strategies and tactics so this is like for all your
• 84:00 - 84:30 uh like maybe on a higher level like on a on a leadership level they may be using these kind of like for example they're having a new uh let's say that Bank of America wants to be launched in Switzerland okay or Bank of America wants to be launched in Ireland or different country from a leadership perspective right they want to do this most analysis what is the mission of this new launching what is the objective how are we going to what are the strategies that we are going to follow here the language
• 84:30 - 85:00 is going to be totally different will will the people will be like for example I can tell you an example like if the World Bank of America is there I'm 100% sure Europeans are not going to they're not going to be um I mean they don't want that word America because they are like too reluctant of American products they don't want that word America they so you change that name it can be under the same brand okay you can it can be from the same brand but you change the name according to your that country call it
• 85:00 - 85:30 as Bank of Switzerland or call it as Bank of Ireland but it is a product of Bank of America nobody is going to know that so from the leadership they have to like understand that these people are like so much towards their language they will never accept a brand from us and uh I'm going to change the name of the company there even though the parent company is an American company I'm going to change the name according to the local Brands I'm going to change it to look like more local nobody's going to
• 85:30 - 86:00 like see who is a prior and Company so Coca-Cola has like some thousand products under the under the same brand but we'll never know these are the same products from Coca-Cola okay lace can be one of the brand or maybe like they have a drink they have like chips or they have multiple things from the same brand but we will never know these are the same products from Coca-Cola or these are the same products from Pepsi like that every like this is mostly on a leadership level they will be doing this analysis what is the mission of this project what is the objective of this project what are the strategies that we are going to do and
• 86:00 - 86:30 what are the tactics that we are going to do so mostly on the company's culture or the where this functionality whatever like automation we are doing in the particular let's let's take this like from an application perspective okay so I'm going to do something in Florida Florida has like English people as well as Spanish people they have two major populations there so we have American we have a lot of Mexicans there okay there like Spanish is like hugely used in uh Florida so when I'm dropping an
• 86:30 - 87:00 application even say if it's Bank of America web portal it can never be only in English nobody is going to get enroll it should be in Spanish I'm supporting Spanish language because 50% of the population in Florida is Spanish so anything like enrollment okay or if some kind of like uh accounts uh somebody's getting loan I need a Spanish translator there I need the application to be in Spanish when they download a mobile application that needs to be in Spanish when they are
• 87:00 - 87:30 processing a check that needs to be in Spanish so everything text messages needs to be in Spanish I'm like supporting English as well as Spanish there because the population there if I want to grow my business if I the VP of of some functionality in Bank of America I have to like think about what is a mission okay I have to expand my mission is expanding my business in Florida objective is like maybe getting a like 2 billion like profit this year for uh Bank of America in Florida for the
• 87:30 - 88:00 Florida market now what are the strategies I have to use make sure the application has Spanish make sure all the paper forms has Spanish what documents that you're sending to their members home okay any bank statements or anything like um new enrollment products or any anything whatever discounts everything needs to have both English and Spanish and also uh if they they want to download a mobile appli that also needs to be in Spanish okay so these are the strategies I'm going to use and what are the tactics I'm going to use how to Market this make sure that
• 88:00 - 88:30 everybody's enrolled making making sure everybody is using only Bank of America and Florida and then how we are going to enhance the business there and I'm how I'm going to get the 2 billion uh dollar profit so this is from a leadership perspective they are doing this most analysis but from a business analyst perspective you can also say I'm going to automate a functionality automate a particular workflow what what should be the mission or objective of the particular automation how can I benefit the business owners like uh one person
• 88:30 - 89:00 told here right so two clients are doing it why are you why are you not doing it if you do it this is the profit you're going to get so one thing you have to always like keep in mind that this will help the members nobody is going to like enhance that nobody's going to apply that product you will get a 2 million profit if you use this functionality or if you you going to get a 5 million in profit if you're going to use this functionality if you automate these things definitely there'll be a uh you
• 89:00 - 89:30 need not worry about the profit right everything is about everybody any MNC or any corporate is about profits that's why they firing people okay early early like every year they have to show more profits so from a profit perspective you can always say instead of saying that use this functionality and um members will be you will be fine like there'll be more customer satisfaction more than that answer if you say that if you use this functionality I'm sure you are going to get at least a 100K profit or
• 89:30 - 90:00 200k profit or a 1 million profit in maybe that will like convince them to use more functionalities or automate more things okay so this is called most analysis and why I'm teaching you all this um techniques in detail tomorrow I'll be teaching more I'll cover this in two or three days why I'm teaching you all the techniques in detail is you will not be using this every day okay so you may be using once in a while when a new enhancement is there once in a while you'll be using but during the interview if you want to impress the interviewer
• 90:00 - 90:30 you cannot plainly answer that I will be gathering requirements I'll be gathering requirements that's not the answer you're going to say you're going to say that these are the techniques I followed and I want to explain it with the example with the case study it can be a very generic case study like um this Amazon or maybe different um you can take different companies and do a case study or you can take a case study from your resum one particular functionality and then how you did that Automation and then you can showcase your resume always answer
• 90:30 - 91:00 with the case study okay if 10 people are there if you want to be very different from all the nine people always answer every question with a case study okay even if you don't have experience you have to make sure like what is what analysis you give the abbreviation now I'm going let me explain with the case study you're going to have only like maximum one hour interview so uh by explaining with case studies they'll be thoroughly impressed okay uh does anybody have any other questions so I'll will continue with the
• 91:00 - 91:30 other techniques tomorrow anybody have any other questions let me know any doubts till now prip I have one mhm so these techniques are based on interview questions but when we are using these uh do we use this in PowerPoint presentations or Excel presentations and when we are putting this when do we with whom we discuss all these textes usually within the internal stakeholders or external so SW uh you
• 91:30 - 92:00 can do PowerPoint all these uh for example let me show you can do PowerPoint you can do word you can do diagrams for example this process modeling and all right this and all like like this diagrams you can do and you can show T to them so whom we will do with all the business you have vendors you can like um let's say you have vendors like IBM or you have like different vendors who are going to integrate with you for particular portion then if you want to talk to them to them also and showcase
• 92:00 - 92:30 the um all these uh mod models then you can also do it's not only like up to only internal and all okay yeah you can use like uh not only PowerPoint there are like different um tools right so you can use any of these tools do the diagrams do PowerPoint presentation or whatever required just hi pra could you please uh also
• 92:30 - 93:00 provide us the links uh to these uh most analysis SWAT analysis yeah sure so I will upload in uh YouTube right and I'll put an add in the description is that fine yeah yeah perfectly fine thank you I add in the description that easier to click okay hi pran here like we had a position yesterday like you said like devop I just want to move to ba you remember mhm yeah so right now I'm in office like
• 93:00 - 93:30 today I have a uh this like uh not regarding uh today's lecture so just I want to share one thing so I had a discussion with them so they asked like what I have done so what you said in the recent like I just said I take requirements and all so that doesn't worked here so they're expecting deeper uh thoughts and all uh so I explain some uh strategy for app like how payment integration app is focused on what and all so they're okay with that so right
• 93:30 - 94:00 now they give some assignments so I have a review on Friday itself okay send me the assignments yes like uh it's like General we already have one product developing in in our company so they just want to go through all those things and they just want to say what I have understand from that okay yeah yeah send me that and I will uh make sure that um I will tell you how to represent I think I don't have access like this company thing like if I can download those
• 94:00 - 94:30 things I can download and I can send you m yeah but I just want to share this update like see they know that I will what I'm telling is they know that nobody will use these techniques in day to-day so when you are on the call right you will not be like okay today we are going to use most analysis like nobody is going to do that everybody's like can you please explain this that be very basic conversation but the interview that definitely they want you to be like very professional they want you you to know the basis right like Basics so
• 94:30 - 95:00 because you are from non they can't ask you any Java questions they can't ask you anynet questions so they're going to ask you like basic like Theory questions which you have you need to know yes exactly yes okay thanks yeah yeah thanks hi yeah hi UHA these 12 techniques you have mentioned in the pp presentation these are the combination of prioritization technique and then Elation technique all techniques right
• 95:00 - 95:30 uh when we are doing the market re market research and market analysis we will use part when we are comparing with our competitors and then when there are not only like 12 there are like in BB has more than 50 so you can use any of these but I'm just saying the most important ones uh and then uh the area of usage is different right when some are some are techniques we use in the prioritization of uh prioritization of user user
• 95:30 - 96:00 stories or these kind of epics as for the prioritization we use MCO technique or Keno analysis and then when we are doing the market analysis with the competitors we use benchmarking or SWAT analysis kind of techniques right yeah yeah so I have done all already like benchmarking yeah I have done that in previous videos if you've seen that you will know this called as business analysis training like I did like eight months back that I there I covered all the 50 techniques okay okay and one more
• 96:00 - 96:30 question pra when we comes to uh documentation part we have brds and fds fds is a combination of functional and nonfunctional both are in the one document or uh non-functional and functional requirements having two different documents we'll write the two different documents B is business requirements and FD is functional functional requirements yeah if is a combination of functional and nonfunctional right I mean it's it's named as functional but you can also include
• 96:30 - 97:00 nonfunction yeah and then one more point when we are writing the uh functional requirements uh the nonfunctional requirements we'll write one by one or suppose if I'm taking one particular spe one future I'll Write the basic flow and then data objects and everything Grocery and everything next immediately I'll write the nonfunctional requirement which is relevant to the particular requirement or combinedly we can write all the non-functional requirements at the end of the document how it works and the end of the document or first
• 97:00 - 97:30 functional okay don't confuse the developer he won't see okay so functional fully everything functional and the last is completely non-functional okay perfect thank you thank you yeah okay so I think we are good for today I will see you tomorrow thanks for joining everyone thank you thank you so much thank you so much hi everyone thanks for joining so in today's video today is day three and we are
• 97:30 - 98:00 going to talk about some of the uh business analysis techniques so I'm going to continue with what is BPM and other techniques okay so we completed most analysis yesterday so today we're going to talk about what is business process modeling and how to like draw all these BPM d diagrams and flowcharts and everything okay so what is business process modeling business process modeling is nothing
• 98:00 - 98:30 but uh it is nothing but it's a way of like creating a map or a flowchart or maybe like a a diagram on like the complete end to end process okay so that that is like helpful for the business owners also for everyone within that particular who is involved in that particular project everyone is able to understand what is the end to endend data flow and uh like how the process is working currently how
• 98:30 - 99:00 it is working and in future like what kind of automation we have to do so why why is this business process modeling important because not everybody even the business owners right they may not know uh the complete end to endend process because let's say like for example like I'm taking Georgia Market okay in Georgia Market uh let's say okay so we we um let for
• 99:00 - 99:30 example let's say Bank of America okay Bank of America is launching something like for example uh mobile check deposit mobile check deposits nothing but you can scan the the deposit checks by using mobile app like Bank of America app okay and you can get the app you can like uh login uh through your member ID and your password and everything and then you someone gives you a check okay for $100 what you can do is you you need not go
• 99:30 - 100:00 to the bank okay there is you need not go to the bank or you need not go to the ATM none of that is required what you can do is directly deposit using your mobile application I don't know whether this is in India but in us it's very common here to use just your mobile app what you have to do is you have to like sign at the back of the check and then you need to write um write a deposit at Bank of America only something like that so you can use your smartphone then make sure that you take
• 100:00 - 100:30 pictures of that particular check and then when you scan it through that application what will happen is the system this mobile application right that will be automatically it will be able to pull up the member data using the OCR process OCR is Optical Character recognization right so using that OCR process it is be able to like um identify whether this is a valid member ID or whether this handwriting is um I mean also the amount and everything and
• 100:30 - 101:00 also it is able to get whose account this has to go so everything it will do just in like a minute or something it'll be able to identify the data so it is able to identify the member data and um able to like uh deposit the
• 101:00 - 101:30 amount in your bank account and maybe in like maximum in 3 4 minutes you'll be able to deposit these all the checks that you receive from your friend or someone okay so you need not go to the ATM also you need not go to your bank or something and stand in the line or so you're like saving about like one or two hours of work so if this is this Fe is currently not there and Bank of America business owners are coming and telling you like you are from this it team they're coming and telling you we need a mobile
• 101:30 - 102:00 application feature so where uh people can deposit paper checks okay so paper checks they want to deposit that using the OCR process and uh our mobile application must be able to identify whether this is a valid member and it needs to do all the basic validation okay first name last name all the validation and then whether this uh also able to like understand the handwriting and also must be able to understand the correct amount and
• 102:00 - 102:30 everything and after the validation is over it it must be able to process the amount give you a notification that the amount has been processed and deposited so this is a new requirement that you're getting okay for your application so in that case what if you want to create a business business process uh modeling diagram okay because currently it is not there but you want to do that in future for that you need to know currently what is the status of that workflow So currently how are we depositing like we
• 102:30 - 103:00 going to the bank and someone from um uh from the bank is able to like you're giving the check and they must be able to like manually enter and then validate and everything and then they'll process and give it to you or you can you go to the ATM ma that machine and you'll be able to process it there are different ways right how to process so that is the current process but in Future How It has to happen that automation that we are trying to do through using the mobile app so that we have to create as a ba
• 103:00 - 103:30 now you have to like now draw like diagrams and show to the business owners developers everybody because you are seeing that you you this is the final product and you're seeing it now but as a ba you have to think this imaginarily you'll be think hypothetically be thinking this is how the application will work now I have to create a diagram for this and uh if there is any mistake of course the business owners will try to help you but you need to like
• 103:30 - 104:00 understand like um from when there is a brand new project or enhancement project the easiest way to like make sure everybody understands about this process is to uh create diagrams so that can be like it can be process flow diagrams it can be flow diagrams so that is that is what we called as um business process modeling right so this is called as um model annotation we have flow diagrams we have um data flow diagrams flow charts there are so many diagrams I'm going to show you so for example I meant
• 104:00 - 104:30 to lose it flow uh chart here if you see there are like um all the diagrams will be there okay flow charts is there and then we have uh business process modeling examples collaborative diagram process flow diagrams so I'm going to click on this okay this is how you will create a uh bpmn diagram okay so in Lucid chart right automatically the template is available so what you have to do is like you can directly get this
• 104:30 - 105:00 template and then you can just you have to like change the wordings that's all you need not create everything you need not even know the meaning of all the symbols but I'm going to teach you the basics of the symbols but um when you have like this um softwares like where already they have templates for all these kind of diagrams okay so you can use these and then you'll be able to create any any kind of flowcharts or you can create uh mind maps or you can create uh business pro process diagrams
• 105:00 - 105:30 so if you see here if you want agile you can create every day like daily standup meetings diagrams I mean you won't be doing um stand up meeting diagrams but you'll be doing all these kind of diagrams okay bpn diagrams so what is the difference between flowchart and uh business process for diagrams is I'm going to tell tell you what is the difference but you need you have to draw these diagrams you need to know how to draw these diagrams because it's very
• 105:30 - 106:00 very very crucial for you to when you create a BRD or when you create something in Confluence and you want to document everything the very first thing the developer is going to ask you is like can you give me documentation I want to understand what is the current flow I want to understand what the business wants okay so they want everything to be documented another thing why we need to document is because today you may be be for that particular project and tomorrow you may be going to a different project or you may leave the organization we don't want the knowledge
• 106:00 - 106:30 to just go with you we want every for all the projects we want that every like the diagrams all the documents to be somewhere available for the future teams and future Bas because otherwise it's very complicated the like the new Journey right they have no idea what's happening in this project what did the previous VA do for this project so we don't want to do that right so that's why project maners are they will be very particular um and like for you to like the draw all
• 106:30 - 107:00 the diagrams and do documentation so you need to learn how to draw these diagrams is very crucial so um I'm going to like okay I'm going to teach you on the symbol so if you in Lucid chart right if you go and type like um BP MN diagram symbols and notations you'll be getting like the basic like what are the different um symbols okay common symbols
• 107:00 - 107:30 and then what are the even types what are the activity symbols so you'll be getting all these like basically what is this um definition of all the symbols you'll get everything they've given very clearly in this lucd charts okay I'll give the link you can go and read so this is not flow diagrams so you need to understand the difference between flow diagram and bpn diagrams okay bpn diagrams have like very set of standard symbols it's not flow diagrams flow
• 107:30 - 108:00 diagrams you know like we have done in schools and colleges and all like the rectangle or square symbol and all right so that also I will tell you for example here in Flor diagrams it is going to be very different the symbols are going to be very different but in BPM and diagrams you will have like different symbols so for example we will have something called event types so okay like start event and then intermediate event and end event okay so here for example start means like something like the process is starting and what is in
• 108:00 - 108:30 the middle something that occurs between um the start and the end and the end event simol so this is different this is not in flow diagrams in flow diagrams you won't have this okay in flow diagrams if you see here there'll be a start that's all and there'll be end that's all okay in the middle you'll have like other different processes yes or no like that kind of combinations but uh in bpmn it's it's going to be different okay then in event symbols for example bpmn event symbols you're going to have a message symbol message symbol
• 108:30 - 109:00 is something like it will trigger the process or it will be like uh finishing the process for example trigger a process means in this application in this request um once the check is being scanned okay using your smartphone uh the OCR technology is able to identify the first validation that it has to do is like it has to like capture the member ID right in that first check has capture the member ID and uh basic
• 109:00 - 109:30 details so that's the first thing it has to do okay before even it has to um forget about the amount and everything the first validation is member validation so same thing here some process that will be like that message symbol is something that triggers the process then we have a timer symbol like the time date and recurring um time or the date that triggers the process or completes a process and then you're going to have escalation symbols so and
• 109:30 - 110:00 then for example like um this is like a subprocess right so for example I'm I'm scanning the uh check but the member ID is invalid now what I do okay if member ID is valid it is able to um identify the amount and everything and it is able to process okay but it's not able to identify the member ID now the sub process what it has to do okay escalation means now what it has to do so whether it has to like say that this is an invalid check or maybe please scan
• 110:00 - 110:30 properly or it's like invalid or scanning issue some kind of error it has to throw so that is called as escalation symbol then we have conditional symbol this is like business rules right so like for example they have to have a member ID they have to have the correct amount they have to have the signature and only if three three conditions are available only then process the check so what this condition will be like given by business owners so for that representation you can use this symbol okay these are like standard business rules for that particular process
• 110:30 - 111:00 business wants to do these kind of uh checks or validations so without that we will never process it so those kind of conditions and then we have link symbol so linking from one process to another process then we have error symbol like I told you invalid member ID then you have this error symbol then you have cancel symbol compensation signal symbol so there are like different symbols here you can go through uh take uh show you here the diagrams so you can like Google
• 111:00 - 111:30 and then see like multiple just use like different kind of case studies on the symbols okay so how uh the symbols are used for um in case studies and make sure you write it in your resume that you know how to write how to draw a bpmn diagram you know how to draw all these diagrams you have to put it in your resume okay so bpmn diagrams flow charts data flow diagrams data flow diagrams and then uh
• 111:30 - 112:00 you know how to draw there different diagrams there you this and all you need to add it in your resume very crucial for the uh the senior ba to understand whether you know how to draw the diagrams because they will expect you to know how to draw diagrams also like what kind tools you have used okay they may ask you have you used like for example here I have Smart sheet here so I have um uh I mean I have used my email ID and
• 112:00 - 112:30 I have logged into smart sheet if you go to smart sheet right you'll be able to when I click on create new you'll be able to create lot of things so here it says upgrade but still you must be able to see see here simple project plan and then you will be having like um what are the diagrams so almost all all the flow charts and
• 112:30 - 113:00 diagrams will be available here okay you can either use these but the problem is these are like paid ones so you have to upgrade I'm currently in the free plan to just show you like you have Smart sheet you have lucid charts so in Lucid charts also like um for example yeah I've logged into Lucid chart now so if you want to create mind map the basic like uh structure is already provided to me I have to just now enter only the I have to like for example I have this back like a main idea is like process checks
• 113:00 - 113:30 through using OCR okay process okay so uh by using this technology I'm going to like um process all my uh checks so I'm just giving you an example like this you can already instead of like doing it from scratch you can always use the kind of like tools and created um at least for learning purposes before you like go to an interview right get the free version of
• 113:30 - 114:00 all these uh tools and then like uh just play with it to understand what is mind mapping what is flowchart what is the difference between data flow diagrams and process flow diagrams like for example what is see here so here they they have an example of um see the timer symbol is there cancel symbols there message symbol is there start symbol is there end symbol is there so all these symbols are there and this is not flowchart so that's what I'm trying to tell you this is not flow chart
• 114:00 - 114:30 flowchart is going to be different and interior may like if you say I know how to draw BPM and diagrams interior is going to ask you for example like in product based companies like Samsung I have been to Samsung they will ask you to draw diagrams if you say something right they'll be asking okay can you can you draw something from me so you don't uh mess up with them you always always learn the basics of different if you say something in your resume that I know this please know the basics of that okay and what is the difference they may ask
• 114:30 - 115:00 and why are using uh bpmn and flowchart they may ask you so like be prepared when you put something in your resume please know the basics without knowing the basics don't add it in your resume you'll be like it'll be an embarrassing moment for you there because the interviewer is like understand they have experience they'll easily figure out whether you have experience or not okay so um understand the basics just play with all these tools so you can add all these tools in your resume tool so some people are like I don't know what tools to add
• 115:00 - 115:30 so you can always add the smart sheet I mean this um uh Lucid chart or you can always in uh in Confluence you have that gfy flow diagrams so you can use any of these diagrams and U tools and start um practicing all your diagrams okay very very crucial for you to draw the diagrams okay so uh anybody has any doubts till now on these diagrams hi yes yes B
• 115:30 - 116:00 hi for these diagrams we we use these Lucid chat also for UI diagrams as well or is there something is for UA right like for front end diagrams like um like how it has to be there you can use like it depends upon what what is the coding language right for example like if you application is use um created from Pega language then you have a Pega like UI diagram software too you can directly draw
• 116:00 - 116:30 Pega or if you can directly draw Salesforce too like to understand how that UI will be for example here right this is a pegga application Bank of America this is Pega so here if you see right this uh the check um diagram should be on the left and then like other like for example chat with Erica set up customer alerts and then uh debit card log fingerprint log login bill pay so all this has to be in the bottom then like clearly what the instructions has
• 116:30 - 117:00 to be here so if you want to draw a diagram okay UI diagram of this particular page you can directly do it in Pega itself otherwise if you want to draw it here you can also draw UI diagram so that's not like you can always create um but if it's you're going to draw in Pega it's going to be very easy instead of you're drawing in here right um in lucid charts if you're directly using that particular software and their UI models it it'll be easy for you to draw because that's what exactly
• 117:00 - 117:30 that is what the developer is going to do they're going to like understand okay the Box needs to be here and then uh the wordings needs to be on the right side and then there are like five different boxes on the bottom so it's easy for them to replicate the same there okay thank you okay uh yeah pradipa difference between the BP MN and the flowchart uh so flowchart is like we will show in a flowchart based on for
• 117:30 - 118:00 particular feature right yeah and bpn means like overall business process flow how that particular overall product or in that way so for example here if you see right this process flow means there's a start I mean flowchart means it's very basic simple representation okay okay member is like now I'll give you an example member now scans the check okay now there is validation done s means
• 118:00 - 118:30 process the check load the amount into that um members account then end that's all this is standard negative it it's not able to identify member data okay validation is not there then you throw the error standard flowchart very simple diagram but in business flow it will not be like that completely end to end so member has to first like take the um check right write down the details like everything in detail you have to do business process means every single thing so it's a combination of like
• 118:30 - 119:00 process information as well as like some kind of like validation information too you understand flowcharts is very basic diagram okay but here uh in business process right it's like a little more detailed as I told you if you see here little more detail here if you see like you're going to exactly tell like what is going to happen if there error message means what kind of error message if there is some kind of issue means what kind of issue you're going to put that error message
• 119:00 - 119:30 and say this error message understood so um FL when you compare flowcharts this is a basic diagram if you see here just you're telling one standard process in single line you're just saying okay if this yes or no combinations whereas in process flow it's not like that if there is invalid member ID what should happen okay what kind of error needs to be thrown if it is a valid member ID then what is the next step what needs to happen so this is like more detailed this is a combination of both business process and Technical a
• 119:30 - 120:00 little bit of technical details not too much but we are going to at least say how the member validation has to happen how the what are the basic OCR process like um uh like details that we need to capture if we are unable to capture then what needs to what kind of error needs to be thrown so this is a little more detail whereas in flowchart if you see you know flow process is like like standard like you're just defining the process in one single diagram that's all like very high level I would
• 120:00 - 120:30 say yeah got it thank you yeah so um it depends right whether what kind of like how your project managers how your developers want um the diagrams they may be like so for some developers flowchart should be fine they'll be able to grasp things for some people they'll be like no this is all very basic please can you do more documentation so that we understand everything every single thing what's happening in the data flow so only then you're going to draw this I always recommend to you to learn how to
• 120:30 - 121:00 draw all kind of diagrams because every project is going to be different every business owner is going to be different so okay every once every six months your projects is going to like you're going to get new projects everything will be different for you so in order to also in order to enhance your own ba skills okay you need to know how to draw all the diagrams so just practice the ramp number of resources available in Google so try to practice you can always use any all these tools and you can add that in your resume the best part is like you
• 121:00 - 121:30 can add a case study in your resume so for example I know how to draw these diagrams I have drawn a diagram please see my attached assessments or something like this you can add so that your resume will be like okay oh this person knows how to do stuff and I added documents so especially product based companies forget about CTS ccs and all Samsung Microsoft Google Amazon Tesla uh all these companies right their interview is very different from the service based companies so in product
• 121:30 - 122:00 based companies they ask they will definitely ask you to draw everything you put something in your resume they going to ask you a question ask you to draw because they definitely want you to see like whether you have those skills or you're just fcking your experience so um in my opinion please understand the basics in the resume please be very like true to what ever you have written in your resume and don't be don't get embarrassed in the resume you add something and you don't know the basic information about it then um then I mean
• 122:00 - 122:30 like you will you will not have confidence to proceed the interview then okay so next is what is this uh pestel uh analysis so this analysis is nothing but P is for political e is for economic s is for social T is for technological e is environmental and LS for legal so let's learn about this okay what is a special analysis
• 122:30 - 123:00 okay so this is nothing but it's a analysis with all this like six factors okay so well for example you are taking your um you are launching something a new product in a particular Market okay let's say a Healthcare Company and uh they are launching something uh maybe a new healthcare plan in a particular Market okay so if they're launching something
• 123:00 - 123:30 they need to understand like what type of people are there in that particular State and then like what are the political uh factors for that particular State what is the state law for this health plan and um how are we are going to like for example in the US um every state has have their own laws okay so for for example in New York something can be legal in Florida that can be illegal in Virginia something can be legal whereas in New Jersey that will be illegal so every state have they have
• 123:30 - 124:00 their own uh political factors they have their own social factors they have their own economical factors so everything is going to be different Let me Give an example of Medicare and Medicaid okay Medicaid is nothing but a state benefit that's an uh insurance for low income people in every state that is given by the government okay state government is giving them that benefit if you are like if you're earning below like for example $20,000 per year then you are eligible
• 124:00 - 124:30 for this Medicaid insurance program you can apply so if I am health insurance and I'm going to like expand my business in for example in um New Jersey Medicaid area okay so I'm a health insur for example I'm Signa I want to like uh create new additional plants in New Jersey area especially for the Medicaid Market Medicaid health plans I need to understand the pr and cons of implementing that plan in that particular State because we never know that will be a success or a failure so
• 124:30 - 125:00 every Insurance in the US it's all like private insurance there is no like government based insurances in the US okay so it can be ATA it can be Signa it can be Anthem it can be Blue Cross Blue Shield elevance health anything anything all the insurances are private insurances whereas the government is giving certain health plans like Medicare Medicare these are government based insurance like schemes that they're giving but everybody has to go through this private insurance only so for example I'm eligible for Medicaid I can get a Medicaid approval from the
• 125:00 - 125:30 state but I have to choose one of these insurances and using those insurances only I have to like get that benefit so here we don't have government hospitals or we don't have um uh directly like in India how we have government hospitals right we don't have such things here so everything is private hospitals all the hospitals are private okay so give me a second so we have 10 minutes more okay so all the uh insurances are like um um they private
• 125:30 - 126:00 insurances all the hospitals are like private so if I want to get a government based like um subsidy or a government based Insurance even though I I get approval from all the state and everything I have to choose a private insurance I have to either go with itna I have to go with siga or I have to go with them or brost blue something like that I have to go through them only and then that insurance right they will be like processing even for Medicare medicate they will be processing all the
• 126:00 - 126:30 claims and they will get the reimbursement from the government that's how the process here in the US okay so when I'm launching a new healthare plan in New Jersey or will I'm launching a new Medicaid healthare plan in a particular State I need to understand whether that particular um what is the political uh factors available in that particular State and what is the economical factors in that that particular state if I do something whether it will backfire the company and whether there'll be like a loss so we
• 126:30 - 127:00 have heard that for example compliance issues in certain in certain states are going to be very very very difficult they don't allow certain products they don't allow certain things to do in uh New Jersey whereas it can be very opposite in Georgia and Georgia is legal anybody can uh do uh CBD they can do cannabis they can do like uh drugs is legal and certain States so it's different right from one state to another state it's like the economic or social factors environmental factors are totally different when you get such kind
• 127:00 - 127:30 of projects so if you're working for a insurance company and that is a new Medicaid plant that's going to be launched or rolled out in that particular State and they're coming to you they're saying that okay now we have a new plan so if there is a new plan what will happen if there is a new Medicaid plan going on for New Jersey so they going we are going to add new members so the members have to uh must be able to like uh log in through their web portal or they have to like um submit um
• 127:30 - 128:00 for example in the web portal right they must be able to um do registration they must be able to log in also they must be able to see all their documents previous documents or any kind of referrals they must be able to see or if they for example if it's medic Medicaid means um if there are um some of the um like um like gloves or like uh we have
• 128:00 - 128:30 accessories right wheelchairs all that can be reimbursed even if they're using that um um what is that uh if someone is a bed ridden they can use that napkins right so for all that will be reimbursed using insurance will reimburse everything so food also they'll be like for example they're having only liquid food so uh those kind of products also reimbursement they can submit claims so if you are working for it this web portal right for this particular plan only for them that features needs to be available so if I have a health can I'm
• 128:30 - 129:00 in uh Open Access plan okay this is my plan only that particular member must be able to see those all these features I can submit a maybe an accessory claim I can submit a wheelchair claim I can submit like maybe a food food claim or maybe all the physical like walking Street Claim whatever it is I can submit only for that particular region only New Jersey members only that who is having that particular Medicaid Open Access plan right only they should have access to that particular features not
• 129:00 - 129:30 everybody across uh Anthem or not everybody across siga or not everybody across Etna must be able to view those features in the web portal even the web portal is looking same for everybody but if I when I log in through my username and password that the backend database must be able to identify okay this member ID is for this particular plan so for all these features has to be open so they can submit a claim or they can they'll be able to reimburse the claim or whatever so business owners will give you like this is particularly for
• 129:30 - 130:00 Medicaid and uh this is for New Jersey members and then uh they will be they need access to submit claims through web portal or maybe uh they they need to uh download all the documents through the web portal or like this they will give you very specific scenarios for that only you'll be using this PES analysis this is like a very very high level analysis this is not like an um feature
• 130:00 - 130:30 level analysis we are not uh talking about um feature level every single feature we are not talking about we just taking from like a like from a plan perspective what is what are we going to do whether they will agree or not because we are not supposed to lose money understand this is all private insurances if they're launching a new product in uh one of the states their end goal is to get at least some billion 1 million or two I mean one billion or2 billion dollars for that particular Market that will be their profit level
• 130:30 - 131:00 so in order to get that they want more number of members to like join the program like I already told you if there are 100 people everybody has Medicaid but they have that option to choose to go to it now to go to Signa or go to uh blue Closs blue sheet they have option so now like we have to be very competitive and get those members make them they enrolled into our program so that we get the benefits from the uh government so as an insurance we are very profitable and we are growing so
• 131:00 - 131:30 that we can buy other competitors company when we have huge profit we have 4 billion profit we have 5 billion profit now I can acquire other company I can become more profitable that's the end goal of any private or corporate insurance right so uh this is on a very high level project level they are doing this analysis but as a ba you need to know because you need to know if you are you want to become a senior ba Junior ba will not be uh doing all this analysis but if you are a lead ba the business
• 131:30 - 132:00 owners will be asking you okay I'm launching this particular feature in this uh New Jersey can you give me data for the other plans how much response was there so for example if they have to enroll in some kind of um survey okay Healthcare survey okay healthare usually like any kind of insurance that they'll give you survey so that is a survey tell me give me a report like last month for other plans
• 132:00 - 132:30 like how many people submitted that survey through web portal how many people submitted the survey through mobile application how many people submitted that survey through paper or through facts can you give me a report now as a ba you have to get that report from the database okay so you will be like making sure you query and then you get that report like through paper for this particular plan for this health survey through paper like the th000 people submitted and through web portal like 3,000 people submitted or through uh facts like 200 people submitted like
• 132:30 - 133:00 you will give uh all this report to the business owners now they will be able to take decision okay I'm launching I'm launching something using web portal only like major people are like they are submitting a health uh Health survey let's focus on the web portal because that's where the maximum members are responding instead of paper paper is going to take a l lot of time you have to mail them they have to then they have to like submit the surve back then we have to process everything then again that will be loaded into database it takes about 2 weeks timeline so let's
• 133:00 - 133:30 make sure like we have the members um opt in for our insurance using the web portal let's Market more of web portal services so they want the data before even they launch something on the particular um uh State they want that some kind of feedback from you some kind of report from you from it perspective this data is very very very crucial for them before even they launch okay so that time as a ba you have to like like make sure you query and get the reports
• 133:30 - 134:00 from them you can take a help of a engineer and then you give those reports to them so that on a very very high level they do this analysis and they can make sure like how to like launch a particular product first we make sure that the web portal is going live then we make sure that paper is going live then we make sure that uh fact is going live like that one by one they will roll out so that is special analysis um okay so I think our call is going to get cut can you guys uh
• 134:00 - 134:30 rejoin so let's focus on so that's why we are doing this special analysis so um you need to know about all these and then when the interview is going to ask you you can always say that why this is done give them a case study and then how what did do you you do in your project if they ask like just combine all these techniques and make sure like you answer it that you have done okay because they want to know whether you have done some kind of like different kind of analysis
• 134:30 - 135:00 like uh most analysis what analysis all is very common right so you can always say this too and then we have the last one is catw so C is for customer A is for actors T is for transformation W is for world view O is for owners and ease for environment okay so what is this uh C let me
• 135:00 - 135:30 take okay so what is this uh cat analysis this is called as uh this is one of the analysis for stakeholders okay so why are we going to like uh do analysis with stakeholders because it's very crucial to understand who's the KE key players and who needs to give approval and how a business owner is very there can be 10 business owners so that you need to understand not only one person so like I said in the previous example
• 135:30 - 136:00 right we are launching something in New Jersey that New Jersey Market they are all full-time employees of of over own company they not some different vendors you need to understand that when I say business owners right they are full-time employees of the particular insurance so there is a leadership level so you have the CEO then you have the VPS then you have directors then you have managers project managers simultaneously under the project managers or maybe different line they'll be like this business owners they are also like as we are from it right these people also are like
• 136:00 - 136:30 full-time employees of that particular insurance company so they are not from different uh company or different background okay they are our colleagues so there may be multiple people for that particular Market if I they say New Jersey Medicaid there can be four to five people of business owners who's going to come and throw like their own uh ideas because they like I told they may be colleagues they may be like reporting to the same VP so everybody's like I want I want this application to look like this
• 136:30 - 137:00 I want this application to look like that so when there are like five business owners and you are lead ba you scheduling that first call and everybody is throwing their opinion then you are like which should I follow whether I should listen to her or whe whether I should listen to him or like how what what should I do now so that is why we have to understand this Stak analysis is very very crucial to understand their ideas their priorities and wishes before we we put forward our recommendations
• 137:00 - 137:30 okay so because we don't understand like why five people are giving five ideas when they are reporting to the same VP okay some will say AI is important I want the chat bot for example here it says like chat with Erica right when I click on here it goes to um that application that chatbot name is Erica okay so like how Alexa is there for Bank of America we have Erica Erica can talk to you how many languages it can talk now it is only available in English what
• 137:30 - 138:00 is uh Eric do it can always like answer all your basic questions okay so regarding um yes we have recording we we keep a record of your conversations with Erica so this is like a chatbot for uh Bank of America so for this feature right let's say for this they want one business owner is saying we want like an AI chatbot uh we want like all we don't want customer care calls right there are too many people in the queue answering
• 138:00 - 138:30 that we want something like this like Alexa we want in mobile application we want the members to chat and find the ansers so this feature one business owner saying they want another business owner is saying no no no uh we don't want we don't want that uh I want everybody to call to the customer they're having conflicts between themselves and you are lead B you'll be like okay tell me like finally what do you want I um you can schedule multiple calls and they can still have conflicts and they will not give you requirements this is a practical difficulty that
• 138:30 - 139:00 every ba is facing they can also be in questions to you have you faced a conflict uh with the stakeholders how do you handle a negative stakeholder when they are having conflicting requirements how do you handle that so that's why we are going to use all these techniques okay so we'll be like we cannot say um everybody keep quiet and then one one should answer we cannot talk like that right so you'll be like you'll become very creative and you have to say that okay um the next call I'm going to do uh catop analysis and then like um we'll
• 139:00 - 139:30 make sure like I know everybody have their own ideas so what I'm going to do is the next all we going to perform this analysis and we will come to a conclusion what is better for the customer uh that's what we are going to do right business owners want something we are not supposed to do that we want like from an end user perspective from the customer customers perspective um whatever we whatever is useful whatever is helpful whatever is beneficial that's what we want to do as a organization so uh let me take
• 139:30 - 140:00 that okay so that's why we have to analyze the stakeholders because difficult we'll have very difficult stakeholders and sometimes you'll end up being like frustrated you'll be like how how do I handle this should I escalate to my manager escalating to your manager is not going to help you because these stakeholders are giving you money and you are you're submitting a time sheet because of the stakeholders they are giving you a new project and you are being in the job because you're doing something for them and your time sheet
• 140:00 - 140:30 right it's from that budget only there is some there is like a new project for another six months your time sheet is now like submitted because of that budget only right so escalating a manager is very childish I would never escalate to my manager unless an ENT is necessary so I'll be like mostly like handling everything by myself making sure that even like however the difficult the stakeholders are can be we are all from the same organization and they are your colleagues and they can have conflicts they can give their
• 140:30 - 141:00 opinions they can be very tough they can give all their concerns and everything but end of the day we are we are launching an IT product an it or software application for the benefit of the customer also to show profit so that as as a team nobody's getting fired even the business owners is not getting fired you are not getting fired so that kind of mindset said you need to develop nothing needs to be personal here because you take everything personal then you cannot grow an organization okay there'll be like different level of human beings with
• 141:00 - 141:30 their own ideas they can be very complex thinking and then uh some can be really rude so always like you have to have the Detachment with um these business owners the stakeholders and also with your colleagues that this is a professional working environment I'm not going to like show my emotions here and then going to be like for example next time they join the call you are being very mute on the call and you're not going to answer because you have some kind of conflicts with them you to everything personally so I would like um you have
• 141:30 - 142:00 to learn that skill of Detachment also like not being emotional with any of the stakeholders even they are screaming you have to be like very polite and you have to say that okay I think today is not a good day let me reschedule this call and the next time I'm going to um do some kind of different uh analysis so these analysis will help you because when you to brainstorming so we have a technique called brainstorming right so uh this brainstorming means uh this we call it as brain writing so what will happen is
• 142:00 - 142:30 in this brain writing examples everybody will be giving their own opinions there are five people means five people will give this um for example this is called as brain writing okay that's why I don't use this brainstorming methods because five people are there everybody is going to give their own like uh opinions and then uh there going to be conflict as a ba you'll be like stuck on what opinions you have to do like five people they giving the process needs to be like this
• 142:30 - 143:00 or process needs to be like that we want Erica we don't want Erica like they may be like giving their own opinions after a 2hour call you don't know whether you are getting requirements or what is this are we having coffee with them so this is that's why I don't want people to go to this brainstorming techniques instead use some of these analysis techniques it can be SWAT it can be most or it can be on the special or this can be um as we said like now we have this cat like get
• 143:00 - 143:30 into like a very specific technique so that you don't give the time for the stakeholders to blabber something okay so this is what I want for example if it is catw means um we have like um what does the customer benefit from this program okay and then What actors means what is the role of like what is main what is the business process why are we doing this what is the core process why the customer is going to for example here in Bank of America what is the what is the benefit of the customers we need
• 143:30 - 144:00 not go to the bank we need not go to the ATM and what is the main business process we are depositing checks and what is the transformation The Core process that uh delivers is the customer is getting the money within like three to four minutes okay so a lot of time is being saved and what is the world view this is a technique that is developed by so this catw technique right that was developed in I think in 1981 yeah 1981 by a professor called
• 144:00 - 144:30 Peter cchan in Lancaster University so he only developed this process technique what he is saying is you need to understand when you develop a software application when you develop a new process you need to understand that why why we need this process why the customer need this what is the value that I'm giving to the customer and because of this like uh how much time he can save and how much money he can save and um how much user friendly that application is is going to be so all
• 144:30 - 145:00 that from a world view world view means from a customers view or the end end user view we need to understand the values and the um benefits that the customer is going to uh get because of you doing something for example this Erica Erica can be very helpful you need not call be like in 20 minutes on in some like automated um customer care machine and then at the end of the day to say and to say something is not available so I need not wait for 20
• 145:00 - 145:30 minutes to get a status of something right I can manage everything for example you can manage your cards you can get your account information you can pay through zel like all your online payment you can do you can invest also so for all this this era is going to help this is what my customer wants okay my customer doesn't wants to stand in cues my customer doesn't want to be uh calling the customer care for 30 minutes and uh to get some like um like maybe in the middle of the call itself that is going to drop your call is going to drop
• 145:30 - 146:00 again you have to call and get the status right so all that to avoid all that we have to make sure the world view is very very very important and you're going to when you develop any software you have to get all this like why am I do why we are doing this what is the benefit and uh get all these values and then you can Define the process okay that's what this is called as catwa analysis it's very very very um easy so we have um for example we
• 146:00 - 146:30 have a case study here so the case study is um in one of the um in one of the areas right the C they want to do um High Street clothes store okay so high in some clothing store if they want to develop that what are we going to do why we want to have a high brand a highend Brand store okay so when people are focusing on like inexpensive fashion clothing why are we targeting youngsters to be like interested in this
• 146:30 - 147:00 highend closeth this branding and all right so from that brand from Tommy giler from Michael kores from um different kind of high-end Brands why why people has to buy this highly expensive clothes when they when they are able to buy the inexpensive clothes right so what what are we going to do BU so remember we are focusing here for the highend brands we are focusing on people who already have money we are not going for middle class people so when people already have money you have to like have
• 147:00 - 147:30 a impression like if I wear a Michael korus dress and there is a Michael K label on my shirt I feel proud I feel like I'm a brand I'm my like that gives me confidence so when when you always see like this high-end Brands when they're selling some shoe some handbag for $1,000 like um like Lou Von you have the basic handbag itself like for $2,000 why people are buying it I can use a $10 wallet but I'm going from buying for a
• 147:30 - 148:00 $2,000 wallet why why should I buy why should I buy because that label that highend Brands label whether they are luxurious or not or they from same made from same quality or not we don't know we don't know the manufacturing process but the marketing process is like to make sure the customer when they buy something and come out of the store or the high-end store they feel happy they feel like I'm a new brand now I feel confident when I wear this expensive shoes I feel confident when I have this expensive
• 148:00 - 148:30 handbag I feel confident when I wear this expensive watches I feel confident so that kind of like customers thinking right that's that is the first thing for marketing whether it's valuable or not that nobody's going to care whether we we want the customer to buy it how can we make sure someone enters into my store and and buy a $2,000 wallet okay so for that kind of high-end analysis even for Apple products you can say that compared to other phones Apple phones are like very very very expensive so
• 148:30 - 149:00 they may always be like doing analysis on launching whenever they want to launch a new product on September right they'll always do all these kind of analysis and make sure that um the um they'll be like to enter into people's mind into customers mind and they'll always like see this for example iPhone is the best phone even though it's expensive that is the best phone and then they'll make sure that you buy that product that's how mnc's are so when you develop any software also you when uh multiple
• 149:00 - 149:30 people like stakeholders are having issues you always go with this kind of techniques and you make sure that um you get the information from them and then um you provide from that information right in the next call you provide back the feedback I would not recommend this brain writing it is very complicated and it is very tough for for you to handle a huge crowd like 20 people in the call and then everybody throwing their ideas is very tough so my recommendation is use other techniques like standard
• 149:30 - 150:00 specific techniques so that uh you can at least come to a conclusion of this is the requirement that they want okay any doubts still now okay sounds good and tomorrow we I'm going to cover the other techniques okay so what is MCO and use case modeling other techniques and from Monday we are
• 150:00 - 150:30 going to talk about documentation so I'm going to teach you how to write uh brds fds SRS documents also other documents like in Confluence um how to write user stories and everything that will documentation class will start from Monday but uh tomorrow we will cover the other five different techniques okay okay thank you thank you everyone for joining thank you hi everyone good morning thanks for
• 150:30 - 151:00 joining so today is uh day four and we are going to cover some of the remaining um requirement Gathering techniques okay give me a second so I am going to um yeah so the first one we are going to
• 151:00 - 151:30 start with the mosco um technique mosco is nothing but must have should have and then could have and wouldn't have Okay so let's go to this technique okay so what is MOS code technique so if you you see here um this is a prioritizing prioritization technique or requirement Gathering also you can use for both so during Gathering
• 151:30 - 152:00 requirements right you need to know what are the requirements that is like non-negotiable and it's very very very important it's a must have and then we have what are the requirements what are the features that is like should have should have means it is important but it is not like like essential okay essential in the sense like non-negotiable is must have should have means it's important but it is not like essential could have means it is nice to have these features but there will be a
• 152:00 - 152:30 very small impact if we don't do it and will not have uh nothing but these are the requirements that is not a priority at all okay so what is must have requirements must have sorry about that so um so must have requirements are nothing but these are very very vital requirements and you have to finish this task and if you don't finish these features uh you cannot proceed for example uh like I said about S Bank of
• 152:30 - 153:00 America project right in order for the OCR process to take place the member must be a already a registered member the members should download the mobile application member must be able to log in using a username and password then only scan the check and then may be able to um and the OCR process will be able to pull the extract the the data from the check paper check and convert into a digital money right but so you know for that feature okay what are the must haves must haves is the member has to have a mobile app okay and then must
• 153:00 - 153:30 have is like they should have a valid member ID and a password and so it's not a new user this is an existing user so that feature is for an existing user if there is a new user for Bank of America they have to make sure that they register they log they get a login and a password and then they have to like download they need to have smartphone so like for example like um iPhone there will be a different um mobile app and for other phones we are going to have a different app so they have to like make sure whatever phone they have
• 153:30 - 154:00 accordingly they have to like download the mobile app of Bank of America and then they have to proceed that uh um process so must have is like without this without a proper username and password without downloading the mobile application this I mean that particular feature cannot be done so those requirements are must haves it needs to be an existing member the member needs to be registered member needs to have a username and password and member needs to have the mobile application downloaded thesea must have requirements should have requirements means some of
• 154:00 - 154:30 the task like uh um like for example like this is nice to have but this is not essential so once they log in once they log in now we are telling like um once they scan the process right like for example they scan the paper it's nice to like um get get only the member for example member ID is enough but in order to produce like various different validations you're going to uh check whether the account number is correct or if the handwriting is
• 154:30 - 155:00 correct uh account number is correct or if some validation is correct right so these are requirements for should have some can be it's okay if during the OCR process if the handwriting is like a total mismatch then we cannot proceed but if the handwriting is uh is mostly all the optical character recognition technology right they'll be able to identify the handwriting but if they are not then what what those are called as Fallout requirements Fallout
• 155:00 - 155:30 in the sense like for example in the OCR process if I am um okay so if during the OCR process during scanning the paper checks if suppose in case the system is not able to identify due to a bad handwriting okay they're getting the member first name last name like uh for example I write $100 okay and numbers also I put $100 but uh my handwriting is not like
• 155:30 - 156:00 good it's when the OCR process is not able to capture the handwriting then what should it do it's called as Fallout No it should throw an error what kind of error like please rescan properly or this is like um invaluable check something like that it has to throw an error right so that and all what error it has to show on or whether it is needed or not or what happens to the Fallout scenarios and how we are going to notify the member these are all like should have should have means it's very nice to have to tell them like what is
• 156:00 - 156:30 the problem but not not required right like not everything need to be like a proper notification you can always say invalid check uh or invalid please rescan like one of the notifications or error follows that notification is fine but you have to like very nice to have like very specifically you tell the member it is because of the bad handwriting the application is not able I mean the OCR process is not is unable to extract data or it will be like telling you please scan properly please scan properly so whether you're going to
• 156:30 - 157:00 like show the error like please scan properly or whether you're going to show the error right uh invalid handwriting or whether you're going to show the error like um bad image what because there can be coffee spills there can be water spills it can be a bad check it can be a very old check can be crushed one so there are like few scenarios right whatever error we going to show those kind of Fallout requirements right these are like should have should have means I'm going to show some error okay because I'm unable to extract data from
• 157:00 - 157:30 the paper check but what kind of error I'm going to show whether it's going to be a plain simple one or I'm going to like very specific about those errors so these I should have nice to have but it's not essential right just throwing error it also should be fine and then could have means um it it is I mean it is not like a mandatory like should have or uh like must have could have means it's nice to have but it is not at all like mandatory so those kind of requirements and Wen have means I'm not supposed to have all these so um the
• 157:30 - 158:00 presence or absence or Wen haves have no bearing on the projects for example like uh I would say um if there is a new security feature for like they saying vulnerab software patching vulnerabilities like this has like if there is going to be data patching every month or every weekend there's going to be some kind of uh data patching then uh there can be new security feature for your mobile application to do that update uh that
• 158:00 - 158:30 software patching but we cannot we cannot focus on security measures for the application so it team right they will have very different it teams so application development team is going to be different and for this all these patching there will be a different team to do and uh so performance and all we don't know how long it will take for the mobile application to download how long it will take for the um system to capture that paper check we don't know right so all the security measures performance and all we cannot like our
• 158:30 - 159:00 team cannot take responsibility it depends upon what coding language you are doing what is the database how many systems are interacting in the back end so all that will take um uh that will take importance so for our Engineers for our developers is mostly about developing the application the functionality then the performance of course performance is is also needed so if I'm having a check for five minutes and it's not able to capture then that's an issue right if I'm showing a check and mobile has to
• 159:00 - 159:30 capture that in one or two seconds only then it is performing well right but I am not a responsible for capturing that um like that performance or security measure right it is not our developers responsibility our developer is only respons responsible for capturing the data making sure it's being validated and it's being down I mean like the data is being like loaded into the database everything is the transaction is properly done that our developers can do but all the security performance that's why these are called as non-functional requirements so functional means
• 159:30 - 160:00 something like from end to when our developer can develop that and fix it and make sure that in production is going well whereas performance issues security issues and all it's called non-functional requirements because we have no scope for it so this is like of the lowest priority if something is like uh taking like 5 minutes to download it's not my developers problem it is like the whole like not only the application also um the the coding language right whatever using the tools we are using right for example ETL
• 160:00 - 160:30 process it can be an ETL process or it can be Pega depends upon like in the back and what's happening that sometimes our developers have no control over also so these are like wouldn't have requirements so okay so you can tell you can take a particular case study and you can always show them like what is must have should have couldn't have and wouldn't have so you can always say this can be a requirement Gathering technique also requirement prioritization technique also I have 10 requirements which is must have in the next print for example
• 160:30 - 161:00 it's an AEL methodology I have a three weeks print in my next print I have to I have to start something I have to start something then what will I do okay so I have 10 requirements I have to only two developers two of them are on PT or on vacations to India so what I do now now I I have to make sure only like I can take only like four only like four different user stories then those are must haves so this can be a prioritization technique as well or you can be using as a requirement Gathering
• 161:00 - 161:30 taking also techniques also so both can be done using this mosco technique okay so the next one is use case modeling use case modeling is a very important one so I've uh taken um an oracle example of use case modeling what is use case modeling and um in use cases like what are the different templates we follow and I'm going to show you one by one so introduction to use case modeling use case modeling is nothing but we are
• 161:30 - 162:00 defining the requirements using this uml diagrams okay so you are using every every feature or every functionality you are telling it as an use case okay there'll be lot of use cases use case means for example member has to log in okay so with valid member ID and password that is a use case remember once they login what they do they scan the check okay and so the system has to validate whether it's a proper member ID or not okay that is an use case that
• 162:00 - 162:30 validation isn't another use case next is uh extracting data from the paper that is a use case so everything will be a use case and then transferring money from one account to another account that is an use case so in use case modeling you'll be this is a combination of different use cases and every use case right it will be in an uml diagram so uml diagrams in the sense like I can show you what is this is mind
• 162:30 - 163:00 map okay so for example do I have umls here yeah use case diagram so this is an uml diagram right so you'll have actors customers like this so one person what is that one person doing how it is like um what are the includes and excludes so this diagram is called as an uml diagram this is different from uh mind mapping or different from process flow diagrams and different from flowcharts okay so I will give you a brief idea of about in
• 163:00 - 163:30 uml diagrams right what all should be there so okay so see here use case diagrams so you use case diagrams are using by this uml diagram so you'll have something called actors actors means like whoever is performing uh the um event okay so let me take what are the primary properties use case properties we need to have a scope what is the scope okay scope of that particular use case and who's a who
• 163:30 - 164:00 who's a stakeholder someone who's like having an interest of this particular goal who's a primary actor who will be using this use case to achieve the goal and then like what is actually the performance of that uh functionality of that particular use case and then what are the preconditions and post conditions precondition means like I told you like member needs to be a existing member without username password he cannot log in so precondition is he's an existing member what if he is a new member new member means cannot log it new member means has
• 164:00 - 164:30 to go and register so if someone is a new member you have to say member um member is not an existing member please go and register or maybe member ID not found please go and register like that you have to throw an error precondition is for logging into Bank of America's mobile application he needs to be a existing member post condition is um at the end of that particular um scenario you are giving at least a minimum guarantee that this is a success so post condition is now the amount is being
• 164:30 - 165:00 transferred to your account so it is a successful transaction so it's complete means it is a post Condition it's completed that event is completed okay so a trigger is what is the event event or sequence of triggers that initiate the use case for example there is a use scale like Fallout right I'm scanning and paper check but it's a member ID is an invalid member ID invalid mean in the sense and database is not able to map this member ID okay so you are having a member ID okay
• 165:00 - 165:30 someone is giving you a check and when you scan it the Bank of America is not unable to it's unable to pull for example check bouncing the amount is not there or member ID is invalid okay so one event has to trigger a sequence of events here so it is going to say uh like this amount is not found in the bank account so bouncing the check okay or this member ID is an invalid member ID so some kind of one event is going to trigger a sequence of events going to tell you like uh like what you have to
• 165:30 - 166:00 do in the future so please uh reprocess the check or please um give a proper member ID something like that it us to throw an error so these are the basic like properties of a use case and using these use cases right you will be drawing the um use case diagrams and uh like for example like this okay use case diagrams you will like for every use case for example log ticket in the sense uh
• 166:00 - 166:30 you're calling the customer care and you're um logging some ticket so the helpess uh the customer care right they they are asking your name and address they are searching in the database once they found your name they are going to lock some tickets for example if you're working for TCS you have some system issue you're calling their TCS customer care right it support you're calling them they're going to ask your employee ID and they're going to ask your mission details some of the there's a sticker on your laptop right so you're going to
• 166:30 - 167:00 tell that mission ID so they're going to figure out and then they're going to log in a ticket using your employee ID and further details so that is a basic log ticket scenario so in that log ticket scenario there are two actors one is you and one is the help desk employee what is the activity that is going on lock ticket and include is you're going to find the customer and log a ticket so this is one use case so like this you like every functionality right you will be like creating the small small use
• 167:00 - 167:30 cases and you will be like representing the um requirements why because there are multiple ways to gather requirements there are like 50 different ways but if my uh business owner is like a very old business owner okay some 60 years old cannot understand aile terminologies cannot understand stories cannot understand anything like very complex uh require ging techniques so you're going to tell them through pictures okay see for you can going to
• 167:30 - 168:00 tell them through like small small use cases and small small pictures so that that particular business owner is able to like quite understand okay now I understand there is a small picture here this one is customer this one is help desk both wants to log a ticket and find the customer oh yeah now I understand so this depends upon who to whom you are showing to whom from whom you are gathering requirements understand most most business owners will be like old people why because they are in the organization for like many years 20 years 30 years they that's how they
• 168:00 - 168:30 become business owners so what is business owners if I a business owner for Florida I'm in that particular for for Signa if I'm the business owner for Florida okay the whole Florida Market I'm having the scope and I'm the business owner for Florida I have to know in and out in Florida how many health plans are there and how many uh Medicaid plant are there how many Medicaid plant are there and how many um inducers are there whether it's four 1.5 million users 2.5 Millions what are the different health plans we have what is
• 168:30 - 169:00 covered what is not covered what is state law everything I have to know only then I will become a business owner right so these business owners right will have will be usually at least like 15 to 20 years of experience they'll have in their own like process flow they will not have any technical knowledge but they know in Florida what is happening how much profit was there in last year like how many new health plans we rolled out how many we terminated why we terminated in this particular Health Plan what are the
• 169:00 - 169:30 benefits we give for example one Health Plan is only for low income people one Health Plan is only for like um um like special needs people one Health Plan is only for above 65 Medicare plan so what is the difference between one plan to another they know they'll always be in contact with the sales team and they know what is happening in Florida so for those people usually there are old people and you are an IT expert you are going to tell them you're going to convert that business requirement into your functional requirement because your
• 169:30 - 170:00 team is an IT team your developer wants everything technically right he don't want in simple words he don't want any requirement in like small plain English he want everything uh to be technically given to him only then it's easier for him to develop so you have to gather that plain English or to convert that plain English into something like a functional requirement that's why we are showing all these diagrams that's why we are creating the small small use cases and everything like for every uh feature
• 170:00 - 170:30 right we are showing some diagram diagrams and all that so that it's easier for the business to understand what we are doing and it's easier for the developer also to understand what is a functionality because after developing the application right they may not even understand they can give you sign off but once you develop the application it's already in uat that's when some of the business owners will come and tell you this is not what I told you no no no this is not what I told you so you will be in a very like embarrassed position because you are gathering requirements
• 170:30 - 171:00 whatever you have told the developer is already he has developed he the testing team has already tested and we are already in uat now now the business owner is saying that no no this is not the right requirement so we want to make sure every use case here is in like um small small use cases and also like we have some pictures so it is very nice and fancy also the uh business owners can understand okay what is the use case so you can use this use case modeling through this uml diagrams okay this one of the requirement Gathering techniques
• 171:00 - 171:30 then the next one is then the next one is like five y these are not five W's these are five y okay so five y in the sense um let me take that five wi so for every feature right you're going to ask like five wi why why why why why okay so I'm going to for example let's take an example why did you get a parking ticket
• 171:30 - 172:00 because I parked in a spot I wasn't mean to be so the second question you are asking why I was running late so I didn't go there like on time that's why I par in some spot okay so why why are you late because I got up late why because the alarm didn't go off okay then why because yesterday night I was late and I forgot to set the alarm then I went to sleep so these are the five different way five W question is
• 172:00 - 172:30 different those are like what where why when that is different these are like five y questions okay for every you take every scenario you're going to go to the root cause of that scenario so before you say this five wi to the business owner tell them this is a fivey technique okay and then why we are doing this I'm going to do a root cause analysis why this problem is happening to you and this is a technique okay tell them very clearly this is a technique
• 172:30 - 173:00 because randomly you go to schedule a call and you asking them why why why for everything they may get offended so you have to like tell them uh today I'm going to perform a root root cause analysis technique this is called as a FY technique so I'm going to ask you like why this problem is happening I will ask five times so please don't offended and I just want to like get notes from you to just understand why there is a production issue or why the why there is an incident that is happening very frequently and I'm we are going to do a root cause analysis so by
• 173:00 - 173:30 finding out the exact root cause of that particular production incident or any um incident that is like they're having a huge issue right that's why they're coming you for enhancement by understanding that root cause you're going to like give them proper solution okay now okay the data can be moved like this or the data flow can change or we are going to interact with the different system or we are going to change the process or the data itself so that's why we are using the
• 173:30 - 174:00 fivey techniques okay so I'm going to show you the five wi see for example here this scenario one and uh in scenario 2 they're going to ask so one of the main pillars of this year strategy is to increase the sales
• 174:00 - 174:30 why and how will this project achieve this goal okay so they want to increase some uh sales now they going to ask like why we are going to what are the um like in Project right in this particular project how are we going to implement that and Achieve that goal so um we are offering click and collect to our customers okay so click and collect in the sense like for example um retail sales has been declining due
• 174:30 - 175:00 to many reasons incl uh including lower football and more pessimistic economic climate yet our online sales have continued to go from strength to strength we offers we feel offering click and collect to our customers can harness the growth of our online business and help improve retail sales in the uh store so why click and collect click and collect in the sense customers want the service to be available to order and pick up the item so you can
• 175:00 - 175:30 always order at home and uh you may not go to the store you can order at home and then you can collect okay pick up in the store so why do you want to do that because 76% of online customers will like to use click and collect uh because you save time and I want want something by like I'm in the office by end of like the day I want something to collect okay so I'm ordering on my phone and then I can just go and park it in my parking lot okay and then because there is
• 175:30 - 176:00 always for pickups right there's always specific parking lot you go there you call them or you give like a specific uh number they are going to uh come from the store and give it to you that's how in the US there is a process like pickup pick up there will be a pickup slot parking slot so you can go and leave your car there and you can inform that that I'm in slotty one or two or three and they are going to come okay someone from Target someone from Walmart someone from the any from KS or any um uh retail store they're going to come and they're going to give you all the products you
• 176:00 - 176:30 need not you need not even get out of the car they're going to give you you paid you paid online so you're going to leave to the home so I'm saving like about like 30 minutes to 45 minutes I'm not even getting out of the car and it's very user friendly and I'm able to achieve right so we going to save time so 76 of the online customers are going to use this click and collect Services why H why have we fallen behind because the technology wasn't in place so earlier we don't have that but after covid we are doing this pickup uh online
• 176:30 - 177:00 uh procedures now we are able to handle it and why it is important it is important because the customer can order um at their convenience they can uh make sure they'll be able to pick up not only on that particular day we have a timeline like 3 days 4 days within that particular timeline they'll be able to pick up the product so um this is like five wise so you can take any situation for you to get the requirements and you're going to ask like five wi for example that processing paper check if
• 177:00 - 177:30 I'm going to put the same uh case for this five wi you can ask like why the paper check needs to be processed through a mobile app because the customer doesn't want to go to um the bank why the customer doesn't want to go to the bank because going to the bank it takes about um 1 hour or 30 minutes why he cannot spend 30 minutes because he's because the banks are only open on the week days not on the weekend so for the week days the customer is not
• 177:30 - 178:00 available to go to the bank he's already in the office he cannot go to the bank why because he's already working and he doesn't have enough time so these are the five wise that's why we want a mobile application where the customer can process the paper check at home in his own convenience and making sure everything is uh deposited in his account um properly these are the five wi for that particular use case so when you are using the five y you always have to tell to the business owners that this is a technique and I'm going to ask you five
• 178:00 - 178:30 wise and you have to like tell me uh the root cause of like why this is happening accordingly we can develop a software product okay then the um next one is six thinking hats so when you're going to do some decision making on requirements you're going to use this technique called six thinking hats so six thinking hats is like I have for example these are the thinking hats okay so I have um this technique was developed by Edward
• 178:30 - 179:00 in 1985 and uh we have six hats so the blue hat is called as a conductor's hat green hat is called a creative hat red hat is called a hot the hat for the hot yellow is called as Optimus hat and black is called the judge hat so why we are using all these hats in the sense like when you are developing a product okay and when you're looking at a problem you need to have different ways of thinking
• 179:00 - 179:30 okay you cannot be just thinking like this is a um users issue okay so what I am going to tell you is you have to take all the six perspectives and then we are going to arrive to A solution for that problem so what are the six uh um way of seeing a thing right so first is when you or your team are in the blue hat mode you're focus on controlling your thinking and managing the decision- making process so you have
• 179:30 - 180:00 an agenta ask for the summary and reach conclusions so conductors hat in the sense like you are always thinking about decision making you're asking for like what is the agenda why why are we having this conversation and then uh what is the summary of this conversation and we're going to come to conclusion whereas if it is going to be green hat you're going to now creatively think now okay um there are a different range of ideas for this particular problem and
• 180:00 - 180:30 then like brainstorming right when you're in a creative hat you're going to get ideas from different people and you're going to like arrange these ideas and you're going to like sum up the ideas and you're going to like proceed forward that is a creative hat then the next hat is like instincts that feeling of no this will go wrong no I know about the people in Florida they may not like that I know in New York it is very sensitive they don't like it I know uh in California like half the population
• 180:30 - 181:00 are Mexicans they may not like it so you just like this is like instincts and feelings about like um you H you want to launch a product in that particular State and this is like from your own gut feeling or Instinct right you'll be thinking like no no no no this will not work there that state is different people are very unique they may not like it so that is called as hat for the heart so these represents feelings and instincts next is Optimist hat this yellow hat is nothing but more
• 181:00 - 181:30 positive uh so you're always thinking about the benefit and added value for so we are doing this because the member is going to get benefited we are doing this because time will be saved we are doing this because we'll have more uh additional opportunities in that particular area so this is like more Optimist hat yellow is the most Optimist hat and the black hat right this is the judge hat this is the most powerful hat because this is very critical you're taking risk now so you'll be like okay what happens wrong you launch a product
• 181:30 - 182:00 in a state in Texas something you're launching and then what if it goes wrong what will we do what is the plan B and then um you're launching something in um like for example in New Jersey if something goes wrong now what will we do so this is like most most L like assessing risk and then you're being cautious and you're always going to be judgment about any product that you're going to like any software that you're going to design or any solution you're going to give to the business owner so this is like you're going to be very
• 182:00 - 182:30 critical about the decision okay then the factual hat factual hat is something like thinking about um information that You' have already collected but also information that you already missed okay so now you gathered some idea about that particular area or particular feature that you're talking about but what is that something you have you have missed for example here some colors have cultural implication so you may be uh picking a new hat in one of the areas so in China
• 182:30 - 183:00 for example green hat means Unfaithful spouse so please don't use that so that maybe in cultur also you have to be very careful on which country right you're going to go to China uh and you are implementing some software during requirement Gathering you have to be very careful what color represents word because culturally defines something okay so factual had is something like you represent information gathering you have some knowledge about that product but you don't have enough okay so some information may be missing so you're
• 183:00 - 183:30 going to be now deciding on okay where can I get the remaining information whether I have to do more document analysis we have to get the documents from the government whether I have to get a document from the compliance team whether I have to get the document from sales team so because you can Define any product okay but unless the sales team is like able selling it okay remember these is all mnc's finally we have to like make sure everybody is benefited okay anybody it can be CTS or TCS anybody what is the ideal goal for
• 183:30 - 184:00 them annual revenue okay like last year they have 4 billion Revenue this year they going to have at least 4.5 billion Revenue I'm telling you an example so we have to you can develop any AI product you can develop any electrical car everything you can develop okay and I can become a great product unless the customers or the sales team is able to give positive feedback on that sales team will tell you okay this is a very good product we are getting enough
• 184:00 - 184:30 customers for this product it can be a health insurance product it can be any kind of this banking uh mobile product or it can be like for example uh Facebook like a social media product it can be a website developing product it can be any product e-commerce product anything you can launch unless as you're not the sales team is not comfortable in selling it okay the very first month they will give you feedback okay this is not going to be a profit so you have to do some enhancements in this project because people are rejecting it for so and so reasons okay so for that kind of
• 184:30 - 185:00 situations you have information but I need an additional information that is called as a factual hat that is called the white hat so when you're going to take critical decisions for the team when you are going to be becoming a lead ba then you will be involved all the decision making skills they will come and ask you like for example practically I can give you a scenario so in our organization right we were doing some Automation in a particular um scanning process and I don't want to tell you the what is the
• 185:00 - 185:30 form but we are doing a scanning process we're making sure all the paper documents are loaded into the database and all that but we don't have the member is not filling the paper form and returning to us okay we are sending the paper forms but we don't get enough feedback from the member so we cannot be like calling them again and again right member has privacy member has preference like don't call me don't text me and so what we can do is member we have to send this form to the member and member has
• 185:30 - 186:00 to fill this form and send it back but the return return ratio from how much uh how many people are sending back this to to the our organization right it is very very less it's about like only 10% so our leadership team was like why members are not filling this and sending it back it's very crucial for us to have that feedback because we want to improve the product and we want to know the ground reality why the members are not filling the form so they came to us to it team then saying they are asking like can you tell us like what are the different ways
• 186:00 - 186:30 we can approach the member and so we we are in the high level of like how that product can be from paper how we can uh make sure that they fill this so we went for that reward $100 reward or $50 reward $25 gift card something like that so because only then people will be like okay I'm going to get $25 let me fill this surve form I'm going to take a $50 let me fill this that's a boosting experience right for the customer nobody's going to fill a form just like that if someone gives you a survey form
• 186:30 - 187:00 nobody's going to fill it but if I'm going to reward you with something maybe a $10 card $25 Amazon card or maybe $100 um physical form uh completion okay for you complete all your physical forms yearly you complete all your routine checkup you check your BP you check your diabetes you check your cholesterol everything is done you do you do all your routine vaccination now you get your $100 card then people are going to do that and we are going to have enough information about the member in our database because we know whether this
• 187:00 - 187:30 person has diabetes we know whether this person has cholesterol we know whether this has this person has a risk of heart disease accordingly we can change their premium next year so they're getting your feedback because because they want members details in the database so that we can improve or we can change a health plan accordingly next year okay that's the that's why we're getting feedback from the member but member will not know this member will do the survey and give it to you so but like if lot of people are not doing this survey then we going to give these Rewards or gifts or something like that right so they come to us so our team I was the lead so we
• 187:30 - 188:00 were able to incorporate all these Rewards or gifts programs when member uh enrolls into a particular insurance we give them rewards when member fills the form we give them rewards when member completes the annual check we give them rewards so now like for the next next year we were able to see there was like about 50% increase 50 45 to 50% increase in filling that survey so you have to like think okay what will be the negatives what will be the positive and uh sometimes business owners will come
• 188:00 - 188:30 and ask you for guidance so you have to like put all these hats and think what is the positives what are the negatives and accordingly you can provide them Solutions okay so the last first one is uh yeah we have two more so the next one is mind mapping mind mapping is nothing but we have one idea and uh that will be a central theme and then
• 188:30 - 189:00 uh from that right other ideas will be radiating so I will show you the Mind mapping diagrams so I have got a document from this University so this is the Mind map d diagram okay so main idea will be there and then surrounding that main idea you're going to ask why are we going to do this who is going to perform this feature what is that feature where are we going to implement this when are we going to do this and how are we going to do this
• 189:00 - 189:30 okay this is called as mind
• 189:30 - 190:00 sorry about that okay so we have one main idea then surrounding that idea right you're going to implement all this why who what where when and how Okay so okay so uh for example like I I've already told you okay so for example
• 190:00 - 190:30 like um there is an insurance company they want to meet some goal what is the goal they want that survey to be completed uh they want more people okay more members to complete that particular survey that's your goal now what are we going to do we are going to be like uh taking action so we can give them rewards okay we can make sure that um they complete if they complete the survey they're going to get Rewards or they're going to like get some benefit right we're going to maybe a case manager maybe a nurse is going to call them and give provide additional um so
• 190:30 - 191:00 for example I write I have diabetes I have hypertension in my survey now like a nurse or someone from the insurance company from the case management uh uh Department they're going to call the patient and they're going to say that okay you have something uh both um diabetes and hypertension you have the risk of heart diseases so you have to make sure you follow all this diet or something and make sure you reduce your cholesterol you make sure you your diabetes is on control so all that
• 191:00 - 191:30 action we can take so you get a survey from them uh and so by you're giving them rewards you're making sure that you complete the survey but what happens after that after that someone from case management is going to call the member and make sure like we give them advice right regarding the nutrition and how to exercise you give them a plan why the insurance is doing all that because we don't want the member to get admitted in the hospital the member is getting admitted in the hospital the insurance has to pay so in order to prevent that
• 191:30 - 192:00 in order to lower the cost for the insurance we are gu we are giving them that preventive measure okay preventive care for the member so this is like for one particular action one one particular main idea what are the uh surrounding ideas we have this is called as mind mapping so one main idea surrounded by like how different ideas okay so how are we going to benefit from using mind mapping mind mapping is nothing but they going to give very like a high level picture of
• 192:00 - 192:30 our software so if we are going to implement this particular idea what will happen what are the pros what are the cons and then um how are we going to make sure this is happening and how are we going to be like 100% effective in this idea other is change the idea if this idea is not working if you don't have good benefits then change the main idea itself that's the benefit of Mind mapping then the last one is requirement analysis so this is very very very important you can get the requirements
• 192:30 - 193:00 by 100 different ways but you need to know to analyze requirements so elicitation means Gathering the requirements the other name for requirement Gathering is called as elicitation okay you can say requirement Gathering techniques or elicitation techniques okay so you get GA all the requirements by using all these analysis techniques and then uh you are going to now we are going to make sure what are the requirements that are incomplete what are unclear now what are the like
• 193:00 - 193:30 mandatory requirements essential requirements that we have to complete for this particular project and then from there you're going to make sure that you create for example if it's waterfall you can create um brds you can create use cases or if it's agile methodology then you create user stories and then uh process specifications okay so first Gathering the requirements the second step is analyzing the requirements now you like separate now what are functional requirements non-functional requirements you separate
• 193:30 - 194:00 that now then the third one is you're going to know whether do you want to create use cases or you want to create user stories okay so that that you're doing that is called as requirements modeling and finally you are going to review all the requirements with your team okay with your team in the sense scrum team like developers testers your product owner scrum Master you're going to review the requirements with them and only then you're going to make sure okay these are the proper requirements now my developer can start developing if the project is funded
• 194:00 - 194:30 enough because after you gather the requirements so there is a process right how you will be like for example how you do budgeting it's very crucial for be to understand in real right in real life something called budgeting will be there so you gather all the requirements okay high level basic you gather the requirements then you give something called LOE LOE means level of effort okay so for this project it is
• 194:30 - 195:00 going to take some 500k $500k okay so $500k that will be that' be close to some um Pro I mean like into 8 four crores or something okay in Indian rupees so $500k this is my budget and U whether you guys have funding for this because you cannot give a very like like a vague
• 195:00 - 195:30 U uh LOE and once you define the requirements you know the developer is going to tell that it's going to take three Sprints it's going to take four months for do the development it may be taking like two months for just doing the testing because you have this application needs to interact or integrate with multiple different applications I need to do proper end testing this will take at least um like at least 15 days of uat testing so they you may gather requirements and give a
• 195:30 - 196:00 very high level looe okay budgeting you can give but after you define the requirements then you like you have properly defined all the requirements right that's when you will know actually what is the effort for this particular work how much it will take how many developers is needed how many testers is needed and how long this will be needed when can we go live with this project so once you have defined all the requirements you have to talk with your uh product owner and then scrum master and they will be doing some calculations
• 196:00 - 196:30 but you can always give your uh level of effort so okay for BA it will take this will take for at least uh two sprints for developer will say this will take at least two sprints testing team also they will give their own level of effort finally calculating everything we are going to give a budget to the business own own us seeing the budget they may be like okay we are fine this is a mandate from the state we have to do this approve the budget or they may be like we don't have enough budget now what we do only then you're going to go to the your project manager okay and then your project
• 196:30 - 197:00 manager will take a decision whether the LOE has to be reduced or it has to be like no we cannot do this without approval some projects just by seeing the budget they'll run away they'll be like no I we cannot do this this is like huge you know right always like software development is going to be very very expensive we we need to have on-site resources offshore resources we going to coordinate with them uh so it will take long time to complete any like for example very big projects it's going to take at least four months or five months
• 197:00 - 197:30 for completing the whole full project right it's like building a house so this budgeting also as a ba you have to know in the interview if they ask you you have to say that yes I have um I have a little bit knowledge about budgeting so once we gather all the requirements and defined all my user stories uh I will give my level of effort for every user Story the developer will also give testing team also will give and we will work with the product owner and the
• 197:30 - 198:00 scrum master and we'll come up with the budget then that will go for project managers review Once project manager is like okay yeah this is a good budget then we are going to submit to the business owners if the business owner is fine with the budget only then we are going to start the development if they are not fine we going to drop okay so this is called as budgeting very very important practical um practically without this you cannot submit your time sheet right so you need to know next is um yeah and also with the resume so when
• 198:00 - 198:30 theoretically now you know all all your um techniques okay so now how am I going to add it in my resume so I see all your resumes are very blank in in one page uh so many people are sending me resume it's not at all impressive like Val you it just shows like where you give me a second so everybody is giving your where did you study your bachelors's your Masters and your experience and all that
• 198:30 - 199:00 especially if you are a beginner and you don't have any experience in ba you have to add case studies in your resume okay you're very new to ba add one or two case studies in whatever domain like you like okay so you add the case study and then you need to add all at least in one page right you take one case study and you need to tell them that you have completed all these analysis I have done SWAT analysis most analysis maybe one or two analysis and
• 199:00 - 199:30 you add the diagrams that you that you've created okay uh some bpb and diagram or maybe this um even SWAT analysis that is a diagram right that you can do or maybe use case modeling diagram that you have to add in your resume nobody is adding all the res res that I have seen it's like plain like one single page and you're just giving your uh like your basic information right like no with that your I'm sure the resume will not get picked up you have to tell them that you are a good ba
• 199:30 - 200:00 even though you don't have an experience you are trying to become a ba and you've shown all your effort to become a ba okay so for how will you tell them by adding case studies so you need to add especially if you don't have any experience as a ba you don't have any domain skills or you don't you're starting from scratch you have to add one or two case studies and then make sure you add all your diagrams and your notes and then this is what I did see in my mind mapping this is a particular use case for that I have drawn my flowcharts
• 200:00 - 200:30 this is the flowchart and then um this is the Mind mapping diagram that I have drawn like this you have to add information okay don't like uh add more than one or two pages so your resume can be the first page and after that you can maybe one or two pages you need to add that information that will really help the interviewer like okay this person is really really interested this person has put in some some effort even though this person has zero experience he's willing to become willing to learn and trying to become a b so make sure you add all
• 200:30 - 201:00 these skills in your resume okay all these topics and then some use case studies in your resume okay so anybody has any other questions still now yeah I'm sorry you can continue yeah pradipa can I know about L Sigma tool like one of the recruiter asked as a ba you are aware of work down L6 Sigma tool
• 201:00 - 201:30 is there any particular tool yeah I have completed my lin6 Sigma certification so they want you to get certified or they want to know only the tools uh like they have been asked are you experienced on L6 Sigma Sigma right tools right okay let me let me take that you can complete that certification um Arin arind right I'm sorry yes yes yeah yeah so it's easy only it's not uh very
• 201:30 - 202:00 difficult is this required in healthcare also because there was one other Healthcare uh person's uh recruiter she was asking me do you have this Six Sigma certification Six Sigma can be used in any industry not only in healthcare so Six Sigma is nothing but it it's a like a technique for improving the quality of your work right for example if I have a food industry okay a massive food industry and I'm going to do packaging
• 202:00 - 202:30 of the food okay Frozen um let's say frozen samosas I'm going to do frozen Samos mass production it's very different from doing at uh at in a hotel or very different from doing at home right so what are the standard um techniques quality techniques that I'm going to use in order to make sure there is zero error okay so that every box looks same every packaging looks same and then uh we don't have any kind of um uh problems or errors in packaging also
• 202:30 - 203:00 quality also like everything like every Samosa has to be the same right in every package it it must be the same so this is like like a Japanese technique just for to improve a the quality when especially for production company like in a Tesla is developed okay so how are we going to check how are we going to make sure like every car is going to be the same how are we going to make sure every performance of everything is going to be the same right so uh but you can also use for software development okay
• 203:00 - 203:30 so I'm going to take a tool give me a second okay let me share my screen now okay give me a second hello yeah uh I'm sorry uh can we uh connect after the lecture I wanted to have a conversation with you suant right Healthcare domain no Sid yeah yeah Sid
• 203:30 - 204:00 yeah so sidat like um I have uh Sprint planning meeting at 9: so I may not be able to connect so can I connect maybe tomorrow yeah yeah sure no problem so I have to log in at night sorry about that no no is yeah so you can maybe I can connect tomorrow if that's okay with you yeah yeah sure okay so these are some of the Six Sigma tools are so if you want I can take a class and I can also tell you how to like clear the
• 204:00 - 204:30 certification yeah we have C and then we have different tools so this will take at least one or two classes but I can take maybe a 30 minute session at the end of this training okay so as we discussed in uh uh requirement Gathering and also root cause analysis so these also come under for Quality purpose kind thing right so this also come under Six Sigma kind
• 204:30 - 205:00 thing example yeah so difference between requirement Gathering and Six Sigma lean Six Sigma is mostly like making sure you have good quality also you have like yeah you have to achieve quality any product you develop right why I is very successful because of the quality right so how to achieve that quality in any product that you develop that te yeah yeah techniques uh we focus more on like for requirement
• 205:00 - 205:30 Gathering other techniques right we we focus on the overall functionality but lean Sigma is especially to improve the quality yeah okay okay does anybody have any other questions yeah pradipa how can I get get in touch with you apart from this Zoom class uh for any few doubts regarding the resume preparing and all uh and other doubts as well yeah there is do you have that my email ID I can uh no no no no I don't
• 205:30 - 206:00 have give me a second can you please in this chat chat box yeah give me a second are you able to see now in the chat yeah
• 206:00 - 206:30 yeah yeah thank you thank you you can email me and then when I get time I can respond okay hi pradipa this is sh uh so I wanted to know apart from these Concepts uh relating to business business analysis and of course the the projects or the case studies as you mentioned uh do we also need to like learn uh SQL like in detail or Tabo in detail uh I mean the the things that I have
• 206:30 - 207:00 mentioned on my resume is Microsoft Excel uh which is I know very basic but that is like I mean I I know that but apart from that are there any anything is there anything that I SQL SQL I think uh is very important especially if you're trying to get into Amazon or different um like product based right SQL is very very important tabue for reporting you can learn just but just learning these to will take a lot of time since you're from non-it background
• 207:00 - 207:30 I won't um ask you to learn more tools right now okay so even with SQL right like make sure you know like the basics also you know how to do different types of query if they ask you to write some queries right different scenarios you must be able to write right so even in SQL it can be very difficult for you to crack that's what I'm saying right right okay so but the basics of uh SQL not like going too much into detail about yeah you should know the basics and then once you catch the
• 207:30 - 208:00 basics right uh you can go advanced level but especially from Finance background it will be very tough for you to learn the basics too do you do you know already no no I don't know that's why like if I have to start from scratch like uh I mean I and also like keeping in mind that I would have to uh work a lot on the business analysis Concepts The Core Concepts right so then Basics uh knowing the basics of SQL would should be the first step right like I mean yeah so
• 208:00 - 208:30 learn all the business analysis Concepts and also domain and everything and then you can go for SQL and Tableau correct correct and also like while answering any question right asked in the interview so basically suppose if it is a theoretical question I can always like attach any uh normal case study and it need not be a case study that I have mentioned in my resume or any project that I've mentioned that I've done in my
• 208:30 - 209:00 resum is that correct like if you are able to like correlate and create so some let's say you are adding a project in your resume if you're able to create mind maps or any kind of diagrams for some that project that will be good that's what we want to see but if you are unable to do that then you can go for generic ones but if you are able to create all these documents for the project that you have listed in your resume that is that is going to be nice yeah good yeah so I think one more
• 209:00 - 209:30 person hello ma'am yeah hi um my name is Shak kaduk I'm from Kolkata W Bal and uh good afternoon ma'am uh basically right now I am pursuing MBA for business analytics so I have a question ma'am that is I want to learn scum master so uh I just want to know your advice about it scrum Master but
• 209:30 - 210:00 you've done your MBA in business analysis I am doing I'm in first year right okay yeah so sagnik right sagnik uh so the problem is Kum Master there will be very few jobs s so for example in a in an IT team right you have like five business five Bas or maybe five developers and five QA people there'll be one only one scrum Master for every scrum team okay okay okay so the requirement
• 210:00 - 210:30 like the jobs available in the market for scrum Master right it will be very less compared to BS okay come yeah you can take both options okay you can learn both okay okay also you can learn all the concepts and also scrum Master also if you want to do you can but scrum Master you have to do certifications invest in all the certifications right like CSM PSI those certifications you have to do that they can be very expensive so but uh the job
• 210:30 - 211:00 opportunities right scrum Master is going to be very less like I told you the ratio every scrum team there will be only one scrum Master okay I see but I actually I got some curiosity from after uh learning some after observing some videos from YouTube so I got some curiosity about it that's why I'm just asking you for some advice thank you so but you can do so we never know right if there is a scrum Master opening if you're able to crack the interview then it's good yeah okay
• 211:00 - 211:30 we have to get the job that's our ideal what's our end goal is everyone has to get the job and enter into the industry so that then you can change your goals and everything once you have familiarity with the situation and environment inside the it teams but um from my opinion like um scrum Master jobs will be very less compared to um business B jobs yeah okay okay thank you ma'am and ma' one more thing I want to uh say you
• 211:30 - 212:00 thank you again for BRD and other documentation you have made the videos on it and recently I was going through on it day by day and found that uh that you have uploaded this videos and and I asked you for the zoom meeting link and and I am attempting this video and this is really value added thank you you're welcome I'm hope this helps right because like I said the end goal is
• 212:00 - 212:30 everyone has to get a job if everybody in this call gets a job then that I achieved my goal then yeah thank you thank you thank you so yes um praa and other people I'm sorry like I have to drop because I have to make sure my goes to school I have just one hour before I log in so sorry about that maybe can we disc session tomorrow right not tomorrow on Monday Monday Monday okay Monday we can drop a mail right uh maybe yeah email you can drop an thank you so much
• 212:30 - 213:00 thank you everyone joining happy weekend bye thank you just last minute uh I have dropped you an email so if possible is it possible for you to connect on weekend yeah sure I can call you tomorrow so I have like a long day to day I have so many meetings today so maybe tomorrow I can catch up okay I'll drop an email with my contact please do let me know yeah sure okay thank you thank you everyone by thank you thank
• 213:00 - 213:30 you okay thanks for joining good morning everyone so um today we are going to today is day five and then we are going to learn about some important um skills required for a ba Okay so we going to learn about documentation okay what kind of documentation you need to do as a ba before we get into documentation um in it right so you have to know what are the different methodologies in stlc stlc means software development life cycle so there
• 213:30 - 214:00 are like uh two methodologies so first is agile and waterfall so what is waterfall waterfall in the sense like I can give you a quick glance of what is waterfall so any software product we are going to develop first we are going to do the development okay and then we are going to do testing okay so qm means quality assurance so that is testing then you perform uat uat means user
• 214:00 - 214:30 acception testing then the code will be going to production okay so first is development and then testing then uh Final End to and testing n to end is nothing but U user acceptant testing that is our stakeholders right whoever is giving as requirements they'll be performing the testing once they are fine with the testing they give the sign off then the code will be going to production production means it is be available for public for the members that is this is the stlc this is called as software development life cycle right
• 214:30 - 215:00 so you do that but there are like two methodologies that you can do it it it is being like before like 10 years before like 2020 I mean 2012 right we mostly like use this waterfall waterfall in the sense that is like for example you guys like business analyst will go get all the requirements so that may take about one month and then what you will do is you will be like um doing all the documentation so you'll be creating brds so fds SRS
• 215:00 - 215:30 documents and then um all the documents whatever is necessary for the project and then you will give that documentation to the um developers developers still then they'll be very like happy if you see in India right all the developers they'll be like having good time because they are not doing any kind of development so it's only you your Gathering requirements till then they'll be having a nice free
• 215:30 - 216:00 time so once you um once you gather all the requirements you made it into uh proper documentation so you know what are the requirements now now you given to the developer only then the developer will start development okay that will take another maybe one or two months so Gathering requirements will take maybe 1 month and then development will be like another one month and then testing once the
• 216:00 - 216:30 development is completed we will tell the testing team to complete they they testing so system integration testing that is called sit testing system integration testing so this will be done by the QA team QA uh team maybe that will take another one month okay and then finally U will happen U will take maybe two weeks or something to get the sign off and then once the business give us the sign off
• 216:30 - 217:00 then we will decide on the go live date or maybe we will like predetermine the go life date also accordingly we will like make sure we do the gather requirements adjust all our timelines and we'll go live okay production the code is going to production is available for the members this is called as waterfall this is a very traditional method so in 1990s or um 1987 1990s when the IT industry was starting to boom and uh like that's when we are starting to
• 217:00 - 217:30 get like small small products right so that time this water water we had no other choice that that that's um we had only waterfall and we only know this way this is the way so we gather requirements ba will gather requirements and we do all this paper document ation and then we will like make sure um uh we give this to the developers they will do then testing name this is a traditional method this is called as this is called as waterfall okay waterfall
• 217:30 - 218:00 means give me one second why we are calling a waterfall means it is only one-sided okay what is one-sided so it will just fall from top to bottom right water what is waterfall water will fall from top to bottom so just only one way there is no
• 218:00 - 218:30 like going back it cannot go reverse water fall means water is falling like one way that's all so business um requirements you're Gathering all the requirements development testing U production there one Lan so just falling down that's all there's only one way that's why this is called as waterfall whereas in agile okay in agile it is different so agile means I'm going to show you to sh the screen okay now if you see
• 218:30 - 219:00 here in agile here this is called as Sprint okay so for example so for example you get the requirements then you have the the design then development then testing then you uh uad testing and deployment then this is pro pro production validation everything will happen in like in Sprint Sprint means it's usually in two weeks 3 weeks or four weeks okay
• 219:00 - 219:30 so what you'll do is so this will happen in Sprint everything will happen in Cycles okay and that will be in uh very short time two weeks 3 weeks or four weeks more than four weeks we don't go okay so every we this it depends upon your team you may be in IBM your Sprint cycle in your team your Sprint is only two weeks you may be in cogniz and your Sprint time is only 3 weeks you may be in TCS your Sprint time is only four weeks it depends upon the organization the client and also your
• 219:30 - 220:00 own team okay whatever your scrum Master product owner is deciding that will be your Sprint timelines so but usually it will not exceed 4 weeks okay either two weeks 3 weeks or four weeks so within this short period of time now what the you have to do is you have to do everything so you will get the requirements you will create a user story so in Nel it is called as user stories and then within this particular two weeks right your developer has to develop your testing team has to test that feature that user
• 220:00 - 220:30 story and then we are going to like U you have to complete U everything review everything and the code will be going to production so in two weeks the business owner will be able to see some kind of like functionality in the production environment so that is why this is called agile agile means continuously is changing okay waterfall Ive told you how is that waterfall like top to bottom there is one way so you have to complete the um Gathering the requirements only then you can start development you have to complete development only then you
• 220:30 - 221:00 can start testing you have to complete the testing only then you can start uat you have to complete everything to go to production whereas in AEL it's not like that you are creating something called user stories user stories means it's like something viable product okay minimum viable product something like a functionality which can go to production in two weeks or three weeks this is depending upon your business owners your own team your scrum master your project manager if two weeks is like quite like you think is a very short time for 10
• 221:00 - 221:30 days it's a very short time then you can go it for three weeks but it is all like a like everybody should agree for that okay mostly we have 3 weeks and four weeks in my organization we have it as four weeks because 2 weeks is like very short time for it's going to be very stressful for our developers to develop something and fix something and then if you find bugs then you have to like immediately fix that so we take we go for four weeks Sprint but two weeks like for example we in Facebook and all like they like they're rolling out new features like every week
• 221:30 - 222:00 right for example you you take all the product based companies they UI everything like every week they'll be like um if you see that UI right there something new will be popping up so for them and all it's two weeks is fine but for some organizations like 4 weeks okay so you need to understand the difference now waterfall is slowly dying because this is like you go you give order and then after five months you see some product you I mean this is not something
• 222:00 - 222:30 I wanted okay you for example you want to build a house you call the architect you tell them like this is what I want then he do does a designing and you're not seeing anything and then after after 5 months you come and see the house and you're seeing the house and you're not impressed you're like this is not about want that is going to be waterfall whereas agile means constantly something for example the Builder is building the living room you're going and seeing the living room you're like fine yeah I'm fine with the living room then the uh Builder is building the kitchen then you go to the kitchen you be like okay I'm
• 222:30 - 223:00 fine uh I'm fine with the kitchen so this is like bits and pieces you are doing some kind of um like we we going to take chunks of U uh development and then uh we going to make sure that it's like completely done and then you're going to show to the business owners they going to approve and that will be going into production that is called agile agile we are uh doing in only for the past past 15 years and then now like most of the companies are following agile methodology this is what we recommend because we want the business
• 223:00 - 223:30 owners like to be with us like if you're are in aile constantly you'll be interacting with the business owners maybe every week or something because they have to do the uat and all so you'll be constantly involving with them it is little bit of pressure too but M for we have a lot of disadvantages because this one the budget can exceed because we don't know how much effort it is going to take and finally the during U some business owners are like this is not what I expected you have to redo everything so there's a lot of cost involved a lot of Advantage disadvantages in waterfall but some
• 223:30 - 224:00 government organizations they still follow waterfall they're fine with it some research organizations also they are fine they don't want to adapt agile uh but mostly like um the famous Fortune 400 companies right mostly everybody is so any doubts till now aile and waterfall please let me know hi hi pra when we are doing the
• 224:00 - 224:30 documentation in waterfall or as we are preparing BS and SRS this kind of documents right what is the difference between when we walking under waterfall what is the difference in the documentation and when we are working in NZ methodology what is the difference in the documentation like in NZ methodology we use user stories and use cases but waterfall we only use use cases in hybrid model also hybrid methodology also what is the difference in the these
• 224:30 - 225:00 documents what the structure will change in the brds and fds and Fs functional specification documents can you elaborate on that yeah so that's what we're going to learn today right see here so in be in waterfall right I can give you 100% we are not going to create any user stories so user stories means that is only for a okay so here we create brds fds SRS RTM requirement erasability Maxes Matrix and then sit system integration test plan uad test
• 225:00 - 225:30 plan and lesson learn document whereas in agile right we are going to like Focus only on user stories whether we'll create brds uh it depends upon like how many teams you are interacting for example all your all your systems are only internal okay so for example you have four systems to interact give me a second I'll I'll take that
• 225:30 - 226:00 documentation so we have four systems okay if you for example you are working for a client okay let's say you work for Bank of America and you have a project and in that project all the four systems are going to be internal Bank of America's teams okay you're working with internally then aile is fine I mean like user stories is fine because everybody will H have access to your J board so this is your J board okay because you
• 226:00 - 226:30 are internal so this is a j board and then I can create user stories for example I go here I click it I click here then I click on user story okay then for example I'm going to have uh something like login functionality okay I'm going to add all my documentation I'm going to create a user story here this is a user story right so this is the user story and if you see here I'm adding it to the
• 226:30 - 227:00 release okay it is in the backlog backlog if I'm able to see if you see here there are L of user stories I'm going to create that and if I provide this link okay what's the number number of this user for example I take this user story is fjt 10 okay I provide this number to someone if they are internal to Bank of America they'll be able to see the story right anything the internal I can give just this link and they'll be able
• 227:00 - 227:30 to so um yeah so here if you see here this link right this everybody can see because this G when you get if you uh when you go into a project or uh if you um If you hired right the first thing they will be doing is the very first day they'll give you access to this jira so when this um when you are hired by someone and uh that particular team's access also you will get for others team's access also you'll be getting so
• 227:30 - 228:00 if they share some J number for example here you have right FJ um see here this is the um user Story number okay fjt 10 fjt 14 FJ 15 okay these are the sample user story that You' have created this can be seen by other uh Bank of America's it team okay so you have a pricing team you have maybe underwriting team and maybe have member portal team you have like check processing something like there are different teams right inside Bank of America I'm just saying for an example
• 228:00 - 228:30 they'll be able to see this in that case you need not create brds because everything like whatever system that you're going to inter interact they'll be having access to your user stories for example I'm going to like uh like U um integrated with a vendor okay vendor maybe an IBM vendor let's take an example of sending uh Account Details so I have a system okay I have Bank of America is there Bank of America what they do is they need to send
• 228:30 - 229:00 letters right they for example like when you have like maybe account statement okay every month credit card statement they have to send in paper to your um home address so now what they want to do is they want to Outsource that printing to IBM okay IBM has their own printing vendors here so what they what Bank of America thinking is this is too much for us we don't want to handle this printing what we will do is we will send all the members data for example this member has
• 229:00 - 229:30 to get this information or this member has to get this am uh this accounts information if they want paper they can go paperless in that that case it will be in email but if he wants in paper then that like what is the last month statement everything has to go to that members address now they want to like just Outsource that printing Factor that's the letters and then logos and then member details members first name last name member address and everything especially current address like that
• 229:30 - 230:00 they want to send information to that member's address then we are going to Outsource that to the vendor IBM so in that case IBM doesn't have access to your J because they're they're external entity okay so they don't have access to your J then how am I going to provide requirements to them even though it's agile I cannot be creating user theories for them that's not my work right I a BF of Bank of America and I'm scheduling a call with IBM and they are maybe they are they are agile they waterfall we don't know and we need not know also
• 230:00 - 230:30 they have to like finish their work in that particular go life day that is what we are expecting so now in my case I have a j ID I can create all the user stories for my team but if I share it with them they don't have access so what will I do in that case in that case that only then I need a br even though it's an agile in that case I need a BRD because they are external vendors they don't access to our system okay so in that case I have to for example here this is
• 230:30 - 231:00 a real project you see here this is state of New York State Department Health that's the real project okay this was done in 2012 okay 2012 so if you see here what they've given is table of contents introduction and then uh what is the business purpose who are the stakeholders and everything project diagrams then you have assumptions and constraints then you have business requirements business requirements means
• 231:00 - 231:30 like what is for example for this project right what are the different kind of requirements but they also added user stories okay I'm going to go that so for example here so we're going to give the purpose of this document this is nothing but this is New York uh Health Insurance Exchange I can show their um yeah this is New York uh New York state of health okay this is the
• 231:30 - 232:00 department for this is like a government based project so what they are doing is so I will also show you the requirement what they want okay so the purpose is like this new York Health exchange system health exch health benefits exchange right they have tie ups with multiple like back end they have tie ups with multiple health plans this insurance availability programs like with different uh insurances but this is like one one portal from the state from the state
• 232:00 - 232:30 itself they are giving the this kind of portal like member can uh like do enrollment all the like Medicare medic anybody can do enrollment but back and right they are interacting with different like for example different Department of Finance ccial services and then Department of like um Health Department of this National Association of insurance Commissioners so all these agencies right uh will support this New York Health exchange um website and we are going to integrate so that's the purpose of this project so what we're
• 232:30 - 233:00 going to do is like um I'm not going to like I'm going to like show this project in detail in tomorrow's class for today's class what we're going to do is I'm going to just like tell you write the BRD that's fine and you write all the user stories and every I mean like um all the business requirements and everything but there can be in some cases where you have to like incorporate user stories in that also for example here if you see we are drawing the um
• 233:00 - 233:30 project diagrams we are writing assumptions we are writing constraints we are writing all the risk these are the uh business requirements business processes so we writing everything but we are also writing the US the story so that's what I'm going to go let me take that uh sorry to interr basically my doubt is that it's a default thing or as for the requirement
• 233:30 - 234:00 it's like a very like um unique to your project only I cannot Define that you like waterfall it has to be only BRD or a means only user stories I cannot we cannot tell that depends upon your project what they they want so when you put it in your resume you just say that maybe one uh one project I did waterfall so I know how to create so end what the interviewer wants to know is whether you know both the things okay whether you know to write bdfd SRS documents also whether you know to write user that's
• 234:00 - 234:30 what they want and mostly the interview will like currently like mostly the hiring will be for agile only so you instead of like you can tell I know how to write a BRD but mostly they'll be looking for user stories only that's for sure so when I'm clicking here if you see for the same project right they are written user stories too okay if you see here as a as an exchange administrator I want to create a process to receive the Medicare manage
• 234:30 - 235:00 Managed Care MMC plan data from the Department of Health so that I can make the plans available on the exchange this is the annual load of Medicare and Medicare care data so this is one usage story so this is a combination of because many people are asking me this questions whether if it's waterfall if it is only BRD or if it is like um aile means only user stories yes agile is of course user stories but you cannot tell that I want only BD I don't want user stories because right now uh whatever
• 235:00 - 235:30 practically what we are working is we may create a BRD for the vendor for example in this scenario we may create a BD for the vendor but in the document in the BRD document we will also add these are our user stories like how they have added here right so like this we will add so for in our team internal to Bank of America this is the user Story number okay this is the J ID number this is the name of the user story and I'm going to write the description and what category
• 235:30 - 236:00 and whatever it is just to document everything and from our perspective what are the user stories that we have worked on also in from vendor perspective like overly what I mean like end to end process so you cannot be uh saying like only brds only agile stories I mean user stories like that it depends upon your project whatever you're going this is like a realtime project in 20 in 2012 this is for New York state state project this you see that's why I'm taking a real time one so that you need to
• 236:00 - 236:30 understand okay and and and one one more thing uh uh when we are following the a methodology we are preparing the B document in the B document we write require ments along with the user story or as for the client requirement we'll write both or only write the requirements or use user story for separate document how does it uh so see that's what I want so for example a brand new project comes to you sometimes
• 236:30 - 237:00 there is no need to write a br also if they are all internal okay internal to your company they can directly click on this and view right so in that case you can just send an email to them or maybe create an epic for example I click here and then have an epic epic means under this epic I can tie all the user stories I create one Epic for example automation of uh claims okay automation of paper claims okay so
• 237:00 - 237:30 I create one Epic under this epic I can attach all the user stories that whatever for that particular project so I create an epic epic means high level so
• 237:30 - 238:00 okay so I'm creating okay I'm creating an epic Okay so epic is very very high level for one project okay under this epic I can create all the user stories okay I can attach all the user stories for example it says link issue so I can if I link the issue I may be like for example it is uh relates to then I find
• 238:00 - 238:30 all the user stories login functionality link it okay then I click on link issue and then uh relates to and then I have another story link it I have to so you can create one epic under that you can all the user stories for the Epic and share this epic to your business owners because they are all internal business stakeholders right so for that you don't need to create any other document you can always share one Epic in an email and then say that this is the Epic under this epic you'll be able to find all the
• 238:30 - 239:00 user stories for my team also the status you need not ping me every time so whether it is to do in progress for example whether we have started that uh user stories whether it's in progress or whether that user story is done so all that they they may not ping us okay so just seeing the user stories they'll be able to understand whether what is the progress for this particular project so you can share that if they are internal you can share it through email there is no special documentation here but if they want can you give us
• 239:00 - 239:30 all the they won't ask you because they will have a story board and for example like uh the business owners right they may have a j board for them and they're going to just link this epic to their J board and they so so that everything is automated so we don't want to do anything in paper money because we don't want the documentation to get lost okay because one business owner uh you can email them the document and then nobody is aware of the document you are a ba you create all the
• 239:30 - 240:00 requirements maybe all the these stories and you put it in a document you send it through the email it's going to that person's email ID and then nobody is aware of it right when he leaves or you leave then that information about the project is gone we don't want that we want everything to be in the board actually okay so when if you leave or someone else leaves when a new ba comes when a new business owner comes they are aware of okay this is what was done in last three years or last four years so these are the work it was done cool
• 240:00 - 240:30 they'll get a review and then they can go on with a new enhancement or something we avoid doing this word documents and all because as I said we don't want the information to be lost okay so yeah so if you um but you have to tell in the interview like uh if um do you they are going to ask you these type of questions do you know what is BRD FD difference between BRD and FD and SRS and how uh can you show me an example or they may be like um can you
• 240:30 - 241:00 can you um write something for me like they may ask you depends upon every interview right but you have to know as a ba you need to know these are the very Basics documentation skills that you you need to have so you need to know how to write a BRD what is table of contents how a rear BRD will look like this is a uh this is a good project document and then I can put this in in chat also so for example
• 241:00 - 241:30 uh if you want you can take a I added in the chat okay so please take a look at this document and then and one more question uh suppose you are assigned to a new project and then you are in a discussion initial call or second call discussion with stakeholder when we are interacting the stakeholder and identify the what are all possible requirements do you follow any kind of frame workor like
• 241:30 - 242:00 kind of uh techniques are technique is there for uh all the entire project in one level of framework by taking this framework I'll go each and everything step by step and then I'll I'll close all the requirements in one go like like that any kind of framework is there you're asking about like this wireframe um no usually like in my experience whatever we have done right right I will tell you practically what
• 242:00 - 242:30 we do practically what uh as a c what we do is we go we use all the techniques We Gather requirements in my project right so we gather requirements we write user stories and then like I have to be constantly in um I'm not saying like overall this is the requirement because why because I am representing only one ID team okay so that is like work of a technical project manager whether all the requirements are done that and all like uh a technical project manager has to do so I am uh responsible only of my
• 242:30 - 243:00 team right so there can be like three to four teams maybe there so I'm not responsible for that overall like uh drawing diagrams whether every requirement of from every team is being completed that I'm not doing in my my case these are the use I have a four-week Sprint so these are the user stories for current Sprint and for example there is a go live in for example like September 1st okay till September 1st these will be my user stories these are the developers who will be working on and currently we have
• 243:00 - 243:30 a Memorial Day holiday we have Independence holiday and then my one developer is going on vacation so we plan all that but we I'm not I'm not on on the on a project level whole like uh everybody's requirements I'm not taking care of that I'm only taking care of of my team requirements so that will be under this epic okay so as I said I create an epic I create all the user stories and then in the Sprint planning meeting uh we have to decide what are the essential user stories for the next Sprint for the next four weeks what are the user stories that we have to focus and we have to complete and then we go
• 243:30 - 244:00 on for the next set of user stories we focus on that we complete and the third set of user stories system integration and implementation user stories and we complete that and we go like okay you got it PR yeah yeah I got you pra and one more Point pra if possible can be able to show me one or two requirements by writing by taking any kind of small project um one or two one or two requirements only okay yeah yeah I can show that like
• 244:00 - 244:30 tomorrow right we will start um creating some user stories and then maybe I can take a small use case and then I can tell you like how to create user stories epic user stories and everything right I can maybe I can do tomorrow and then the framework I mentioned no in the discussion I gone through one framework that's reason why I'll I'll share it with you as well the framework maybe it may be helpful to you as well uh uh someone Shar to me what is the framework that you're talking uh framework is a
• 244:30 - 245:00 name is a popular framework popular framework uh p means uh process uh people and then objective w means and another p is the process flow and then uh likewise aberation is there and each and each and every alphabet there is some sort of list of questions framework name itself is popular framework yeah name itself see it's a it's a customized
• 245:00 - 245:30 framework done by someone and then I gone through that uh uh thing that that presentation and then I am asking you whether in your past experience have you gone through Frameworks like that kind of Frameworks like that you can share it with me yeah yeah that may be a new learning for me so we are not doing it so our is a very fast-paced uh um de I mean like U we have very quick like four week Sprint right so usually like in my everyday to day-to-day responsibility that's what we
• 245:30 - 246:00 do so we get an intake request okay so intake request also they uh will be on this J board only for example someone is like creating a task like um we need a new automation on this particular project so they they may create a request or they may ping me also through email stating that pradipa we have a new requirement can you please uh can I call you or something like that they may approach me because they know we are the lead ba so someone would have given contacts and all so they come to us and then we usually we have like first
• 246:00 - 246:30 one-on-one like very short call with the business owners on exactly what they want and then what is the requirements high level requirements I us to sketch down all the high level requirements then I will be like I have to go to my um project manager and then say that we got this intake request and then um so first thing I'll be asking is is it funded without funding we cannot do anything is this funded is it approved by the state or um like some are the the compliance issue like some compliance rules are there right so everything I'm
• 246:30 - 247:00 going to ask them then if they're okay with that then we had funding is approved on all on a very high level then only I'm going to start scheduling the requirement Gathering call so first call will only like one-on-one with like a very key stakeholder or staff VP or a director someone on a very high level right leadership level they're going to on a program level they're going to approach me and then I'm going to start okay I may be like okay for this we need to have four to five teams or this for this we need to have this particular vendor or maybe this is like brand new this is from this is a brand new project this is not something like existing then
• 247:00 - 247:30 what should we do do we have a technical project manager for this particular project so all that we have to do and then we have to schedule but everything whatever you're doing it needs to be in the J board because your time sheet has to be tracked even if it's if it it's like 30 minutes or 40 minutes you're spending some some time with the business uh owner you need to have that as a task here for example click create and then task and then you can say that requirement Gathering call
• 247:30 - 248:00 with yeah sh that image can you please have a look no like this you have to create the task okay what did you say let me
• 248:00 - 248:30 yeah I'm able to see that it's called as P for prod product and people o for objectives and options P for process flow U for user interface L for life cycle events and then a for algorithms AR for risk regulations and reports yeah so this called as popular framework yeah okay good so this is on like um on a project level you're talking right
• 248:30 - 249:00 like on a like on a high level you're talking like what is the yeah we are going to do yeah I've never heard about this sorry money I've never heard about this I've never worked on this Frameworks mostly like um I worked on the whatever I'm teaching you right that's what I'm I have worked on like all these analysis techniques and then no by seeing this framework I can correlate the questions as well and then uh I can get some idea about uh in all Dimensions not only one one area in all
• 249:00 - 249:30 Dimensions we will C question ourself we'll get the uh requirements list as well what kind of questions we can placeing suppose if we are uh working for a healthcare project or suppose if you for another Finance project what kind of situations and then where could be the possibility of uh asking questions in terms of risk in terms of reporting in terms of algorithm calculations and in terms of process who is who are the users and then what is their ages as well and then which doile they are looking at all kind of
• 249:30 - 250:00 questions are populating to our mind and then eventually we'll ask the question to the stakeholder so we'll get the uh requirement gathering in a very short span of time I can say that yeah so we are just looking from each and every yeah yeah I I I I'll share you that uh that thing the entire video you can can look have a look on it yeah okay I think our uh call is going to be cut okay can you guys join
• 250:00 - 250:30 back okay so uh the other um documentation that you have have to be working onest like in AEL right like the Sprint planning document Sprint retrospective document yeah otherwise PR if you allow me I'll run that video itself so that everyone
• 250:30 - 251:00 having a clearcut idea about uh this thing know how the requirements will uh take care of the requirements oh sorry you cannot hear me so I'm just describing we thinking like you are searching for something or oh okay sorry about it so I was just saying that Confluence is what we are using in our organization so um here uh for all the documents we just use templates okay I
• 251:00 - 251:30 go and click on templates here you have all the documentation like default templates so if you're a beginner and then if you don't know how to do the documentation from scratch then you're going to go with this one of these template right for example like meeting notes I use meeting notes means like you you go for a session and then um at end of that you have to send the meeting notes to everybody right so you just like instead of doing it a notepad and then again writing an email you can just
• 251:30 - 252:00 like do it here and then you can share this link with everybody through an email or if you want to do something like brainstorming session okay you're going for a brainstorming session uh instead of WR writing all this world documents so I already told you we don't want to do it in word something you do we want that to be in Confluence of jira in this board because when you leave that needs to be there forever so we Rec we always recommend writing everything in Confluence and J so uh yeah so what is the facilitator
• 252:00 - 252:30 it will be your name participants name brainstorm date and then brainstorm planning method and then what is the agenda and then what are the outcome summary decision everything you write everything here you publish and share that link with all the stakeholders so that's how we do documentation practically in in our project we use only tools okay we we are not using so much of what documents we want um everybody to use only this Confluence
• 252:30 - 253:00 and and um jira also there is something one more uh tool called um click up that's an AI tool so that also I can say but defaultly I'm I'm sure 100% if you're going to put agile in your resume you need to know very well uh what is jira what is Confluence I already made videos on this so please go and watch it in and out i' I've made a video on what is jir how to create epics how to create user stories how to create task what's the difference between user
• 253:00 - 253:30 story and epic and a task and what is Confluence in Confluence tutorial I have told you how to create diagrams and how to for example there uh the different apps here right so you you can always like integrate Confluence with all these apps so I'm going to explore more apps I click on Explore More apps so I'm going to WR here glyphy diagrams so I have glyphy diagrams so I'm going to click on glyphy diagrams so for example this is like um like you can
• 253:30 - 254:00 create all your process flow diagrams here itself you need not use this micro Microsoft products right so I write a requirement in jira I do all my documentation and Confluence then I integrate one of these apps um in Confluence at jira itself and here I can draw all my diagrams for example I can draw all my uml diagrams and also my all the diagram process flow diagrams all the diagrams I can draw
• 254:00 - 254:30 here okay so I can uh integrate everything so everything is in one place now so somebody use your user story right they will have like complete uh information about what is this user story what is the Confluence link for this user story and what are the diagrams for this particular user story for this particular epic so they will have everything in under that one user story itself so for example all the flowcharts all the UI wireframes for web
• 254:30 - 255:00 desktop and mobile apps so um all the last class we saw about bpmn right so all the workflows uml diagrams everything can be done by this glyphy it's free so uh uh if you want to like practice more diagrams means this Zira Confluence also glyphy all the three are free for some time I think for only for a month or something it's free 30-day trial so if you want to like practice just by using your email take my sample uh email ID then create account in J
• 255:00 - 255:30 Confluence and also make sure you try glyphy also and then uh take a use case one or two use cases so what you do is you create U user story or create everything okay create an epic create an epic create a user story create a task create a bug and then have it in your backlog then go to Confluence and then in Confluence please um this is also free okay so get get the Confluence and then you add all your documentation so create all your Sprint planning uh
• 255:30 - 256:00 document so this is the Sprint planning document and then uh something like uh assume that you're doing some analysis create the brainstorming document Sprint retrospective meeting doc like this you maybe some project documents you create that and also make sure you uh download this um glyphy also and start uh using this create some um diagrams and all so that when you put it in your resume at least you have some confidence like yeah I know how to
• 256:00 - 256:30 create a user story I know how to create a documentation and confidence I know how to draw diagrams in glyphy diagram so that confidence you will have so these are the tools that you can say so but you can also add um can also as Microsoft Word Excel
• 256:30 - 257:00 PowerPoint viio is uh basically U this a licensed one so I think you may it is expensive so I don't recommend with you instead you can do glyphy glyphy you have a 30-day 30-day trial period so you can always practice okay so these are the um documents that you have to create and when you add it in your resume please be very specific in your summary that I put all these words okay BRD business requirement document functional requirement Document Systems requirement
• 257:00 - 257:30 integration RTM requirement reability matrics system integration test plan uat user acceptance test plan lessons learn document Sprint planning document user stories I know how to create epics tasks bugs defects effect tracking uh that document also and then uh Sprint planning document review document uh Sprint retrospective document all the document I know on the tools you can always add all these tools okay jira Confluence cliy diagrams Microsoft Word Excel PowerPoint V you can add as I've
• 257:30 - 258:00 told you this is a licensed one so if you want to add that you should have experience otherwise don't add it otherwise you can see videos on how is Vu and then maybe you can add it that then I'm going to tell you an exact one called what are the AI tools for creating br so I found something called clickup okay so clickup is nothing but so this is um an AI tool for generating the BRD so I'm going to log in I'll
• 258:00 - 258:30 stop so yeah I have logged in here so this is inside clickup this is an AI tool okay for creating the brds okay so we have um so what I'm going to do is I'm going to go on docs click on dogs and then create document once in create document I'm
• 258:30 - 259:00 going to go for Generate template and then here I'm going to give it as so it is it is writing it for me right so I go here I'm I'm clicking on the a writer so I'm I'm writing like um business requirements for claims management system and it is giving me a
• 259:00 - 259:30 few uh requirements see here it's writing it from okay now it is stop writing so you can always use this also this one I have found like yesterday I have not used this but this is one tool which is now in the market so if you want to add this in your resume like um this is the tool for AI so I know in AI like they want something like upgraded uh recently what
• 259:30 - 260:00 are the tools you have used do you know about AI or have you like uh Incorporated some AI products in your work something like that if they ask then you can always use this um this product okay so you go you click on documents here then you click on that and then you want to generate a template or something then you can always say that you are on
• 260:00 - 260:30 mute I'm just waiting for that to end okay create user stories so these kind of AI tools can we use in for official purpose or we have any restrictions uh to work on usually your own like your organization right they will have their own AI tool okay like whatever organization
• 260:30 - 261:00 you're getting right maybe the top 10 definitely they have their own system so they maybe you may not be aware of their names but you can always say that I know how to use an AI product so that they'll give you access and you can do it and apart from that like you as we came across like AI tools so if you are not aware of AI tools or like to create like BRD FD so the companies will be following like we'll be given any reference of the templates we need to
• 261:00 - 261:30 follow accordingly or by our own we need to no no nobody's giving you training nothing let's be real like nobody's giving you nothing no no no it's not like training I mean to say any template we need to follow like old templates according to that or we need to prepare by our own or that I mean to say so that depends upon your team right whether they're willing to help so you you can ask them but we don't know whether they willing to help that depends upon your colleagues your Bas your developers they
• 261:30 - 262:00 can show you some kind of links usually what they do is they show some links and then you should be on your own so they won't too much KY they don't give yeah the very first day like they give you all the access and then they want you to be like prepared within a week or something so within that like how much hour you can talk with your colleagues maybe review all the documents and then you get a fair idea but I'm sure like nobody's going to sit and train you and this is the template I want or this is what I want they not going to
• 262:00 - 262:30 tell you so you have to like really do observe and then find out like uh maybe like even you have to be very professional don't bug them so because then they'll think that you are a fresher you don't know anything so just observe and then whatever you know you do and then uh please go review all the documents and Confluence also so what is the format and also you have to learn by yourself and by observation that's they won't tell you uh so that's for sure and they don't provide proper K also that is for sure so they want you
• 262:30 - 263:00 to be really quick they want to pick up things very fast so you have to be really prepared the first three months you have to be really on your toes and you have to like absorve very well okay so yeah I think that's for uh today um I have to leave so by tomorrow I think um money I um I'll give you like maybe 10 minutes so you can uh teach us all about this popular um wireframe
• 263:00 - 263:30 okay hello ma'am yeah hi uh good afternoon ma'am M uh I'm shakri ma'am I have just one curiosity uh the thing is that did you use uh clickup for documentation yes clickup okay okay then ma'am did you ever feel that you have to modify uh something after preparing a documentation from yeah yeah of course it's giving like very plain generic
• 263:30 - 264:00 template whatever is in in Internet only it's like picking up and giving us so at least it's like doing the search for us in we doing the search it's doing the search for us right so it is giving only plain like uh template but we have to do after that like we have to we have to do it yeah it not it's not going to give you everything for you I have a small doubt in finance sector do we have any templates like while preparing the um functional requirement uh companies will provide
• 264:00 - 264:30 the specific template to prepare the requirements for functionality for finance no I have never worked in finance I'm all about Healthcare okay yeah so I don't know about anything Finance I'm sorry about that yeah all my experience right I was in health so and one sorry ma'am yeah uh through glyphy glyphy diagram so we are going to
• 264:30 - 265:00 use process diagrams am I right yeah you can do any kind of diagrams through glyphy okay okay and I want to know one more thing uh what would be the I mean the simple difference between Confluence and Zer so Zera is for creating all the user stories where Confluence is like only for documentation so you cannot create user stories in Confluence okay okay ma'am okay and and one more thing uh when I am going to use
• 265:00 - 265:30 epic in summary we choose epic and then I realize that uh it's a kind of uh a set of user stories no no epic is very high level for example I'm automating something that it's like a heading okay under heading you have multiple like small small thing user story so one user story is what minimum viable product okay I can develop something and then I can go live in two weeks three weeks or four weeks that is a user story okay for example log login is a
• 265:30 - 266:00 user story that can I my developer can develop that test that and we can go live okay ma'am that is US story but whereas automation of something like very high level under one Epic you can have multiple user stories I see it's like a tree that root is one okay okay I understand okay okay thank you and one more thing that is for user stories is it like something that I am making understand the values of
• 266:00 - 266:30 something to customers sorry clients like yeah so what is like what is a user story user story is nothing but one minimum viable product that can be developed again developed tested and it can be like going going live in a particular span of time in a very quick span of time otherwise you cut down that one story into a two US story okay so if I'm not able to develop a requirement in like two weeks or three weeks or maybe in four weeks then that's not a user story now I have to make it
• 266:30 - 267:00 as two user stories or three user stories H so whatever I'm able to develop any functionality that I'm able to develop test and I'm going to I can go live in that short period of time that is called a user St okay okay it's like uh the it's like the principal of Justin Time jit rule is like this okay right so if you take a requirement business requirement or functional requirement that cannot be
• 267:00 - 267:30 done in four weeks then you can cut down into multiple user stories and okay thank you so much thank you thank you thank you everyone for joining thank you thank bye okay so I think we are good so today is uh day six and uh we are going to learn
• 267:30 - 268:00 about a case study okay so this is like a practical uh case study that I'm going to teach you and um I need um actually like 10 volunteers so I hope we have 10 people in our call so what we will do is so I'm going to give you roles okay so let me explain what is a project the project is called as electronic medical records so electronic medical records in a sense uh like example it's like
• 268:00 - 268:30 a okay so let me take uh sample of an um electronic health record okay this is a software so there are multiple in the in the industry right we have multiple like uh softwares that EHR software is available so what this software will do is like um for example like I'm uh I
• 268:30 - 269:00 have a hospital okay that hospital we have like 10 gynecologist and then we have nurses and then we have building team and we have a whole group of like St with me okay now I I'm the owner of that hospital now what I have to do is I want I want to automate things right I don't want to do it in paper so and I don't want to like spend time in developing a software on my own also okay I'm a I I have hospital I want some software like this where uh my staff
• 269:00 - 269:30 will be able to like schedule so I'll have a receptionist and then I have a medical building team coding team then I my nurses will be there so for everything right I need a software so for scheduling for charting and even for the patients whoever comes to our hospital we give them a login and a password so that they'll be able to see all their data their their test results and uh they can schedule online also so I want a software like this that's why in the US
• 269:30 - 270:00 right we are uh if you see this EHR software is very very very popular and there are like you can do e prescription you can send prescriptions from the hospital directly to the apartment Mery and all so uh this software is very very very famous here this is done by this like for example if you can see the clients here primary care doctors urgent care doctors and physical therapy Opthalmology Dermatology like there are Gynecology like there are so many like
• 270:00 - 270:30 all specialities right uh they are able to use this software this is one of the softwares that I'm going I'm showing you like this we have n number of products in us okay so and uh this depend upon like why like the cost right for example like get a free code so what they want they want your number your email ID if I'm the if I'm from the hospital I own a hospital then I give my number here I want to like tell the requirements who's going to use the software and accordingly they'll be giving a code and how many patients will be accessing this
• 270:30 - 271:00 software if there is any like issues then what is the support they give okay so we are going to develop this kind of software okay so the project that we are going to do today is we're going to develop this kind of software and we already have a open EMR software that is available for us to test so that's why that's why I went with this open EMR so if you see here this is a fully working EMR like electronic medical record software okay and they have given us the
• 271:00 - 271:30 link for testing give me a second they have G the demo link okay so if I'm able to click here for example if I'm going to click on the patients portal if I'm going to click on that they're asking for a username and a password and email address so I'm going to like already I have taken up
• 271:30 - 272:00 so I'm able to log in okay log in and see from I'm using the patient credentials okay so I'm able to see here
• 272:00 - 272:30 for example um as a patient like um what kind of documents I will be able to see and if I want to like for example I can schedule the calls so if I go to my um like profile here right I'll be able to see my profile so what is my name what is my date of birth this is all example they have given okay what is the address and what are what are my primary uh providers and what is my occupation my employer name what kind of insurance I
• 272:30 - 273:00 have policy I have first name last name middle name and who is actually owner of that insurance whether it's me or my husband and their name name and everything employer details what is this is my primary Insurance details and secondary insurance details and I'm going to like for example if I want to like schedule uh appointment right my appointments going to click here means like let me schedule a new appointment I'm able to like
• 273:00 - 273:30 see request new appointment okay let's see how do I request my appointments I go to my dashboard okay these are my medications now my appointments like uh schedule a new appointment oh so I have to call them I have to request in the sense I have to call them in even though it's saying it is showing like schedule on new appointment I have to call them because it's it's not giving access to their calendars okay so my messages inbox
• 273:30 - 274:00 whether the doctor or nurse has sent me some um messages okay so this is the project that we are going to do because this a fully functional software you can use it as your case study in your resume or if if you want to add it in your resume like if you have done one of the healthcare projects you can try to do this so what we I want is I need some 10 people so we going to like I'm going to be the business owner who's going to give you requirements for this software okay so I want 10 volunteers and um like I'm going to choose like three people
• 274:00 - 274:30 are Bas three people are developers and three people are testing team and then we need one scrum Master just to like mimic that we are an IT team and how to gather requirements and how to make it as users story so once you get the requirements and how to convert into user story and if you want to like uh create more user stories like so this is like a very big software right we have um like if you see here yeah this is mation Portal but they
• 274:30 - 275:00 have uh credentials for let me go to their homepage this is documentation okay why am I not going to the homepages I'm already inside their authorization module okay let me take their homepage so what will happen is like uh you'll be able to like yeah this is the page I want so from here right
• 275:00 - 275:30 you want to like create user stories from an admin perspective from a physician perspective from a clinician perspective clinician means nurse like someone staff like that and then accountant perspective from a building team and from a friend desk perspective so all these that's the US stories we want because everybody is going to have their own like unique like what what can admin can see the receptionist cannot see what a physician can see the receptions cannot see what an accountant
• 275:30 - 276:00 can see the other people cannot see billing information so that will be like very unique requirements and then we have to make sure that and also for patient portal right it will be very simple they can see only their own records they cannot not see others records whereas The Physician can be able to see all the patients records and an accountant will be able to see um all the building records and everything so we have to like make unique user stories according from the access level right so user stories will be differing like for a physician your user stories will be
• 276:00 - 276:30 different and for the receptionist your user stories will be different and for the from the patient perspective your user stories will be different of course uh the link whatever they're giving for the um for all these people is going to be the same link but uh this is for um like for if you see patient portal right there is a different uh link but um but uh the uses we are an IT team so we have to like um for us the goal is like this needs to be a fully working EMR or EHR
• 276:30 - 277:00 software where like our clients can do um medical building they can do accounting and they can do patient portal and we should be able to support them so we'll have a production support team and what ideally we want this is actually a real software but I mean I'm telling you this is actually in the market so if you want to buy you can actually chat with them and then you can get a quote also so if you see if I click on you can see here this is a real time
• 277:00 - 277:30 um so I'm going to like show you on how long this uh project was there this project right if you see the release right release means print timings okay the very first release was in June 2001 when we say release it's Sprint okay when two weeks Sprint or 3 weeks print we don't know uh uh so it is like very first version on it June 2001 okay from there then like the next release was in enhancement was in 2002
• 277:30 - 278:00 then every year they're having some enhancements they're adding something new and then like for example um if you see here they are adding like a lot of ESR certifications 26 l languages 30 languages they like enhancing the software like more right then if you see um if you see on Feb 20 2022 um they are doing some kind of enhance they doing some user interference interface Improvement patient form Improvement patient document template form support So doing a lot of like critical security
• 278:00 - 278:30 fixes they're doing enhancements here okay so here also support for fully integrated T Health modu T Health means um like um through uh through calls right so the patient is not coming to the office uh I mean the doctor's office they are coming they are doing a video call and now a doctor is providing some um prescription okay or prescription or it can be anything they're just taking the calls that is called as T Health modules so that we are doing in 2021 and
• 278:30 - 279:00 then uh we are doing like for example covid came they are doing some vaccinations schedules and everything in 2021 so we they doing a lot of enhancements here right now the last enhancement was the uh the version 7.0.2 November 15 2023 if I click here they'll be telling like what are all they did they did some support improvements they did FH improvements fixes API improvements clinical usage lab fixes billing fixes Insurance claim fixes patient dashboard prescription fix
• 279:00 - 279:30 they did a lot of fix in last version so this is an existing software this is a realtime software and anybody can um if if I am a hospital owner I want to get open open EMR I can ask them for a quote and they'll be able to like support and tell us like how much it will cost okay so we are going to develop this kind of software so develop in the sense we are not going to do the coding part because we don't have the coders here but um from I'm going to teach you on if
• 279:30 - 280:00 suppose we are developing this from scratch uh what as a ba what should you do and how are you going to gather requirements what kind of documentation you have to do what kind of user stories you have to do and how need to test this all these functionalities how to create for example for admin how to create a test plan for physician how to create like for those scenarios right all these scenarios how to create test plans and how we are going to do use end to end testing completely into testing how we are going to do and how we how we want
• 280:00 - 280:30 to make this product goal like so this is a case study that I'm taking because many people you guys don't have a proper case study in your resume and um your if you don't add a real-time working software like that kind of case study in your resume it's very um it's very difficult for your resum to pick up okay if you don't if you want to show your actual experience then add this as a case study okay you can say that I don't have an experience this is from my training and uh this is a case study I worked on I created all the user stories
• 280:30 - 281:00 I created all the diagrams like that you can add the case study or if you want to add this as a sample resume I mean sample project in your resume just from this uh you can uh um add this like you worked on this and then uh but you need to like answer properly if you worked on that means end to knowledge you need to have okay so are you guys okay with this as ample case study
• 281:00 - 281:30 yeah okay great so what we will do is um so I need some few people right um yeah so I need 3 Bas who wants to be a ba just give your names who who can like for example like share your um screens and all right because um I may ask you to show the user stories and all so be
• 281:30 - 282:00 prepared for next two days I may ask you to share your screen sidat are you ready yes okay s that is ready okay okay next is uh praa okay I'm just seeing the chat guys if you want you can answer or you can put in the chat to if you're not comfortable raising your voice you can add in the chat to I want one more ba who wants to be ba So ba
• 282:00 - 282:30 should create the user stories for me and show it here Puja okay okay Puja and then we need three developers so developers will not not have too so much work here so all you're going to ask is like a few questions on like how I need to code this like that kind of questions so mostly you will not be doing any kind of documentation you'll be just questioning the B so who
• 282:30 - 283:00 want to be like developers anybody any volunteer otherwi I'm going to pick names here yeah trti tripti okay and then anybody testing who wants to be a
• 283:00 - 283:30 tester this is like you will not be doing any testing so we will create test plans for you but I'm just adding you as a tester so I need one name AB are you okay just put in the chat if you're okay AB now yes okay AB
• 283:30 - 284:00 [Music] now okay and then uh one scrum Master we need one scrum Master who's going to lead all the status calls for us like tomorrow and there after tomorrow we need someone who can lead the status calls sagnik can be a scrum Master sagnik uh yes ma'am okay okay now sagnik is going to be our scrum Master okay so we are an IT team I gave
• 284:00 - 284:30 the name like the Champions Okay so the we are a scrum team and then I'm going to be the business owner so I'm going to give you requirements so we have so your team we have the Bas are sidat praa and Puja then developers is trypti then we have only one tester because okay let me change this to one develop test then one tester is abina we have a scrum Master our scrum Master is sagnik okay now we got this new intake so I'm submitting the new intake okay in jira what I do is this is your jira board
• 284:30 - 285:00 okay so I'm creating um a story for you guys okay what I do is I go then I what I do is I create and I pick or maybe I can create I don't know what to create right I'm a business owner I'm creating a task or something I use a story so I'm saying that I need this is how they will do I need a EHR software for my
• 285:00 - 285:30 Hospital okay for my hospital and then they will not know how to write a US story I will tell you what's the way to write a use story but this is from a business own they don't know right so they just writing I need a EHR software for my hospital and then experience criteria is this uh story is complete once I have a working fully
• 285:30 - 286:00 working a HR software okay that's how I'm writing my acceptance criteria and also description I'm creating it I'm putting on the board and then what happens is it's on the board okay it's on the board here okay now what happens during your Sprint calls okay there will be a Sprint review call okay in the Sprint review
• 286:00 - 286:30 call so this is in the Sprint review call since we all follow AEL methodology so uh in the Sprint review call or scrum Master right who's our scrum Master sagnik will come and tell that okay we got a new request that request is like for automating the all this Healthcare records so I want someone all the Bas I want a lead ba like all maybe all the three Bas this is going to be a huge project so please um speak with the
• 286:30 - 287:00 business owner okay business owner is prip as the business owner point of contact please contact her this is the email ID she has sub a request and start scheduling calls with her on a high level if you are able to gather the requirements then like we can uh you guys have to create more user stories okay that scrum Master is giving you instructions scrum master or product owner anybody can give you okay whoever
• 287:00 - 287:30 some in some project project owner will not be there in some projects scrum Master will be there okay uh I mean like all the projects kras will be there but product owner may or may not be there depend upon F I mean budgeting right sometimes if there's a tight budget then we don't have a product owner okay so now sagnik is giving you instructions and uh in our team like we have sidat praa and Puja they are going to be our lead B now they have to like
• 287:30 - 288:00 uh sidat pradipa and Puja what you're going to do is for the very initial calls you three you three guys are going to like be in the the call and they you're going to ask me questions okay you scheduled the um call with me now like randomly ask any questions with me okay so I'm the business owner you got a intake request now one of you like start asking questions okay so you are a ba you want to you're very excited about like uh starting this project so
• 288:00 - 288:30 whatever questions you want you ask me then I will say like how to ask and and what you should not ask and how to ask okay pradipa you want to start pradipa uh yeah pra yeah if this is the very first call we have scheduled okay so you can you can throw me some questions okay uh so yeah pra so do we have any existing uh already existing EHR for your hospital or
• 288:30 - 289:00 any document that you already have so that can defer to yeah right now everything is uh in paper we don't have any kind of software installed for our hospital so everything is in paper we have uh like a room full of like everything paper files for all our patients existing patients okay but we don't have any kind of uh the actual working any kind of software in our office okay [Music]
• 289:00 - 289:30 fine so this you want this to be as an um software for the members where they can supposed to log in and check their health records the patients yeah so I want a software like I have a team like I have um like a whole like I have like four Physicians I have four uh nurses and then uh I have like two receptionists and I also have a medical
• 289:30 - 290:00 building team like two of them who are coding all everybody's charts okay so in total about like uh and also patience level right we have since we have four Physicians four gynecologist overall like the existing patients would be somewhere around like 100 to 200 patients are there they're with us for a very long time so from in my office at least like at least 15 people should be able to use the software and members
• 290:00 - 290:30 right I have like at least 200 member members okay so what are all the uh details uh that you want want to be displayed on the user interface like yeah so from uh like main issue we are having is scheduling right so um patients are calling all the
• 290:30 - 291:00 time and they want like uh availability for all these Physicians so it is very difficult for us to track everybody's appointment and what when they will be on PTU when the physician is not available rescheduling and some people want to reschedule so we have a very tough time during this appointments okay so that's the first thing we want to focus on okay you want all the Physicians and nurses their calendars to be uh integrated with a particular
• 291:00 - 291:30 software so that like the receptionist or the admins right we should be able to see all the patients schedule and then when the patients call is right we should be able to give an exact slot we should be able to tell them that for this particular day this physician will not be available okay so you need a software where patients can log in and schedule the appointments online right now first in first phase right we don't want the patient to schedule we want the receptionist to schedule and once like after maybe like we will see how this
• 291:30 - 292:00 works and maybe um after like two to three months we want the patient also to do their scheduling by themselves okay I think I'm pretty much done pradipa okay so with this questions what have you got uh what what is the idea you get yeah I mean uh it's an internal
• 292:00 - 292:30 software that has to be built uh for that particular Hospital MH uh where the receptionist uh maely the reception will uh uh uh check the appointments and then uh call the patients and then inform whether the appointments are there or not so accordingly rest of the I mean employees also that can access to it m but later you can we can do the enhancements uh where even the patients can also log in and schedule
• 292:30 - 293:00 their appointments but that is in second stage but initially uh a software where the receptionist can able to schedule the appointment okay you got that appointment that module like you you think that is the first thing you're going to work on appointments mhm okay okay good okay next we want um what's who's the other ba sidat sidat you have any questions for the business owner please
• 293:00 - 293:30 ask yeah I mean basically from this uh software uh like how do you like want it to be in its uh start like implementation phase like you know how soon do you want this to so right now we are in uh end of May so we want some time in uh August first week is that possible uh I mean we would definitely
• 293:30 - 294:00 would like this uh software to be implemented as per the deadline but I know at this moment we need to get in touch with my team and you know uh get an understanding that is is feasible or not okay do you have any other questions for me uh as per the uh data discrepancy goes
• 294:00 - 294:30 you know like where are where where are the points where you feel like the patient data or any other requir data should not be you know with ible or as per when the patient data logs in and all so what kind of data you feel should be very private and you know secretive as per yeah so we going to follow the health seven uh HL 7 standards okay so HL 7 standards and
• 294:30 - 295:00 Hippa standards so in that standards what we're going to do is like the receptionist should not be able to see billing information the receptionist must not be able to see um patients diagnosis or anything so that's the first thing they should be able to see like only members first name last name Insurance details that's all they should not be able to see any kind of diagnosis or anything all the receptionist can see is members like primary details Members First name address phone number primary Insurance
• 295:00 - 295:30 secondary insurance all the insurance details and from The phys Physician schedule they should be able to see when this physician is available and uh whe whether this physician is on PT or not okay that's that's the we we are going to have limited W for the receptionist whereas the Physicians should be able to see all the data they should be able to see all the lab results they should be able to see uh uh like their past history what kind of diagnosis they have so
• 295:30 - 296:00 Physicians can see everything nurses will be must be can see everything and lab results can be seen only by the nurses and uh doctors lab results should not be seen by the receptionist and medical coding team and building team can only see the patients charts okay and they are not supposed to see any kind of um other information for example uh uh like for example they will be able to see only like from a coding perspective what is the patients chart and how much they need to get built and
• 296:00 - 296:30 only that much they should be able to see so these are the three requirements we have so we need a module for receptionist and we need a module for the Physicians and the nurses and then we need a separate module for medical coding team great great so these are the two important questions from yeah and the patient right they should be able to see only their information MH okay MH
• 296:30 - 297:00 okay do you have any other questions for me no questions from okay thanks abina so the next ba is Puja Puja yes uh so I understand that most of it was everything on paper basis and uh you want to digitize it now so that the appointments and all has to be done so most of the questions are asked by my
• 297:00 - 297:30 fellow BS what I want to check is the previous historical data you have do you want that to be also um added in future or um yeah so we want uh I mean earlier right all the paper records that needs to be scanned and should be available online for the Physicians to view the past history okay okay the historical data has to be integrated great
• 297:30 - 298:00 okay also I wanted to know what uh what is the main reason you want to digitize now yeah we have a limited uh capacity for um like scheduling all the appointments and we have a huge customer feedback saying that every time they are online calling okay they have to wait for at least 30 minutes to get my reception going right so they're getting frustrated so we want to avoid that okay
• 298:00 - 298:30 okay I understand the goals um that's it from my okay pja thanks so are there people like do you have any questions I don't want to guys to um do the opportunity to ask any questions the business own so do you have any questions for the business owner for this project that's a b sagnik any questions as a scrum master or a ba hello oh Ma'am I am scrum master
• 298:30 - 299:00 so so yeah no you can ask me also like if you have any questions B also you can ask this is like you practice without this in interview will be struggling if they ask you what did you do okay thank you I am thinking ma'am hello yeah hello uh ma'am I would like to ask that uh which websites or what are the threats of this of your
• 299:00 - 299:30 company threats for what software yeah so we have a very clean uh like the Hippa rule that needs to be established so we are working for New York here the mandate is like you're not supposed to like uh leak data right so these are very very sensitive datas in our system we have SSN numbers and then we have health information number health for all the patients we have sensity diagnosis for all the patients so we are going to make sure that this application whatever you are developing right uh should be like have higher security and
• 299:30 - 300:00 performance also we are going to make sure that I mean you need to make sure that there is no data leakage happening anywhere using the password and everything no hacking nothing like that okay ma'am I got that's the security concern we are having okay because everything is going to be online now okay that's a question you have okay good s so yeah so a pretty good job right so for the very first call for the
• 300:00 - 300:30 business owners they are able to understand uh like at least the basic questions what we need to ask the business owners for the very first call this is fine but on the second and the third call now you have to like as a ba right what as a lead ba you need to understand like one of the functionalities that praa covered was appointments okay so from the yeah can you hear me yes I'm I'm sorry for Interruption I gotten one question in my mind that uh I would like
• 300:30 - 301:00 to ask that uh you in your company there are so many users so I do believe that there are some prime customers gold users or what can I say gold customers so um I do ask you that is there any seasonal basis thing like uh in January the p number of patient is um um an amount like XY Z but in November or in October this is there is huge
• 301:00 - 301:30 differences between the numerical numbers so right right yeah so in November we have Thanksgiving so and also December we have Christmas holiday is and New Year right so from November 15th till the end of December we will have less appointments because people are on vacation they are on holidays and also our physicians will be on like major holidays okay okay okay okay yeah so from January again uh we will see to we will be able to see a lot of crowd but from November 15th till de I mean till
• 301:30 - 302:00 January 1st our physicians also will not be available and we have less crowd okay in our office okay so okay ma' thank you okay great questions okay so now like uh pra covered on the one module called like scheduling appointments okay but uh we have other modules also so scheduling appointments is one of the like for for the business owner this is one of the primary concern okay
• 302:00 - 302:30 so yeah so she asked questions about that but the next module that we have to cover is from the from the Physicians perspective so they are able to schedule appointments the member is the patient is coming to the office now the reception what happens now is the receptionist right she needs to make sure that uh she gets like she's going to check in she needs to check in okay check in in the sense
• 302:30 - 303:00 like she's going to ask your insurance details she's going to ask your um uh like your driving license for example a few things she's going to ask you she's going to ask your driving license okay DL then she's going to ask your insurance card okay and then she's going to uh yeah once she verifies everything and she will check whether you have any copay copay means something amount that needs to be like paid for your insurance so for example your gyne like for the
• 303:00 - 303:30 Gynecology visit if the copay is um $25 so you have to pay that also so you give your credit card you pay that Cay then and you're sitting on the waiting room so you're just waiting there now what happens is uh the nurse comes okay so that check in message right when she checks in right internally the nurses should get some alert that this person is already checked in that feature also we want to do okay if they check in the nurses and the Physicians should get an alert
• 303:30 - 304:00 saying that this person has checked in so because otherwise we don't want every time coming and checking the nurses they don't want to come and check back and forth we don't want to come and check whether this whether this this patient has has already checked in or not we don't want that so we send an alert once they check in they should the nurse should get an alert said this person is in the waiting room so the nurse comes first the nurse is going to like uh me do your measuring your height your weight so basically your weight she's going to take care of your BP and maybe
• 304:00 - 304:30 going to ask you like whether you have any concerns so what is the reason for today we said you're going to say this is my routine checkup this is my my annual checkup so I'm just coming for my annual checkup okay then she's going to be like okay wait and then uh our physician will be there in a few minutes so next The Physician comes physician now I want the physician to do everything not in paper take notes in your software the in the
• 304:30 - 305:00 open EMR software right I want the physici to take notes there not on the paper okay I think this call is going to end please join back sorry about that okay so what we have to do is physician has to come to your room okay you are your wife's room let's say let's take a because gy College I don't want the boys to be left out okay so you're going to the gy colle with your wife so they're doing everything for your wife or if you are your are going so physician is coming to the room and then uh they going to ask you okay hi
• 305:00 - 305:30 hello good morning how are you this is Dr maybe Patel and I'm going to like um I'll be your um gy today so can you please tell me what is happening with you so you'll be like yeah I'm fine I'm doing great so I have no issues I'm just coming for my annual checkup so I'm going a great doctor so he has to take the notes so I want the notes to be taken in the open EMR software okay so people use a lot of
• 305:30 - 306:00 software there's something called epic software you should you would have heard that's a very famous software this this software was actually created by a woman she's a very popular one of the I say top 10 or maybe top 20 um richest human being in the world okay so she's the she's an engineer I think in 1980s or something she developed this apic software okay so we have many softwares like that we have epic we have opena like I said we now now we have like too many softwares but initially the very first software was was called
• 306:00 - 306:30 as epic it's still being used in some urgent cares and all if you see if you go to Urgent Care you'll be able to see so um like a black screen The Physician is able typing something right in the very old coding language so they don't have any kind of web portal or something it's very old so that is epic software so but in open EMR if you see the layout is um something like this so same the same thing is going to be for the physician so they should be able to log in they
• 306:30 - 307:00 should be able to get uh the member or patients details and they should be able to able to add their notes notes also um yeah so notes in the sense for example you're getting like so this is a routine annual checkup so if it's routine annual checkup um that doctor is going to do a paps meia test okay check if you have any cervical
• 307:00 - 307:30 cancer or something okay paps meia test checking for cervical cancer that's a part of a routine test Okay so IAL cancer so basically I going to do one or two tests maybe um yeah so maybe check your abdomen or whatever I mean like lower abdomen and then do going to do like um all the basic evaluation physical evaluation make uh trying to make notes in the software so nothing paper here we want everything to be digital so no paper nothing and then
• 307:30 - 308:00 once and and uh um the woman now she's saying that no I want to check my ions now I feel like I'm very anemic I want to check my irons now so she's like uh the doctor is like okay let me light up lab prescription okay for checking your iron levels hemoglobin levels okay and they're writing only one lab of prescription I mean for the labs for the test and we have the hospital has their own like Labs so you can go downstairs
• 308:00 - 308:30 and um by the time you reach downstairs within like five minutes this prescription will be in the same software so that nurse who is available in the lab must be able to pick pick up this prescription and may be able to uh draw Bloods for you so you should be good now okay that's what the physician is saying and physician is like do you have any questions for me and uh the woman is like yeah I'm fine I I don't have any questions and says thank you and leaves in like 20 or 30 minutes so this is a phys this is a um member visit that we are having by the time she goes
• 308:30 - 309:00 to downstairs uh from the labs right they going to have this so that also I want to be in openr okay so by the time they go there that for this particular member uh that's why we say clinician right see here if we have one of the axis we have we say it as clinician so less access than physician who is that clinician clinician can be lab person they can be a nurse but they are not doctors right they are not MDS so someone may be working in the labs so they are less
• 309:00 - 309:30 access than physician but what they'll be able to see in their portal is first name last name and only the lab prescription this this person has to have a diabetic test or this one needs to have a like for example um like the iron test or something only that much that clinician will be able to see okay so uh they go the woman goes to the labs and then they are able to see that they able to draw the blood and they telling that uh the results will be available in 24 hours you need. call us and it will
• 309:30 - 310:00 be available online you have a login if you don't have a login please ask the receptionist so you should be able to have a login and a password please ask the receptionist and then you should be able to see your test results in 24 hours right now it's 10:00 a.m. tomorrow by 10:00 a.m. you should be able to see the lab results in your patient portal okay if they say this so you don't have a password now what you do is you come to the receptionist you'll be like I don't have online access can you give me
• 310:00 - 310:30 and she's be able to generate and give one for you so because the admin access should be able to give it if she's not able to do it okay reception is not able do this should be there'll be some admin there the admin should be able to generate a username and password for the patient and uh should be able to give that or send it through an email ID or text or something and after 24 Hours by 10:00 a.m. that patient should be able to get a notification like either by text or email saying that um yeah you
• 310:30 - 311:00 have uh some test results available uh in the portal please go login and check the portal now the member has to come to the patient portal and using all this um password and username when they log in okay it should be like my documents when they click on my documents my messages okay something like this inbox right now nothing is there so but something some notification needs to be there and then uh they
• 311:00 - 311:30 should be able to see for example uh medications lab results if you see here lab results is here no so from lab results it needs to be hemoglobin results uh it is like now 10 or something it's not up to the mark so please contact your physician so physician also will get a simultaneously notification right they'll be like the standard value is 12 you are only 10 so you need to take some iron prescriptions we are sending the prescription to the whatever um I mean the I mean the pharmacy that
• 311:30 - 312:00 you have for example it's Walgreens so the address was is nearby your house like whatever you have given uh they should be able to send the prescription online and you should be able to pick the prescription you need not go to the pharmacy the paper everything is online here okay the me the the physician is sending the prescription through online to the pharmacy Pharmacy is able to get that they able to process that they able to send a notification to your phone number because they're able to tag that phone number okay from the physicians's office you get the notification that you
• 312:00 - 312:30 can pick up that and you go to Walgreens you pick up the during like drivethru itself you can pick up or you can enter in and pick up the uh your medication and then you're going to come back so this is the software that we are going to work on so there are other aspects more than uh appointments that's what I'm trying to say here of course we are going to like uh appointments is the first thing that the business owner wants but end to and everything right like uh seeing all the patient should be
• 312:30 - 313:00 able to see all the medications all the issues and then all the lab results and also the nurse is able to process the lab request and the physician is able ble to send the prescription request to the um Pharmacy and um you are getting all the notifications in time you are getting the lab results in 24 hours so the software that we are going to make uh needs to have all these functionalities and you need to have an open idea end to end because right now you are seeing the software okay right now you're seeing it so you have an idea
• 313:00 - 313:30 like how it works but in real scenario you'll be the one who so you have to like imagine hypothetically how this software will look and all like you have to like really like bring all your imaginations and okay this is what they want and you have to ask more questions in a very professional way so then the next call you'll be like okay fine I understand they want appointments first but what happens after next so after appointment what is the what needs to happen so all these functionalities needs to happen so what is the next module we are going to work on so we are
• 313:30 - 314:00 going to work for this check-in module for receptionist and then we going to work on for this nurses they need to get an alert then we are going to work on physician login access what they will be able to see and take notes then they be we are going to work on the lab prescription so that also the clinician access right so that's why we have like five different aess here admin they might be able to generate the password login and password for the member Physicians access what they'll be able to see clinicians what they going to see and finally like once all the visit is
• 314:00 - 314:30 over um the medical coding team they have to like see all the patient charts they have to create ICD uh the CP code and they have to submit to the insurance you have paid only $25 the remaining $200 the insurance has to pay if it is approved that's fine usually like annual visits approval that there should be no questions but if it's denied why it is denied then they have to resubmit and all that so that the accountant should take care from their module they should be able to take care so this is a fully
• 314:30 - 315:00 working software this will take if I say like today is June 1st or maybe today is end of May and then I want a fuling working software in August then this is this needs to be a very fast-paced project so you have to really discuss with your developers and say they want the full module can we do that or we going by faces whether you want to do only the receptionist thing like very first and then you want to go like one by one whether you want to do that whether business owner is okay with that
• 315:00 - 315:30 kind of approach or they like no no no we can wait we can wait till maybe September or October but I want like fully functional fully working like into I want all the credentials for both all the physician everyone we want that so it's up to the business owner right what they want and what is the urgency and if they only focus on um because they're going to lose their customers if the customer is going to like call back and they are waiting in lines for like 30 minutes 40 minutes they'll be like fed up okay let me search for another hospital so they're going to lose their
• 315:30 - 316:00 uh customers right so what is the urgency if business owner is like yeah I'm fine with the just the scheduling options for August this is like we are losing customers we losing our business we want this functionality immediately then accordingly you will be doing that approach or they are like no no no we can wait then accordingly you'll be like developing your user stories okay so today we okay any questions still now on the like end to end this like for this particular software and how we going to approach different modules any questions uh
• 316:00 - 316:30 yeah yeah yeah please go ahead yeah uh so I just have a question so as you discussed all these now uh so initially I I just asked questions on the scheduling the appointment so I'm just wondering in real time will the business owners be the persons who will discuss uh in detail like what they what they want or is it our responsibility to shoot the questions more and then understand what they really wanted yeah
• 316:30 - 317:00 yeah they will not know because you they are non8 people they are from the uh clinical side they don't they have zero knowledge about it okay how software development works so it's that's why you are a lead be so you need to throw them questions for that you need to understand the like full like whatever I describe right like how this data is Flowing how the data is Flowing from uh how the data needs to flow right from calling to how that uh like bilding right how the data is flowing in this
• 317:00 - 317:30 entire uh system that for that you need to have an idea end to end okay okay got you thank you okay someone else was Yeah so basically when we say we need to know the data flow from end to end uh there uh when I'm like as a ba when we are going and asking for a project from the scratch there also comes into integration with other systems right so how how do we approach how do we get an
• 317:30 - 318:00 understanding of that this particular system will be connected to what other systems so for that yeah you need to have an so this is like from scratch web building this okay so for example like uh this we building from scratch but I also told you that uh the paper documents needs to be scanned and loaded into the system right that is one approach I told like someone was asking like Puja was asking like what about the previous documents you want that so that one we cannot do because ours is not a OCR technology right this is just like
• 318:00 - 318:30 scheduling system eh EMR or EHR modules okay but for scanning of course yeah we need to integrate with the third party so something like AWS okay so maybe here if you see we have a cloud product so even like for example this um software Way open EMR right they are also cloud-based product so AWS Market you have something called OCR process if you see you'll be able to see a lot of
• 318:30 - 319:00 optical Amazon trct okay let me see Amazon textract okay so if you see here this is a OCR project and that Amazon gives you okay so this is nothing but this is an artif AI product okay so what it will do is it will if you scan all the documents it is able to scan all that and able to send
• 319:00 - 319:30 it to open EMR and you can integrate these both of these okay so all that your developer has to say you can always like say like from like functionality perspective this is they want they want but uh the developer has to say no we are not capable of doing this this is like very limited capacity we can only code this is in C++ or something I think this open EMR I have to see like uh the development document they've given a lot of documents I have to do research on uh what is the coding language I think it is
• 319:30 - 320:00 C++ so we have only limited capacity we cannot do any scanning this not an OCR process so we we need an external vendor or maybe ation with a different system so that when they scan it scans and sends the images so that images are loaded into our system so now we have to integrate with Amazon textract now we have to integrate with a different OCR process or now because we don't have that capacity our software is right not having that capacity so you may have only limited knowledge about your but at
• 320:00 - 320:30 least you need to have like what you are doing you need to have that awareness but for integration with other products right you definitely need help of an engine ER because it will become technical whether you can integrate or not you don't know okay so you need a help of that engineer and you can always discuss if it's going to be brand new project you have to ask the business owners like whether they have any other vendors for printing for example if they want we have everything online but the member want also wants a paper copy of
• 320:30 - 321:00 their account all their bilding right they want the paper copy like they like no I don't want to go paperless I don't want I want please send me the reminders and paper so open EMR cannot do printing so what we have to do is we send sign like files so this is for this member we need to send this the last month billing copy for this particular claim for the insurance denied this particular claim so it is patient's responsibility so we have to send that statement billing statement to the member's address so we cannot do printing that part needs to be
• 321:00 - 321:30 outsourced printing needs to be outsourced so this open EMR needs to be integrated with a printing vendor printing vend can be IBM it can be condent it can be like there are so many printing venders are there um for example United um there one nice yeah so there are like different vendors I don't want to name the vendors here so but there are like different printing vendors uh who can print stuff for us so what we will do is we will send as a file to them member ID um not
• 321:30 - 322:00 member ID yeah member ID first name last name and then uh this person has this kind of balance please like send a letter and they will have a standard letter template and they're going to send that to the member so our function like the scanning we don't have the capability and printing we don't have the capability but then we have to integrate with other vendors so you have to know like what is the capability of our software what our developers can do cannot do so for that an
• 322:00 - 322:30 architect you're talking from like from an architect level right so you need a help of an architect or a lead engineer here yes I have a question here yes so when it comes to third party or vendor is that BS job to contact or should we involve somebody else if there's some usually if it is like uh like a very big project right you'll have a project manager uh who will be doing all the coordination but if they want you to do then you should it's the learning thing
• 322:30 - 323:00 right if they want to do you can also do try to contact maybe there'll be someone called vendor consultant so you won't be directly contacting the vendor so in your for example if I'm working for CTS CTS will have a vendor consultant you will contact them they'll be the primary point of contact for that particular vendor so if CTS has a vendor vendor consultant for IBM you won't call IBM directly you'll be calling the vendor consultant that person will schedule calls with IBM okay thank you okay so I think we
• 323:00 - 323:30 are good for today and then tomorrow like uh we will discuss on how to like separate all these modules create a user stories for all these different modes and how we can test this end to end and how we needs to go live and from an interview perspective also how to answer if this is the case study that you're going to add in your resume how to add how to answer this case stud okay I think we should be good for today okay thank you thank you everyone for watching thank you thank you thank you hello
• 323:30 - 324:00 maam hello uh ma'am I have a question can I ask you yes thank you ma uh ma'am basically I have no experience in ba I just pursuing ba as a part of MBA right now so I have one question that uh if I'm selected as a ba or hired as a ba for a company what kind of job will be there
• 324:00 - 324:30 for me for the initial part so if in it right if you're part of ID then mostly your day-to-day responsibility will be like someone will be submitting the intake request and you'll be part of all these requirement Gathering sessions and if suppose like directly they come so you're doing an MBA right so if suppose they hire you in campus and they know you are a traine and all then um it's it's different okay
• 324:30 - 325:00 so they're going to give you only less work but if you're going to go directly to MNC MNC like service based then in that case they expect you to to become to lead the U whole requirement Gathering everything you have to lead you have to document and then uh you give instructions to the developers testing team and then you should be making sure end to end you are doing that project yeah okay ma'am thank you do you have any campus interview
• 325:00 - 325:30 scheduled for you yes ma'am okay when is it no no ma'am actually I didn't recognize your words can you repeat it please so do you have any campus interview schedule for you right now no ma'am basically I have completed this first year and now I am in internship I am completing and in I am in internship actually I'm an intern of a global company IT company after
• 325:30 - 326:00 that uh I will try to find a company for business analyst Ro for of Campus so in internship right like are they teaching you all these stuff uh yes there are some technical part and non-technical part now for technical part they are providing me the lessons from python SQL some database format and for non- technical they will
• 326:00 - 326:30 teach me BRD but I have um already learned it from YouTube and from your videos and from other videos so that is the thing okay but they're not training you in like one profile uh actually training is ongoing okay yeah so once you are done with internship when you're trying right if you have any concerns let shoot me an email and maybe I can before the interview right can we can schedule a
• 326:30 - 327:00 mock interview so that it's easy for you to correct okay thank you so much thank you okay let's get started started so today is very important uh training day uh we are going to learn about so we get an intake request like for a software like openr right now as a ba what you will be doing the very first step what you have to do the first step what you will do is you will draw you will be drawing a process flow diagram because we want to like
• 327:00 - 327:30 show this diagram to the business and we have to like um uh I mean mean like get confirmation from them that uh this is fine okay so let me open the process flow diagrams so this is how you will draw the process flow diagram very simple diagram but everybody like business owners when they see it they must be like yeah this is correct our data flow is correct and you please proceed so the very first D you
• 327:30 - 328:00 will draw this in either in as I told you earlier there are various tools for you to draw this diagram you can draw in glyphy diagrams you can draw in VI whatever is U you familiar you can draw this there is no like a perfect tool that you have to use uh you have to draw that's the first thing so yesterday we gathered like basic high level requirements from the business owners the first step is you draw this diagram why we are drawing this diagram because the next call with the business owner you're trying to show them okay so this
• 328:00 - 328:30 is the from last call um from whatever we got the requirements from my understanding I think this is the process flow uh can you please review and tell me is this okay and this is not very technical okay this is a like very plain um process flow diagram so anybody who can read English will be able to understand so for example let me go through the process so what is happening in the office in the doctor's office in the patient intake what is happening is patient is coming to the office okay
• 328:30 - 329:00 patient is greeted okay and then patient has an appointment yes if patient has an appointment what are we going to do we are going to ask uh the patient to be seated and wait for the doctor then the patient is going to the doctor's office and in the doctor's office the patient is treated and um the doctor is like uploading all the diagnosis treatment option everything in the open EMR and
• 329:00 - 329:30 also doctor is giving the patient is giving indications like for the next appointment please go to the receptionist okay the doctor is saying you're good you can go and someone in the reception will guide you then patient is coming we getting the coopay and um now whether a follow-up appointment is needed or not if the followup appointment is needed yes now patient uh the receptionist will be scheduling the new appointment and uh the patient will receive an appointment information through email or through text or
• 329:30 - 330:00 something and uh after the appointment right they there there can be a survey like tell me about uh today is appointment how do you feel please provide feedback that can be through email also and patient leaves the office or if the patient doesn't have any um like followup then they directly take the survey and they leave the office this is one process flow and the second one is patient is coming patient doesn't have an appointment and it's a walk-in okay
• 330:00 - 330:30 walkin in the sense like they don't have prayer appointment they're just coming and so they don't have an appointment now we have to check whether doctor um depending upon whether um whether it's a sick appointment like for example in the US here we have two kind of appointments one is routin checkup on a sick appointment sick appointment means um you are very sick and you have to see the doctor right now so in those cases either you can go to your doctor the primary physician or you can go to urgent care or you can go to emergency
• 330:30 - 331:00 emergency care so let's say but you're going to your primary physician and just as a walk-in you don't have any appointment you're very sick and uh you're going there what will happen is they will check if the doctor is there or not if the doctor is not there they have to check the um uh if doctor accepts appointments yes then they go to the same thing right doctor is like taking them and then checking them and then they go the
• 331:00 - 331:30 process if doctor is not um available we have to check the schedule and then we have to give an appointment maybe we can say that no today doctor's appointment is completely full but you can go to urgent care or you can go to emergency room in the hospital or if uh you can wait till tomorrow then uh we can have it for tomorrow tomorrow morning the very first appointment we have an opening so if you want I can schedule it right now it's upon the emergency right if it's like abdominal pain then you have to go to
• 331:30 - 332:00 the emergency room or urgent care or if it's something like very mild and you can like wait for a day then you can take the next appointment and go okay so this is the uh I mean like a basic process flow for this like scheduling that module okay scheduling in the sense they can be two ways patient can call and schedule or patient like uh is coming and through checkout process everything we are uh showing it to the um business owners this is a sample I'm just telling for every module if you
• 332:00 - 332:30 have time and if you want to learn if you are going to add this in your resume so my recommendation is for the next four to five days please draw these diagrams because just by seeing and I'm explaining you will not like your mind will not grasp it that is not that's not how a brain works right it has to do it with hands only if you do it with hands uh your um it will be like subconsciously you will develop that confidence otherwise it will be you will not be able to answer in the interview
• 332:30 - 333:00 very confidently because there is no practice okay it's like cycling you cycle you fall down and then like after a couple of um weeks you're in the muscle memory so automatically if you take this cycle you will go you're not even thinking about same thing so if you practice for like 5 to six days uh these diagrams in various scenarios so this is like only patient coming so maybe that's an next scenario like uh patient once they leave now what the doctor has to do write the notes for example I have a process flow here for uh doctors okay uh
• 333:00 - 333:30 like for example this is the workflow for a doctor after they leave after patient leaves we collect their information uh we enter uh in the open EMR and um what we're going to do is the we going to like for every uh diagnosis diagnos in the sense like for example fever or abdominal pain all that is called as diagnosis for that we have ICD now the version is 10 okay I'm going
• 333:30 - 334:00 to write down so that you guys understand it so in us especially if you're adding us Healthcare in your resume these are very very important so once the patient leaves what does the doctor do he writes the diagnosis okay that will be in ICD 10 version that's a code okay and then he'll also be writing a
• 334:00 - 334:30 procedure procedure okay that will be in CPT okay so diagnosis in the sense for examp example if he's a dental doctor he's doing routine um um dental cleaning then the checkup is annual dental checkup okay and then the procedure should be like routine uh dental cleaning so they should be this is what he will write he will write in pain English he won't be taking the Cod he will write only in
• 334:30 - 335:00 English but the medical billing team right they will find the corresponding ICD code because there is no time for him to write so he has only like maximum for every patient he'll be having only like U maximum 20 to 30 minutes right so what he will do is he will collect basically uh all from from the physical checkup um he can order the labs and x-rays whatever it is and then he's going to add that in the open EMR he's going to basically add one uh one or multiple diagnosis or procedure code not
• 335:00 - 335:30 quotes he's going to write in English and then leave it in the chart and then what will happen is there will be a medical coding team for within the office or they are going to Outsource to India either two things can happen if it's going to be a major practice major Hospital like for example who have worked in medical coding they would have known like there are like very big hospitals here like U Mount chai hospitals they very big like large hospitals they cannot handle their coding here so that's why we have medical coding um offices in India if
• 335:30 - 336:00 you see we have omega Healthcare and um I think gen P like there are different medical coding um offices in India too so but if the doctor is having his own private medical coding team then what he will do is what they will do is they will be like for every diagnosis if this is the diagnosis they're going to take the ICD 10 version right now it's not in nine it's in 10 and they going to put the CPT codes and then they're going to
• 336:00 - 336:30 like um create the claims okay depending upon whether it's a medical claim Vision claim or Dental claim I have already if you have seen my claims video you would have known that the claims are going to be very different for medical dental and vision okay they are very different three different types of claims now we are going to submit the claims and uh to the insurance and insurance can uh verify and receive give us the payment and uh Insurance can also deny if you
• 336:30 - 337:00 have received payment means if there is anything balanc uh you are going to check with your patient or if there is anything overdue you're going to call the insurances but um if the insurance is denying from for some some reason we going to find out why the claim is denied you're going to fix the denial then resubmit the claims and um repeat until insurance appeals exhaust so when you're resubmitting the claims there is like a time limit or like within how many days we have to resubmit how many
• 337:00 - 337:30 times we can resubmit like that so are we going to appeal or what we are going to do or or if you have no choice it has to be built to the patient then you have to call the patient or tell them that uh you have a due because your insurance didn't cover this procedure give me a second so we going to call the patient
• 337:30 - 338:00 and we are going to ask them for um to pay the amount okay any uh doubts still now regarding the process flow diagrams like what you have to do because I mean in the initial call uh with the business owner uh if we are not aware of the data flow I mean it's not like not completely aware of but at least if we have any doubts can we ask in initial call either with business
• 338:00 - 338:30 owner the solution as or how it works yeah yeah you can ask that's why we are scheduling right so you can take help of the architect business owners otherwise uh yeah we have to be like also depends upon like the way you ask right it has to be very professional don't ask them like very silly questions so that can be like they may think that okay this does this person doesn't have any like basic knowledge about this uh Healthcare System so you have to do before you schedule the first call you have to do like analysis Google a lot of materials
• 338:30 - 339:00 online so to understand what this can be and cannot be understand basic terminologies you cannot go and ask them what is EOB what is explanation of benefits tell me what is claims you cannot ask those such things M okay understood so if you are going there for Doctor like like you need to know what is claim what is um eops what is uh how can how different the claims can be submitted what is electronic billing what is ICD what is CPT like basically
• 339:00 - 339:30 like I told you right diagnosis means it will be ICD 10 the version is 10 now without knowing all this basic Healthcare terminology IES if you schedule the call and if you ask them to like um give requirements you may not actually understand the requirements too got it so yeah that's why we don't want to get embarrassed right because it can be it can be a very high profile people coming for the call yeah yeah like Hospital like staffy pce can come and give you requirements okay someone
• 339:30 - 340:00 reporting to the CEO can come and give you their requirements so we want to be like very professional and then uh as much as possible before the call please do some analysis and then learn terminologies and then make sure if you don't know something uh if you are thinking that this can be a very um uh stupid question then don't ask okay okay you can ask with your developer or we can do some research but very first call yeah first impression is the best
• 340:00 - 340:30 impression right so we have to like so when they when they hear you when they see you Gathering requirements they should get conf confidence like yeah this person knows something and I'm yeah she is very professional I think she will take care of things so that kind of confidence the very first call you should be able to give uh for that you should definitely do the basic analysis okay because when they submitting the intake request right they will give you a few information you can ask your project manager your scrum master and all that okay okay yeah good
• 340:30 - 341:00 thank noes I have a question mhm you you said that there would be different departments Al together and everybody would not have all the access that are there so how would it access be given to each one of them that your developer will be like during uh coding on he will take care of it all that you have to tell is like um for admin um that person should not be able to see these things like that you have
• 341:00 - 341:30 to customize and tell but uh that coding should be done by developer yeah but we'll have to do some process modeling or something like that in order for him to understand what exactly is needed yeah so let me show you an example okay this is for okay this is for receptionist login okay reception is logging in and what she's able to see
• 341:30 - 342:00 isup what did you say yeah I asked you about like how the access be given to each of the department that exist over there right so let's see here this is for receptionist login okay
• 342:00 - 342:30 so ma'am you are not Audible we lost you again pipa we are not able to hear you can you hear me now yeah yes right now we issues with my microphone okay yeah hello yeah now a okay I don't okay I
• 342:30 - 343:00 think it's constantly changing between my Apple microphone and um Jabra whatever I have okay so okay um so during the receptionist login right if you see she's able to see the um Physicians calendar okay Dr Lee's calendar Dr Smith's calendar Dr Stone's calendar so let for example I'm going to take Dr Lee's calendar okay so I'm going to like take um what who else can be the patient I'm
• 343:00 - 343:30 going to do the patient search by ID and then I'm going to give something I don't know maybe 1 2 3 whether I have a patient no okay phone number I don't know I don't have any patient so maybe add a new patient then I'm going to like save so you need to have a patient that's the problem in the test data they don't I don't have anybody popping up with the
• 343:30 - 344:00 numbers let's say now click here to add a patient okay I'm going to add a patient now so patient new patient address is okay create a new patient not found okay so I need to create a patient okay only then I can schedule an appointment for that um a patient so we have the receptionist is
• 344:00 - 344:30 going to have calender finder flow recalls recalls means for example um if annual is due you can always send a reminder like um your last year's checkup is uh um I mean the current date it's due please schedule for a new appointment like that you can send them through text or email then uh like patient you can if you want to add a new patient you're going to add it and then you're going to save it you're going to add what um what is their employee status employer status and who's the
• 344:30 - 345:00 guardian and then what is the current address and everything and then you're going to create a new patient right now it's not allowing me because it's going to be test environment so yeah you create a new patient only then the receptionist can schedule appointments so if you see here the receptionist cannot see anything like patients like data okay what she's able to see is only like um the physicians's
• 345:00 - 345:30 appointment I mean like what are the schedules their calendars and if she wants to find some um patients um date right that she's able to see and recent patients information she's able to see and for example we have Phil see here any patient data it's not allowing me to process anything okay I'm I'm able to see only a few uh data here and then visits current visit and visit history
• 345:30 - 346:00 reports means from the insurance site what are the reports and then um you you're going to have um okay so like patient right like which there are like if there are multiple hospitals we are for all the four sister concerns we are using only one portal then also we are going to see like when did they come and then how many visits they had what is their history and then um what
• 346:00 - 346:30 are the insurances and all so only like very few information she's able to see she's not able to to see diagnosis information she's not able to see um uh procedure information she's not able to see anything other than the only sensitive information she's seeing is the SSN okay so as for my understanding we'll have to create separate portals for the each of the department right okay
• 346:30 - 347:00 and so you are going to name that okay provider portal patient portal and then desk portal all that will be separate modules like that and will there be any integration between all of them yeah yeah it should be right from the front
• 347:00 - 347:30 perspective it's looking like only one application okay so there would be a particular system individual system which has all the qu is in that right okay okay now I so the user may not understand the difference but using the credentials when they log in it'll be different for everybody uh ma'am would you be able to share this link with us I sh okay let you want this open demo link right yeah yeah so that we can actually create those wi frames and stuff for our future
• 347:30 - 348:00 reference MH let me share give me a second I'm going to take the link it's called open yemma demo okay I had a very hard time finding this link but this is really very interesting we'll be able to learn through that thank you so much yeah so I was like I need a project I need a project I cannot simply tell them in words so yeah that is easy to comprehend because other projects are really very
• 348:00 - 348:30 difficult in order to understand MH okay I have add the link in the um yeah chat okay please and please make use of this uh uh link okay because we don't have anything like I cannot create something and show you right because we don't have developers so yes ma'am so this I with with so much difficulty I found this software because I really want to teach you and give you examples when you're adding something like a case study in your resume you should have tested something from a
• 348:30 - 349:00 testing perspective you should have tested something right so this will be very helpful for you to test like you can log in through receptionist or you can log in through physician and you can test all the modules create test documents for all these modules and so you like at least you have worked you feel like you have worked in a case study okay the next important one is now you after finishing your process flow diagram now we are going to write our user stories you you got a fair idea about the um project now we going to
• 349:00 - 349:30 like uh create epics and then user store okay so before we do that now we have to do something called budgeting okay let me take the budgeting um looe template pra budgeting will be done by
• 349:30 - 350:00 project manager or business analyst so like uh if you want to become a lead ba right then in that case uh like I was I'm involved in budgeting for a very long time so I don't know whether it's different and offsh sure but in on-site right they will definitely involve the lead be yeah
• 350:00 - 350:30 because in some of the interviews like they are asking have you do you know about budgeting have you involved or have you done so yeah they that's why I don't know in uh offshore I don't know but uh here right we are definitely involved yeah yeah not the junior okay even I was under the impression that it is being handled by the project manager yeah of course they will review
• 350:30 - 351:00 but uh you only will know the like every user story is estimation right for example if you take here I create a user story okay this is for an example I create this user Story Only me my developer and testing team will know what is the story points so story points is like how how long this is going to take I have a four week Sprint and I have no holiday so I have 20 working days in that 20 working days can my developer developer develop this story can I the testing team test this story
• 351:00 - 351:30 can we go live after four weeks Sprint so yes means like so it see you are creating user story we never know how much work the developer has to do for this functionality right so that's why we have story points story points is nothing but so for here if you see every story will have a story point so story points means it can be a one-pointed story or it can be a two-pointer story it can be three-pointer story or it can be fiveo it's fony series okay
• 351:30 - 352:00 so there is no four-pointed story so be careful in answering in the interview one pointer two pointer three pointers five pointers 8 pointers 13 pointers that's the max we are doing we are not even going for 13 because if it's more than eight then usually like we do we want to split that into multiple stories then if it's a 13 pointer Story please divide that into eight pointer and a five pointer because 13p pointer is complex
• 352:00 - 352:30 and we don't want uh people to take so for example to be easier let's say one pointer means 8 hours okay one means eight hours yes okay someone is taking eight hours to complete a story then it's a onep pointer story in one day okay okay two pointer means 16 like this you just keep on adding the work hours okay so we have only like for example your team is a 4 week Sprint and for that particular
• 352:30 - 353:00 month you don't have any holidays you have 20 working days and you have uh two developers and then uh two ba and then two testers okay and then it's not about only this project right you'll have multiple projects so don't just think this is the only project you multiple projects so you have about like now um 10 user stories and every user story is going to be um a five pointer story okay then how many my developer
• 353:00 - 353:30 can pick 20 working days how many my how many how many points my developer can pick if it's every day it's 8 hours every point is 8 hours can you estimate 40 hours we have basically five mons 40 years and 10 years stories every week or every
• 353:30 - 354:00 Sprint the Sprint is of four weeks right how big is the 20 days working days days then for that particular Sprint how many points can developer take each day maximum three maximum three yes we want to give that gap for him right so you take 15 points 15 uh like totally we are doing 15 15 points
• 354:00 - 354:30 for him yes why we are giving that we are not taking that in full capacity because he has other work also to do right because there'll be new projects coming in and we have to attend calls also production issues like for example new projects calls and then yous as well right you have production issues going on simultaneously you'll have status calls and then you have Sprint calls then you have multiple escalation calls all the calls then you have oneon-one with your manager calls all that is there so we don't want him to
• 354:30 - 355:00 work in full capacity that's not a good agile technique right so we always have to give some so that estimation we have an Excel sheet but that's not our work that's why I'm not teaching you that technique so like what is the how many for next Sprint how many working days how many holidays and how many capacity uh like how many people are available is anybody going on vacation is there any like holidays national holidays like this calculation know that is Scrum Master product owner job it's not our job but I'm just
• 355:00 - 355:30 telling you they have an Excel sheet to calculate and all so during the Sprint planning meeting they will tell you for the next release we have four holidays for example this week is a Memorial Day weekend so Friday is a holiday for me and Monday is a holiday for me so I uh for those days we are not that points will not be calculated so then it will be only 18 working days right if there is holidays yeah only 18 working days or if it's going to be Independence Day in India
• 355:30 - 356:00 it's even like better every month we have a holiday yeah so so upon depending upon that we want that user stories to be prioritized we want like depending upon our team's capacity also it's not only your project remember there are multiple projects so which is comes first is is called as priority which comes first is called as a priority right so for you maybe like um you can discuss
• 356:00 - 356:30 with the business owner and say that we can only like do reception module for next print because we have limited capacity and we have other projects priority also we can do only that that module and that also you have to check with your developer can we complete all the end to end development within that four weeks or like how much we can progress can uh we have only the calendar module and then with just the um finder and then maybe like they can schedule that much only that much we
• 356:30 - 357:00 going to have or can we do everything can we complete that within four weeks can we go live within that particular date so this is like you everyone should agree right your developer should be very confident your testing team is like yeah we can test this and also your business owner should agree to this decision also if they say that no no no we want everything to be done we wanted as like a full finished product I don't want only this module then you have to wait because we don't have capacity so you have to wait for three months or four months but still we will be doing
• 357:00 - 357:30 agile only but we'll complete everything except that we won't go live we'll finish all the uat and all but it will not go live all the modules will be completed and then we we'll fix on one particular go live date and we can go live that's how we do ma'am I have a question MH oh thank you ma'am uh suppose I'm a be of a company now through agile methodology I am uh creating the user stories now the thing is that uh in in my team there is
• 357:30 - 358:00 other department like there is a development team there is a analyst stream and there are testing team now um if it is kind of application B based project then um uh there there are may be some bugs that that are G to testers to identify it uh to testers have already doing this works and then they are providing uh the error part to the
• 358:00 - 358:30 development team so is there will be there any kind of changes in the user stories when you find the defects uh yes I mean there is a there is a change and the change is ongoing yeah so you're you're telling that your during development phase your business owner is coming your new requirements yes no no no we don't accommodate that that's why I'm saying budgeting is very important okay so for example I'm not accommodating according
• 358:30 - 359:00 to their mood swings see here so now like first initially what we do I'm creating all the task and user stories for every user Story how much it's going to take and then overall what is my um um LOE level of effort we submitting this to the project manager and the project manager like she's like okay how many people are there I have two developers what is their time sheet uh I mean how much what is their pay whether they're full-time their contractors then their billing going to be different and uh so how many hours they'll be working
• 359:00 - 359:30 and then for for this month what what should be the budget She'll always have that extra like maybe $1,000 or something and um so we going to start so accordingly she will approve and she will submit the funding and once the funding is approved that's why funding is very very important once we uh funding is approved it means that sorry about that okay okay so yeah so that's why like we we want to
• 359:30 - 360:00 get approval so this is very crucial guys you guys have to get approval once you define all the user stories or if it's brds that's totally fine but we need to get that approval before we start the project now there is no going changing requirements during development phase or during like testing phase like someone has told here we can we know agile means like accommodating new changes we know that but how many how
• 360:00 - 360:30 much to what extent because if that requires additional funding then you have to be very smart to tell the uh business owners that no this is not told in initial requirement phase so uh this will be a new requirement change for us okay so let's say that this open EMR uh this open EMR right um this is what they earlier they requested and during testing now during U testing uh the
• 360:30 - 361:00 business owner is coming and telling that no I want to maybe integrate another facility okay so so here we have all facilities there are like 1 2 3 four four facilities here and now the business owner is saying that no we have acquired two more sister companies okay so we have to integrate all their data here can you add two more facilities you you should be like no we cannot do that that requires lot of work if it is like small enhancements that's fine something
• 361:00 - 361:30 like they want to add a new tab or something like that then that's fine because because the is not going to get differ so much but if there are going to be like major requirement changes and so it has to come to uh a process called Change Control process okay that process we call it as Change Control process Change Control process means again they have to submit the intake again we have to review with our development team our uh scrum team and
• 361:30 - 362:00 then we have to like make sure whether this can be accommodated for the because the then the goal life is going to get extended if they say that no no no we have acquired two more facilities we want that to be added then the goal date has to be changed because our developers H needs work right they need to integrate new things and then we have to test again from the beginning again sat testing so there are three types of testing one is unit testing that is by done by a developer then system integration testing that is
• 362:00 - 362:30 done by testing team or sometime there is no testing team you will do then uat that is by business owners so all these testing is now completed again you have to do it from scratch for all these new requirements then your funding is going to change and in that case uh we cannot like go with that already like estimated a goal life date it will be different but if there are going to be very small changes now like very very few like very small small
• 362:30 - 363:00 changes we can discuss with the developer they'll be like yeah we can accommodate for this current Sprint we can do this uh with the current Sprint go live date itself then we can add that but for all this if there any kind of change requirements it has to come through Change Control process defects bugs that is different defect is like I'm not for example here I'm not able to add a new patient it's throwing me error okay if I submit create new patient see something is throwing an
• 363:00 - 363:30 error this is a defect you should not show me during uat it's not supposed to show I must be able to create a patient and add a new patient here I must be able to schedule for example scheduling I take um schedule something yeah it's only showing me like only few when I add uh new patient patient ID I'm going to add here there is no test data here okay no records found I have to give them test data if I want to add a
• 363:30 - 364:00 new patient it's not allowing me to add so this is a bug right so that defix you have to fix because it's it was like part of existing requirements we have to fix that but something new like I already told you we adding two more facilities all that cannot be accommodated in that current release because agile is very fastp it can be very stressful for the developers to add continuously adding requirements it can be very stressful that's why we have established a process so that we can be
• 364:00 - 364:30 very professional we need not go to Every call and fight with them they are the one who is funding us remember that that without them funding you there is no time sheet for you to submit okay remember that so we have to be very polite polite with them and also we have very professional and then you have to say that I understand your concerns but we have a process for that and uh the this U this will be going through the Change Control process so as a scrum team for anything like during development if there is any new changes coming you have to go through this
• 364:30 - 365:00 process only so I can help you with how to submit the change request and all that can help you like this you have to be very polite and professional talking with them instead of like how can you tell me that you signed off all the um user stories now you cannot tell me what to do you that's not how the business works right so they're giving you a project it can be a multi-million million project and uh we have to accommodate we are just it application development so we are part of the organization uh so we have to be very
• 365:00 - 365:30 cordial with them otherwise they they will be like oh this team nobody is cooperative that's the name we will get okay ma' thank okay so one question sorry so basically when we are coming across like in the interview they ask this question most of the times that you know you are in the middle of the Sprint and you're working on the module and suddenly they come up with a new uh
• 365:30 - 366:00 requirement something like that so in that case we can give this kind of an answer or this is the right answer this is an existing process we fall in my organization okay any new enhancements we can take up but there is a process so it's called A Change Control process we are not denying anything of course so we have to submit again the ticket in jira you see here yeah submit again we have to review with our existing scrum team scrum team means scrum Master product owner developer and tester and I have to
• 366:00 - 366:30 check with them whether they can be accommodate for current release if it is like I can accommodate it's fine if something like major uh new requirements are popping up then the L will be different the go date will be changed we can accommodate I'm not saying we cannot accommodate because agile means changes yes yeah why this is called a methodology because like see like business owners are there they are not they are not changing requirements right is the situation also
• 366:30 - 367:00 circumstances also if a company is hiring new products and and they have new contract with a different state or something like we never know from sales perspective what's happening from customer perspective what's happening from it perspective we only think oh this is too much work they're adding requirements but we never know in ground level what's happening in sales in in product level what's happening we never know right so we from an IT perspective do not react that's the first thing I will advise and then uh you have to always you can always say that yeah I
• 367:00 - 367:30 have to discuss that with my manager uh I'm totally fine with you but we have a process please submit I have to discuss with my manager and also my scrum team and I'll get back to you okay that's the way you will deal this but my experience they're constantly changing they're constantly they changing and know they may be like during U they will change and uh we have to accommodate otherwise it will be waterfall in waterfall everything is
• 367:30 - 368:00 fine and then uh at the end of the day they're going to see that we are going to fix some defects and then we going to go like but in agile um that's why we have very short Sprints two week Sprint 3 week Sprint four week Sprint so that if there are any new changes we we can maybe we can say that yeah this will take maybe another 3 weeks maybe next release we can accommodate this and usually they'll be fine they know we are submitting a new request so this will take time for them and they'll be okay with that something very urgent or maybe like for example state is giving you
• 368:00 - 368:30 fines and someone is going to sue you that is a very um important production issue so in one scenario this is a realtime production issue that happened was one of a one of the members uh in a in a particular state right his eligibility date he in his insurance is already terminated he said I don't want that okay and then his insurance is terminated so but it was not updated in the insurance system okay he already said I don't want this this
• 368:30 - 369:00 is the last day then maybe he didn't pay I don't know some uh case but it is not updated in the insurance system so he's going for a a surgery and an emergency surgery okay some like abdominal pain he's going for appendectomy some major surgery is going there and then what happens is the hospital is like checking for this existing information they are able to submit an authorization because in our
• 369:00 - 369:30 system it is showing that he's still eligible okay and then what happens is like uh they approve the authorization okay and then the whole surgery is performed now when they submit the claim now there is a denial stating that he's not eligible for the services so the hospital is going to sue the I mean like Hospital didn't Su the hospital is giving some uh like $120 um and 120k Bill okay including all
• 369:30 - 370:00 that 10 days like um um accommodation everything they're giving a 120k bill to the um member member is like now asking uh no I've already told yeah I remember like um it's dominated but why did you approve because his lawyer is like my patient cannot uh pay this bill it's too much for him is out of his capacity but the lawyer is actually asking why did the insurance approve the authorization
• 370:00 - 370:30 that's how they want this case because in in in our system it's still still showing that in our like database right it's showing that he's eligible for services that's why we approved his authorization now like when this is a production incident now they are asking us to do like check on why his domination days is not updated why his termination days not updated so in that particular state I'm not I'm not telling that state that in that state it takes about 30 days after 30 days of termination only that updation will
• 370:30 - 371:00 happen till then he's eligible for the services so none of the business owners were aware of the particular scenario because they have not had this incident for that particular State even if you terminated today like 30 days after that date the patient is still eligible for services so lawyer is bringing this this attorney is bringing this point and none of the business owners actually know that this is like something happening that particular State and they want the case and our insurance has to pay that uh money 120k they paid it they won the
• 371:00 - 371:30 case so we will never know business owners are not aware in ground level what is happening then they will not know every state mandate they will not know federal law so they that's why they then if something happen like this happens then they again come to you they'll be like termination days has to be updated the same day don't give 30 days except for these few few uh States and then you have to maybe send a notification to the member in our database for this particular States uh if there is a 30-day extension there needs to be a popup or something for
• 371:30 - 372:00 this authorization team something that will be a new requirement during the uh development and you guys have to accommodate but there because there was a um something was going on and our insurance has to pay so this is a major production issue business owners are running to your team they asking do to do this fix so in that Cas of in that case right we have to accommodate that we cannot say I cannot do it we know this is an issue with our insurance so we have to accommodate that in this particular case this
• 372:00 - 372:30 patient was admitted within those 30 days after okay yes so our system in authorization system it is uh they approved because he's still eligible but when during claim submission they denied they said that no he is not eligible yeah so then that's why the issue happened right even the actually the patient is not aware the attorney actually he took points but the patient
• 372:30 - 373:00 in this case would be aware like he might he was aware that he's not covered right so he might be having some other no they usually Sue so that this 120 can become maybe a 10K something like that for that so why they sue the company is like why did you approve it's your mistake it's not my mistake if I'm not eligible then you should have never approved you you like you understand the patients perspective then why did you
• 373:00 - 373:30 approve we submitting to the insance Insurance yeah why did the insurance say this is covered so there is like a gap between this authorization department and claims department that's what I'm trying to say in authorization it is saying eligible in claims it is saying not eligible but authorization the The Physician always tries to get an understanding from the payers point of view that this is covered or not right
• 373:30 - 374:00 that's the authorization they will submit any any major surgery they will submit an authorization they want to know whether this is covered by the insurance and when the patient was not covered since okay okay so when but the patient was aware that he is not covered but when the prior authorization under prior authorization it was stated that he's covered yeah but that's emergency and it's upy he's in pain he's not going to like think about whether the authorization is covered or not all he want to do is like remove my app appes
• 374:00 - 374:30 so you have to understand situation okay patient is in great he's not going to say is my authorization approved he's not going to ask that he'll be like doctor get out of my get this out of my system I'm having a huge trouble here and he's admitted for 10 days it's like a major you know like apam is like it can really be very painful so when the bill comes now there is a 120k I cannot pay now the hospital
• 374:30 - 375:00 is like no you you have to pay it's your problem and then uh they are like then he goes to the court and then attorney is like for this particular State he's still eligible but our business owner don't know that that's the problem right if the claims department should know that those are the business owners right they should know state law okay who are the business owners mostly when we talk about in this case like the particular real life like in the real they will be fulltime of that
• 375:00 - 375:30 particular insurance for example if I can be business for for Florida you can be a business owner for New Jersey so we are all working as full-time employees for right now okay so we are you can hello yeah so will will it be a part of him that uh I have to reduce the gap between the claim and authorization site so the source of Truth is some
• 375:30 - 376:00 database right so authorization is also pulling the information from the some system system and the claim system also is pulling the membership information from some system I don't want to name the system here so that should be same right that if it's changing that's how we will find out so what is why why there is uh not we have a common database or some system that system should be showing like if there is a bug in the system that's when all these will happen or you don't have a requirement for that particular state
• 376:00 - 376:30 after 30 days for Kentucky after 30 days even after 30 days uh the member can apply for services you don't have that requirement for that for that particular State then you're going to get into trouble yes because this is already mentioned H already there's a state law business owners don't know and during all this production incident only they'll come back to you to the ID team they'll be like fix this immediately we don't want to happen this
• 376:30 - 377:00 again this escalation right this goes to coo level yes yes okay so this is a real PR incident if you want you can take this as an incident and tell in the interview and then uh tomorrow will be the last day for this week and as I said like Friday and Monday is holidays for me so I'm going for vacation so tomorrow will be uh I'll follow up whatever is remaining I'll follow up for tomorrow and then the next class will be on Tuesday okay thank you so much thank you
• 377:00 - 377:30 I want to ask one question uh maybe you can stop the recording uh if you want yep yeah okay let's get started so today we are going to learn
• 377:30 - 378:00 about the user stories okay today is day eight and we going to learn about for this open uh EMR project how to create user stories okay so first we are going to go with the receptionist model uh module so this screen right that's for this screen only we are going to write the user stories so I in jira board and I'm on click let me start recording
• 378:00 - 378:30 okay so I click on Create and uh I'm going to first create the epics okay first epic for this story so creation of or automation of um
• 378:30 - 379:00 FR desk Port okay so summary is what we are going to do is uh we going to write so there's a format for writing the um user story okay as a reception list I need to
• 379:00 - 379:30 view the calendar tab so that I can schedule the appointments for my patients okay so first this we are telling we want that um this calendar right this is the
• 379:30 - 380:00 one we want this to be shown this the first module we are going to work on okay so what is there here if you see it is calendar give me a second scream
• 380:00 - 380:30 okay so as a re receptionist I need to login First okay so this includes login functionality so I need to view right so first what will happen they have to log in and then once they log in with the
• 380:30 - 381:00 valid uh username and a password uh they they should be able to see this um calendar tab okay so um what you're going to write in the description is you're going to write like detail what needs to happen Okay so receptionist U um needs are valid first number one valid username
• 381:00 - 381:30 uh valid uh password okay and then once they view in they should be able to um see the calendar tab so once they click on the calendar tab they must be able to view the um facility right for example if you see here they must be all the providers like
• 381:30 - 382:00 for this particular um they can one or more hospitals like um combined together in the same portal because usually in the US right it's all sister company so maybe the first floor is all gynecologist and the second floor is like full of labs and like so we need to see everything whether there is a pharmacy whether is a hospital or there is a clinic all that will be integrated mostly they are all owned by the same um uh owner so they're all sister companies
• 382:00 - 382:30 but the names will be different okay it's a for example chrisy Hospital chissy prasy like that so we want to incorporate all the facilities and all the providers so who all will be available for example here Dr Lee and Dr Smith and Dr Stone so only these three people are there and uh they are the uh we have to schedule for these three people so the receptionist has to view the calendar on the left side and all the providers names and everything and then they are able to see the calendars
• 382:30 - 383:00 and the slots okay from 8:00 a.m. to like if you see um this is like uh evening 5:45 okay that's the last appointment because 6:00 I think it will be closed okay so 3 4 5 yeah 5:45 from 8:00 a.m. to 545 everything like every 15 minutes he has an appointment okay so we can like just click that and we can start scheduling so once he clicks that's different but first like what the receptionist has to
• 383:00 - 383:30 see is first the calendar tab then finder then flow recalls patient fees admin and all so what you have to do if this is a Pega application I'm just giving you a real time example so if this is a Pega application you have to create a prototype prototype means here itself like um in Pega you can create a prototype or you can have some prototype uh tools also I can show you some of the tools so what you're telling to the
• 383:30 - 384:00 developer is this is how the front end should be and uh this is how how like um the if you click on calendar this is what it needs to be here needs to be that calendar box and below that we need to have all the providers name and all the facil facilities name and on the right side you need to have all the Physicians um schedules like this this is what the Prototype you will tell and exactly how he was going to make there can be a few changes that the developer can add or they can do but you're going
• 384:00 - 384:30 to give an idea of how that UI should look like and uh when you create the Prototype right you have to discuss with the business owners also that this is what you want they may be like yeah I don't want this feature I don't want that feature they may tell that but uh accordingly you have to develop the Prototype ex especially if you're working with like customer Cas facing UI perspective right this is what uh you have to definitely create that prototype and show it to them so what you will do is you will create a
• 384:30 - 385:00 screenshot okay you will like exactly tell how it is and you create a screenshot let me share the screen now so that you'll understand how to so you can use one of these prototyping tools okay there are so many different tools so you can use one of these tools okay let me click
• 385:00 - 385:30 here okay you can see here flinto uh or web flow or you can use um sketch sketch is very easy also and yeah we can use balsamic also right yeah yeah you can use balsamic also yeah whatever is easier for you just create a prototype on this like screen okay UI um prototype and then you need to attach it here in the uh user story just attach it here browse click and attach it okay why
• 385:30 - 386:00 we are attaching that is like our develop has to have that um idea on how exactly like login functionality it will be the same depending upon the coding language right it is it's going to be the same the UI is going to be the same but once they log in for Physicians it's going to be different and for receptionist it's going to be different so we going to give that like vision for the developer in the story itself so you attach that and then um we are going to
• 386:00 - 386:30 uh yeah we are going to create this user Story Once you create that user story and uh it will be if you see right it will be in the backlog if you go here if you see it will be in the backlog here there are so many user stories so um
• 386:30 - 387:00 so if you are able to um if you creating like 10 user stories right if it is in the backlog it's not your job to like uh groom it so we called it as Sprint
• 387:00 - 387:30 grooming okay let me take a story grooming okay during the Sprint review call okay it's called as uh story grooming so what you you will create the user stories that's all okay you will just add like um the description and also acceptance criteria that's all you will leave it but during the Sprint review call um the scrum master and the product
• 387:30 - 388:00 owner okay what they will do is like uh they will be grooming the user story so what is grooming the user story let me take an example here so going to take this one if if the user story needs to have a story Point that's a mandatory without story points we cannot like progress or we cannot pick up for the next print so every user story needs to have a story point if that particular user story needs to have some subtask means that also you have to
• 388:00 - 388:30 create for example I need to create a uh BRD for this or maybe yeah BRD for this project okay I need to create that or I need to create a um a mapping document for this particular uh user story yes or I need to create a UI prototype okay so that all will be task
• 388:30 - 389:00 under this particular user story all this will be task once you complete one by one you'll be closing it so I've already told yesterday um that story Point estimation is basically upon if it's one story point it's 8 hours in my project it's like that I don't know about other projects in our project it's like if it's one story point we calculated for 8 hours so how we are going to do that story Point estimation is how long it will take for the developer to develop that and how long
• 389:00 - 389:30 it will take for the tester to test that and uh also the ba if you're going to do all the coordination you have to combine all the points and uh you're going to give it as like uh maximum we recommend giving eight not more than that so you give uh the story points so why because we have to I would like to ask you give give extra maybe give one pointer extra or two because if you are a newcomer and then if you are going to have you need to have KT with the other Bas or you don't know the process it will take some
• 389:30 - 390:00 time for you please give that one point extra if you are experience then you know like exactly how much time this is going to take so let's say that it's going to be an eight pointer eight pointer means it's going to take eight days right eight days to complete this uh for this particular user story under the particular user story you have all these task task will not have any story points okay only user story is have story points so what is user story the story of a user so from the user's perspective only we are
• 390:00 - 390:30 writing all the stories okay as a receptionist as a physician as a clinician as a member so like from their perspective only we are writing every functionality that is why it is called as user story below every user story you can have subtask and subtask and all there is no story points needed you're just going to like um create subtask and once you are done you're going to make it as uh in progress and then uh or you can go make it as done so BD is completed next I have to complete the
• 390:30 - 391:00 mapping document that is in progress and maybe that will take one day or two days and then I completed that it's done prototype I've completed maybe it took only 4 hours so that is also done now I can put all my comments here so that I can tag all the developer who's working on it and I can say that please take a look attached to VD attached mapping document attached U prototype like this you can like attach give comments tag him okay tag him and give comments if
• 391:00 - 391:30 you want you can ping him but if you tag itself he'll get a notification in his email ID and once you've completed once for the next Sprint so we are not picking the story in the current Sprint so how you will work is there are two types like you will have your existing Sprint and you will be gathering requirements for future Sprints existing um user stories you'll be working on it but for future also uh like for the next Sprint or upcoming Sprints you they'll
• 391:30 - 392:00 always be intake request right they'll submit something and you will go ga the requirement so you will do both things existing Sprint user stories also you will be testing whatever coordination you want to do you will do that and if there are new uh projects coming up you will schedule Gathering um requirement Gathering calls for that part uh new project to so existing uh Sprint work also you will have new project index so you simultaneously you'll be working on uh both these so current
• 392:00 - 392:30 Sprint you're finishing all the testing you're uh getting the U sign off and then you are uh making sure everything is going well and you desing on the go live date and you're going live okay go live so in that case we are good then what will happen you'll have one before you go live for example we are going live this Friday this like Thursday right Thursday means like today you'll be having your Sprint planning calls Sprint planning
• 392:30 - 393:00 calls for next next Monday from next Monday if the new Sprint is starting means so you'll have like either on before that Friday or Thursday know that's when you'll have Sprint uh planning call in that Sprint planning call uh what your product owner or scrum Master they will do is they will be uh looking at at the backlock and uh like currently like how many stories it's being worked on and is everything completed okay these are the stories in backlog now we have to make sure that um
• 393:00 - 393:30 we uh uh we do that prioritization meeting so Sprint in Sprint planning itself you will be doing prioritization or you can do earlier also we can make it as two calls if there are so many it's a big team right so one is prioritization call and then um the second one is called as Sprint planning call so in prioritization what you're going to do is like for example there are five Bas and they have created so many like maybe
• 393:30 - 394:00 like 20 to 30 user stories but we have limited capacity and also there are holidays for this next Sprint so which which which all stories needs to be essential essential means it has to be done essential and then which is like priority priority means next to essential and which is like uh which can be in watch watch means we are just watching on that user story it can be picked or it is fine if you leave it okay there are three different types essential stories priority Stories and
• 394:00 - 394:30 watch stories for example this reception story right that has to be picked up that is an essential means now that us a story you're going to pick from here to the current Sprint okay you'll pick it and then um other stories for example um Physicians admin and all you can maybe after two sprints also you can do those those stories and all will be still in the back lock only it will be in ready so if you see the user stories can be in three status okay it is in
• 394:30 - 395:00 open open means when you create it will be in open and then it will be in ready ready means like you're ready to pick up for the next print once you pick up for the next print it will be in in progress after you complete uh the user story it will be in um resolved and it can be closed okay so here we don't have that because this is not um paid one right this is a basic version but in uh in your office it will be more advanced
• 395:00 - 395:30 you you'll not only see to do in progress done you will see like a ready open when you create it will be in open ready and um in progress and closed so interior may be asking your can you define what is the meaning of ready that's a very very popular interview question what Define ready status what is ready if a story is ready what do you mean by if the story is ready to pick up for the next print means that user story
• 395:30 - 396:00 contains all the information for example it contains all the like for example uh heading and also acceptance criteria contains all the subtask all the documentation required for that story points is added we know like everything about the user story so now the user story is ready for development that's the meaning of ready if a user story is in ready means ready status means uh everything regarding that user story is complete now the developer can pick it up for next print and start development
• 396:00 - 396:30 and testing think and test that is the meaning for ready open means you just have created youve Created but you have not added all the description acceptance criteria documents related to that you have not created process flow diagrams so it's still in open or you can be in refining too refining in the sense you're still working on that so you can create a story it can be in open status but it can also go to refining status refining means you're still working on you still have have two or three more
• 396:30 - 397:00 calls so it's still Gathering requirements in that St that user story will be in refining so one advice like what I will give you in practically itself when you have a high level like idea about the project please start creating user stories because you'll forget you have multiple calls right it's not only working on only one project in my experience you you go to a call you you record the call ask the permission record the call and then immediately after that once the call is
• 397:00 - 397:30 over start creating user stories because if that is funded if not funded means you're not going to do but um you know this is be funded this is some mandate or something you start creating user stories because you don't want to forget so always the recording is there but please start creating and start working on it so the next call if you get something add the documents the next call if you get some process flow diagrams whenever you have time you create process FL diagram please add it
• 397:30 - 398:00 because otherwise like uh you'll be jumping from one call to another call to another call there are like three different four different projects you're handling production issues you're handling in between that there are multiple uh emails that you have to answer somebody is pinging you I want that I want this like this so many people will be interacting with you you'll forget what is actually the new requirement also and again you have to go through the recording and all so to save time please start creating as soon as the call is finished whenever you
• 398:00 - 398:30 have like 10 15 minutes please start creating user stories so that you know that you have created it's in the backlog and you're adding points in those stages it needs to be in refining stage it is not ready ready means everything regarding that user story is there so the developer can pick it up for next print okay it's a very very important interview questions they'll definitely ask you ask you for a case study and ask you to explain the whole process so if this you are able to say this is what
• 398:30 - 399:00 exactly it people are doing currently everybody is doing this only whatever companies Microsoft Google Facebook Twitter Tesla everything they're doing the same thing so if you're able to explain this properly all these meetings this is why I did my roles and responsibility is I um go to the requirement Gathering calls Elation calls and I gather requirements through all the techniques and I create user stories and uh every user story uh I'm I have to make sure that all the
• 399:00 - 399:30 documentation is available so my documentations are available in Confluence I create here so for example here I create all my notes okay my brain brainstorming session notes my retrospective notes my um like yeah all the notes whatever everyday meeting notes I I make sure I document here and my brainstorming session notes I document here my 5way analysis session I documented here so all the analysis whatever you are done you make sure that you document in Confluence they rade
• 399:30 - 400:00 templates so you're not doing anything from scratch your BRD also you can document here if you want you have an external vendor you're creating a BRD for them so you're going to document everything in Confluence and I will create all my user stories in jira and if I want to draw some diagrams then I'll make sure that I integrate liy okay
• 400:00 - 400:30 yeah so I will integrate this glyphy and I will make sure that all my U diagrams you can you can draw through glyphy also okay so I draw everything make sure everything is documented and see here this is one process flow and end everything is there uh and uml diagrams are there so everything I'll make sure it's documented and once it is ready I'm I will make sure that uh that particular
• 400:30 - 401:00 story so they will be asking you do you know what is priorization what are the techniques what is invest technique what is um estimation right how do you do story points estimation how do you do what is fony series and uh tell me like how the story points are given and if there is like they giving too much pressure what will you do and if there's so many conflicts the developer is not able to do it in that case what you do how do you manage the business owners so they may give you some real life like scenario based so for that you need to
• 401:00 - 401:30 know agile project means what are the meetings they are going to have you're going to have Sprint review meeting where story grooming will be done then you're are going to have prioritization meeting where we we going to make sure all the stories and we're going to review all the user stories and we're going to make sure that okay for the next print which stories are essential which are on priority and uh what are which stories can be in watch okay we have to make basically you're making
• 401:30 - 402:00 sure which stories can be essential and be picked up in the next Sprint so prioritization is very important uh uh Sprint review is important Sprint planning is important and then at the last once you pick up the user story right now we have to um create the sit documents and all so that maybe I can tell you how to create test uh test scenarios how to create um test plan and everything that every use case like we can take and we can create but for now you need to
• 402:00 - 402:30 know or if you have time like we don't have class tomorrow on Monday right if you have some time please start creating user stories for this particular module and then I can review whether those user stories are good or create one diagram for me or uh create one Confluence page and then tell me is this good or create one diagram one Confluence um page on one or two or three user stories for me and I can review with you if you are doing um as expected okay any questions till now
• 402:30 - 403:00 so hi pradipa so for user story we'll be writing in summary right yeah you will write you will write uh sumary you write description yes Des description pain will be like for writing acceptance criteria so there are three let me take that so here yeah so epic name right this is called as um The Heading okay and summary right
• 403:00 - 403:30 this is called as description yeah where we will be writing user story over here this is epic name yeah this is how you will write heading like for example as a yeah user story description will and then here details details in the sense like we need to mention clear about whether that user story is uh accept means everything like for example I've told here right that um uh first we
• 403:30 - 404:00 need that user needs to be existing user needs to have a login and a password then once they entered what and all they have to see okay so that you will add and acceptance criteria will be basically very simple this um this story is complete once the receptionist is able to log in so the testing will be based on the
• 404:00 - 404:30 acceptance criteria only yeah because these scenarios only will be there in testing right they have to fulfill this steps so this uh story is complete once a receptionist is able to login uh and view the calendar module that's all that is the acceptance criteria I have a question yeah yeah what is the role of a product owner in
• 404:30 - 405:00 this project so uh so you from you are a ba you're going for three to four projects like this there will be two three Bas right so everybody will create their own user stories what the product owners main responsibility is they have to make sure that uh in the backlock for example here we call it as backlock right so so if you see here backlog there can be so many user stories it's not only
• 405:00 - 405:30 your user stories but also others user stories also so they have to make sure their main work is like scheduling this Sprint planning calls and prioritization meetings so I have 100 user stories for my team how to prioritize everything because for you your project is essential for me my project is essential but we have very limited developers and um testers okay so they will be like okay
• 405:30 - 406:00 on all these we have to prioritize like tell me which one has to be essential then I'll be like yeah uh okay let me we have only like three developers and two of them are going on PTO so we have only like each can do only 15 points so maximum we can do maybe only like 45 points developer can take only 45 points okay now what I can do let me pick up the stories which are very very highly essential and because every user story
• 406:00 - 406:30 can be like one can be eight St 8 pointer one can be 5 pointer like that so we have as a team remember you are an IT application and as a ba you yourself like Senor ba you will be collecting projects for requirements for three to four projects other lead Bas they'll be doing three to four projects so overall that can be at least like 10 projects going on so we need to make sure which is essential which has to go live others will be in refining only that decision you cannot take
• 406:30 - 407:00 you can talk for your projects but you cannot talk for the as a team as a whole right that uh what about if can you understand my point um rupak there are two to three Bas are there yeah we are one team and everybody is under one manager two to three Bs are there and everybody has four four projects so everybody has created some 20 user stories who will deser which has to go live but I have a doubt in this case
• 407:00 - 407:30 because usually what happens is that the product owner only creates those user stories right no no no no no practically they don't but they don't have it knowledge they're morly on the non- technical side mostly what this they will not have knowledge like you you will be having end to end knowledge like about the application about like data flow you will have like complete thorough because you are gathering requirements right you will know when this has to go like whether a state maned or not they will be like like on a
• 407:30 - 408:00 higher perspective Ive they know this person is working on uh maybe this openemr project maybe this ba is working on a different project this person is working on a different project the high level they know but in and out they don't know nothing like they don't know the data flow they don't know about testing they will not know you will have knowledge on all these techniques how to test how to get U sign of how to go live so that it perspective knowledge only you will have they won't have SC Master product owner they will not be involved
• 408:00 - 408:30 in any kind of testing all they'll be involved in this uh scrum Master will be like mostly for stand scheduling the standup calls everyday status calls right so he has to make sure that's done and product owner will be mostly scheduling all the Sprint planning calls retrospective calls prioritization calls okay yeah and I have I have one more doubt I don't know whether it makes sense or not uh well like usually with other it companies when we are dealing
• 408:30 - 409:00 with those uh business clients they also have an IT department right but what about this Healthcare thing I have no idea about it so if there is any technical thing how would we be able to know about the client infrastructure the non-functional requirements who would help us with that again you give me a scenario I'm not able to understand the question see every company in us right every company has an ID Department okay so in healthcare also an ID Department would
• 409:00 - 409:30 be there yeah any any company right how can they have be just Healthcare and don't have an it okay okay no no I don't have any idea about the healthare so that is the reason I'm asking you because yeah any pharmacy company any hospital or any insurance everybody any Healthcare company they will have their own it that is beneficial instead of like them Outsourcing everything to maybe CTS or that's not profitable for them okay so there will be people yes inside healthare system yeah the
• 409:30 - 410:00 products can be healthare but they will have an IT department that's why we will all be working okay okay because we need to know about the infrastructure at the end in order to come up with the solution right so you'll be a part of that healthcare industry products can be different products can be you you can be working for a hospital but you are in their it Department okay I got you yeah thank you here it's mostly everything is Corporate right not like India not small small here it's like everything is Corporate
• 410:00 - 410:30 if there is a hospital that hospital all over Virginia if there is a hospital that is uh in like major hospitals right New York has very big hospitals all over New York they will have um branches and Florida means all over Florida there is a children's hospital all over West Virginia there'll be the same Hospital same logo they will have like different specialities so it's not like very small small clinics like in India here it's all mostly mnc's corporates okay everything is private my doubt is clear
• 410:30 - 411:00 now thank you yeah in US is everything is private forget about it's not like in India right so mostly everything is private everything is Corporate okay I have one more question mhm in an interview if the interviewer would ask me like uh how many story points do you pick for one of the Sprints that you working on so what should be my answer in that because in real time I do not have Fair idea about it so you can say that my Sprint was
• 411:00 - 411:30 like four we Sprint okay so in my project it was four week Sprint four week Sprint means usually it is 20 days and 20 days in the sense according to my estimation I can only pick 15 uh story points so 50 story points means that can be um one story point is eight hours no no no see here this story this this particular story can be a one point or two point I told you at fibon Series
• 411:30 - 412:00 this yeah it can be one pointer 2 pointer 3 pointer 5 pointer 8 pointer 13 pointer depending upon the complexity of the user story okay so you can take 15 onep pointers or three five pointers or maybe one eight pointer one five pointer it depends so in total 15 story points yeah that's your capacity Max okay okay if it's two weeks can you tell
• 412:00 - 412:30 me if it's two weeks Sprint I have only 10 working days then how many user stories I will pick how many story points eight eight story points and here pradipa like for development and it should have for testing also so we have to consider in that way right we have to once the development has been done it has to move for no no no so how we will do that yeah very crucial question you have asked okay in Sprint planning we
• 412:30 - 413:00 will have an Excel sheet okay that is she is called is um we'll have an Excel sheet and there is a a formula to calculate how many there are 10 people sorry about that this call C disconnected okay so is arind here yeah so arind like in the planning called right usually the product owner will have an an Excel
• 413:00 - 413:30 sheet or some kind of sheet they will be having where they must be able to like for example here we have a planner right yeah so there will be an Excel sheet what they will do is like there are like five people or 10 people in our team us what we do is like everyone will not have 15 points right now I'm saying that you will have 15 points but in reality everyone will not have 15 points
• 413:30 - 414:00 it's a seniors who are having this 15 points if you are Junior and all your points will be reduced they will give you only like initially like only this month you're starting right they will give only maybe 10 pointers or maybe sometimes they don't even give if you are joining as an intern and all very first month it will be observation only so it's not like everybody is getting 15 points but the seniors who are already there they will be to their full capacity they must be able to take that story Point what we will do is like we
• 414:00 - 414:30 have to there are 10 people there and everybody is like 15 15 points and two of them on New Journey so we are not going to assign them maximum the team's velocity is maybe like maybe we can take only 100 points okay so it's the it's the responsibility of a product owner to make us comfortable we cannot be like taking up on user stories since everything is being funded and we cannot like um confirm with the business owner
• 414:30 - 415:00 is like yeah I can do this project this can go live I can develop that my developer can do this that and all we cannot do that this is an IT team and the scrum te velocity is like very very very limited so they will be using a formula to calculate on if it is a senior person like how many story points can we give if it is a junior how many we can give if it's an intern how many that's a respons of a product owner we are not involving in it all we have to do as a ba is we will join this call
• 415:00 - 415:30 okay pration call and we were going to tell that I'm fine I can get only 15 user stories but this open EMR receptionist module has to go live that is a mandate from my business owner so we you tell that for this module is mandatory this has to go live in next print from my perspective in that 15 point I have to take this so but developer can choose his points will be different right for you you are creating the BRD you are creating all the mapping
• 415:30 - 416:00 document you creating protocol for you this can be an eight pointer but for the developer this can be a five pointer so from your points you're reducing the work if for example there is one uh login or user story that can be for you it is a one pointer what you're going to do is you're going to test but to create that for him it can be an eight pointer so you can take the same user
• 416:00 - 416:30 story okay and for you this can be a onep pointer so you're taking this and you're taking the additional uh maybe 10 stories but for developer he's going to do development on the story this will be an eight pointer for him so in that Excel sheet right we going to combine all the points so this um so three points for the developer two points for you totally Five Points I give totally Five Points so this is a combination of developer points and your
• 416:30 - 417:00 points points you're not giving only your points okay during in that Excel sheet whatever the product owner is filling right in that only your points will be accumulated so they'll be like for this story it's assigned to both for pradipa and another developer pra's points is two pointers for that developer it's three pointers so in that from that 15 point the two point will go then I'll have 13 more points and I can accordingly I can choose my next
• 417:00 - 417:30 stories that will happen the Sprint uh planning or prioritization call you got it uh you mean pra both will be happen like developing and testing for that story points estimation combination of both will be given at a time if it is exceeding 13 then we going to break that so for development maybe it's a development is a separate story your name is not there for testing and implementation you have maybe a is split
• 417:30 - 418:00 13 pointer is split into eight and five development story only his name is there your name is not even there for testing story your name and his name is there okay yeah it's not that every us story your name should be there it's not like that okay yeah any other doubts anybody has on this is very very important topic ask okay I have understood that this a
• 418:00 - 418:30 kind of set this kind of combin of all pointers yeah yeah okay ma'am my question is that uh you have shown some tools about the Prototype tools but uh um something is unclear to me so can you please give me a short example uh so that I can understand the purpose of usage the tools this prototypes so what you are doing with
• 418:30 - 419:00 prot that's your question I want to know the purpose of you purpose of that uh the the story or why we are using prototypes in the story yes yes yes yeah so yeah so the developer is using some coding language right let's say that he is using Pega and he without like you are giving only requirements in writing okay this dashboard is not seeing you this is the final product he's not seeing you and the business you gathered all the
• 419:00 - 419:30 requirements and everything is in words okay so imagine that you not you have not seen this dashboard but you are having only this everything in words like I need a calendar just close your eyes and think I need a calendar receptionist has to log in I need a calendar and also need a doctor's names and also need how will he imagine and do this is like building a house without having a map map or maybe architectural diagram okay okay it's kind of a blueprint Okay so protot typ is nothing
• 419:30 - 420:00 but you're giving a visual representation of what the business owners wants okay okay it is totally predictive thing it's totally futuristic thing right kind of especially when you're doing it from scratch he will have no idea okay if it's an existing proing enhancements that's different but this is going to be a brand new project and you're do to do all the UI development from scratch he'll be like tell me how
• 420:00 - 420:30 the screen should look otherwise this can be in this can be here this can be here this can be here it can be anywhere right he can develop anywh so we are like creating that miniature we are going we are showing that diagram so that and you get approval from business owners also so it's not that you take responsibility and also so you draw something show it to the business owners and you like uh you just verify with them is this okay do you want to change anything because they are the end users yes and if they are fine then you
• 420:30 - 421:00 add it in the uh um the jira story so that uh the developer has Fair idea on what to do the development how it has to look oh okay okay thank yeah he's like blindly going to do something and business owner is like this looks very ugly I didn't expect this okay okay yeah that has happened also so initially in waterfall like that only right they don't see to get to see
• 421:00 - 421:30 anything only at the end of the U project like that testing they'll be able to see the visually the software and they'll be like this is not what we expected it's like that's why like people move to Agile so if they're not happy then we can change an exper also we can change I see I see yes I got the point actually uh okay ma'am uh as a business analyst uh did you use the functional or non-functional tting or because this the
• 421:30 - 422:00 work for testers but did you have to do this thing what is functional and nonfunctional yes I'm asking you what's the difference do you know uh no actually I don't know that's why I'm functional means it has to like for example the receptionist now logging in able to do all the functional work right able to schedule for Dr Lee able to schedule for Dr Smith able to add all
• 422:00 - 422:30 the uh new patients and everything this is the functional requirement fully functional the software is fully functional we are able to do everything nonfunctional is the loading of this for example the login time how many seconds it's taking for the user to log in how many seconds it's going to be very slow then that's a performance issue or if the user ID and the password can be leaked somebody can hack the software then that's a security issue right performance is nothing but
• 422:30 - 423:00 how long it's taking for the um data to be loaded into the database for example I click something I schedule an appointment how long it's taking for to for the member to get the email notification whether it's immediate or it's going to take some like 10 minutes remember in like some applications right you'll be just waiting to get the notification you'll still say that no I didn't received it I didn't receiv receiv it I for example PTM you scanned
• 423:00 - 423:30 it amount has gone but still you don't get that notification that is all performance issue yes okay so that is not in our hands our developer cannot take care of this performance issues and all that be like slowly initially phase one we are going to work only fully on the functionality level okay then uh I mean for nonfunctional testing whatever I understood it's it's like for the customer customer expectations
• 423:30 - 424:00 right so you can do per this performance testing also but initially we are not going to do that that is like I need maybe 100 test data 100 logins and I want immediately everyone like to login at the same time and test whether the system can handle it or not or it's getting uh like broken pradipa I want to give the example here regarding functional and nonfunctional uh correct me here uh functional requirement is generally we
• 424:00 - 424:30 look how the system is working means here like functionality and all and non-functional requirements is like as you said uh performance loading security so that comes under non-functional right right yeah thank you that also testing we can do okay non-functional requirements testing we can do performance testing we can do but first they will focus on the functionality level and then only like to to test this
• 424:30 - 425:00 non-functionality requirements right for example like I need 100 uh users to just log in at the same time to see whether the application can handle that also we can do but first business owners will be working they'll be focusing only on the functionality first more than the performance that all will be like face to you got it first we need to have the application developed then once we are fine with all
• 425:00 - 425:30 all the features now we can test to some level we can test this security or functional I mean this performance and all for that also we need proper test data and then we can go live and if there is any production incidence accordingly we can do some enhancments the system is able going for functional first right right I mean see nonfunctional we cannot test right see
• 425:30 - 426:00 in reality let's say that I mean it is depending on the customer s i I mean customer but we also Monday through Friday there'll be huge people like logging in on weekends nobody's so we never know if something in production issue major issues are happening and software is not working then we have to take measures for that we need to have the product first
• 426:00 - 426:30 yeah thank you m for the clarification yeah but you can say in the interview they ask like tell me the difference have you worked on it you can always say for performance testing I've done perf testing and so usually it's more than 25 users business unit we create test data in new at and then we ask them to like log in and then maybe test and then at the same time just to see how that application is working whether it's able to accept the load like that you can tell so s
• 426:30 - 427:00 that you both you should need to know how to test is system integration don't say that I'm a ba only tester has to do so there's something called system analyst role where you will be the tester and the ba okay that's the thing I want to know okay yeah ba means no testing that's very plain ba right if you're going for Pega Salesforce and all you will also do the S testing there will be no separate testing time so you will GA the
• 427:00 - 427:30 requirements you give it to developer because they very highly paid the pay is on all like it can be like 2 crores like in us right Salesforce and all like 210 K it's like about like two crores to three crores that's the package every annual package so expectation is you will be like doing the combination of ba Gathering requirements creating test cases and then um you'll do fully like testing and uat also and uh so it's like it's called it's not B it's called
• 427:30 - 428:00 system manag list so you'll gather the requirements also do SAT testing and everything package will be very high since you're doing both okay so it's good you learn all that because most product based companies expect you to do SAT testing and all so my recommendation is if you want to have a hands-on experience because I told you like it's like cycling only unless you do it you will not learn it just by seeing someone cycle you're not going to learn it right
• 428:00 - 428:30 same thing you have to create user stories you have to create flow diagrams you have to create all this USD test scenarios everything by yourself and practice take this case study and practice and Monday or Tuesday you can submit the assessments and I can review and give you feedback if you want you can you can do that see you okay I think we're good for today happy weekend and I'll see you on next Tuesday thank you so much thank you have a good bye
• 428:30 - 429:00 hi pradipa so before starting uh I want to know the difference between like uh uh technical business analyst and functional business analyst means uh what the difference in uh real uh uh job scenario will be function business in a sense like did you get any requirement
• 429:00 - 429:30 uh no no no no I mean to say just I want to make sure like what uh uh responsibilities will be there for technical business analyst means uh like where he'll be not involved in like domain knowled uh domain perspective or uh how come it will be okay yeah so yeah let me what I'll do is let me complete the session and then um at the end I can tell you okay because I
• 429:30 - 430:00 just uh we have only today's session and then one more session I have to complete the syllabus let me complete that and maybe last 15 minutes second okay then okay so um hi everyone thanks for joining in today's class today is day nine and um we are going to learn about uh how to create test plan and test scenarios do really like business
• 430:00 - 430:30 analyst do have to do uh these kind of testing um so as we know earlier right in last class we saw that how uh this open EMR application like how we have to like uh create different um modules and then how we have to write user stories for each uh modules and all that so usually um Bas are not required to do the testing but
• 430:30 - 431:00 uh on site right we have a requirement to test but usually uat uat we have to do because sit maybe sit is system integration testing so that you may have a QA team and all who can who will be doing the testing for you guys but uat right user acceptance testing that is the end to end testing that's called as uat that's with the business owners so once the product once the code
• 431:00 - 431:30 is in QA region now like you want to test with the business owners because they are the ones who gave you requirements so basically you're going to tell give them like uh test uh plans and test scenarios okay so for this application this is how you need to test so I'm going to give you a real world testing template this is um this is for the company medfusion okay Med Fusion spent portal and uh what
• 431:30 - 432:00 they are doing is they're going to test the member portal member portal means uh the uh patient right they can log in and they can see their results lab results and everything so if you see this is a 11 page document what they telling is general information what is the product what is the version and this is the testing URL so if I click here it is going to take to um nextgen's page okay NextGen is a company and it is going to
• 432:00 - 432:30 like um tell all the version and everything so but I'll show the template is very important now so what you will do is like you have to create this template and you have to for U also I'm telling Okay this not for sit even for U region you have to create the template because they don't know how to test and you have to create these documents and share it with them and so you're going to tell like how are we going to test and what is the measurable metric okay so how you can say whether it's a pass
• 432:30 - 433:00 or a fail so pass means like they must be able to use the link and they must be able to add all the real time data and also but these are not dummy data only these are not real means it's not the production data these are like U test data and you have to like coordinate with the testing team and make sure that member IDs are valid in the uat region once they click on that URL right uat URL and start testing and that member ID all should be like available in the uat region so that coordination that you
• 433:00 - 433:30 have to do creating test members in U region and then making sure all the test data is available for example they need a email ID that dum email ID should be available for them to be tested so all kind of testing based upon the scenario that data should be available in the UT region otherwise they cannot test so it's not production data so always never give production realtime data to the uat members I mean the business owners you have to specifically create all the test data for them and either that depends
• 433:30 - 434:00 upon the team right whether you have to create all the test members or uh you have you have a testing team like the QA team they can uh uh create data for you and all so but this document you have to create okay how they going to log in how they going to test the um portal team for example like a lab report should be available so what kind of lab report should be there and what kind of wordings needs to be there and is it U according to their expectations so for example and and diagnostic image report
• 434:00 - 434:30 needs to be there that needs to be a dummy like um PDF needs to be attached there so that they will be like you cannot or if you have test um like documents like X-rays and CT scan reports or something like that that also you can attach but they need to be test not real time um xrays or CTS so first you have to like develop this test plan document and then you have to like make sure that what are the exact scenarios that they
• 434:30 - 435:00 have to test and you are giving them okay this is the plan and uh this is what you have to test and you are going to like get the sign of and all what's the email ID who needs to uh complete this and all you're giving the date and all and you're giving now how they will record it as pass or fail for that you have a Excel sheet so this is the Excel sheet okay so this I got it from uh smart sheet but you can create your own
• 435:00 - 435:30 Excel sheet also but if you are new you don't know how to create um you can always like download it from smart sheeet they have very different templates for this um testing and all for manual automation uat like for every testing they have that um like format so what you're going to do is what is the type of test you're going to do what's the priority and what's the test date and how like how they going to test in what environment they're going to test and uh you're going to like give them
• 435:30 - 436:00 like exactly steps okay so all this you can fill step one okay the user needs to as a new user um I must be able to register and
• 436:00 - 436:30 create a uh username and password okay once they do that the next scenario next scario is as a existing user I must be able to log in
• 436:30 - 437:00 and view the patient portal patient portals dashboard okay I must be able to view the dashboard okay and then [Music] um and the third one is once I'm I'm into the patient portal now as existing user
• 437:00 - 437:30 must be able to see my upcoming doctor appointments okay so like this like every scenario you have to list on all the scenarios when they're going to test expected results actual results expected is for example uh user and a password needs to be created so you have a
• 437:30 - 438:00 username and a password and you can also add screenshots if you want right expect the results like how it has to like I can show you how that screenshots would be okay so here like for example here um they have given like example like how that screenshot needs to be there right like this you can take screenshots so this one um I can put this link in the chat
• 438:00 - 438:30 that here they tell you what is functional testing how to write a test case um scenarios and then performance testing how to write and then security testing how to write and all like like what are the different um types of testing all this they have added here so maybe I can put it in the chat so you can take a look when you have time so uh yeah what you do is like what I'm trying to tell is like you create
• 438:30 - 439:00 everything and what they have to do is just like make sure they follow the steps okay step one this is what I have to do step two this is what I have to do and then if they they not seeing the ex expected results uh if they able to see the same then it's a pass okay and but if they're not able to see it's a fail and uh they're going to write notes why it's a fail okay unable to see the dashboard un able to view the
• 439:00 - 439:30 dashboard like this so all the scenarios what you're are going to end to end everything like you cannot test with them okay they have to do the testing U you cannot test them you cannot test by your sat you can test but uat business owner has to test and they have to provide the sign off okay they have to say whether it's a pass or a fail if it's a fail means that is called a defect so you have to again go to J ask them to raise a defect or you can also raise a defect in U in uh like um
• 439:30 - 440:00 for them and then like make sure that defect is fixed for example um this like um patient portal dashboard they're unable to view so only if they able to view other everything will be a pass if they unable to view then you that will be a defect they're raing a u defect in jira um so then you have to like assign that to the developer make sure like whatever is a problem that needs to be fixed again they will start testing so finally like once the all the testing is a pass only
• 440:00 - 440:30 then they going to provide the sign off okay until then they are never going to give you the sign off you should also not get the sign off so it's very important that uh you create all these documents for like your end to end testing and in the interview like there ask they like like AR is asking right what's the difference between functional business analyst and Technical business analyst technical business analyst means you have to know in and out technically like what is the API that we going to test
• 440:30 - 441:00 how to test like that and all I will tell you in detail but technical business analyst means everything about technically what is happening uh inside the application and you need to know um what kind of testing scenarios will be coming everything and there'll be no QA team you will be the QA you'll be the ba you will also be the QA and you will also like all technical documents you only you have to create so developer he will develop and he will do his his side of testing that that is called as unit
• 441:00 - 441:30 testing but other than that right you have to know what is API like what is soap API what are the two different types of API soap API rest API why we are using API instead of batch processing and uh you have to know at least one of if if you're going to use automat tools for testing uh then I have to know selenium selenium means that is Java based so that means in that case you need to know Java so uh functional business analyst in the sense they will know only domain knowledge skills domain knowledge means you know
• 441:30 - 442:00 Healthcare you know uh property and casuality and you know like banking like specific software you know to do but overall like you will not know other aspects like for example um like these are two technical right um selenium means you Java like highend Java you need to know you need to know a little bit of coding and Pega also little bit of like how Pega applications are being created how to test in Pega Salesforce also you need to know into when sales force what is happening those are Tech
• 442:00 - 442:30 technical Bas and you all you can always say a system analyst also technical system analyst and all but the pay for them is very high but um this is like you have to build the resume give me a second
• 442:30 - 443:00 so you have at least if you're not a if you're very very new to uh ba and and you're from a non IT background it's very hard for you to grasp all the concepts then my recommendation is like please go like take baby steps learn one by one okay first I'm learning basics of ba and then I'm learning um like for example see here what are things you have to do how to become an expert in business analy and how to make sure your resume is selected first you need to
• 443:00 - 443:30 learn the basics okay basics in the sense uh there are two methodologies we all know that is waterfall and agile and what kind of documentation is needed for both the methodologies if it's waterfall I'm going to put add in the resume I need to know how to create a BRD FD SRS documents if I'm going to add AEL kind of methodology in my resume which is very popular that's what they want you need to know how to create user stories what is a user what is the Epic what is a user Story how to write them what's the format of writing a user Story how
• 443:30 - 444:00 to um uh make sure that every user story has story points and basically all agile terminologies like Sprint planning Sprint retrospective Sprint review all the agile terminologies you need to know then you need to know like diagrams that is mandatory like even if you're waterfall or AEL either way you need to know how to draw diagrams Z and Confluence like I told you these are the tools that you have to learn especially if you're adding agile you need to add Zer and Confluence so this is all Basics apart from that if you're going to
• 444:00 - 444:30 become a technical ba or a system analyst then you need to know how to do this API testing so there are two type of testing called um um soap testing and rest testing I will just give you a highlight of what to do I make a separate video they very technical so I will do a separate video on how to do this API testing but you need to know like for example let me take a scenario real time scenario then you will understand
• 444:30 - 445:00 okay now siga this is the member portal of siga right so for anything the member has to login so but this is the front end now they want to submit a claim okay they have to log in okay they have to log in here and then they have to submit the claim right so when they click on this they'll be using all this is member
• 445:00 - 445:30 portal okay member portal means member is using this portal they have to uh click on that and uh they have to submit the claims okay but if do you think they are the same application they are not the same application member portal and claims will not be same application so let me say click on claims okay or maybe how to submit claims
• 445:30 - 446:00 okay manage claims and then view claims and submit a claim online and also you can play your uh I mean pay your claims okay so for that you have to activate
• 446:00 - 446:30 your account and then you need to submit a claim here they have said that you have something supplemental you can submit a claim Okay click on that okay now it's taking to a different link once you log in right this is not the application you're going to see that will be a separate application so you may think this is like only one application but member portal is is what is member is facing but on the back and right it is connected to different teams okay now let me take the
• 446:30 - 447:00 um so frontend member facing okay member portal is what like a public is seeing but as a technical be you need to understand that back and right from the member portal okay it will be connected to claims claims application from there it will be connected to authorization application and then from there it will be connected to uh appeals application
• 447:00 - 447:30 so everything will be a separate it team okay claims will be separate department and separate it support will be there authorization separate it team will be there appeal separate will be there and then um like for example pricing uh separate team will be there like this like different uh all the backend right different teams will be there case management how they will connect with each team is from member portal they'll
• 447:30 - 448:00 be calling the claims API or uh if the patient is clicking on submit claims right what will happen it's through the API API means it's kind of link so if I see here in soap testing right if you see you'll be able to for that you need to learn what is soap and how to test and all for now
• 448:00 - 448:30 just remember that from for any like soap or rest what we are doing is we are accessing the uh from for example see here we are giving we are giving a URL right so from the member portals URL from this URL there will be a link submit the claim if you click on that what actually is doing is it is going to the claims URL okay that by by access by using that API you are actually accessing the claim system and
• 448:30 - 449:00 you submitting or loading the data to the claims database so that is called as request so we are sending a request request like with valid member ID because already the uh member is already logging in through the member portal so he'll be a valid member so we have a valid member and then uh what he's doing is he's submitting so we'll be asking the questions once we uh he click on the form there will be a questions right what is this claim whether it's emergency claim what type of claim it is medical dental vision whatever what type
• 449:00 - 449:30 of claim it is and uh so we'll get all the details in that form once he clicks submit what will happen is it is going to the claims department through an API okay just in one click okay one member one click it is accessing through the um claims API and the data is loaded into the claims database in once the data is coming to the claims right then we do the validation what validation we are doing uh of course it will be valid member ID but anyway we have to like check check
• 449:30 - 450:00 with the membership system so membership system can be like facets or there are many members systems right like you can have to do the validation and then we have to write the validation okay our developer has to when we give that developer will be coding accordingly so when we get the members they have to like check whether we it's a valid member then we have to check for some kind of keyword okay emergency emergency word means it's SLA will be like within 2 hours to 4 hours so it has to go to
• 450:00 - 450:30 two or three qes okay Q in the sense if it's some word like emergency urgent those kind of keywords are there then the system has to pick that claim and it has to go to a different queue so the SLA will be like somewhere within 4 hours and also which Market okay it will be doing once we found out the member uh in membership system we'll identify which market right whether they're from New York or Florida depending on Market also the SL also will be changing so
• 450:30 - 451:00 accordingly our system has it has to do at least like four to five type of validation first check the member ID check which which uh Market it is then you have to check whether you have emergency words like very important key words if those words are there then we have to like make sure that that is going to a particular queue with because within that certain queue the claim has to be approved or it will it will have some timelines or if it doesn't have any kind of those kind of words then it will go into the normal queue uh and you will send back the um response stating that
• 451:00 - 451:30 claim is submitted so that request response will be immediate okay once the member submits the claim immediately we will give a response saying that your claims is submitted please login and view for status or progress something like that but this validation on will be secondary only immediately the member will get a response saying that your claim is submitted immediately that is like within a second or something they'll get the response and rest is even faster they'll be able to process because there are multiple members 1.5 million um members for one state um at
• 451:30 - 452:00 least like every day you will have at least like thousands of hits at least 10,000 hits you'll be having for that particular claim steam API it must be able to like perform and make sure nothing is uh there is no error and all so that's where this performance testing load testing all this testing is coming right so if if you are technical ba they are going to like ask you so many questions on okay have you really worked on any
• 452:00 - 452:30 kind of API testing and do you know how API works from one system to another system can you give me an example like what kind of uh testing we have done how what is soap why we are using only rest instead of soap what is the difference between soap and rest and tell me a example because you told you worked right can you please tell me so you have to be prepared to answer all these kind of questions and they can you can get embarrassed if you're on a surface level if you learn this and you put it add in your resume you make it really
• 452:30 - 453:00 embarrassed but if you want to become a technical ba and if you want to like build your resume and you don't want to become a vanilla ba then I would recommend this is not like rocket science anybody can learn you if you if you're able to learn English and if you're able to communicate in English anybody can learn soy but it will take time since you're not from the not from the technical background it will take time at least one or two weeks and someone has to really know so has to
• 453:00 - 453:30 teach you so I will probably make a video maybe next month or something on this because this will take at least four to five uh videos on like first I have to uh explain about what is soap what is rest difference between then how to test show you examples and all how to test and how you can add in your resume but you if you want to build your resume in a more technical way then you can add all this soap and uh rest also tabed for reporting so if you want to if they ask you like do you know reporting have you
• 453:30 - 454:00 created generated reports and all then you can add tblo and um apart from all this definitely you need to have domain knowledge either it's Healthcare or banking or it can be like property and casuality whatever it is like any that domain knowledge is very very very important functional business analyst only will know only like domain knowledge but technical business analyst will be like knowing like for example everything end to end testing everything they will need to know okay any any
• 454:00 - 454:30 doubts till now uh no just one question pra when we talk about testings uh basically as a business system analyst what testing scenarios we come across like what kind of testings we almost like in a generic we come across like if sometimes they may be API testing or may not be API testing yeah definitely not API testing but uh that ENT an application whatever
• 454:30 - 455:00 your Gathering requirements right that you need to test okay let me take an example of that open EMR okay okay so this is one an application that you have gathered requirements now you have the link okay testing link you
• 455:00 - 455:30 have and you need to test like all these scenarios as an admin you need to test as a physician you need to test as a clinician you need to test accountant you need to test receptionist you need to test also a patient portal right that also you need to test they have given two different links for portal they have given different uh links and for other credentials they given different links so you have to make sure that the in sat if they want you to test once the developer has completed development they're moving the code to QA he will
• 455:30 - 456:00 tell you the code is in QA now please start testing and then he'll give the links also so you have to like make sure that you open and then um do all the testing like he'll give you all this details so all this username password he will give you and so what you have to do is you have to um log in and then because you are the one who gathered requirements so you should know how to test and uh what is the business owners requirements right for patient portal how it has to look for clinicians how it
• 456:00 - 456:30 has to look and accountant means what it has to look and because you already have the BRD all the user stories and all that so you have to uh find out all the scenarios you will miss the scenarios also like I said here so like this is the document so write all the use cases test scenarios and then like make sure you test in sit if you're not getting results then you put as a fail and send back uh create a defect in jira and ask the developer to fix it in this is an sit and in sit everything is good then
• 456:30 - 457:00 only you're asking the um uh business owner to test in U you got the point okay so basically after the development is done uh print What in in within the Sprint after the development we go for the sit we check it and then we get back if there is an isue right you raise anyx and he has to fix it and then
• 457:00 - 457:30 I'm sorry yeah so when you in s if you raise a defect right so he will again fix it in sit again you have to test in sat only if everything all the scenarios are passed in sat the code will go to U okay after the end of the Sprint only right this also us to happen within that three weeks Sprint 3 weeks Sprint to okay yeah okay so if you take a user story that user story needs to be developed tested and uat pass everything within that three weeks three
• 457:30 - 458:00 weeks and uh so that's why like that's why we taking very small pieces of user stories okay whenever you are not able to test a user story then they have to split that it's a very big functionality but like like for example here we cannot test the patient portal in one Sprint here or I need to have two to three developers to test every functionality or the Sprint needs to be at least like four weeks Sprint or something to test everything in two weeks Sprint I cannot complete all the testing right in two week he cannot develop
• 458:00 - 458:30 everything and I cannot test everything that is not reasonable so for this functionality for this kind of testing at least it will take four weeks Sprint to test and then if there is any bugs again it's going to like uh we are going to expand right we're going to like make sure for example in a particular Sprint within four weeks you are not able to complete UA then you need to postpone that and then that's why during estimation is very very crucial like you need to know if for one users Story how long it will take to like test I always
• 458:30 - 459:00 give extra points don't give like if it is you think this is a five pointer please give it as eight pointer or if you think this is a three-pointer please give it as a five pointer because we never know what kind of bugs you will get and you need time to fix that okay so yes any other questions any doubt uh regarding like
• 459:00 - 459:30 what is Ba's role in testing okay so um my um my recommendation is like for everyone who wants to become a ba um please take things slowly and this all can be very overwhelming for you like when I tell like you have to learn this this this you'll be like oh my God there's too much to learn but you need to understand you are not learn you're not learning coding okay you're not learning this is not coding at all
• 459:30 - 460:00 except when you are if you're going to go for selenium testing then only then you need to learn about this Java and all otherwise you're not learning any kind of coding and uh you will be able to learn and even though this may look like simple in reality we are we are finding it very hard to get a technical business analyst because not everybody knows what other in in public right in general public like academies what they're teaching is like they are teaching only
• 460:00 - 460:30 the basics of ba what is ba what is waterfall how to create BR that's all to that level only in the market people are teaching but they are not teaching exactly how to do these kind of testing or how to in a project from end to end what a B has to test and all and where it's very easily we in the interview we'll able to figure out if we are getting trained in like 10 days or 15 days we can easily like figure it out um they don't have like that depth of knowledge in anything so don't be
• 460:30 - 461:00 shallow if you take anything you can become if you take Pega please be please learn Pega properly if you are going to become a Salesforce B please learn Salesforce properly and uh like uh after some after like after sometime right your mind will capture it will be able to identify okay this is how we have to test so please take multiple case studies and you have to like uh write documents and then this testing also there are like a number of free tools um in Google so please do your research and
• 461:00 - 461:30 start learning the concepts one by one and uh otherwise it's very hard for your resum to get picked up it's very competitive even in India too so just by writing like I know waterall agile your resume is not going to pick up pick up right so um for very if you want to enter into Fortune 400 companies or maybe product based especially product based like Amazon and um Amazon definitely they want you to know all
• 461:30 - 462:00 this testing just play V be they can hire any American okay so um please learn one of these languages like pagos a force and then um one of the testing okay not so so and one more thing if they ask you do you know where soap rest don't tell that um in one project just write soap and another project write rest they'll be asking so you had two apis like why why do you have soap and rest so you may say that
• 462:00 - 462:30 soap was very slow then we build when we then we we upgrade it to rest but if you don't have enough knowledge about API U please choose just only one soap is easy then rest rest is actually very faster uh so just learn the basics and then um add just one in your resume or maybe in one project add soap and in another project you can add rest don't add both in the same project if you going add in the same project they may ask you why why did you change from soap to R so you need to maybe give um scenarios and then
• 462:30 - 463:00 tell why you changed or maybe give some production incidents and because of soap it was unable to um like take so many hits we have performance issues and so we wanted to be a little faster that's why we upgraded to rest and he's going to ask you so many questions so be careful when you're adding these kind of testing okay that's it for me U for today and uh so for like next half an hour and for tomorrow session I'm just like going to uh like interact with you and then
• 463:00 - 463:30 tell you like give guidance on like if you have any questions you want to discuss your resume or what do you want to do like if you have any questions for me you can ask so tomorrow will be the last class but uh the next half an hour and tomorrow is like 1 hour it's going to be just interaction you have any questions you can ask PR I have to want to talk to you actually s with respect to uh some user stories if you can have with respect to PNC Insurance property and casual yeah yeah
• 463:30 - 464:00 so you have interview tomorrow right yes you want to do a mockup now no I'm not ready you're not ready tomorrow is your interview you have to be ready I mean I can I can talk about but the thing is um I'm like still making myself ready for tomorrow's point of view like what kind of US stories I can pitch in or if I say I have some experience that I mean you know so you can say claims claims uh this property let me take up the
• 464:00 - 464:30 e UI okay I will edit this in uh YouTube okay this will not be in YouTube I I did this so this is a a is property and casuality okay property and casuality means they do like home insurance and uh they do auto insurance if you see their uh if you see their um um portal you'll
• 464:30 - 465:00 be able to see that um there are many kind of worldwide so let me so they are they are in America they are in Europe they are in Asia Pacific they are in Middle East also in Africa so they support like 30 to 40 countries around the globe and everywhere it is called as EIG only and they are one of the leading property and casuality um providers I mean insurance company okay so what so this is a front end and there is a direct link Pega
• 465:00 - 465:30 application here if you click on claims okay and then if you want to submit claims or um so if we want to log in okay submit a claim reporter claim something if you want to log in right uh this is peega hi do you see the dashboard it's different yeah this is Pega UI okay and uh so you give the username and password again and you log in and it's directly taking to Pega so this is different okay
• 465:30 - 466:00 this website web portal is different but when you click on it will go to for example I click here this is member portal just by seeing the uh UI you will know so a login is member portal but if it's claims right it's going to report a claim or anything related to claims is going to Pega Pega application will be front and be like this only very simple UI will be there so what it's doing is once you log in it will ask you for a question and that question question right will be like what is the claim for
• 466:00 - 466:30 example that is an accident this is Property and Casualty right so uh maybe you have a car accident and the glass was broken take this scenario okay so you can say that you work for claims and that interaction is like from the member portal directly it will hit the Pega service and then you um in Pega modules the you can see that I was working as a ba so my responsibility is like uh for uh auto insurance um claim processing or um any one module you can take either
• 466:30 - 467:00 Auto or home whatever it is you can take this one module and then you can say uh I was working for claims and uh once the member they log to Pega they'll be able to see a survey like or maybe a form like claims and they should be able to add so you are going to pick up the words something like emergent Glass Broken um because auto insurance for example the car was there in the parking lot uh the glass was broken uh it in us it is uh it is legal to to submit that
• 467:00 - 467:30 claim and we have to cover the have to cover if a glass is broken even if it's in the parking lot but they are supporting other countries too so you can say I hi everyone in today's video we are going to learn about top 25 aile business analyst interview questions and answers let's get started so the very first question they are
• 467:30 - 468:00 going to ask you is what are the roles and responsibilities of an agile business analyst can you please explain with examples so there are about like um six to seven roles and responsibilities of an Azel business analyst for any project the first is you need to analyze the current business processes for example like um what is the like currently how is that system
• 468:00 - 468:30 working what is the data flow and uh why we need an enhancement or if this is like a completely like uh manual project and now they want to automate things so you need to understand currently what is the uh process that the business owners are following and why we need ex enhancement or if there is some kind of like automation already happened and this is a uh enhancement project so you need to understand first of all the
• 468:30 - 469:00 current data flow and in Future How It needs to be enhanced and uh the second responsibility is once you understand the data flow and how the um currently how the project is working now you need to identify improvements and you need to propose some solutions for example so for example like um you have uh I'm going to uh show you with an example so let me take a project so
• 469:00 - 469:30 um okay so for example we have a WhatsApp project okay so let's say that um WhatsApp the application mobile application whatever we are using it is a current project and they have some existing functionalities but they want to improve and they want to make we add some new functionalities so if you are
• 469:30 - 470:00 working as a agile business analyst for WhatsApp uh first what you have to do is you need to understand what are the existing functionalities of that application so you're able to send messages you're able to send pictures you're able to send uh voice notes and uh you able to like or comment on um others messages and also you are able to view like what is the history of the um conversation and everything okay so that is the existing functionality suppose if
• 470:00 - 470:30 there is a requirement like for example we want to like delete like you you send a message and within like a few seconds or something maybe within 50 seconds or maybe 30 seconds you can delete the conversation so that is uh an enhancement now you need to understand that this can be area of improvement right so there are some existing functionalities but you can always like um Identify some new key areas where they change changes needs to be done and
• 470:30 - 471:00 uh it can be improved so I'm just giving you an example so that you can understand so WhatsApp is a uh mobile application so they have some existing functionalities and if they want to you can identify what what are the new functionalities that we can improve in that mobile application and you can also propose the solutions and uh the third one is you need to analyze the data so for example you need to identify what are the existing Trends and patterns and like for example last one month how that
• 471:00 - 471:30 application was used and how many bugs were uh identified in production and um like how many times the system was down because of a particular functionality and uh how many how many times people were uninstalling that application and what is the reason is it because of the bugs found or because of the privacy issues so some like many people like they don't want to use WhatsApp right they uninstall and they don't want to continue use that mobile application so you can always take that Trend and you
• 471:30 - 472:00 can also identify uh what is existing data for the past month and you need to analyze the data so once you analyze the data now you are going to um create user stories task and defects so if you are a normal business analyst right if you're not following AEL methodology then you will be like creating brds and that is like traditional way of gathering requirements and developing the application but for agile business analyst list very very important um like
• 472:00 - 472:30 rule is like you have to create this user stories task and defects so for example this jira software that whatever uh I'm showing in the screen this is one of the primary like tools that you'll be using in your work so you need to create for example if I click on create you need to create all this issue types for example it can be a story it can be a task or it can be an epic or it can be a bug so this will be your primary roles and responsibility
• 472:30 - 473:00 of creating user stories creating bugs bugs means defects and you have to create task so if in the interview they ask you like uh what was your primary responsibility you have to tell like for example I was responsible for creating these user stories these task and these defects so this will be your primary responsibility of an a if you are in an AEL uh project this will be your primary respons ibility okay and the next is
• 473:00 - 473:30 negotiation and stakeholder management so what is negotiation and stakeholder management so you will have different stakeholders right for example you will have business owners so who's a stakeholder anybody involving in the project is called a stakeholders it can be business owners it can be developers or you are dealing with multiple teams internal teams external vendors so you need to have proper stakeholder management skills if you are a lead agile business analyst you need to know
• 473:30 - 474:00 how to like a lead a call how to gather requirements with various stakeholders how to make sure that there are no conflicts between various teams how to make sure that if there is a dependency on other teams uh we need to make sure that the dependency is completed right before we start the project if you have some dependency on external vendors we need to clearly like understand how long it will take for them to create that uh dependency product and give it to us so negotiation and stakeholder management
• 474:00 - 474:30 is crucial the next one is resolving conflicts so in every project there will always be conflicts you need to understand the reason for conflicts and why uh it is occurring and you have to take necessary steps so escalation is not the um like a proper way right so you can escalate but how long you'll be escalating and how many times you'll be escalating if you have some leading capacity you you need to like resolve the conflicts internally because always escalating to your manager is not an ideal solution if
• 474:30 - 475:00 you need to be capable of resolving conflicts but within yourself within your team or if you have any conflicts with an external team with your developers or with their Engineers you need to have the capacity to resolve conflicts and the last one is achieving business goals so whatever may be the project at end of the day we need to make sure all the business goals and needs are achieved and we have to make sure that satisfaction is achieved among all parties so meeting objectives and uh achieving
• 475:00 - 475:30 business goals is the uh like the final responsibility of an AEL business analyst so the next question is what is aile Manifesto and explain in detail so I'm in this Atlas uh atashian software page so where they clearly told about what is AEL Manifesto and what are the principles for uh for following AEL methodology so there are about like 12
• 475:30 - 476:00 principles let's go through that in detail so what they're saying what are the principles be behind agile is the first priority is to satisfy customer in the like by how by early and continuous delivery of a software so it's a valuable software so uh we need to make sure that we are developing of a software very quickly and we are continuously delivering our valuable
• 476:00 - 476:30 software okay that's the first principle the second principle is whenever we are having changing in the requirements even in the very last stage of development we are able to make that change and we are going to make sure that change is done okay and also we need to make sure that in a very very shter time scale for example in a couple of weeks to couple of months we have some kind of working software so very very quickly we are able to develop the
• 476:30 - 477:00 software tested and we are going to make sure that uh software is available in production also business people and developers must work together daily throughout the project so means like every day you'll be having uh requirement Gathering calls every day you're going to have status meetings every day you're going to have um like a Sprint planning meetings and all that so you're going to make sure you're going to closely work with the business people
• 477:00 - 477:30 so that whatever software that we are developing is going to be like satisfying right at the end of the day the business owners needs to be satisfied so that we're going to clearly communicate on what are the status of the development of a software where how are we progressing and we're going to make sure that every feature according to their expectation is achieved throughout the development of the software so build projects around motivated IND individuals give them the environment and support
• 477:30 - 478:00 they need and trust them to get the job done so we're going to make sure that since like this is a team effort so if one individual is motivated we are not going then product is not not going to be great so everybody in the team who is developing the software had to has to have this agile U mindset for example this will be like a very very quick way of developing the software right so within like two weeks 3 weeks four weeks the business owners want to see the
• 478:00 - 478:30 final product so uh it there can be pressure during the development or during testing or during uat testing you can find all kinds of pressures but we should always have that mindset of this is an agile project things are going to be very quick and uh it's not like waterfall Weare it's going to take months to create a software so here everything is going to be measurable everything is going to be um quick and um and buiness owners are going to track our all our user stories uh they're
• 478:30 - 479:00 going to see our like progress in the user stories they're going to ask us so many questions regard the status of the user stories so we need to have that motivation like every individual should be like motivated so that we can deliver the software quickly to the business owners and the most and effective way of uh conveying any information and also within the development team is face to face so this is all before covid right so before covid we used to have that Sprint planning meetings or this uh Pi
• 479:00 - 479:30 meetings Sprint retrospective in the office where everybody will come and like we have to sit together and discuss and all that every user story on the jira board and it'll be like fun having those kind of meetings but after uh covid right it is all like virtual now and most of the companies are following hybrid um model of like you can work from home as well as if you want you can go to office so this is being reduced now but earlier all the Sprint meeting will be uh will be actually face to face
• 479:30 - 480:00 so working software is the primary measure of a progress so they don't care about like the documentation part so you create all the stories everything is documented fine that's good but finally what they want is a working software and also the agile processes right like they they promote like development sustainable development means you are going to like like deliver product in like a constant Pace okay so the developers the
• 480:00 - 480:30 testers also the business owners you have to like work with regular intervals and you like constant attention is needed uh you have to like monitor developers and testers like constantly so that you're actually having some kind of control on over the software right because you cannot be like waiting for months and then finally if you see the software you are not happy with that so what they're trying to say is like constant attention and communication within the technical team to so that's what they're saying so continuous
• 480:30 - 481:00 attention to technical excellence and uh good design enhances agility agility means constantly the requirements may be changing but uh we need to make sure our development team is like accustomed to those kind of changes and we are going to make sure that is achieved so finally the goal is like we are going to have a working software and the best architectures requirements and Designs emerge from self-organizing teams so this is one thing so you may be working with multiple teams and you are like why
• 481:00 - 481:30 should I um bug that team okay my work is done so I should keep quiet so that's not a good way of like uh working in a project right if even though if your work is done your team's work is down you need to follow up with if you have a dependency with other teams or if you are having a dependency with any business owners you need to follow up on them okay self organizing the team the sense you need to have that motivation of like uh working with other teams or you need to like in initiating a
• 481:30 - 482:00 conversation or following up with them if even if they are not progressing you need to have that follow up like what is the status of user stories and all that okay so that is self-organizing teams um at regular intervals the team reflects on how to become more effective then tunes and adjust Its Behavior accordingly so agile is like a very fast way of like doing things okay so earlier in waterfall method you will take months to create a BRD you will take months to like write all the like designing and
• 482:00 - 482:30 giving the requirements to the developers again for testing is going to take like one or two months finally when the product is there the business owners are like I didn't this is not what I expected and they're going to be like it will take to to see the final product right it's going to take months for them but in aile it's not like that so we have something called Sprint okay so it can be 2 weeks 3 weeks within 3 weeks they want some kind of working product within two weeks they want something they want to see the end product so this is a very fast way of developing
• 482:30 - 483:00 software and U in most of the companies they want an working software over documentation so what is aile Manifesto these are the principles individuals individuals and interactions over processes and tools and working software over documentation customer collaboration over contract negotiation responding to a change over following up a plan so that's what they're saying you have to be like quick you have to be
• 483:00 - 483:30 like don't show that like the chalking attitude of like no I have we already have a plan now you're asking us to change requirements can we do that so the the more agile is like the more flexible we are in developing a product or a software and the working software is like takes over anything okay so they are not too much bothered about all these brds fds or all this like all this documentation thing okay all they want is a working software customers collaboration all this like contract and
• 483:30 - 484:00 all they not bothered so they always say that um customer satisfaction or customers collaboration and the final end product of a like a properly working software uh is the primary goal in agile man in agile projects okay so you have to keep in mind that don't be shocked like the business owners can be constantly changing requirements and you need to have that mindset of okay that's fine this is an agile project and we are going to take their uh request into consideration and we're going to like
• 484:00 - 484:30 make those changes okay so if you're working in aile project that will be big difference in waterfall it's all St steady and you're going to have some time processing all the new requirements and everything but in AEL it's not like that within 2 weeks there could be a change within 3 weeks there could be a change the final final product can be completely like different and U when compared to the initial very first call whatever you're having with the business owners so you need to have that uh mindset for adapting this constantly changing the requirements
• 484:30 - 485:00 okay so the next question is what is Scrum and what are the scrum values so scrum is nothing but it's a framework under Azel methodology so uh there are like different kinds of Frameworks under agile when we say agile you have scrum scrum framework you have Comin and uh you have like like a hybrid model as well so but scrum is primarily a
• 485:00 - 485:30 framework like majority majority of the fortune haunted companies they use this framework so it's nothing but they have a set of values and principles and practices so we are going to understand what is Scrum and what are the ceremonies and practices inside scrum framework so the first thing is like they're going to ask what is the difference between scrum and agile right agile is nothing but it's a methodology it's a overall methodology under agile
• 485:30 - 486:00 you can have multiple Frameworks like scrum and Coman and like Hybrid models and all that but specifically for scrum we need to understand that if if your project is having scrum framework definitely there will be a scrum team so that team we will be having a scrum Master we will be having a product owner and also we will be having developers and testers and um business analyst so we will definitely have a scrum team so
• 486:00 - 486:30 the members of the scrum team definitely uh there will be a scrum Master that's a big difference between scrum and other Frameworks okay so um under scrum framework definitely there will be a scrum team and that scrum team will be of uh product owners scrum master and a development team so under development team you will be having developers testers and also designers and also business analyst so this is a crew okay
• 486:30 - 487:00 this is the members of a scrum team that's a very big difference between scrum framework and other framework also under uh scrum framework there are like certain values that we need to follow so that is those are called as scrum values so what are scrum values in the sense for example there are about um five different types of scrum value so one is commitment second one is courage third one is focus fourth one is openness and fifth
• 487:00 - 487:30 one is respect so these are the five different scrum values it's a very very very important interview question so the interview is going to like um there by asking this question they going to understand whether you really know about scrum okay what is Scrum team how many people are there in scrum tap what is this framework what are the core scrum values so you have to say these are the five values first of all what is Commitment if you are under aile
• 487:30 - 488:00 methodology and if your uh team is under uh scrum team and you are one of the member of a scrum team what is like the commitment you are having towards the um user stories that you are developing or the work that you're doing you can be a business analyst you can be a developer you can be a tester but the commitment overall commitment is like you have to make sure that uh there is working work in progress so that's why we have daily standup meetings okay whatever user
• 488:00 - 488:30 stories that you are creating or whatever task that is assigned to you or as a agile team itself you have to make sure that the entire team is committed and there should be frequent communication between all your development teams scrum master and product owner the second one is courage so you should be brave enough to question the status of other user stories also for example you might have completed your user stories but the developers work was not completed or the testers Works may not be completed in
• 488:30 - 489:00 the daily standup call you can always ask them like for example what is the status do you have any delays do you have any roadblocks should you want I mean do you want me to schedule a call with the other teams do you want me to schedule a call with the business owners so like this you need to have a courage to ask questions between like you should not be like shy and you have to keep quiet you you you should not be like okay I have done my part now it is about like developers headache to do his work or not so that's not the a value right the value is you should have courage to
• 489:00 - 489:30 ask questions between your teams also also raise a question if if suppose like other team is having some dependency and they not finishing their work you need to uh ask them also the questions like why there is a delay and is there any roadblock or do you have any questions for business owners like that you need to have courage to ask the third one is focus so what is the overall Focus you have to complete the work in that particular span of time so Sprint means like in scrum we say Sprint means it can
• 489:30 - 490:00 be two weeks it can be 3 weeks it can be four weeks time span within that time you have to like make sure that software is being developed right so Focus the overall focus of the scrum teams is like to make sure that your work your task or your um commitment towards for that particular Sprint is like completed so focus is always to make sure that you have some working software and your work is completed and the fourth one is openness so in the
• 490:00 - 490:30 daily standup meeting you definitely have to ask what work did I do yesterday what am I working today or there are any issues that is blocking my work and you need to identify blockers and you have to make sure that you like uh share it with other engineers and other testers or also scrum Master to make sure that you're progressing on your work the fifth one is respect since because we have a short time period and you like collaborating with multiple team members and also multiple departments and also
• 490:30 - 491:00 multiple vendors so you may have like so many conflicts and you may be like uh at some point of time you may get frustrated also because of this coordination you always have to make sure this is a professional environment you have to maintain respect and always ask questions in a more professional manner rather than being rude okay so these are the uh five different values of scrum so question number four is what is a
• 491:00 - 491:30 user story and how to write a user story so user story is an informal General explanation of the of a software feature okay so for example the tool that we are going to use to write a user story is called jira software so it's a very common tool that is being used in the industry so when we when you have an access to jira software so when you get a job they will will give you the access right for this software once you get that and once you
• 491:30 - 492:00 start um Gathering requirements from the business owners now you have to create a user story okay so we go here click on Create and then in the issue types it comes as it story so story is nothing but user story and usually the format of this is as a like like I told in this slide okay so as a I so that so as the end user I want
• 492:00 - 492:30 to log in so that I can see my account page as a um new user I want to get access to my bank account page or as existing user I want to update my um personal information in the uh bank account page so like this you'll always like write user stories as if you are the end user so user story is nothing but it is written from the perspective
• 492:30 - 493:00 of a end user or a customer so so instructions will be like as a I want to s that okay so let me give you an example so if you want to say that um you're creating uh okay so you're creating uh a login page okay so you can say that you are new customer now you want to get access to your account what you say as
• 493:00 - 493:30 a new customer I want to get access to the member portal so that I can update my personal information okay so always a user story starts from the customer's View and you
• 493:30 - 494:00 will be always saying what the customer want to do and why they want to do okay that is the user story so once you create that then you put like uh all the description like detailly like for example how where what is the member portal link how the first page should be what is in from login page right if they don't have an account how to create an account how to register and create an account all this detail you will add in the description but in the summary the headline it will be always be like oneliner like this as a new customer I
• 494:00 - 494:30 want to s that so this is a standard like the way of writing a user story uh and in some companies like um Microsoft and all that they will ask you to they'll give you examples and they will ask you to write a user story so you always be prepared don't don't always like answer in a very generic format answer in a format that uh how they want to like they want to see it like for example they give you an example then you have to like write they may give you a case study and then they will be like
• 494:30 - 495:00 can you write a user story for this so for that you need to know this is the format as I want so that okay you can take any examples from your resume like the existing examples that whatever um uh you have or if you don't have experience I have given a couple of case studies in my YouTube channel you can go and watch that from that you can grab uh the user stories and you can tell that too so that's how we write so this is a format as a I want so that okay and in
• 495:00 - 495:30 the description you can put it detailly but this is how you create a user story once it is created it will go to the backlog okay it will be in the backlog if you see in the backlog you'll be able to see it in the backlock okay okay now the next question is how work use the stories epics and task different so from the previous
• 495:30 - 496:00 slide like I have told like once you have access to zero software you'll be having like many types of issues okay so you'll be having stories you will have task you will have epics and you'll have bugs there are four different types of uh like issue types we say it as in jira like in agile we say it as issue types so what is the difference between all this four that's a question that's the interview question so user story is are nothing but they are simple explanations of the business requirements but we are
• 496:00 - 496:30 writing from the end user perspective okay we are always writing like in very simple terms in one lines we writing the summary for the user Stories the business requirements is always very straightforward and simple anybody who's reading the user story is able to understand it that simple it is what is epic epic is nothing but usually like a high level high level uh of all the user stories under epic you can have so many user stories so I'm going to give you an example so if you want to
• 496:30 - 497:00 create an epic like okay for example automation of um like I have already given automation of check so this is a project okay so we are going to uh what is this project manually nowadays we are going to the bank and we are going to um give the check and process it right but you can do it from home itself so if you have a check you can just scan through the mobile application and then you can you are able to process that check so if if that is the project
• 497:00 - 497:30 the very very high level requirement right we are writing it as epic under one Epic we will have multiple user stories okay so epic is nothing but it's a very very high level requirement and it is actually usually very large and complex under one Epic you can have multiple user stories so the user stories can be like um how to make sure that uh check is getting scanned through mobile application through uh like barcode or uh how it is able to pull
• 497:30 - 498:00 extract all the members information like for example first name last name account number and how it is able to identify um actual amount and how it is able to identify whether is the correct check it is not a duplicate of an existing check so all these validations that uh mobile application has to do right so everything will have a separate user story so all that can be us as stories but epic is nothing but a higher level requirement okay overall like overall in the project that you have a very big requirement that is called a epic and
• 498:00 - 498:30 what are task task are nothing but it is used to break down user stories so it is the smallest unit in the scrum framework and uh it takes about like only one or two people or within like 3 to four hours maximum to do to finish a task okay so when we create task like you can always create it like um creating a BRD okay creating a
• 498:30 - 499:00 BRD or maybe creating a mapping document or it can be creating a uat test plan so all the small small task okay so this will not require like like for example 8 hours or more than that of work right so this is like for example Le you need to create a u test plan this can be done within 4 hours so all these
• 499:00 - 499:30 like small kind of work that needs that needs that can be done uh can be identified as task so then what is the difference between uh now task and story story is like more than 8 hours I would say uh if you have something to work more than 8 hours then that is a story and if it is like less than 8 hours and you can finish it within like 4 hours 3 hours or 5 hours then I would identify it as task and also bug is nothing but it is defects okay so something you are
• 499:30 - 500:00 doing testing you identifying some kind of defects that will be identified as bug epic is nothing but higher level requirements so these are the four different types of issue issues in agile methodology so they may ask you to give you examples so you have to take one case study and then you have to give them like separate and uh uh instead of telling it very theoretically you can always take like one example and then you can say this is an aepic and this is a user story and this is a task and this
• 500:00 - 500:30 is how we identify the next question is what is a Sprint and how long is each Sprint Sprint is nothing but the amount of time required for a developer and tester and also a business analyst to complete your work so for example basically in uh in Sprint right there are like many types so you can have a two week Sprint 3 weeks Sprint four weeks Sprint so in
• 500:30 - 501:00 two weeks for example if you have a two weeks Sprint you're going to have 10 working days of course if there are no holidays in 3 weeks Sprint you're going to have 15 working days and in 4 weeks Sprint you're going to have 20 working days in case you don't have any holidays right so mostly uh Sprints are always like 2 weeks in the sense it is 10
• 501:00 - 501:30 working days 3 weeks in the sense it's 15 working days and 4 week is nothing but it's 20 working days so within this time if any user story that you are picking up in that particular Sprint for example your project is having only a two week Sprint means in the 10 days whatever user stories that you are picking or your developers or testers they are picking they have to complete within that 10 days okay so your timeline to finish a uses story is only 10 days and if your team is having 3 weeks Sprints they have to complete all
• 501:30 - 502:00 their user stories and task and all their work within like 15 working days and if it is a 4 we Sprint you're going to have 20 working days so when you create user stories for example where you creating all sorts of like uh in the backlog you can say that I have an epic I have a bug I have a task you create all these user stories but you will never know like how long it will take for an user story will get completed that's why why we have something called story points so when I open here uh there is
• 502:00 - 502:30 something called story points here to finish this like how long it is going to take what are the total number of points it is going to take so depending upon the points you can always like identify whether it's a one pointer user story two pointers thre pointer so for example here it has thre pointer user story and this one can be um uh like a two-pointer you have to discuss that with developer and you have to identify what are the story points so
• 502:30 - 503:00 one pointer means it's going to take less time two pointer means um it is going to take a little bit more thre pointer means a little more five pointer is like it is a complex eight pointer is like too much complex that story is going to take a lot of time so what is a Sprint whatever user story that you are taking for example you can take two uh two pointer stories you are able to complete that or you can take one eight pointer story if you're able to complete
• 503:00 - 503:30 that so just by seeing the user story right for example this user story this one can be as complex like an eight pointer okay so if it is an eight pointer user story I can take only only this one story in my particular Sprint and finish it so don't rely on like the number of user story it's not like you take 10 user stories means you are like you can it can be done in two ways no it is about the effort for every user story for some user stories it can take only one points for some user story it can
• 503:30 - 504:00 take two points for some user stories Can it can take three points so you have to discuss with your development team and then make sure like every story like what is a uh story point for every user story accordingly you need to choose your user stories within that particular days and finish it so that will be done in Sprint planning session so that uh during Sprint planning right uh yourself your developers and also testers and your product owner your scrum Master everybody will sit together they will
• 504:00 - 504:30 review the backlog and depending upon like the story points uh we can take the user stor so they are not assigning you you are going to pick up the user stories which you whichever has the highest priority and you are going to make sure that is done in the next Sprint so this is about uh Sprint and how long is each Sprint the next question is what is the difference between Sprint backlog and product backlog so as I've told you here Sprint backlog means like for
• 504:30 - 505:00 example whatever you create here it will be always in the backlog so this is called as product backlog so this is like for example you create 10 user stories and your colleague is creating 10 and another developer is getting 10 and the tester is they are creating their user stories so they're going to have as a product backlog as a whole team you're going to have 200 or 300 user stories right but depending upon your Sprint timeline for example you have a 4 week Sprint okay you have 20 days working days for the next Sprint so
• 505:00 - 505:30 in that case you can choose only limited because you have limited capacity with your team someone is going on vacation or someone is sick they are not able to come for next 10 days so you have limited capacity you have only two business analyst two developers and two testers So within that capacity like how many user stories you can pick and you can you'll be able to finish in that particular Sprint so the number of user stories that you will be like finishing in that particular Sprint is called as Sprint backlog product backlog is
• 505:30 - 506:00 nothing but as a whole like how many user stories you are having in the uh like complete in your team like totally how many user stories are there in the backlog that is product backlog so there is a difference between Sprint backlog and a product backlog okay so you can always say that like for example there here you can see this is Sprint okay that Sprint is there and we can always this is the existing backlog like all the user stories are there and if you want to push the user stories from here
• 506:00 - 506:30 to your current Sprint you can always drag and drop okay so if you're able to drag and drop here and you can always move this your current Sprint so you can make it as in progress okay so that's the difference between uh Sprint backlog and product backlog so Sprint backlog is nothing but in your current Sprint how much uh you are user stories
• 506:30 - 507:00 you are having product backlog is like overall in the team like how many user stories you are having so when they ask you in the interview do you know about product backlog yes of course we know product backlog is nothing but it's the list of user stories or epic task which is created by our entire team whereas Sprint backlog is nothing but the user stories that we choose to complete within that particular amount of time that is Sprint
• 507:00 - 507:30 backlog and the next question is what are daily standups can you explain what happens in a daily standup meeting so daily standup meeting is nothing but a discussion that happens every day so every day morning or in the afternoon sometime regularly we are going to have a daily status meeting you can always say standup meetings or status meetings so in this meetings everyone from team has to join so developers testers business analyst scrum Master product
• 507:30 - 508:00 owner everybody will join manager may or may not join sometimes the manager joins but usually they don't join so what we do in this uh standup meeting or status meeting is nothing but we are going to track everybody's work so once we assign user stories to um our team every day we're going to track the status of this team so what whether it was done or whether it's in still in progress or you are it to start and if you have not not started why why you didn't start and if it's in progress you have some blocker
• 508:00 - 508:30 or you're dependent on some other uh Team or you're dependent on some other developer or tester then you can always say that I'm dependent on this tester I'm just waiting for the feedback so everyday status call is nothing but to actually like track the status of your user stories so if you have any blockers you can say there or if you want to coordinate with your team members you can say there or if you have any dependency on other teams you can always put it there and also discuss with your team members of course you can always like Ping them uh you can always
• 508:30 - 509:00 email them and you can always connect with them privately also but this is like you're telling the entire team what is happening with your user story so that everybody's aware of the status of your user stories and as a team as a scrum team like how you are able to achieve the completion of your user stories within that particular span of time so that is that is the reason for daily standup meetings and the next question is what is Sprint
• 509:00 - 509:30 planning so this is very very very important Sprint planning like I've already told you once you've created and your team have created all the user stories and uh you ready for the next Sprint for example the next Sprint is next Monday the upcoming Monday now this Friday you're going to have a Sprint planning call where all your user stories like from the entire team right they're going to we are going to go through all the user stories and we're going to pick up only certain user stories for the upcoming Sprint since because you created like 200 or 300 user
• 509:30 - 510:00 stories doesn't mean everything has to be picked in the upcoming Sprint okay so Sprint is like very short timeline it can be 2 weeks 3 weeks or 4 weeks depending upon your team it will change and depending upon the company also it is going to change okay so suppose you have a 4-we Sprint your team is following a 4-we Sprint and you're having an upcoming Sprint on like from the next Monday Friday you are going to have the Sprint planning call the product owner is going to go through every user story and they're going to
• 510:00 - 510:30 ask you what are the story points and um what is which are the priorities and which business owner has that highest priority and how many capacity we have like as a team like who is going on PTO how many holidays we have and we going to calculate all that when you're going to pick up the user stories that is called as Sprint planning call so basically we are deciding upon like uh how much work can be done during the next Sprint and and um how much what is the total capacity for our team okay how many
• 510:30 - 511:00 people are on holidays or how many people are like do we have any like holidays for us uh like you'll have some national holidays right so whether we as a team we are having any holidays or someone is going on PTU or someone is sick so we have to plan accordingly depending upon our capacity and we are going to choose our uh user stories for our next Sprint the next question is what is Sprint retrospective Sprint retrospective is nothing but it's a review meeting that is like done at the
• 511:00 - 511:30 end of each Sprint so like from the next Monday you having a new Sprint this Friday you will have both Sprint planning and Sprint retrospective meeting too so Sprint retrospective meeting is nothing but we are having a review with our entire team on discussing about like what are the problems we faced in the current Sprint and how can we improve our next Sprint and what went wrong in our current Sprint and uh what are the Mees that we can make sure uh that doesn't happen in the next next print right so as a team
• 511:30 - 512:00 we can you can always say that um how you are if you achieved all your user stories and you are not postponing your user stories to the next Sprint that means you you had a good Sprint right you're not supposed to postpone to your user stories if you pick some user stories for that particular Sprint you're able to finish that uh user stories suppose in case like if you don't know if you you had dependency on other team and you didn't finish your work and your uh user stories are postponed to the next Sprint then you
• 512:00 - 512:30 can always tell your scrum master and product owner in this meeting that um in current Sprint for this particular story we had a dependency on then another team and we were not able to get uh get the status from them and we had a dependency and we were not able to finish our current uh user story so we had to postpone this particular user story so this is more like Lessons Learned session and everybody is going to give what what are the good and the bad that we have done in the current Sprint and we're going to learn it we going to
• 512:30 - 513:00 document that and make sure that doesn't happen in our next Sprint so this will be conducted by the scrum master or the product owner you'll be just like an as a business analyst you'll be just attending and give your giving your feedback but Sprint planning meetings and Sprint retrospective meetings are conducted by the scrum master so the next question is what is MVP MVP is nothing but minimum viable product so so what is minimum viable product you are creating a user story and you are
• 513:00 - 513:30 creating some kind of product right so this is software development what we are talking about in agile business is software development so at end of each Sprint like you are creating some kind of product so that the end user or the business owner is able to test it right so always keep in mind that when they say minimum viable product some product that they are able to like the users are able to see the product and they're able to understand the product and they're able to test the
• 513:30 - 514:00 product that's what is called as minimum viable product so for example even if you are you're uh you're creating like a login page and uh you're making sure like some the end user is able to log in okay and uh even in that if it's not it's not going to be a complete requirement at least some part of the requirement is able to to like the business owner is able to test it so I'm just taking like a very small example of
• 514:00 - 514:30 registration or login so even though the complete functionality of that particular requirement is not completed at the end of each Sprint you're able to show them the business business owner something that they're able to see visually and they're able to test it right so for some projects you can complete the whole project in like one or two sprints for some project it is going to take three sprints are more than that so depends upon the complexity of your project the timeline also
• 514:30 - 515:00 changes so for very small project small enhancement projects you can complete in one or two sprints but if there is going to be a very massive project and you are establishing that in like multiple markets then the project can go even though it's an agile project it can go like like from three Sprint to more than that so like until then till the end of that 4 months nobody's going to wait so the business owners wants to see something at end of every Sprint so they may be like can you show me something
• 515:00 - 515:30 and can I want to see and test something so that is called as minimum viable product so in agile at end of every Sprint we are making sure that user story is is is like very end user friendly and the business owner or the end user is able to test some part of that user story so that is called as minimum viable product so next story is about the next question is about uh can you explain story points calculation so story points
• 515:30 - 516:00 are always calculated in Fey series like one pointer stories two pointer stories thre pointer stories five pointer stories eight pointer and 13 pointers so for this story points always like you have to remember user stories can be like any of these point right it can be one pointer two pointer so every story right depending upon how much effort is going to take you're going to give points here now if you don't know how to give points because
• 516:00 - 516:30 sometimes you don't know like this task May or the story may look very simple and you may give one point in reality that may take long hours and you'll end up like oh my God I I I didn't calculate it properly so that comes through experience like how many points you have to give for every user story but basically you need to understand that uh story points estimation is going to be a bigger uh task for you as a scrum team like the entire team you
• 516:30 - 517:00 don't want to lose track of your estimation because like imagine you you think like for example you have about four user stories everything is an 8 pointer user story and you're picking all these eight pointer user stories very complex us of stories for an exper and while doing every story then you realize that you cannot complete that because everything is time consuming and you are able to finish only one or two US stories in an xprint you're not able to finish the other two and in the Sprint call you're saying
• 517:00 - 517:30 that I cannot complete because I'm like already stuck with these two user stories there is no time for me to finish it so that is going to backfire you so you have to be very smart in estimating the user stories before the Sprint planning session and making sure you give the right points and how much work you can done because aile is very like short period right every Sprint is going to be very quick it's going to be 10 days 15 days and 20 days so you're going to pick your user stories very smartly and also like what is the priority for every user story and you're
• 517:30 - 518:00 going to give points so initially you may struggle giving points but this is very very important for you to not take too much work and like um and then get embarrassed in status calls so uh for that you need to understand it is always given in Fibonacci series so it's not like there is no like a four po user story or sixo user story or 7o user story okay so story points are given in series and you are going to estimate the user stories by like amount of time it's
• 518:00 - 518:30 going to take okay so here they say that uh usually story points versus hour so we don't give hours so it's nothing it's not that one pointer means 1 hour two pointer means 2 hours it's not like that we are going to make sure that you estimate depending upon like how many emails that you're going to get how many meetings you're going to attend and how many interviews you're going to have with the business owners and how long it's going to take time for you to get
• 518:30 - 519:00 coordinate with other teams and like uh it is like based upon solving problems based upon difficulty or not time spent so for example don't think about also you have to estimate time that is also there so I would say like you have to combine both time and like uh also dealing with people right like you you need to make sure that oh okay to coordinate with this particular team is going to be tough for for me because they don't respond very easily and I have to like send multiple follow-ups
• 519:00 - 519:30 and to coordinate with this particular business owner it's going to be like time consuming because they don't come to the meetings very usual they're always booked and their time slot is always booked so you're going to like follow up with the multiple time so it is like both how complex is the work technical work and also like how difficult it is for you to coordinate with various different teams so don't directly like uh even though sometimes the stories to finish your technical work it can take like one or two hours but that coordination is going
• 519:30 - 520:00 to take longer time for you okay so you have to keep all that in mind and you have to give your story points and it will take time it's not that the very first call you are able to like um judge every user story properly right so as like as you get experienced you are able to give the correct story points uh but you have to keep in mind that uh um always I would say give an Point extra because you never know like how how much
• 520:00 - 520:30 time it's going to take for your user story to get completed so that is called as story points calculation so the next so the next question is what is a burnt up chart so I'm going to give you an example so if you go to jira software and if you're going to log in into reports okay you'll be able to like for example here in projects right under projects you will have reports and if you're able to click the reports you'll have both burnd down chart and burnup
• 520:30 - 521:00 chart so what is burnup chart so burnup chart is nothing but it is a visual representation of a Sprints completed work compared with its total scope so we are going to like see or we going to track our teams progress and how how many user stories were completed and do we have any problems in this particular Sprint so we're going to track that and we are going to give it as a report okay so mostly you will have
• 521:00 - 521:30 the story points here and you're going to have the time here okay so always it's going to be like monthly wise or depending upon if you can also uh like uh customize it like based upon your Sprint store Sprints one Sprint tool like that so mostly you are going to have time versus story points and how much it was done how much work was done okay what is the scope for our
• 521:30 - 522:00 uh for that particular Sprint and how much work it was done so how are we going to track it we are going to track by means of like um this is this is automatic right so like this software itself is giving you the capacity to track all the user stories depending upon like whether it is an in progress or whether it's completed and what is the story points how much it is completed like that it is going to automatically like track B based upon the event okay when was the Sprint started when was the
• 522:00 - 522:30 um user story added so you need not do anything like manually all you have to do is you have to go here and you have to figure out like uh whether it is progressing or it's going down okay so the next question is what is a burn down chart so this also we can explain in the report section so if you go to reports you're going to have burn down chart okay so in the burndown chart we here we are going to track like story points
• 522:30 - 523:00 versus uh like every day like how much work was done okay so for example Sprint was started in this particular date and then there was scope change there and uh we added new stories in the middle of the story so we removed our stories because it doesn't have any priority right now the business don't want to like progress it so for some reasons we
• 523:00 - 523:30 are adding new stories or we are making sure that existing stories may not be progressed and we are going to make sure here these are the story points and this is timelines and here we can have like every day like what is the progress of that user story and uh how that that user story was completed or not if all user stories are completed for that particular uh timeline for Sprint it means that your burndown chart will be like will be very straight like this
• 523:30 - 524:00 okay and it's a good burndown chart so we can always use these charts to make sure that um how much existing work was done and how much changes was done in every Sprint so that like for the next Sprint right we make sure that doesn't like happen because the requirements as a business analyst the requirements are changing constantly even though you pi up your user stories and you're you're like developing and you're testing suddenly the business owner is saying
• 524:00 - 524:30 that no we need not progress that stop that or maybe add a new feature so it's not like planned very well in agile there'll be constant changes okay it's not like um waterfall methodology here the requirements can be constantly changing and also within that particular timeline you have to finish the work okay they are going to change the requirements but they will ask ask you to finish the requirements because it is an agile methodology so your mind will be like uh what is this I've just
• 524:30 - 525:00 started the work or I in the middle of something and I'm testing something now they want to change something so you need you you should not be frustrated because keep in mind that this is an AEL methodology project and there will be constant changes and you have to adapt to that changes and so for you this is something it needs to be like normal okay so even though you're in middle of testing something or you are like almost you got the sign off now suddenly they're asking you to like make sure
• 525:00 - 525:30 that you're getting new stories so so you may have stories that may be pulled in between the Sprint or some stories which is like postponed or we don't want to carry forward or progress with it so based upon this burnt up and burnt down chart you are able to identify like how this particular Sprint went and we are going to document that so that that doesn't happen in our next Sprint so that is burndown chart and uh the next one is what is
• 525:30 - 526:00 print velocity so I already told you like velocity chart is nothing but like how how how many people are there in our team in our development team and on our scrum team how many people are there so let me give you an example like for example we have about like only like two developers okay let's say that we are very small team we have only two developers two business
• 526:00 - 526:30 analysts and we have two testers and we have one scrum master and one product own okay so in this scenario it's a very small scrum team and everybody is going to like for example your team has only like two week Sprint okay two week Sprint means it's like 10 working days so in the 10 working days we need
• 526:30 - 527:00 to calculate how many user stories can two developers take and how many user stories can two business analyst take and how many user stories can two testers take okay so we cannot like that is called a Sprint velocity like how much how much like our team can take because we cannot make sure like all the 200 300 user stories can be completed in the upcoming Sprint right so our product owner and scrum Master they will be doing the Sprint velocity orint uh Sprint capacity right so we are making
• 527:00 - 527:30 sure that according to our team's capacity we are determining how many user stories can be taken okay so for example um for if it's 10 working days you can have maximum you can take only 10 story points okay so it can be like um two story points and it can be an eight pointer you can take two stories or it can be five pointer and threp pointer or
• 527:30 - 528:00 five pointer and a five pointer so we are we we are making sure that Beyond this we are not like overloading ourselves with too much work because as I told you the most important thing is we have to make sure our work is completed within that particular Sprint so Sprint velocity is nothing but we are calculating how many people are there in our team and how many working days are there in that particular Sprint and depending upon that we are determining how many story points like everybody needs to Pick And depending
• 528:00 - 528:30 upon the story points now you can pick the user stories okay so for example the capacity is like only like um 10 point user stories everybody can pick only 10 point user stories you can pick like 10 one pointer stories or two five pointer stories or maybe um two two pointer and 8 pointer so depending upon the story capacity I mean the complexity you're going to use the choose the user stories okay so this is called a Sprint
• 528:30 - 529:00 velocity so next question is how do you coordinate with other teams so this is a very very important question because in agile you may be like tired of coordinating with multiple teams and dependency with external vendors and um inside your organization itself like you can have divisions like it teams can be like multiple it teams and you have to do cross team coordination so for that we use a terminology called scrum of scrum meeting is recommended
• 529:00 - 529:30 this is usually by means of a scrum master so you can always say in everyday standup call that I followed followed up with this particular team they not giving any response they are not giving any feedback so what I have to do so you have to raise call your risk in your daily standup call and then your scrum Master will be someone who will take responsibility of coordinating with the other scrum teams so if it's going to be a very Mass project and uh you have done your best but still you don't get any kind of response from the other teams
• 529:30 - 530:00 and they are not giving any kind of uh feedback through emails or you don't know what is the status of that in their project now you always have to escalate to your scrum master and the scrum Master will be conducting the scrum of scrum meetings and they will make sure that they coordinate with the other scrum teams and they will take responsibility from as a business analyst your responsibility is like you can try one time or two times and then you have to escalate it to your scrum Master to make sure that uh they will
• 530:00 - 530:30 coordinate from their side and we have to make sure that because you don't want to complicate yourself and uh become tired of like coordinating with other teams right so you you follow up with them like one or two times and then you escalate it to your scrum master and they will be having the scrum of scrum meetings so very very important for achieving cross team coordination so the next is what is scrum of scrum so it's nothing but it's a SC scaled agile technique that offers a way to connect
• 530:30 - 531:00 multiple teams who need to work together to deliver complex Solutions so suppose you have you are having um like four different teams okay four different technical ID teams and then you have two external vendors or not even your company you have some offshore uh teams okay two offshore teams so like you cannot be coordinating with everybody right so this is a massive project you are working you are
• 531:00 - 531:30 representing only one it team and you need to coordinate with multiple teams now what we have to do is we have to perform this scrum of scrum meeting and we are going to make sure that every team is uh able to tell their status of work what is their progress of work and when can they finish their testing when can they finish their development when can uh we do the complete uat testing all these meetings right is called as scrum of scrum this is usually done by a scrum Master but you need to know
• 531:30 - 532:00 because as a business analyst you need to know this is nothing but a scaled agile technique that is used to connect multiple so the next question is what are the three pillars of scrum so three pillars of scrum is nothing but transparency inspection and adaptation so we going to learn that so they're going to ask you if you're following or if your team is following scrum methodology what are the three pillars of scrum so first is transparency what
• 532:00 - 532:30 is transparency you're going to make sure that every user story whatever is in the backlog or entire team is able to see it okay so in this jira board whatever stories you create or uh your um colleagues create everything everybody is able to see it inside your team they will have permission to see it so they can view your Sprint backlog they can view the product backlog and they are going to see what is the status of your
• 532:30 - 533:00 user stories whether it was done or whether it is in progress so you everybody inside your development team or the scrum team is able to view all the user stories and the work that you're doing and the progress that you are making for your user stories that's why we are using jira software that's why we are tracking every even single like task or even like small small even work that you have done we are tracking it to make sure we are giving credit for your work so that is called as transparency by following all this
• 533:00 - 533:30 backlog also having Sprint reviews so every once in a while we are going to have Sprint reviews asking like um feedback with the stakeholders Sprint review is like you are going to make sure all the stakeholders are there and you're going to ask feedback from them that is print review and definition of done when you're completing a task or user story what is the meaning of done so you have to make sure that that particular user story acceptance criteria is actually achieved so that
• 533:30 - 534:00 you can say that that particular user story is completed or that particular task is completed so acceptance criteria is very very very important also the next one is if you are very transparent and scrum what will happen so you can deduct all the bugs in the very early stage okay so defects deduction is nothing but it's very important you make sure that you are able to catch all the bugs or you're able to identify all the defects in a very early stage so that uh
• 534:00 - 534:30 you don't have problems with the business owners going forward so early deduction of all the bugs and issues that's very very very uh critical also you're making sure you're taking accountability right so because you are doing a particular task and it is under your name means like you are responsible for that task so you're not like blaming on some developer or tester every task that you create or every user story that you create it is going to be under your own name so you're taking like that
• 534:30 - 535:00 clear accountability of that particular work that is being done under your name and you can also understand you can engage all your stakeholders so that involves all your developers testers business owners and you can also show them like how much work they need not be directly pinging you all the time so you can always like make sure you give the user story numbers and they're able to see the status of the user stories and they're able to get the like they they will know like when you are able to complete that particular user stories so stakeholders engagement
• 535:00 - 535:30 is very important also identifying risk so once you are doing the development or once you are testing now you can identify a lot of risk and then you can catch it in the very earliest State before the completion of Sprint itself you are able to identify risk so that's why agile is like very popular now because in short term you're able to identify and you're able to like perform really well and the next uh pillar is inspection inspection is nothing but how can we
• 535:30 - 536:00 it's not like micromanagement it's like you're making sure everybody in the scrum team is like aware of what's happening in the team okay so we have Sprint planning calls daily standup calls we have Sprint review calls and Sprint retrospective calls so I've told in the earlier questions about Sprint planning Sprints daily standups and Sprint retrospective Sprint review is nothing but um we are involving stakeholders all the business
• 536:00 - 536:30 owners and we are doing a review with them sprint retrospective is internal to your team whereas Sprint review is like you are involving the external business owners and stakeholders and you reviewing the user stories with them that's the difference between Sprint review and Sprint retrospective the third one is adaptation adaptation is like I've already told you'll have multiple change requests and the requirements are constantly changing backlog is going to change and uh some user stories will be added some user stories will be
• 536:30 - 537:00 postponed some user stories needs to be abandoned so you have to have that agile mindset to make sure that uh whatever new requirement you are getting uh you're going to follow some protocols make sure the business owners are being like addressed with those protocols and also you have to discuss with your scrum master or project manager also right you cannot take decisions on your own so you have to make sure you like coordinate with your scrum Master product owner and the manager regarding the new request
• 537:00 - 537:30 and you have to do all the adjustments and adapt accordingly so these are the three different um pillars of scrum why we are doing this because of customer satisfaction whoever is giving the work to it team we making sure that they are very happy with our process because we are very flexible and we have good quality we know how we fought of a certain protocol and process and we are making sure at end of it everybody's happy they are happy we are happy and
• 537:30 - 538:00 the customer end user is happy that's the benefit of adaptation in scrum that's why LEL methodology is very very popular now so the next question is how to deal with scope crep so scope creep is nothing but uh like for example like um they are giving you requirements but end of the day they are like adding more
• 538:00 - 538:30 requirements and initially whatever they thought we thought that is a requirement right now it is not a requirement anymore so they're constantly changing that so what we have to do is to some extent scope creep like we can accept with the within with within our capacity okay but if you are there going to add very complex requirements and they're going to like um it's going to be very tough for our
• 538:30 - 539:00 development team to accommodate those requirements then in that case it is going to be uncontrolled and it is going to have a great impact on our time our cost our building and also uh during our Sprint timeline rate we are not able to complete that so this is a very big problem in agile that uh constantly they are U giving like more requirements which you are not able to do it right so what we can do is we have something called
• 539:00 - 539:30 Change Control process so for this like when business owners are constantly like giving you requirements you have to deal with that very professionally you cannot be like very rude with them and you cannot say that no you cannot like add on requirements like this so we are not supposed to answer like that we are going to answer in a very professional way so you can always say that we have a process called Change Control process and all your new requirements
• 539:30 - 540:00 needs to be submitted there and we need approval for those change request only then we can accommodate those those new requirements so for example you gathered all the requirements you created user stories and you are working on the user stories in a particular Sprint now in the middle of the Sprint now the business owner is coming and asking that uh sorry we have to change the requirements and we have to add new functionalities now how you need to
• 540:00 - 540:30 answer them is you have to say that I understand your concerns now we have a process called Change Control process that is within our ID teams we follow this process so what I will recommend you is please create a user story for all the changes and you need to submit it for the change request approval so what they will do is business owners they will go here and they will have access to jir as well right so they will go create the user stories okay whatever is the enhancement
• 540:30 - 541:00 or whatever is the new request they're going to add it here and that will be going for approval so who needs to approve of course your manager needs to approve we don't have the uh like the responsibility of approving that right so it needs to go through um different uh approvals from managers and you have to discuss with your scrum master your product owner your manager and we have to make sure that whether that change can be um like whether it can be
• 541:00 - 541:30 accommodated or not accordingly after discussion with your developers everybody the whole group you're going to make sure whether that new user story is going to be added in that this print or the next print okay so we follow something called Change Control process so you should not be rude that's the first thing the business analyst should not be rude they have to deal in a very professional manner you tell them to submit the change uh request and you say that I have to discuss with my manager and also my development team and then we
• 541:30 - 542:00 will get back to you on this change request this is how you have to deal with scope creep the next question is what is the difference between scrum and combin so uh in agile right we have different kind of scrum methodologies so we have something called scrum and then we have Comin so scrum is mostly like I have worked only in scrum I have never worked in combin based projects so scrum means you will have Sprint it can be 2
• 542:00 - 542:30 weeks 3 weeks and four weeks you'll have a scrum Master you will have a product owner and uh we will follow all the scrum guidelines right everyday standup calls Sprint review calls and Sprint retrospective calls and uh uh um and then like all the Sprint uh ceremonies we we do it that is Scrum whereas comeb means you don't have any timeline okay and you don't have a scrum Master you don't have a product owner there is no
• 542:30 - 543:00 no defined roles so this is mostly like for research projects like for example someone is working for um like a brand right like Nikey or you can say any kind of research based products like the research Department right they don't have a timeline so they they have user stories but they don't have a timeline that they have to finish within like uh 2 to 4 weeks so mostly like anybody in research they can be product based for example Microsoft also Facebook they can be in the um
• 543:00 - 543:30 product based companies but mostly in the research Department that's where like they have some amount of extra time and they can do creatively and they are able to come up with new ideas and they're going to track all their work in coment but in proper it professionals like for example you working in TCS CTS or you're working in some kind of like regular Fortune for uh companies not in research Department you are in an IT professional then mostly you will be following scrum only that's the
• 543:30 - 544:00 difference between scrum and cell and the next question is what are the tools used by agile business analyst very very important you need to be an expert on jira and Confluence so as I've told here this is a jira software and we also have Confluence in this so you need to make sure that you are aware of all these products and it is actually free only for one month I think it is free so you can use your email ID and then get this product for free and you need to definitely especially if you're a
• 544:00 - 544:30 beginner you need to like definitely understand there are so many like um products inside J software okay so you have reports you have um how to create user stories you can create projects you can create dashboards and you can always like try exploring the software and also Confluence Confluence is for documentation for creating br is also creating all your diagrams and also creating all your for documentation process right you have to be well aware
• 544:30 - 545:00 of these two um softwares of course Microsoft Excel word PowerPoint all that will come you have to learn that but these two tools are very very very important and um just not just by seeing videos you cannot learn it right so if you want to have really hands-on experience you have to like download it you have to make sure you play with it and then you have like some understanding of all these software is very very very important okay Z and
• 545:00 - 545:30 confence and then what are the reports created by aile business analyst so there are different types of reports that U we can create during this um using this um jira so for example when you go to all reports you can see you have burn down chart burnup chart you have Sprint report you have velocity chart you have cumulative flow diagrams um and also you have version report epic report control chart epic Burn Down release burn down so there are so many
• 545:30 - 546:00 charts here you have like spy chart report average age report like so many reports are the time tracking report So based upon your team you can always create reports based upon your manager requirements because they're going to have a meeting with the staff EP they're going to have um meeting with the leadership team so they may ask you to suddenly give like 10 can you please give me a report for last print can you give me a burnd down uh report or like how many stories our team completed can you please take a report so you can go
• 546:00 - 546:30 here and download this report and you can send it to your manager so you need to be aware of all the reports existing reports that you can get from the jir software so that you can give it to your manager for their meetings so these are the some of the reports okay Sprint report burndown report release bur down report and there are like so many other reports also so you can like download that software and you can learn all about those reports so the next question is how do you handle
• 546:30 - 547:00 constant change in requirements like I've already told you any scope creep or anything like constant changing requirements we need to have a process called Change Control process so in that Change Control process we are asking them to submit uh user stories okay with whatever um like now whatever they want to let enhancement right so we we have to make sure they are submitting the user stories and we are making sure that you review those user stories new user stories
• 547:00 - 547:30 with with your development team okay you have to review with your development team you have to review with your scrum master and you're going to review with your product owner and also with your manager with everybody you have to review and after their approval Only You Are promp promising your business owner that the new request is being granted and it's being approved by our entire team and now we can work on the new
• 547:30 - 548:00 change if suppose they don't approve they're saying that no no no this requires extra billing or this will require extra time we cannot finish this in our current Sprint so that also you have to like tell them the business owners that no the new requirement whatever you have submitted that requires extra billing or that requires extra time we cannot complete that in the current Sprint and you have to explain to them and back and forth you can communicate with your uh manager and then you can give them feedback so you
• 548:00 - 548:30 have to always deal this very professionally do not be rude or angry very very important always be in a very in a professional way you have to like deal with this because you get frustrated because you put so much time and effort in gathering requirements and they're constantly changing it you may get frustrated but understand this is an agile environment this is how it is supposed to be and you have to make
• 548:30 - 549:00 you have to like um have a mindset that this is called agile mindset like this is how this works and I have to make sure this is accommodated and I have you're not alone you have the whole crew with you and you're going to take their opinions and approvals and only then you're going to communicate with your business owners the next question is how do you handle conflicts or disagreements within an agile te now this is something like everybody should learn okay so you have
• 549:00 - 549:30 to stick together so first you have a conflict with your developer or your tester you are all in one team okay escalating is not a solution you escalating a developer developer escalating you and you escalating a tester I will in my opinion that's not a good way of being it then it can become very toxic and one fin day you're going to leave that team right so always like if you want to be very comfortable team and you are going to make sure you're going to have a very happy team then you have to stick together and you have to
• 549:30 - 550:00 believe in each other and communicate with the developer or the test okay they are they are your team people right so you even though you have different personalities and your opinions and experience and expertise and individual skills are going to be very different you have to like respect each other support each other and help each other and make sure that you you're working as one team within your team you can do that but if you're having conflicts with some external team then in that case
• 550:00 - 550:30 also you always make sure you are like communicating in a very professional manner and uh they are also given some they have this uh jira software team right they have given some kind of tips like how to make sure once there is a conflict what you have to do you have to ask for a teammates advice you have to make sure the time is right right and when you when you decide to talk you you have to respect their boundaries and don't risk embarrassment of your
• 550:30 - 551:00 co-workers don't approach them and they are like very like they're very fussy they're very busy and like don't approach them that and you have to start a conversation like um hey I think we have some tension between us is it okay can we we talk about it and you also need to be positive and if they are very they don't understand you have to give them some time for them ask sorry if needed and uh don't put yourself in a
• 551:00 - 551:30 very complex situation with them this is a very professional environment right this is not your home and you cannot scream at people and you cannot use uh very like harsh words with people okay this is a very professional environment so you have to keep focused on the issue do not blame and do not blame their personalities and uh do not talk back that's a wrong thing to do don't talk back with other colleagues about one person do not do that you never know who friends with who and you never know
• 551:30 - 552:00 who's related to whom okay so I would say that you should always be professional you should always uh talk to them if you have any conflict on your person directly talk to them and if you want to ask sorry initiate that okay so you can say I'm sorry man I'm like really sorry I was I was tensed a little bit and I was going through something so I'm really sorry about it I okay with it and how can we be positive and the next time you're having a meeting with them don't have that Grudge in your mind okay and that's how you
• 552:00 - 552:30 have to move on because if you're having constant conflicts with your co-workers that place can be really toxic and toxic and you don't want to deal with that team anymore so you have to make sure that you clear that air after the conflict and uh very be very positive and one important thing is don't talk back don't talk back about others uh with other colleagues okay so that can be really an issue so you have to always deal with them very professionally this is how you deal conflicts with your
• 552:30 - 553:00 internal teams next is the last question is how to use agile kpi metrics so there are so many agile metrics uh that we have for example like uh we have how to kpi is nothing but key performance indicators right how our entire team is doing like you have to like know what you're doing all the user stories needs to be under your control
• 553:00 - 553:30 every acceptance criteria that you write you need to be well aware of what is happening so you can always use certain metrics that's why we have reports Sprint burndown chart or you can have release burndown chart epic burndown charts and velocity tracking and then um you have control chart and you have cumulative float diagram and we have even more metrics also when you have defects how to raise a defect how to fix a defect how to track a defect so all this task tracker defect tracker all
• 553:30 - 554:00 this you can make use of um these charts and then you can use this metrics to make sure that you are following agile properly okay agile means there are so many terms terminologies involved in this agile projects so this will take some time for you to learn every single like terminology will be new to you if you're B beginner so learn all these things one by one and apply get the access to zero software and you need to try it by yourself and understand each
• 554:00 - 554:30 each of these charts and you have to like understand um simply by S I'm telling you again and again it's simply by seeing these videos you cannot be an expert in order to become expert you have to download this software you have to try all these charts one by one by yourself and then you have to get an experience out of this only then you'll be like understanding what are these aile kpi metrics how to use this every chart reports and trackers okay so I hope this uh video was helpful thank you
• 554:30 - 555:00 for watching