What Is A Business Analyst? SIMPLE EXPLANATION!

It's an IT department okay, and we have a business ok and I like to call it parties I just feel like it goes better, but you can call it whatever we have IT, and we have a business ok IT folks obviously those people do code you know they are professionals and the company knows their IT infrastructure is managed by this team -IT business are the stakeholders who make all the decisions about the business you know what the right steps are etc. so once you understand these two groups and every company has an IT department, and they have business parts almost every company this is where be a spoon okay, so a business analyst comes right in the middle of this okay because what is a business analyst a business analyst is a mediator between for IT department and business stakeholders okay their job is very simple these two people who can speak to each other speak a different language IT speaks' technical language. And business speaks business language the business analyst will speak and interpret what business says to them in IT language ok that's right that's right, so it's a communication between business and IT ok business has something I want to tell IT people that you will be that person right, so people are gone What do they mean when they say that the connection between business and IT is right? Let's say a health company or anything in the way you should not know an IT company but if every company can have an IT department it should not be a particular IT company but let's say you have a health company and this military company this so, and I'm a visible person I hope you are too, so you know I can't even draw well let's just go it should be a cross, but you get my point we have a health company okay. And basically they make software so let's make an IT healthcare company they make software that doctors use that you don't use in hospitals, and they have this software ok, so I'll draw a screen here this is their software. Web page and everything is fine so this software as I said is used by doctors and nurses and so on with this company when it wants to make updates to this software, so let's just say the front is right, and they want to have the new web page they want. Building a new and old web page is outdated, and they want to destroy it and new ones go making it much easier for doctors to be able to enter information with a single click ok you get my point to be successful they want to improve this page well if they want to improve this page they will have more people including business analyst in this example what will happen business will continue to think what it really wants in this ok I'm a participant ok you know I want you to know on this screen the many dropdowns I want these many you know buttons I want verbiage here I want these buttons out there, so businesses can think of all these things ok so once they come up with those things BA has gone to business stakeholders and collected those needs so that key word here is that we are going to write down, so you know this is right you want to know what BA does this what beauty is what needs right requirements is what I told you here these changes are needed now about jargon of needs and what they are. We can get into that but most of the time those are the requirements so as we know they will be the needs I mentioned before BA goes to business stakeholders collecting those needs and this is where BA should ask questions they need to make sure things make sense hey he said you want to know this double lets' expand and make you know this way so all those questions are asked. By to be DBS made sure something is not forgetting hey you forgot this part you did that and so that's when someone came in asking those important and businesslike question's oh yeah you're right I forgot about that and exactly those needs. They will be held BA will write them in the right way if you know, and we will get into it slowly but stay with me here there are mythologies BA works in agile methodology they will write user stories hope you can see this business is ok so that's where they put their needs ok most companies move on agile, but you can still write BR these and once those requirements are written now we dedicate them to IT and said here go needs and continue with the code ok and that's what IT will do then by hand, but the work does not end there because if they have any questions if they have any concerns they do not understand something oh they come back to be ok write this on requirements what do you mean you know I explained if BA is good they will write their cases in a way where there will not be many questions and that stop being a good thing because that means they understand the requirements so repeating the BA gap closes. The gap between IT and business because they speak two different things