Business Analyst Training for Beginners: How I Manage Requirements

Рет қаралды 18,733

Күн бұрын

In this Business Analyst Training For Beginners you are going to learn how to manage requirements.
The technique explained in this Business Analyst Training For Beginners is going to help you to keep your requirements maintainable and traceable.
This technique contains information on how to manage requirements, how to engineer and structure them. Furthermore this technique is a solid basis for requirements gathering techniques, especially for business analysts.
Time Stamp:
0:00 Introduction
0:50 Requirements Hierarchy
3:19 Excel Template
8:53 Real Life Example
Keywords:
Business Analyst Training For Beginners 2020,
Business Analyst Training For Beginners 2021,
Business Analyst Training for Beginners,
Business Analyst Training,
how to manage requirements,
requirements engineering,
requirements management,
requirements gathering techniques,
how to gather requirements as a business analyst,
business analyst requirements,
business analysis,
requirements gathering business analyst,
Requirement Gathering Techniques For A Business Analyst (2021),
business analyst requirements gathering,
agile business analysis,
========================================
By Using one of my Affiliate Links you do support this channel financially without having additional costs! Thank you so much in advance.
Links available here: beacons.ai/theagilebusinessan...

Пікірлер: 40

@nwokolodonald3394 3 ай бұрын

This is the best video I have seen. Can i subscribe 10times. You’re my one stop requirement tutor.

@evelyndye5560 2 жыл бұрын

This video is really good. One of the best I've seen on requirements gathering. Thank you

@theagilebusinessanalyst 2 жыл бұрын

Thank you for your feedback! Great to hear that you dive deeper into requirements gathering techniques.

@rhinavillanueva4762 2 жыл бұрын

Thank you so much! Very clear and really helpful!

@theagilebusinessanalyst 2 жыл бұрын

Appreciate it! Happy to support :)

@Njooo5 Жыл бұрын

Thanks a ton Love your work

@tochukwunjoku 2 жыл бұрын

Thank you for this video - very helpful!

@theagilebusinessanalyst 2 жыл бұрын

Great that I could help you out :)

@hanankhogali1589 11 ай бұрын

Thank you, 😊, really appreciate it

@ltgemini1599 2 жыл бұрын

I need this! Thank you.

@theagilebusinessanalyst 2 жыл бұрын

Happy to support :)

@meetelugubuddy..incanada4010 2 жыл бұрын

Really organized and easy way to understand for beginners

@theagilebusinessanalyst 2 жыл бұрын

Thanks for the feedback!

@CoCoTheInvestor Жыл бұрын

Very helpful thanks

@abrjay Жыл бұрын

Thank you for the video. A video suggestion on "how to manage stakeholders" would be great. thank you

@devinathanb3620 Жыл бұрын

Was very helpful for me, thank you

@theagilebusinessanalyst Жыл бұрын

Perfect!

@khalidmemonazeemi6620 3 ай бұрын

Wonderful

@Sourabh_neg 2 жыл бұрын

Very informative... Thank you so much for the video...

@theagilebusinessanalyst 2 жыл бұрын

@gilbaki 11 ай бұрын

really helpful

@errechidnezha7742 2 жыл бұрын

Thank you for the video

@theagilebusinessanalyst 2 жыл бұрын

You're welcome :) !

@lorenzzo8346 Жыл бұрын

Good evening Stefano. Very concise content, thank you for putting this together. The only question I have is: in the "Excel Template" section you explained that if the requirement wa in the user story format we could put it in the 'description' field, however, later in the video, the aforementioned user sroty format is located in the 'Title' section. Does that have an impact in the later management of the requirements? As always, thank you.

@theagilebusinessanalyst Жыл бұрын

Hey Lorenzzo 👋🏼 You‘re right. Nowadays I would suggest to keep the title short, Meaning a couple of words, e.g „client overview for red flags“ and then in the description I‘d enter the user story, e.g. „As a compliance officer i want to… so that…“. If you put it in description or title has an impact if you use JIRA as a requirements management tool, but if you just use the excel then there is no impact, just the way of presenting it. Thanks for bringing that up!

@wendybunton5823 Жыл бұрын

Good evening from.Tampa, thanks a lot for a great explanation. In which cases solution requirements is not write down as user story

@theagilebusinessanalyst Жыл бұрын

Hey 😃 I‘d use USER STORY if its a user requirement, meaning something involving user interaction with a user interface. More technical requirements for APIs for example, I‘d use GHERKIN.

@Njooo5 Жыл бұрын

Can this be used for advanced level requirements gathering? Your thoughts on this?

@joeyvillaceran6204 3 ай бұрын

If I can relate the Business Requirements, if I am correct - this are Epics in JIRA, solution requirements are more of a User Stories. Am I correct?

@lotannaagbaegbu4238 Жыл бұрын

Thank you for this video. How do you document the change log on Jira? Also, what certifications would you suggest a BA gets

@theagilebusinessanalyst Жыл бұрын

For change logs, you could use the comment section in a jira. Or if the requirement is already closed, creating another one which is linked to the original jira story. Or you could use a confluence page. Confluence Pages have a version History. Certification I recommend PSM 1 and PSPO 1 from scrum.org to demonstrate agile methodology skills. On top any project management certification is a great plus and also IIBA business analysis.

@nwokolodonald3394 2 ай бұрын

makes sense, but you forgot ti share the template with us. thanks.

@akshayrohit270 2 жыл бұрын

is there a specific fixed time interval to complete the process of requirements gathering

@theagilebusinessanalyst 2 жыл бұрын

In the waterfall approach you would have a phase for gathering requirements, e.g a couple of weeks or months depending on the complexity. After this phase then the development phase would start. But in an agile approach, e.g via Scrum, gathering requirements is an ongoing activity. We gather a requirement, develop it, get feeback from the stakeholder and if needed gather again a requirement which is more refined than in the iteration before. So we are building increments each iteration which come closer to the desired solution. Hope that helps :)

@akshayrohit270 2 жыл бұрын

Is it essential to know agile methodology for a business analyst as there are big players in the market adopting agile?? If yes, being an aspiring business analyst where can I learn the about the methodology ? Can you suggest some sources?

@theagilebusinessanalyst 2 жыл бұрын

@@akshayrohit270 Agile is becoming more and more key, replacing waterfall in many industries. Agile Know How is partially already a prerequisite in business analyst job descriptions, so worth learning. I recommend to get a first understanding to watch a couple of videos, e.g here on youtube. Inform yourself on „What is Agile?“ ,“What is Scrum?“. After getting a base of knowledge, you should get familiar with the content on www.scrum.org. On top, inform yourself about the roles Scrum Master, Product Owner and Developers within Scrum. All that should give you competitive know how. If you got 200$ left to spend, do a certification on scrum.org, e.g PSM 1 exam. This certification is often preferred by employers and verifies your knowledge.

@CC-yw3kn 2 ай бұрын

@@theagilebusinessanalyst do you have a topic about iteration :) wanted to see how this is and if the requirements are changing, that impacts delivery of product right? so how is this done?

@derespektan3980 2 жыл бұрын

What's that effect in the voice?

@0529kah Ай бұрын

Wouldn't it be easier to first come up with solutions requirements first, then determine the business requirements?

@theagilebusinessanalyst Ай бұрын

If we start with solution requirements, we could end up spending time drafting a solution requirement which in and of itself may be great, elegant and efficient, but not what actually is needed by the business. We only want to build solutions for the problems we have. Some products on the market are great but go out of business, because they solve a problem no one really has yet. Start with the true need. IT follows Business, not Business follows IT. Hope that helps :)