My name is Angelo Kalevela and my goal is to create short videos to provide guidance and tips from my own career as a business analyst and UX professional to help you progress in yours.
Contact Me If you have personal/specific question and want a personal direct response (may still anonymize and make a video to respond) use Facebook messager or LinkedIn - facebook.com/metabusinessanalyst - or directly in FB messager m.me/metabusinessanalyst - www.linkedin.com/in/akalevela
To see a video response to your longer questions - www.metabusinessanalyst.com/contact-angelo-the-ba/
The advice doesn't change really. It's about tailoring the story of your experiences have led you to a systems analyst job. In IT there is some much role overlap depending on team structure, that roles like Business Analyst, Systems Analyst, Proj. Manager, etc can easily jump around depending on aptitude.
hi, ive been hired as functional analyst but its focused on the implemention of sap and manage processes (learning them, how to develope them with the implemention of the erp or other softwares) I thought this role should be called more Functional business analyst. Any suggestions?
A "function" is typically referring to a function of the business. So it's redundant to call it a functional business analyst. A functional analyst is a specific kind of business analyst (domain specific business analyst). Ultimately, you can call yourself whatever makes you happy because as mentioned, it's more about the work you do and expertise you develop vs the specific words used in a job title.
Are most big aerospace, medical and nuclear companies using Agile or Scrum? And how does it affect the software development process? I'd like to move away from the rapid-prototype style to a more formal environment.. perhaps not for FAA/FDA/DOE approval, but to develop high quality/safe products containing embedded software.. for any industry.. aerospace (like Lockhead's SEAL Level X, Boeing , DDPMAS etc) , Medical, or Nuclear industries. I'd love to see a trivial example that shows all the steps and outputs. For example, assuming I document the process on how the code is generated, what constitutes proof that it's safe? Static Analysis? Code Coverage - Statement (Level C), Decision (Level B), MCDC (Level A)? Who defines the unit tests? I imagine there are differences between the industries.. FAA : DO-178X , DO 331 , ARP4754A , ED-12C FDA : 13485 , ISO14971 , IEC 62304 , SaMD and DOE : 414.1x, but what are the typical tools/software needed, and the typical document/artifacts in the various stages of the software life cycle? I saw a good video by CEMILAC Education Program "Airborne Software Development & Certification Process" and it's a bit overwhelming: Requirement Management - (IBM Ration) DOORS, JAMA, Xebrio, rmtoo florath , doorstop-dev / doorstop , reqview Static Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , sonar cloud, veracode PREFast Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Configuration Management / Storage and Version Control System - Git, SourceSafe, Mercurial, MS TFS QA - Helix ALM (I)V&V / Test Automation - VectorCAST, LDRA Testbed , Mathworks Simulink DO Qualification Kit Continuous Integration / CD - Continuous Delivery/Deployment And what is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? Also, how do CPLD and FPGAs fit in to the embedded software picture.. since not exactly software nor hardware, since they are programmable devices written in an programming language like VHDL , (system) verilog , Amaranth HDL ?
Scrum and SAFe are about how you develop, not what you develop. A waterfall team could develop the same thing as a SAFe or SCRUM team. It is not a "standard". The choice to use agile is more about the organizational culture, not any specific industry. You may find some aerospace organizations that embrace agile and some that don't (Google it). That is true for basically all the questions you asked. Open source might mean "easier to find people who understand how to develop on the platform" ... non-open source might mean you find people more specifically trained/certified on the platform which helps in hiring confidence. Some platforms might be better configured to recognize, administer, and facilitate following certain industry regulations or standards. Are you specifically hoping to go into these highly regulated industries?
Ive been confused. Contemplating if as a an Agile business analyst, i should get certified as Scrum Master or as a Product Owner. I guess Product Owner it is !
Product Owner definitely more closely aligns 1-to-1 with the Business Analyst skill set if you enjoy that work. You often see BA experience listed as relevant experience for PO roles.
🎯 Key points for quick navigation: 00:00 *Why Business Analysis Videos Avoid Specificity* - Business analysis is about understanding the nuances of a specific situation. - Providing overly specific examples can hinder your ability to adapt to your own projects. 01:37 *Importance of Understanding Business Nuances* - Businesses evolve over time, and failing to consider these nuances can lead to failure in business analysis. - A successful business analyst considers the unique aspects of each project. 02:06 *E-commerce Integration Project Overview* - Business Analyst integrates e-commerce platforms of two companies (Enterprise X & Company Z) acquired in a merger. - Project aims to minimize disruption to existing customer-facing platform (Company Z). 03:01 *Business Analyst Approach* - Focused on functionalities of existing application (Company Z) to determine data needed for integration. - Collaborated with stakeholders and other Business Analysts to ensure data alignment with order management systems. 04:00 *[invalid URL removed] Importance of End-to-End Testing in Large Projects* - Business Analyst learns the importance of end-to-end testing through a negative experience in a large integration project. - Siloed teams making independent changes to different parts of the process create a domino effect of rework. 05:55 *[invalid URL removed] Impact of Complexity on Integration Projects* - The number of teams and order types involved in the project significantly increase the complexity of integration testing. - Each change requires revisiting upstream processes to ensure data compatibility throughout the entire chain. 06:24 *Challenges of Distributed Teams in Integration Projects* - Communication delays due to time zone differences can significantly slow down development and troubleshooting. - Unclear requirements from Business Analysts can lead to rework for developers waiting for clarification. 07:20 *[invalid URL removed] Lessons Learned: Collaboration and Proactive Communication* - Co-locating teams can improve communication and reduce delays in large integration projects. - Business Analysts should trace data origin and processes to ensure compatibility during integration. - Proactive communication across teams and up the chain of command is essential to identify potential issues early on. Made with HARPA AI
@@AngeloTheBASure. I understand you are doing it from a SAFe perspective, which is fine, they can have any perspective they want. Agile/scrum founders would disagree on that scaling and relationship perspective though. There are so many misunderstandings on what Agile/Scrum is, and not going to the sources just makes it worse.
Good video; obviously before the latest Scrum Guide fwiw. Some thoughts. - Some people try to make a BA a 'Developer', which is too big a stretch. In practice, most of the work they do will not contribute to the current Sprint Goal, it will contribute to the Product Backlog. I can conceive of ways it could be otherwise, & maybe the BA should infact 'learn to code' (ha!) and join the Developers. But this is rarely proposed. - There can be only one PO on a team. Some of their responsibilities can be delegated, but that does not make the person to whom the responsibilities are delegated part of the Scrum Team. A lot of BAs will not be able to actually do the PO role - it's an extrovert role in most orgs, put cruely, & BAs are usually introverted. - A lot of the tasks the Scrum Master is given by the Scrum Guide can be, and often are, performed by BAs in practice, but probably not all of them. I'm not a Scrum Guide purist, but I think it is a good idea to see what the Scrum Guide says as a foundation for subsequent decision making.
This is very useful thank you for sharing .. however regarding the Glossary on confluence .. what information should be populated in the glossary.. should the Glossary contain only information (Acronym) related to the project at hand or some of the key BA Acronym in general? I look forward to your response
A glossary is relevant to a body of work or domain (requirements document, instruction manual, product/project confluence page, finance dept, accounting dept, etc). It should include any term used in the body of work or domain that might not be clear to someone trying to understand that body of work or domain.
I suppose it's because I enjoy the problems solving process. My favorite books growing up were mysteries where as clues present themselves you create a picture that solves the mystery. BA work is the same, you interview, you learn, you analyze, you help others connect dots but instead of solving a crime, I discover a great solution.
This was very helpful and straight to the point you really showcased the sacrifice and effort you’ve made with simply putting this together. Thank you. Well done.🎉
I want to ask is the User story a part of Agile? I mean in every agile is there a user story? And when BA write a user story and documentation please explain
New domain is any part of any organization for which processes, data, & systems exist. Some example might be be Human Resources, Marketing, Sales, Supply Chain in most business organizations, but could also be systems for registration, class management, etc in education or patient management, record management, etc in medicine and on and on.
It can vary greatly and even change within the same company as new frameworks emerge. However all the frameworks work to solve bits and pieces the challenges faced by all IT organizations so knowing any will help you navigate and understand the challenges. Similar to how understanding the scientific method might help you not make incorrect conclusions/assumption even if you aren't conducting true science experiments. ITIL and COBIT are good ones to look into.
Nothing has to come before becoming a business analyst. Management of Information Systems (Business Majors) are often hired directly into the role. Domain subject matter expert (business users) who develop the right skill set can become BAs. IT professional (Developers, QA, Support, etc) can also transition into the role if they can demonstrate the skill set
1. what are some things i can work on at home that i can then present sometime during the interview that will make the hiring manager more likely to hire me as a result of such presentation as i try to break into BA from retail.
Honestly not much. Data modeling, process modeling, data visualization... but If you're being interviewed without direct experience, they are looking for the soft skills that will be more easy to practice and demonstrate at work. Communication, teaching, learning, dealing with difficult people, organized, motivated, driven, etc. This playlist might help ru-vid.com/group/PLHMx3DEmTag8R8ZgxA8KIVxrgyYBRbOyH&si=3Mk_KCJrwSQucPb1
I’m taking courses in BA and I would like to learn more about BRD but where I can a sample of companies document which includes the vision or the requirements before the BA start to document it
There are a variety of documents that could come before a BA is engaged, although often senior BAs are a part of creating those documents. A business case is likely the most generic term and might have a business capabilities analysis, SWOT analysis, financial analysis, etc. In Scaled Agile, it might be an epic hypothesis statement. I cover many here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CJL2k5ZOjno.html at a high-level, which might help you do additional research.
Agreed, Angelo! I think the people aspect is why business analyst work can’t be replaced by AI. Learning to navigate the organization and its people is a huge part of it. Avoiding stepping on political land mines is something I’ve learned along the way
