How Do I Sign Hawaii Banking Business Plan Template

How do i industry sign banking hawaii business plan template

so finally we learnt about how does the industry work and what are the major you know stakeholders in the project we learn the various phases of hdl-c so that gave us some basic understanding about diet industry so we have not learned anything specific to a B role yet but you know it gives us that comfort level where we understand how projects are executed what are the details which almost everybody in the IT industry should know right since a lot of you come from a non-technical background this would have helped you to you know gain that perspective all right now starting today what you do is we'll get into the actual details about the project about the role of a business analyst right the six knowledge areas you know then the next chapters two to seven would focus on that right so we will pick up each knowledge area of what a business analyst needs to know and then focus on that and learn that in detail right now so in the in the previous three sessions have given you that high-level view that you know these are the you know things that a business analyst would be that he helped out in planning he would understand the quadrants you document them he would communicate the requirements you would help in testing will identify opportunities right I've given that high-level overview now we are actually getting into the details and then see you know what do we do as on a day to day basis what all details that you know what are detailed activities that we'll be doing so that is what would be the focus going forward the next you know any unify sessions okay so today's session I would start with requirements planning so before this enterprise analysis happens varying you will identify opportunities and then you know you've created a business case for it and get budgets approved okay but it's a little complicated and then you'd be in a much better position to understand it at the end of the session that's the reason I'm taking it at the end of it so today I will start the requirements planning right so now the context is that once the project budgets are approved and the team is on board okay so what are the first few things that you would do so that would be the focus of today's session okay so a typical project once it starts right so you know on the date on the first day or the first week of the project what all activities you would do would come under this purview of the department's Pam okay now throughout this course I will take one example of a mobile banking app so that you can relate to it right let's assume that you know where we are developing a new mobile banking app now for it for a bantams call it a Citibank and for Citibank we are developing a new mobile banking app and you know if we are the business analyst how do we proceed to whom will you talk to get the requirements all that you know be entitled later that we deny it will give us a real-time feeling about how to approach a product now the reason I picked up that example is because you know most of us tend to understand that you know the functionality of a mobile banking app because we use that right so we have picked up some other complicated example of those again spend a lot of time in explaining the functionality which we could avoid when we are looking at this particular example okay so today's session would be on the planning and I would have would teach you how to you know create the requirements planning and details which which will go in as part of the project plan you will understand the various rules which fit into the project whom you interact with you will also learn how to manage the requirements and scope and when changes comes into the project how do you manage that change is coming in you will also learn how to manage the risk related to them all right so the next 2-3 days you focus on these topics and then at the end of it and take one of my you know projects that have done has a case study and then we will discuss we will try to apply you know the the learning what they have done in the you know these two three sessions to that particular scenario and then see how have a hand in date of how you will get into that discussion more than then see you know how we would have how we should proceed for these activities okay yeah now the first step that's you know the first thing that you do once you get into a project is figure out who are the key people in the okay on day one ideally you should be doing this and so once you getting the project figure out who are the key people now who are the people that you generally interact with it through who are other people in the project would you know contribute to the project let's spend some time understanding those roads right now the most important and the senior most person in the project is the executive sponsor right now he is the he's the person who is allocating budgets to your project and so he would have grow the project and then he would allocate budget now when I say I get budget he will generally be the head of a business unit and as part of that business unit planning he would have allocated some budgets to implement this project and so that is how it would be right now let's say if this mobile banking application is there so you know if the mobile banking application is there now this application would be used by water the detail customers individuals like us so the head of that you know unit business unit of know retail banking head would approve that you know maybe two million or three million whatever it cost to develop the Hawaiian mansion reputation so he would be called as the exhibit responsible so the rail role he would play in the project with eggs with the sponsor now usually these are very senior days so they would be at that you know senior vice president executive vice president levels and we will not even interact with them right so it's for all good reasons you might not even talk to the executive sponsor of the project unless it's very high visibility project they don't get involved into the day-to-day operational activities right so they only look at you know whether you know the project is running smoothly as for the timelines and it's it's on track or not right if everything is going fine that would be that they will not interfere they're not interfere onto the project okay now when when the exceed respond sir is not interfering on a day-to-day activities you would want somebody to actually own that and oversee the project on a day-to-day so what he would do is he would allocate somebody from his team to own the system right so pretty much this guy would be the person who will take all decisions regarding the system I guess you would say you know whether you know some functionality should be added or he mode you know finally your B ID and everything would be approved by the solution all right so all executive decisions regarding the scope or requirements or the system will be taken by this solution owner right now usually all approvals are given by this person so you will interact with him from from a business requirements point of view so he will approve of your business requirements right but again this Ray is also a senior person he will not have enough time to spend with you to explain the details requirements to you right so what he does is he would allocate some people from his team who can actually spend time with you and view the detailed requirements okay now these are called as a subject matter experts okay or SMS so you must have heard this term SMS so they understand the business in and out they are experts in that particular business they are experts in that subject matter so hence that same subject matter experts right now it is these people that you would interact with and understand the requirements in detail okay so a lot of your time you spend interacting with these SMEs so if you want to understand you know how does the functionality of the funds transfer in the mobile banking application right so who is going to tell you the SMEs are going to tell me any business functionality these are the people who are going to explain you the detailed process and what the system should be doing right so you will understand the complete functionality from these guys okay now usually there would be some three or four SMEs for a project depending on those modules which they're experts in you will talk to them and understand the requirements okay and once they you you and talk to them understand the requirements and create the BRD so that would be approved by the solution owner he would review the document and and see whether you know it captures all the details and one the way he wants it he would approach okay then you would have the end-user community as well who are actually the people who are using the system so for all good reasons you might not even talk to them right like in this case a mobile banking application you might not even talk to the end-user because any end user would be the customers of the bank customers of Citibank would be the end-user right so you will not talk to them you'll not get a chance to interact with them together primarily the SMEs who are performing the job of giving you the details of problems okay but end-users are the final team which is basically using your system okay then you would have the we understand the role of a business analyst since you know the last three sessions you've just been discussing what is it that should be doing and done so our role would also be important in the project there would be project managers like so from the client side as well as a vendor side project managers there would be programmers who are actually doing the coding and then there will be architects who are doing the design and then there would be the QA teams who are doing the testing right now there would be also teams would you know manage the system like the ops team right so primarily ops team would have a no introduction list and then the DBA who would basically look at the hardware and then the database making sure that that working fine right so these are primarily once the system is light then they would see whether you know there is enough space in the hard disk so that you know if this there is a space glance you know it will result it nethers right so to avoid those kind of situations they do the DB has to keep on one entering the you know the health of the database it similarly the intercepts are on analyst also has to specify what of the hardware requirements for the system you'll have to monitor the you know the hardware and then the networking you know hardware and networking infrastructure to ensure that they are up and running all the time all this would be ops activities you might not even interact with them a lot of times right so the data modeling and all would also be done by the application active it's generally tend to call this person as a technical architect would do both application design and the database design as well then you have audit teams also who would ensure that you know whether we are following all those standards and procedures which are defined for those particular policies all that would be taken care by the auditing right so these are the typical roles in in the product okay now primary ones that you would interact with close to know seventy seventy-five percent of the time you talk with you will talk only with the subject matter experts right so these are the people who will give you all the detailed functional requirements okay then you will also talk to this solution owner for getting the approval of the systems and you also talk to the you know architects and then the operations team and the dev team and QA team to figure out the non-functional requirements so we will understand about the non-functional requirements at a different point in time when time comes canal if any water but for now these are the various rules but you'll interact so the key takeaway from this slide first step once you get into the project make sure that you understand who are the people you have to interact with to get the detail Department who is going to tell you the detail Department which are basins right and then also make sure that you understand the solution owner who are the people what who is the person who is going to sign off your business requirements doctor who is going to approve your requirements like or review on your documents so that guy would be the solution all right make sure that at least you understand these two rows you figure out who are these people from the business side work or performing this role it's very important for you from the business on this point goal point okay so generally the the responsibilities of a project are either I was explaining about the the roles make sure that you identify the subject matter experts and the solution owners so those are the key people who will give you the functional requirements right so the rest of it again can figure out but make sure that you clearly identify that that's the first step that you do when you get into your car please help me understand one thing what is the who is the solution is it a stakeholder or someone else yeah see he he would be from the business team usually you know the somebody has to take all the decisions and and review the final product final application of system which is developed right we call them as a product owner solution owner or application owner there multiple names but he pretty much wants that system what is being developed on a functional side right now so once okay yeah go ahead I'm sorry so so this guy would basically take all the decisions regarding what should be in scope what should not be in scope if something has to be a right so he will be the person who would actually take all those decisions okay now he is usually from the business team and and all the functionality related decisions he would take his call would be the final card okay now he would assign some people to the project from his team from the business team who would give you the detailed requirements so so you would interact with these SMEs and understand the requirements but it finally would go to the SM to the solution owner or the application owner who finally approve the the B addict right so the requirements what you have documented would finally be approved by the solution on this functional requirements are given by a subject matter experts and solution owners and non false they are given by developers not developers so you know you you if you recall from the previous sessions have told you that there are primarily three teams development QA and ops team right so some of these non-functional requirements would come from the dev team some from QA team and from some of the ops team right now developers actually might be from the vendor team right select like let's say fact sensor is implementing the system the developers would be from the you know the Accenture team but you know there would be a dev team as part of the you know the client also like the city path now they would have some standards but you know these are my coding standard this is my difference architecture these are my standards for you know some of these like features like performance and security and off so those would come in from that dev team right so I think you know when we when I get into that specific you know topic of non-functional requirements I will explain that so that the reason I have not not touched upon that non-functional requirements would come from different kind of people but functional requirements it should primarily be the SMEs you have identified some three four people from the from the business side who will give you the detailed requirements and who would be approved by the application of solution owner right non-functional requirements I'll talk about it a little bit because you know once we get clarity on the functional departments I think you know there's been a much better position to understand about what non-functional requirements are so I'm trying to you know postpone that traffic to a later point so that you know it doesn't create a lot of confusion okay so keep takeaway from this slide identify your SMEs identify the solution owner and make sure that you know you learly know who is going to tell you the detailed requirements and who is going to sign off approve your requirements right solution owners approved subject matter experts tell you that if detail with profits right so the hierarchy would be like this that would be executive sponsor right so under him would be the solution owner and under him would be the SMS right this would be the reporting hierarchy kind of thing so you you might not even interact with the executive sponsor right so there are very senior guys in the project not generally get into the operational activities of the project okay so all those decision-making is done by the solution of the case owner and then the details are provided by the SMS so let's move on so primarily when when and at the start of the project you you know the project manager would ensure that he identifies all these key people and and the roles and responsibilities now he would maintain one document called as project charter right so maybe now you can search for it later it's called as a project charter document which consists of all the details regarding the project right so your roles and responsibilities also would get into the project charter and you're either define it using a detailed of all overview about each of these roles and explain that you know these are the five six things that he would be doing are to represent it very crisply we have a mechanism called as Mahavishnu so RSA stands for responsible accountable contribute and in fact okay now this is a very crisp way of representing what each of the roles of people in the project would be know doing at each of these phases of the project right so on one side you have all the roles and another side of the table you have the detailed activities in the project right like if you take only the planning and definition part now you do the will first made the project plan then the schedule then the budgets you'd identify the requirements use cases right so you know these are the these are the activities that could be done right from planning till the creation of test cases right now unis down those activities then you would miss down all the people in the project right then you would map each role to what they would be contributing across each of these activities right now let me explain each of these role and then you look at what it means right so responsible means he would own that task he has to make sure that that particular task is completed on time and without any major issues right so if there are any problems he is the first point of he has to you know ensure that all those necessary actions are taken to correct it and ensure that it's back on track right so he is the primary person who should ensure that the task is completed so if something goes wrong his head is on the block he would be the first one would be held responsible for right now so that that kind of role is called as a responsible the second one is accountable there would be multiple people working in a particular task a simple example if you look at development right now there would be at least some 10 15 the other person in a you know midsize project right now all these guys are are accountable for ensuring that the program's of theta right and there would be a tech lead who would ensure that all this you know development is completed untied right so usually responsibility is given to 1% and all the people who are actually working on that task would be you know accountable for that particular task right so that's the difference between responsible and accountable right so if you look at it there would be only one person who is who is responsible and then there could be multiple people who are accountable okay so usually responsibilities is given to one person he has to make sure that the task is completed accountable could be multiple people who own the task who work on who are actually working on that particular activity and the first to ensure that the task is completed okay the third type of role is contribute or consult Thanks so primarily the you'll be used for consult also so so what this means is these guys are not you know doing that task right so they won't own any you know particular tasks but they can provide advice so they are experts in some field and then you know actually contribute to that particular task they can advise you they can come some provide that concern and advice to ensure that the task is done in a better way right so that's that's a consult kind of right and then last one is informed so they just need to be kept in the loop you just need to know what is happening so they will not do any work they are not doing they are not even providing any inputs but they should know what is happening right usually the senior management needs to know so we will keep that role as involved right any other systems which are dependent on your system they need to be informed about your focus of your sister right so anybody who's impacted you generally keep them as in pump and then the and and usually the roles are classified into one of these four like if you look at this now you are a business analyst so you would be held responsible for constantly progress you have to make sure that the requirements are captured and then the use case of also captured right so these are the primary responsibilities what are you also doing here also preparing the test plans and scripts that's your responsibility right the rest of it you are contributing you you contribute to the planning scheduling budgeting then your design and you know you have markup screens and all your you're contributing there you don't really own it you have not even entitled accountable you're contributing there which means you have your wording some cleric you know if some otherwise this will party will provide that advice let me flip something can be done with a museum just informed right so this this RACI matrix is generally prepared at the start of the project it's again prepared by the project manager we are not expected to prepare this the other day if somebody gives you an RSA matrix you should clearly know you know this is my role this is these are my expectations right and then you can look at each of the phase and Nancy know who has to do what kind of activity even get that clarity right so understand this document make sure that you clear up of this star so again we are not preparing this document you can only refer this and then figure out what is your role what is other people doing it's a crisp way of representation and then you could have a large word document with detailed goals and responsibilities explain are you would have an RSA matrix which which crisply represents what each one of those persons are going to do understand their role in the project okay so that's the first step you are figuring out who are the key people in the project identifying those key people right once you've identified the key people then you would start your planning activities okay now what all input should be there before you even start planning and you should have a document which is giving you the high level scope so we call that a scope document now there should be some reference which is telling you in our in this system we have to develop these 20 features or 50 features of 100 just whatever it is right now depending on the context of how the project has been finalized there could be multiple documents which would be which could be considered as Pope scope document right in most of the cases even if it goes through that competitive bidding you're the winner of that competitive bidding is identified and then statement of work is that is the sign is the customer right nothing says it would scuba the statement of work would clearly say you know this is the scope of the project you have to deliver these 20 features as part of the system okay now those 20 features will have to expand it into detail departments later but you know it's clearly giving you an indication that these are the 20 things that that the you know that you're expecting as part of the system okay now so this is the primary document which should then maybe be considered in some cases what happens is you know for even for requirements you will not give it to a vendor you will do it in-house like you know if Citibank is there see the bank itself could do the requirements okay so it will do the requirements and once the beard is prepared then it will it might give it to some you know vendor like you know TCS or so for development and and design under the fact or even the development and design also can happen in house all right so those are the possibilities in that kind of scenario there would be at least a business case talk okay so these are the two documents which you can consider as your input to the planning phase right if it's a you know clutch in its bits a client when the relationship where in you know that say Accenture is implementing the system far or Citibank right so then there would definitely be a statement of work okay is you can you can ask for this statement of work which will clearly call out that these are the currently features that we need to develop okay so make sure that you have the document are the second option is Citibank itself is in executing the project right so there is no vendor there is no Accenture or pcs with sanfino and Citibank in in-house is developing this application right so they would at least be a business case document it should have been prepared earlier on basis on which the budget set up to so you'll have that list of features mister in the business case talk okay so these two are generally considered the spoke documents make sure that you have at least one of them if it's a client vendor relationship you will have a suitable if it's if it's a client alone which is doing the requirements then you will have a business case partner once you have this you know the business case documents are they so W then you'd start your planning requirements plan now what do you do as part of the requirements planning you would first create your detailed project plan right so are our inputs to your project plan come in a requirements point of view right and then you know you also identify your your templates and then the document formats like the frameworks in which are going to capture the requirements and the tools all those are clearly identified as part of the planning phase of the project right but the major output coming out from your planning exercise is basically the the project plan so you you'll end up sharing a project plan something like this right so all your inputs to your functional requirements is something which will work outfit and then provide visitors I will come to that before that yeah let's let's go step by step right so that's a major output coming up right a detailed project plan and inputs to that you have identified your team members and all right so we the NIA slides we looked at the RACI matrix and and before that we are in find the key people in the project a chilled-out identified the key stakeholders your SME is the solution owner although the roles would have been identified you have worked out work breakdown structure and the detail the project plan which I just showed you you have also identified the various tools to you know understand them and document your requirements right so this would primarily be the output or deliverables coming out of the planning phase okay so what do we do generally as part of our purpose right so when we are coming over to planning right so we have to plan for these activities so you basically identify all the you know the requirements you'll understand all the requirements ok so how are you going to understand these requirements we have to plan for that so what kind of techniques are going to use now in the earlier sessions have mentioned that there are some 10 ways in which you can engage the customer to understand the requirements so we'll figure out you know what always about on techniques can I use and how to understand these requirements right then you would simultaneously document your requirements right so that's another you know activity that you do you would also ensure that there is a communication plan in place and the communications on where so that's another activity which falls on the rear faux-fur right and finally you would also do the testing they chose you in contribute during the SAT and then directly so that's another area where you onto this so primarily these are the four things that you would work on so your project plan also should reflect these four that you know should be there right now let's spend some time understanding how do we create the estimates right now you have a scenario where you're unloaded onto your project and you are asked to create a VPN project and for your requirements how are you going to do that I have a going yeah so the requirements would be based on communication or requirements like whom is it more of the communication coordination are just analysis based on the notion or see primarily what I meant is these are the four things that you would do right so you interact with SMEs understand the requirements right you would document again you would ensure that it's communicated to all the stakeholders and then it could be tested and so these are the four four activities that you would get involved in a project right so you will identify all the activities which fall under the gamut of the requirements so these are the four things that we do right now we have to create a detailed project plan for these activities right now because see if you ask the project manager how how much time would it take to complete the requirements right so he will have no clue right so he would take the help of the project of the business analyst to get these activities short enough so what I have understood is like we would be and behave we would be gathering the details or the inputs from the SMEs that is a subject matter experts and then we would be preparing they would be analyzing whatever is the information we have or the requirements we have gathered then we would document that into a BRD and then this BRD we would forward it to the same ease and the solution owner to validated and once it has been validated the PRD then it would be forwarded to them next technical team is that Caribbean very good summary I think you have clearly crisply summarized what is expected out of the business hours all right now at a high level yes we are we understand the process now what we are trying to do is we are we are trying to you know get to the next level of detail right when we say you know even before doing the you know understanding the requirements we have to create a plan right so you know there would be a plan something like this right so this man also has to be created now this is also one area where new would contribute you would create this plan for all requirement activities only not the complete project okay now so so so this activity would come under the planning phase of the project okay so if you look at this you know the the the six knowledge areas the first thing that we are doing is we are doing planning so we are identifying all those various stakeholders and we are creating a detailed project plan and once the plan is ready then you know the steps what you have mentioned you know what would be continued that you would understand requirements you would document them you would communicate them and then you would also test it hey all this would happen but before that you would have to create this project plan okay now how do we create that project plan so let's say let's take this example right so we were discussing about a mobile banking application now if the project manager comes to you and ask how much time would it take to you to complete these requirements how would you go about how would you approach to tell him that okay now if you take take me two weeks to complete these requirements and you know and these are the details right you have to be able to answer that question right now how would you create that so this is this is what we would be you look first you know breakdown our activities to the smallest unit right if yo have to do if you ask me you know how much time would you take to capture the requirements for let's say the mobile banking app right on the face of it it's difficult to answer right so I don't know I mean it might take 10 days of 20 days I don't know but if I actually know break it down into smaller tasks let's say you know okay how many features that your mobile banking application have let's assume there are five features so how much would each of those how much time with each of those features take like feature one would take you two days and feature 3 with a 2 you know 5 days so you're breaking it down and understanding how much time would have to spend to understand the requirements then you are also figuring out how much time will take to document your requirements right and then you would send it to the customer for review he would take some time to visit so you basically you know listing down or breaking down a bigger task of requirement you know definition into the smallest unit right so let me show how a typical plan would look like and then you know it right now yeah so typically if you pick up any project they would they would have these activities any project you pick up so these 5 steps would be there as part of all the parts right so you would first understand and document the requirements so this is a major component a lot of time goes into this ok then you submit it to the customer for review the customer would provide his feedback and then you would update that they've that feedback okay based on his review comments you will update the feedback okay and finally the the solution owner would approve the be added right if you look at it you know these are the five tasks which happen in any of the requirements activities first step you would understand and document requirements so this is generally done by the business analyst and this is okay then you submit the BRD to the customer familiar right so this submission so this responsibility is with the business analyst so it won't take any time for submitting it it's just a mindstorm that you know okay we have completed the requirements now the new it I'm giving the document to the to the solution owner right now the review of the requirements would be done by the SMEs and then the solution owner okay and who will update the feedback from them from the SMEs and the solution over which is coming in the the business analyst will do that and and then you know this is the cycle of feedback in our reviews and then the feedback would continue till all the feedback has been incorporated and finally the solution owner would have screwed the Vig okay so these are the generic five steps which should be relevant for any project you pick up okay now specifically what questions you want to won't be able to answer for all projects is the duration its how many days would each one of these activities take right if you ask for mobile banking application how many days would the requirement happen so I don't know but I cannot just answer it because you know it might have some 10 features 20 features this could change all right so how do we approach that activity how do we ensure that you know we break that into smaller activity and then understand it right so what you do so you will pick up that you know the detail functionality let's say there are five features in your application right so first the user comes in and registers then he would login into the application then he would check the account balance he would transfer funds you would also pay the utility right so these are the five features which are there as part of your mobile banking app okay now it's easier for us understand how much time would it take for each of these activities right so you say no user registration would involve like one screen and you know you'll enter these details and then you know what you would find you can capture the requirements into this similarly for logging up to the application I can do it into this for checking account balance functionality I met me through this so you're looking at each feature and then figuring out how much time you would take to understand and document the requirements right then you'll just add this up which will come up with to your total duration of their requirement elicitation one so within 17 days you'll create the first draft of the BRD it's you're adding this to 2 3 5 2 3 5 so everything would be around 17 days so you're finally coming up with this 17 days for understanding the requirements and documenting them into the be adding okay so from 1st of April to 23rd of April if you're excluding the the weekends 17 days to translate into this so 23rd April you are submitting the vrd to the customer right and then from 24 to 38 the customer the SMS and then the solution would provide their the new comments they will provide their feedback ok after that you you would start updating the feedback now these days is not would not provide you the feedback after five days and so on a day to day basis they will do so maybe now they'll start reviewing 1:24 and on 24th end of there they'll say you know what these two requirements make these changes and on 25th they'll give you another set of the path and changes that means to come on a day to day basis they can give you the details so you will update the feedback maybe from 26th or 25th and then continue it for like let's say 8 days ok so if you by 5th of May you you should be able to close out onto the BRB ok so this is how a typical you know plan for your requirements would look like okay now the tricky part is who to identify the efforts for each of these activities like otherwise no the the this past standard you first understand and document you would submit it for review the client would review you would update the feedback and finally the client would approve the recipe Adi okay but the the details about requirements look at the scope and identify it from a feature wise how much time is to take and then you know update it and then work work you know from a bottom up approach to figure out how much time it would take to complete this actually let me understand one thing you said for you know user registration it takes like two days like in what sense it takes two days like do we have to read something and like in two days on that one feature like what you doing really I really draw in the standard yeah so there are two things to it right so first thing your experience will tell you a little bit and since now at this point in time you absolutely have no clue how to understand the requirements and how to document it also right but once you once you complete that part once you understand how do you engage a customer what all details we need to capture and how do we document it right so that gives you some basic understanding okay know what I have to actually understand the whole process have to figure out water yourself to capture I have to design the layout of the screen then I have to you know have that discussions in the customer right and then finally have to document it so this whole process might take me a couple of days right so some of this functionality you'll not even you know for some of the projects there could be some features which will not even understand right so let's say you know this instead of a mobile banking app this is let's say credit oppressive system right now we don't even know what credit appraisal would be right so in those kind of situations we would engage the SME so it may be no ask him to broadly categorize the requirements so is it like complex to complex how much time we'll take so we'll take that input from the SMEs also to create this view okay so there is no hard and fast rule that you know that you know this feature would take you so much time and again it differs from person to person also if it's a you know very senior business analyst you might do it in a day right if it's a rookie it might take you maybe two days or three days as well so a lot of qualitative inputs which point so but based on your team's understanding and the best fitment you do try to know create ahead plan know if you don't have this view if you don't have a plan it's very difficult to gauge the progress of of what of where you currently are right now if somebody asked comes over and ask you on let's say 7th of April how much of your requirements are completed right you won't be able to answer unless you have this plan right so let's say you have completed first one and two you could say no what we have completed like four days of effort out of 17 days so maybe you know we have worked around some you know 20 22 percent of our project is completed yeah you know my question is you know for say for example user registration you're taking two days right so what kind of efforts you put to do you know that you use a registration documentation but to like what you do they're just you know you took an example of like City app or something like could you please explain explain like what you do I mean so see for that you need to understand you know how do we get English and you also have to understand the wave you would document so you'll be in a much better position to answer that question you know understand those topics once you complete the course right at this point in time we don't know how to understand the document or requirements so okay I would say no you have to write a use case for this right so use this will take you a day and then you to engage with the customer in a prototyping session to understand the requirement right so that might take you at least three hours and then figure out how the final product would look like a final screen would look like and then there might be some feedback coming in from the customer so I kept like another half a day for that right so overall you know based on my experience have put in that two days right so like I said it's there is no one scientific approach and there is no one estimate which could be irrelevant for all businesses so maybe you know if somebody who's new to this overall role of a business analyst you might actually take three days right so when I'm planning I have to consider all these factors to consider the experience of the business and ease the complexity of the requirement right and what and and you know I will try to visualize now what are the steps involved in this how many screens are involved and you know user registration with involved two screens one screen would capture the details and then there would be a back-end logic program which would have to you know make some validations and then you know you would finally confirm it so it high-level I understand the functionality but the details are not there yet what all the let's pick a another example I think login would make much I mean you tend to understand this you know for capturing the requirements right now if you ask anybody how much time will take to understand the requirements about login screen say what is there in login screen right it's just you know you enter your user ID password and then login right there's no team no need even to understand the requirements for that right so that's because you know people don't understand what are all the details that you have to capture now for the simple example I can login functionality right now I give you some reasons where it would take you time to capture the details right now what is the security mechanism if you you know you're putting into for the login functionality let's say the user enters the password incorrectly for three times should-should you log that user in case if you log it what is unlocking mechanism right and what should be the you know the the password policy like what should be there you know the you know most of the organization's would have those password policies but you know it should have a capital letter the special character right so unless you ask these questions the customer is not going to tell you the requirements okay so and then you know what happens when somebody you know when you're you know subscription fee is expired should you automatically log you know disable the user ID of only when when sir when the user price to log in that is when you should disable there are multiple things that should actually you know come to you when you are trying to understand the detail because it might just look like simple thing that you enter your user ID password and then login but you know you have to figure out what are all the error messages so what is the error message that we have to display when the user ID is incorrect or when the password is incorrect or when the user ID is not all these have to be agreed to be the customer exactly that this is the message it should be displayed and then you have to design the screen that this is how your customer screen would look like when you enter venues or any password this is how your screen would look like you have to do those wireframes so there are a lot of things that you will have to you know cover even for small functionalities right all the details you will be able to appreciate once you learn about the requirement elicitation techniques and documentation difference for now since you we don't understand that we will not be able to you know relate to why it would take us a couple of days but I think once we complete the course and then revisit this topic then you say know what okay now since it involves all these activities you know what can a summarize like what I have understood as per you explanation because I just want to make sure that I have understood it correctly well in this process we as an be a we make sure that the requirement elicitation and documentation it can be done in following this like you know requirement elicitation what a beer does he usually prepares and you know he collects all this information to be put into the documents by various techniques like you know like analyzing all the documents whatever he has going through n number of websites of the current existing application then you know talking with the SMEs and every other people and then based on all that and based on the current what was a current state of the business he will understand that exactly this model is currently like this and this is what has been expected so as is and to be and then based on that he will try to figure out that this existing model might take this much of duration for each and every application to be developed and then accordingly he will add this number of days and then based on those days what he has added like for example you have added over user registration so registration means the current existing functionality is like this and two V whatever like you know eighty twenty percent twenty percent since this changes has been needed so then based on that he will incur this figure out how much time to take you're right this is based on our experience or maybe how many screens it has and how much time is to take so you know there are multiple ways of doing it right I you know maybe now I'll also explain you about the estimation technique in tomorrow's session but yeah broadly we are figuring out the detailed activities and the time it would take to complete those tasks now how did you arrive at these two days and five days you know at this point in time maybe you know you'll not be able to answer that because you don't know actually what is how are you going to understand and document the farthest right so that's one step where you know the good you'd have to you know take on the face of it for now but once after you complete the course you would have learned the ways in which you document and analyze and document the requirements right so after that I think you'll be in a much better position to answer the same question and then say okay no this takes you two days because it involves activity 1 2 3 4 5 first understand requirements understand all the scenarios then you have to design the screens so these are these activities might take me two days to come so that is how your estimate should be arrived you said like you know 25 days for these so these 25 days are to prepare the BRD and get approval yes so once this is approved and it goes to the manager right that's what it is so so the olution owner it goes to the solution on owner for review okay would review it and provide some out feedback so you'll make that changes to the BI be okay and finally the solution or know if he is happy with the VAD you would give a formal approval he will sign off and then say I agree to these requirements now please go ahead at and design and develop the system so and then it goes to the manager right I mean the technical team the architect would start designing the system so that would happen after the BR they actually stick okay okay so um you know the estimation of time like you know say you know to develop you know these features you know like how I mean like how it is fine for the technical team are they going to specify their you know time you know like say for example you user registration so are they going to specify the time again for their own inputs right so then there would be a detailed design phase and then there would be customized so whatever they are doing they will give their inputs I'm so in for for designing the system it really takes so much time so whatever time lens we have given is only for capturing the requirements only the task it is these that we would be doing okay Thanks so I think I'll give you a little more detail and context to how do we go about estimating the products and all in tomorrow's session and then we'll more