You can grab the Business Requirements Document TEMPLATE from the video in our Business Analysis Templates and Elicitation Questions Package here: the-business-analysis-doctor-self-paced-learning.thinkific.com/courses/business-analysis-template-package Also, your next video should be my tutorial on the Software Requirements Specification (SRS): kzread.info/dash/bejne/f2l4u5WehNzOhaQ.html

This has served as a very helpful reminder for what needs to go into a BRD, thanks!!

@thebadoc

6 ай бұрын

You are very welcome! I'm glad it was helpful to you.

Thank you for this useful info. Much more informative than many of the others I've come across.

@thebadoc

Жыл бұрын

You're welcome! I appreciate that feedback!

Hi @thebadoc, thanks for putting out this video, it is one of the most simple yet effective explanations I've come across reg. BRD!

@thebadoc

7 ай бұрын

You are most welcome! And thank you for that kind feedback. I'm glad it is being consumed as intended. I hope the information serves you well.

I really needed this! Thank you so much.

@thebadoc

Жыл бұрын

You're so welcome! Glad to help!

Wow this BRD video just nails it. Thanks Doctor White

@thebadoc

Жыл бұрын

You are very welcome and thank you for watching! Also, be on the lookout for the video on the SRD/FRD..

This is well detailed and very useful. Thanks for the wonderful video. Hopefully we get some more on the functional and software requirements documents. Thank you🙏

@thebadoc

Жыл бұрын

Glad you found this video useful and thank you for watching it! Yes, the FRD/SRS video will be released next, so be on the lookout!

Excellent content, great job! Thank you very much!

@thebadoc

Жыл бұрын

You are most welcome! And thank you for the feedback! I appreciate it!

You're very good at this. Thank you for sharing your knowledge.

@thebadoc

Жыл бұрын

Hi, James! You are very welcome! Thank you so much for that feedback! I hope the info serves you well!

A very concise summary and great presentation. Thank you.

@thebadoc

10 ай бұрын

You are very welcome and thank your for the feedback! I hope the info is beneficial to you!

This was great! I’m excited!

@thebadoc

4 ай бұрын

Thank you! I'm glad you connected with the content. Nothing beats being excited about your career. Cheers!

Wao,This is the best explanation on BRD that i have seen, Thank yo BA Doctor.

@thebadoc

Жыл бұрын

Thank you for that feedback! I hope the info is a value add for you!

Very precise and detail oriented.... Thank you....very helpful!

@thebadoc

Ай бұрын

You are very welcome! Thanks for the kind words and for watching! I hope it serves you well.

thank you so much, this is extremely easy to follow and very intuitive in BRD preparation

@thebadoc

9 ай бұрын

You are most welcome! I'm glad I was able to communicate the information in a way that resonates with you. I hope the information serves you well!

thank you very much for this insightful session, I really learned a lot

@thebadoc

Жыл бұрын

Hi, Rodney! You are very welcome. Glad to help. Also, be on the lookout for the SRS tutorial coming soon!

awesome analysis on BRD. Thank you

@thebadoc

7 ай бұрын

You are very welcome! I hope it's helpful to you!

That was awesome!

@thebadoc

Жыл бұрын

Thank you for that feedback and for watching! Glad to be of service!

Thank you, It was very Informative session.

@thebadoc

Жыл бұрын

You are very welcome! I hope the information serves you well!

It was so informative. Thanks :)

@thebadoc

3 ай бұрын

You're very welcome! I hope the information serves you well.

Thanks so much!!!

@thebadoc

10 ай бұрын

You are very welcome! I hope you gained a lot from the video.

Thank you very much.

@thebadoc

5 ай бұрын

You are very welcome! Glad to be of service.

Awesome sir .. nice explanation.

@thebadoc

10 ай бұрын

Thank you for the feedback and for watching! Glad to help! Also be sure to watch the SRS tutorial! It complements this video very well!

Hey BA Doc! When it comes to estimate the time required to create a BRD from 0, for example for the project that you showed in the video, how long would you estimate the total creation? In general, when it comes to predicting the required time and effort, how would you do it, when you have so much dependencies (aligning with stakeholders, creating the document from scratch, revising it with your teammates, etc.)?

@thebadoc

7 ай бұрын

Yes, there are SO MANY variables that can impact this. A general common rule of thumb is to allocate 10-20% of the total project time to requirements gathering and analysis. So for a 10-week project, you would expect to spend 1-2 weeks on requirements. But this is just a starting point. I usually start with this and then use the bottom up estimation technique to calculate a more realistic estimate. You can also look at the the amount of time it took you to create the BRD from previous projects and adjust based on the relative size of the current project. I hope that helps.

Thank you so much

@thebadoc

7 ай бұрын

You're most welcome! I hope you gained a lot from the video.

I was so surprised by your voice lol great video

@thebadoc

4 ай бұрын

LOL..that's interesting! What were you expecting? Glad you enjoyed the content.

Thanks bro🎉

@thebadoc

Жыл бұрын

Hi, Deepak! You are very welcome!

Awesome 👌

@thebadoc

8 ай бұрын

Thanks for the feedback! Glad you enjoyed the content!

I would love to see something related to Reporting Requirements. Would be helpful and it's hard to find about it.

@thebadoc

5 ай бұрын

Check out my tutorial on Software Requirement Specifications. I discuss reporting requirements there. kzread.info/dash/bejne/f2l4u5WehNzOhaQ.html

So from watching the video my understanding is that the requirements in the BRD is just business requirements? And then example functional requirements document is created into more in-depth from each business requirement from the BRD. So functional requirements is a separate document

@thebadoc

11 ай бұрын

That's correct. While some organizations include all requirements in one document, it's best practice to include the business requirements and stakeholder requirements in the BRD document. Then create the SRS document for the detailed functional and non-functional requirements. You can learn more about the SRS in this video: kzread.info/dash/bejne/f2l4u5WehNzOhaQ.html

@Ttsweet1315

10 ай бұрын

@@thebadocthank you

So is the brd , a high level overview ? contains the as is , to be , high level process flow and business rules . iam a lil confused as there are some who say .... " put everything int he brd" and others who say " keep the brd simple " and the functional requirement document (frd) extensive and detailed which one is the norm ??? cheers

@thebadoc

Жыл бұрын

Great question. Generally, it depends on the organization. The best practice, however, is to create a BRD with the high-level requirements first, then create a more detailed document such as an SRS or FRD afterward to outline the detailed specification. This is because your stakeholders should approve the BRD to confirm that everyone is in agreement on the solutions scope (high-level requirements) prior to putting in the effort of analyzing and decomposing the detailed requirements. It will greatly minimize wasted effort if you break them up into separate documents or have a living document where the BRD transitions into the SRS after the BRD is approved. I hope that helps. Also, be sure to check out the SRS tutorial here: kzread.info/dash/bejne/f2l4u5WehNzOhaQ.html

@Lord.murugan

Жыл бұрын

@@thebadoc awesomeness and thank you for clearing my doubt :) 🔱 Iam so glad I found your channel.... 👍 Cheers

@thebadoc

Жыл бұрын

@@Lord.murugan Me too! And you're welcome!