Thanks for the support. Are there any topics that you might find especially useful?

@ anything BA related perhaps on how to grow, like courses or certs. Thank you! The way you explain is some of the best! Can’t wait for more, best

Yup - kzbin.info/www/bejne/l2e9i4qloZiKgNU

Great question. Design thinking is for any role that charged with solving problems. For UX designers it is just expected that you are solving problems this way. In the same way that you can use the scientific method to determine which laundry detergents you are allergic to (variables, controls, etc) to get very clear results, but you don't have to. However, it is expected that a scientific researcher is properly using the method. It may not be mandatory to use design thinking outside of "designer roles" to solve problems but anybody who uses design thinking will yield better results (Designers, Product Owners, Product Managers, Business Analyst, Engineers, Inventors, Consultants, etc).

Yes. I do mention in the first 30 seconds that MIS is the most straightforward path to a business analyst role. Business Analytics depends on the person as they may be more geared towards Data Analysis types of roles and not all BA roles are data heavy. As a BA manager with an MIS degree, I would not immediately discount other majors over MIS especially for an entry level role.

@@AngeloTheBA Thanks

This is a template for what YOU should capture on YOUR project. The kinds of questions you should ask, the kinds of things you should be thinking about. Most companies who require a BRD will have a very similar template for you to follow and I have used this structure before a few times. How well it works in the real world is dependent on your ability to think through and capture information fully and accurately

I'm glad you found it helpful!

Good Luck and feel free to let me know what other kinds of information you might find useful in your transition.

Thank you. It should be noted that because I'm making BA videos like this, I'm probably pre-prepped in a what that most people are not.

1. "Easily" depends on your and your skill set, but many organizations hire entry level graduates less based on their major and more based on how well they demonstrate capability and motivation. 2. Excel (Data analysis, transformation,and visualization), Process Modeling, and SQL are a few things you can get into to show you're motivated to becoming a success BA.

@ thank you, any thoughts on 1- R 2- PSPP I’ve heard they’re essential for a business analysis but not sure about business analysts, any advice would help

@@abcd-u3s4v For business analysis, no, for business analytics maybe.

Not on my team specifically but I've seen it happen with colleagues. I would expect coming out of that field there would be a lot of skill that are already built up (data analysis, critical thinking) so I would be looking for the skills that make you an effective collaborator. Conceptualization, visualization, facilitation, communication, etc. Honestly, a pretty easy transition especially if you plan to be a BA in the accounting or finance domain as that subject matter expertise is super valuable.

@ thanks for your input

You don't have to imagine, you can just watch the rest of the video and let us know.

I have not gotten to that point yet. Do you think I should?

@@AngeloTheBAyes

Here is part 2 - kzbin.info/www/bejne/hl66Y4ela8-Ao6csi=6VHTQtSNslKlorgx . KZbin should have recommended it at the end of this video

⁠@@AngeloTheBAthank you so much …I’m preparing for my ECBA exam

It's about relatives not absolutes. Waterfall is not agile, SAFe is more agile than waterfall, having a fully organization bought into the agile mindset is the most agile. Just like exercising doesn't make you an athlete. Sitting all day isn't athletic, exercising a few times is more athletic than sitting all day, training to be mentally and physically more capable than others in a given sport makes you an athlete.

@@AngeloTheBA The thing is no one truly uses waterfall anymore, certainly I haven't come across it in 25 years of software delivery, so relatively speaking it is worse.

@@shazoids My company still uses waterfall (we're in transition). Nimble modern companies use agile. Some industries struggle to evolve. SAFe Aims to bridge the gap for companies unable to make the leap. We're actually not using SAFe, but I studied it because it was our original plan.

@@AngeloTheBA very very few organisations are truly waterfall, they may be lean more towards a structured methodology. There is no case to build a SAFe delivery framework, none of the principles are up held. It's good for big agencies who can scale up and charge for more squads and clueless C-Suite who can stroke their egos. It is a total waste of time, a whole load of effort for a whole load of not much.

@@AngeloTheBAI have joined one leading telecoms company in the U.K. which used Safe to absolute appalling affect. Beying shocking. There is no where which is better of using SAFe, it’s costly, unintuitive and doesn’t work. Not ever.

If you mean how I'd handle a person who is interviewing me that is being difficult, then it would be by being confident in what I know, honest about what I don't, clear about the value I can deliver, and also question them on how their organization would be good for me.