Agile User Stories | Agile Acceptance Criteria | In-Demand Business Analyst

User stories are an important area of an agile approach that focuses on talking about requirements and not just writing them down. We will learn how acceptance criteria is achieved. Acceptance criteria refer to a set of predefined requirements that must be met in order to mark a user story complete.
Join us in our group for a chance to attend live training sessions: / baindemand
Get project-based hands-on training from Sarabjit, visit us at www.itcareers4u.com
#AgileUserStories #BusinessAnalyst #BACourse #AgileCourse

[@sureshnadagouda3352]

Each topic of yours is really very helpful. They are crisp and clear. Thank you so much the efforts you put in.

[@christopher1152]

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.

[@InDemandBAandScrumMaster]

I personally like Agile as well but most people miss the design/requirements aspect needed to make it successful

[@swerviness]

Best explanation I’ve found on TH-cam so far.

[@InDemandBAandScrumMaster]

Thank you for the feedback!

[@celiapajares9443]

Hi! I have discovered your channel in TH-cam and I like your explanations about the tips and clear ideas related to BA rol and Agile. Congratulations! 👏

[@InDemandBAandScrumMaster]

Thank you - I'm glad you find this video helpful

[@ocn2301]

Powerful tutorial, made it as easy as ABC

[@InDemandBAandScrumMaster]

Thank you so much for the feedback

[@Pragatkasana]

Most helpful video on this topic

[@sepjoadat]

These “acceptance criteria” are actually benefits. The format is “benefit” at the end not usually acceptance criteria

[@tomhoffelder1348]

Great, nice level of detail. I like the Sprint ready definition of the User Story.

[@InDemandBAandScrumMaster]

Thank you for the feedback

[@butterfly9841]

Thank you for this amazing gift ❤️🙌🏽

[@InDemandBAandScrumMaster]

You are very welcome!

[@GULAMAHAMEDSBUJARUK]

Thanks for the video.😇
Very insightful!

[@InDemandBAandScrumMaster]

Glad you enjoyed it!

[@meenakkshirajendran3776]

Hi your videos are really Useful. May i know little bit Of Negative scenario How to write In acceptance Criteria

[@katerynadereguzova6117]

That’s exactly what I was looking for. Thank you

[@InDemandBAandScrumMaster]

I'm glad it helped!

[@iamlevik]

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.

[@InDemandBAandScrumMaster]

Thanks for the feedback!

[@habibahshelu8037]

spot on

[@Ravali_wanderingdairies]

useful thank you

[@InDemandBAandScrumMaster]

Thank you sooo much!

[@reemanfahaad]

what about the use case description? do we have to build it if we have a complete user stories?

[@InDemandBAandScrumMaster]

User case and user stories are completely different - I can do a short video to explain the differences - stay tuned.

[@narayanamurthy5397]

fWell, discover your channel ion TH-cam gone through a feasible explanation, about product backlog and acceptance criteria.

[@paarthepanns9085]

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 👍

[@InDemandBAandScrumMaster]

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

[@pranjalitiwari8612]

Could you please advice if I can use words "should" and "must " in the requirements for Commerical Off the Shelf Software?

[@InDemandBAandScrumMaster]

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.

[@endlesstranquility241]

Do we have any Telegram channel or group where we can post query related to business analysis and discuss the same.

[@InDemandBAandScrumMaster]

I do have a FB Group for questions and you can also post questions in the comments on my TH-cam channel. I do look at all comments and respond. Link to FB Group: facebook.com/groups/BAInDemand

[@jessicasherman5537]

where do you add the acceptance criteria? thanks.

[@InDemandBAandScrumMaster]

It's best to add acceptance criteria as part of your user story write-up.

[@trahamatrah8250]

Could you shed light on RTM in agile and waterfall?

[@ALCRAN2010]

What is RTM?

[@InDemandBAandScrumMaster]

RTM = Requirements Traceability Matrix....it's used to track requirements from BRD to implementation

[@InDemandBAandScrumMaster]

There is no RTM in Agile - just created a short video on RTM in the waterfall environment

[@ganeshkurane6880]

Can you please throw some light on "Story Points"

[@InDemandBAandScrumMaster]

Yes, will do a video on Sprint Planning soon. Thanks for the feedback!

[@Musa-Navid]

Where do you get user stories and acceptance criteria from

[@geethav3827]

how are tasks added?

[@InDemandBAandScrumMaster]

Tasks are added when Dev team is reviewing and adding story points to user stories....they usually break things into tasks.

[@feyishow3589]

Why wasn't Jira used

[@fazalurrehman410]

Hey! MaM can you share the slide to me personally? i am waiting for your response. Thankyou

[@InDemandBAandScrumMaster]

I will share slides going forward.

[@user-jk6eg9zz4x]

i want to take clases

[@InDemandBAandScrumMaster]

Hello - thank you for your interest. You can book a session with the team using this link: offers.itcareers4u.com/apply-today

[@Nishthac22]

What is ba role in api integration?

[@InDemandBAandScrumMaster]

Focus on the result of the integration from a requirements standpoint

[@Nishthac22]

@@InDemandBAandScrumMaster thank you 😊