THIS Is The Most POWERFUL Requirements Gathering Format For Business Analysts

[@josephojo5185]

I love the way you analyzed this.

[@theagilebusinessanalyst]

Glad I could help :)

[@josephojo5185]

@@theagilebusinessanalyst can I share my Business case projects with you and connect with you?

[@tochukwunjoku]

Thank you so much for this video. BPMN is a technique I'm beginning to use more and more as I progress in my career as a business analyst so thank you. I would really appreciate more videos on this thank you!

[@theagilebusinessanalyst]

Appreciate your feedback! Edit: An upcoming video will be a BPMN Tutorial, and also a Business Analysis Case Study to build a prototype with BPMN. Stay Tuned :)

[@maheshmohite7578]

Beautiful Explanation

[@theagilebusinessanalyst]

Appreciate it!

[@Njooo5]

Well explained 👍

[@theagilebusinessanalyst]

Appreciate the comment :)

[@Marius-kr9nz]

I agree with some of your points, but I believe that those unclarified things should be put in Acceptance Criteria. Besides that, it is well known that 'or' and 'and' should be really clear in user stories if not possible to be avoided

[@theagilebusinessanalyst]

Great Comment. Agree that Acceptance Criteria should be used to clarify the user story more. But don't forget, acceptance criteria are again plain text, that's why I prefer to at least attach diagrams like the one showed in the video to the user story to enhance it.

[@AdamKaloyirou]

@@theagilebusinessanalyst agree to this completely - which puts it at odds with the title of the video. This is a tool used to help elucidate the requirement, it is not a tool used to gather requirements

[@DarrenStarr]

What is a pitza?

[@theagilebusinessanalyst]

Pizza 🍕