How to Write High Quality Business Requirements -with Examples!

This video gives you examples of How to Write High Quality Business Requirements, We discuss good business requirements vs bad requirements so you can have practical exposure to how to write high qual
#requirements #businessanalyst #businessanalysis #iiba #karaleise
The business requirements document is the artefact used to document software requirements. How to Write High Quality Business Requirements is infused with how to write the business requirements document.
This video takes you through How to Write High Quality Business Requirements with examples and describes what makes a high quality business requirement. In it, I share concrete examples of good business requirement and bad business requirements and explain the principles to apply when you write your own business requirements document.
Watch more about business requirements in the playlist: "All About Requirements"
Also watch:
What are business requirements - • What are business requ...
How to write business requirements - • How to write Business ...
Are business requirements only waterfall? - • Are Business Requireme...
------///----
Hi I'm Karaleise and I have over 10 years experience working as a business analyst and I help people to start and grow their business analyst careers.
#businessanalyst #businessanalysis #scrum #agile
Get the Business Analyst Job Market Report here: www.bajobmarket.com
or buy it on Amazon here: amzn.to/3p9sM2m
Schedule an appointment with me here: karaleise.com/book-a-call/
Listen to this on my podcast here: bit.ly/3ABkBRH
Get more resources on my website at: www.karaleise.com
--//--
This channel covers the business analyst career.
You can find help here on business analyst interview questions and answers
• Business Analyst Job I...
Get a look into business analyst day in the life
• A Day in the Life of a...
Find out about business analyst roles and responsibilities
• What is the role of th...
• The Business Analyst J...
• Business Analyst Train...
You can also answer questions on business analysis skills and job opportunities.
• Business Analyst Train...
I have done videos that help you prepare for the business analyst interview by giving you the questions likely to be asked when looking for a business analyst job.
• How to prepare for a b...
• Do These Things on You...
There is resume help so you can refine your business anlyst resume
• How to Write Your Resu...
Also business analysis case studies and how to take a problem and apply your business analysis skills to solve it
• This is how you create...
• How to Design a New Pr...
And a whole lot more... Thanks for watching Karaleise | Business Analyst Training!

[@missk.2507]

I'm in ATL too, so i'll like the video..and plus it's great content :) !

[@toulaishsharma9255]

Phenomenal content my dear. You are killing it!

[@frankadodo1113]

Great video, I found this very educative and useful. Many thanks Karaleise. You just added a new subscriber 👍🏽

[@raginiprakash9300]

Great video...very helpful. Yours is the best channel out there for BA. Thank you so much, Keep up the great work. God bless!

[@karaleise]

Thank you Ragini! Please check out my other videos in my free business analyst courses: karaleise.com/business-analyst-free-courses/

[@DevsLikeUs]

Great content, these are very important skills. Thank you.

[@lindaokpara4377]

Thank you for this content!

[@ashi1165]

You are the best Karaleise 😍

[@drishtydcosta2330]

Sometimes it's really nice to get to the point of the topic

[@poonamgupta5715]

great one

[@wisdomseeker3937]

So useful thank you

[@allsmiles3281]

Thank you!.

[@biziilo1669]

Thanks for this

[@khusimhlanga]

Just wanted to say that your content is amazing! Watching all the way from South Africa 🇿🇦

[@Merrickul]

Thank you for this video, it was very helpful for writing my business requirements. 😃

[@karaleise]

Thanks for watching! 🙏 You should also download the free templates at www.karaleise.com

[@TheTruthSeeker756]

I can see that Feasible item being an issue. Because a lot of the time you will be depending on the technical competency of the client right? Like who do they have for software developers. How do you know they can handle what you want to do? Can you comment on that?

[@Cloaker3269]

I appreciate how detailed requirements should be. This gives me the impression though that building a website for example will run into 100s of lines of requirements. In your experience, when you create requirements to build an entire website, does this generally result in 100s of requirements? If it does, do you really write all these in your BRD Word document under your Functional Requirement section for example? Does your stakeholder actually review all these requirements and approve these? Also, do you group these requirements and put several requirements together in a ticket for a developer to build?

[@karaleise]

Hi Dragon, thanks for watching the video and thanks for supporting the channel. Your question has a lot of concepts mixed together. Firstly requirements aren't measured like code- we do not refer to lines of requirements as we do lines of code. Depending on the functionality of the website, yes there could be hundreds of requirements but you would make this consumable by putting them in categories or grouping by logical workflow. Secondly the way you deliver requirements to your developers depends on the software methodology you use. Typically we do not write requirements document (waterfall) AND user stories (agile) on the same project.

[@karaleise]

I think where you get confused is in the interactions between the stakeholders and the development team and how to handoff to them. Let me clarify that for you: typically you meet with your stakeholders and get their consensus on the design and functionality of the website before you start writing detailed requirements. The clients need to have enough detail on what the final deliverables will be and what to expect. Once that is agreed upon, then you write detailed user stories (agile) or detailed BRD (waterfall). The client does not need to approve every single detailed requirement that you may put in your BRD or user story because they already approved the high level requirements from the earlier discussions (unless something drastically changed since). When you deliver to dev you need to make each ticket as independent as possible, each one delivering value to the user. You should generally NOT mix several high level requirements together in one ticket. You'll need to figure out what is the right level of detail for your tickets and you can discuss that with your dev team. Hope that helps!

[@Cloaker3269]

@@karaleise this is absolutely helpful. That is actually where I was confused because I thought the client would have to see and approve the very detailed BRD (waterfall). This makes a lot of sense. Keep it at a specific level for the client for approval and then go into the nitty gritty for the devs. Thanks so much for clarifying.

[@TheTruthSeeker756]

And then the client signs off on this?

[@harikc872]

Very Informative ...btw..i dont find any example in this video like How to Identify Business Requiremnt and Functional Requirement from the Client Information in a project...can i get the help?

[@karaleise]

Hi Harik thanks for watching the video! Here is a video on how to elicit requirements: kzbin.info/www/bejne/f5WrqZl9jZJ_iqM and another one on how to write the requirements document: kzbin.info/www/bejne/op27d4Sglthqabc Hope that helps!

[@harikc872]

@@karaleise hi madam thanx for sharing another one .....if i have a doubt in BA Req Gathering can i post to you ...which is the mail id i need to post you .please kindly help

[@madhu.8]

When user select the forgotten password then system will show the page to enter the email id for reset the password....... Is that the right way of writing req. Or is it right req.

[@Lynchoftawa]

Why have you missed of New Zealand on your world map?

[@karaleise]

Hi Mark, you are right New Zealand is missing!!!! - and it's a shame because I love New Zealand! I'll have to fix that.

[@marykshelton2869]

She is too hard to understand!