User stories/product requirements is everything when it comes to software design. The manager I work with sucks at it but thinks Agile is the best thing ever.
Hi! I have discovered your channel in RUclips and I like your explanations about the tips and clear ideas related to BA rol and Agile. Congratulations! 👏
This is a great question - for SAAS requirements - must indicates as "must-have" and "should' indicates that there could be workarounds that can be established. So both can be used when identifying and documenting requirements.
I do have a FB Group for questions and you can also post questions in the comments on my RUclips channel. I do look at all comments and respond. Link to FB Group: facebook.com/groups/BAInDemand
A highlight to the Gherkin syntax. It is not a good practice to use more than one "Then". Also avoid using conjunctive steps, if you have an AND, that should be a separate step.
can we write acceptance criteria without using this typical given, when, then... and Acceptance criteria should be met to do the desired functionality? Thanks in advance 👍
You can write the acceptance criteria without the given, when, then. However using this technique provides a lot of clarity and avoids miscommunication / questions during the sprint
Each topic of yours is really very helpful. They are crisp and clear. Thank you so much the efforts you put in.
Most helpful video on this topic
Powerful tutorial, made it as easy as ABC
Thank you so much for the feedback
User stories/product requirements is everything when it comes to software design. The manager I work with sucks at it but thinks Agile is the best thing ever.
I personally like Agile as well but most people miss the design/requirements aspect needed to make it successful
Great, nice level of detail. I like the Sprint ready definition of the User Story.
Thank you for the feedback
Hi! I have discovered your channel in RUclips and I like your explanations about the tips and clear ideas related to BA rol and Agile. Congratulations! 👏
Thank you - I'm glad you find this video helpful
That’s exactly what I was looking for. Thank you
I'm glad it helped!
Thank you for this amazing gift ❤️🙌🏽
You are very welcome!
Very helpful!
I'm glad you found it useful!
Could you please advice if I can use words "should" and "must " in the requirements for Commerical Off the Shelf Software?
This is a great question - for SAAS requirements - must indicates as "must-have" and "should' indicates that there could be workarounds that can be established. So both can be used when identifying and documenting requirements.
These “acceptance criteria” are actually benefits. The format is “benefit” at the end not usually acceptance criteria
Thanks for the video.😇
Very insightful!
Glad you enjoyed it!
Do we have any Telegram channel or group where we can post query related to business analysis and discuss the same.
I do have a FB Group for questions and you can also post questions in the comments on my RUclips channel. I do look at all comments and respond. Link to FB Group: facebook.com/groups/BAInDemand
A highlight to the Gherkin syntax. It is not a good practice to use more than one "Then". Also avoid using conjunctive steps, if you have an AND, that should be a separate step.
Thanks for the feedback!
spot on
What is ba role in api integration?
Focus on the result of the integration from a requirements standpoint
@@InDemandBAandScrumMaster thank you 😊
what about the use case description? do we have to build it if we have a complete user stories?
User case and user stories are completely different - I can do a short video to explain the differences - stay tuned.
can we write acceptance criteria without using this typical given, when, then...
and Acceptance criteria should be met to do the desired functionality?
Thanks in advance 👍
You can write the acceptance criteria without the given, when, then. However using this technique provides a lot of clarity and avoids miscommunication / questions during the sprint
Hi your videos are really Useful. May i know little bit Of Negative scenario How to write In acceptance Criteria
Could you shed light on RTM in agile and waterfall?
What is RTM?
RTM = Requirements Traceability Matrix....it's used to track requirements from BRD to implementation
There is no RTM in Agile - just created a short video on RTM in the waterfall environment
where do you add the acceptance criteria? thanks.
It's best to add acceptance criteria as part of your user story write-up.
i want to take clases
Hello - thank you for your interest. You can book a session with the team using this link: offers.itcareers4u.com/apply-today
Can you please throw some light on "Story Points"
Yes, will do a video on Sprint Planning soon. Thanks for the feedback!
Where do you get user stories and acceptance criteria from
fWell, discover your channel ion RUclips gone through a feasible explanation, about product backlog and acceptance criteria.
Why wasn't Jira used
useful thank you
Thank you sooo much!
how are tasks added?
Tasks are added when Dev team is reviewing and adding story points to user stories....they usually break things into tasks.
Hey! MaM can you share the slide to me personally? i am waiting for your response. Thankyou
I will share slides going forward.