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

  Рет қаралды 36,532

Business Analyst & Scrum Master In-Demand

Business Analyst & Scrum Master In-Demand

3 жыл бұрын

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

Пікірлер: 53
@sureshnadagouda3352
@sureshnadagouda3352 7 ай бұрын
Each topic of yours is really very helpful. They are crisp and clear. Thank you so much the efforts you put in.
@swerviness
@swerviness 8 ай бұрын
Best explanation I’ve found on KZbin so far.
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 8 ай бұрын
Thank you for the feedback!
@christopher1152
@christopher1152 2 жыл бұрын
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
@InDemandBAandScrumMaster 11 ай бұрын
I personally like Agile as well but most people miss the design/requirements aspect needed to make it successful
@Pragatkasana
@Pragatkasana 2 ай бұрын
Most helpful video on this topic
@celiapajares9443
@celiapajares9443 Жыл бұрын
Hi! I have discovered your channel in KZbin and I like your explanations about the tips and clear ideas related to BA rol and Agile. Congratulations! 👏
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
Thank you - I'm glad you find this video helpful
@ocn2301
@ocn2301 11 ай бұрын
Powerful tutorial, made it as easy as ABC
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
Thank you so much for the feedback
@tomhoffelder1348
@tomhoffelder1348 9 ай бұрын
Great, nice level of detail. I like the Sprint ready definition of the User Story.
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 8 ай бұрын
Thank you for the feedback
@GULAMAHAMEDSBUJARUK
@GULAMAHAMEDSBUJARUK 2 жыл бұрын
Thanks for the video.😇 Very insightful!
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 2 жыл бұрын
Glad you enjoyed it!
@butterfly9841
@butterfly9841 Жыл бұрын
Thank you for this amazing gift ❤️🙌🏽
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
You are very welcome!
@katerynadereguzova6117
@katerynadereguzova6117 6 ай бұрын
That’s exactly what I was looking for. Thank you
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 4 ай бұрын
I'm glad it helped!
@sepjoadat
@sepjoadat Жыл бұрын
These “acceptance criteria” are actually benefits. The format is “benefit” at the end not usually acceptance criteria
@meenakkshirajendran3776
@meenakkshirajendran3776 2 жыл бұрын
Hi your videos are really Useful. May i know little bit Of Negative scenario How to write In acceptance Criteria
@Ravali_wanderingdairies
@Ravali_wanderingdairies 2 жыл бұрын
useful thank you
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 2 жыл бұрын
Thank you sooo much!
@reemanfahaad
@reemanfahaad Жыл бұрын
what about the use case description? do we have to build it if we have a complete user stories?
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
User case and user stories are completely different - I can do a short video to explain the differences - stay tuned.
@pranjalitiwari8612
@pranjalitiwari8612 5 ай бұрын
Could you please advice if I can use words "should" and "must " in the requirements for Commerical Off the Shelf Software?
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 4 ай бұрын
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.
@iamlevik
@iamlevik 2 жыл бұрын
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
@InDemandBAandScrumMaster 2 жыл бұрын
Thanks for the feedback!
@habibahshelu8037
@habibahshelu8037 17 күн бұрын
spot on
@paarthepanns9085
@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
@InDemandBAandScrumMaster 11 ай бұрын
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
@jessicasherman5537
@jessicasherman5537 2 жыл бұрын
where do you add the acceptance criteria? thanks.
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
It's best to add acceptance criteria as part of your user story write-up.
@trahamatrah8250
@trahamatrah8250 2 жыл бұрын
Could you shed light on RTM in agile and waterfall?
@ALCRAN2010
@ALCRAN2010 Жыл бұрын
What is RTM?
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
RTM = Requirements Traceability Matrix....it's used to track requirements from BRD to implementation
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
There is no RTM in Agile - just created a short video on RTM in the waterfall environment
@endlesstranquility241
@endlesstranquility241 Жыл бұрын
Do we have any Telegram channel or group where we can post query related to business analysis and discuss the same.
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster Жыл бұрын
I do have a FB Group for questions and you can also post questions in the comments on my KZbin channel. I do look at all comments and respond. Link to FB Group: facebook.com/groups/BAInDemand
@ganeshkurane6880
@ganeshkurane6880 2 жыл бұрын
Can you please throw some light on "Story Points"
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 2 жыл бұрын
Yes, will do a video on Sprint Planning soon. Thanks for the feedback!
@Musa-Navid
@Musa-Navid 7 ай бұрын
Where do you get user stories and acceptance criteria from
@narayanamurthy5397
@narayanamurthy5397 8 ай бұрын
fWell, discover your channel ion KZbin gone through a feasible explanation, about product backlog and acceptance criteria.
@geethav3827
@geethav3827 3 жыл бұрын
how are tasks added?
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 2 жыл бұрын
Tasks are added when Dev team is reviewing and adding story points to user stories....they usually break things into tasks.
@feyishow3589
@feyishow3589 11 ай бұрын
Why wasn't Jira used
@fazalurrehman410
@fazalurrehman410 Жыл бұрын
Hey! MaM can you share the slide to me personally? i am waiting for your response. Thankyou
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster Жыл бұрын
I will share slides going forward.
@Nishthac22
@Nishthac22 Жыл бұрын
What is ba role in api integration?
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster Жыл бұрын
Focus on the result of the integration from a requirements standpoint
@Nishthac22
@Nishthac22 Жыл бұрын
@@InDemandBAandScrumMaster thank you 😊
@user-jk6eg9zz4x
@user-jk6eg9zz4x Жыл бұрын
i want to take clases
@InDemandBAandScrumMaster
@InDemandBAandScrumMaster 11 ай бұрын
Hello - thank you for your interest. You can book a session with the team using this link: offers.itcareers4u.com/apply-today
How to Gather Requirements - Business Analyst and Scrum Master Roles
23:01
Business Analyst & Scrum Master In-Demand
Рет қаралды 7 М.
Crafting Effective Agile User Stories: A Guide
11:32
OeLean
Рет қаралды 141 М.
Её Старший Брат Настоящий Джентельмен ❤️
00:18
Глеб Рандалайнен
Рет қаралды 7 МЛН
ТАМАЕВ vs ВЕНГАЛБИ. Самая Быстрая BMW M5 vs CLS 63
1:15:39
Асхаб Тамаев
Рет қаралды 3,4 МЛН
Role of User Acceptance Testing (UAT) for Business Analysts
27:47
Business Analyst & Scrum Master In-Demand
Рет қаралды 35 М.
How to write User Story and Acceptance Criteria in JIRA
14:22
Pramod Hanumappa
Рет қаралды 161 М.
5 Common Mistakes In User Stories
17:28
Continuous Delivery
Рет қаралды 88 М.
LIVE Q&A: 20 Questions New Business Analyst Need to Know
36:38
Business Analyst & Scrum Master In-Demand
Рет қаралды 11 М.
All about APIs | Business Analyst In-Demand
48:20
Business Analyst & Scrum Master In-Demand
Рет қаралды 21 М.
How To Gather Requirements | Agile Methodology
22:43
Business Analyst & Scrum Master In-Demand
Рет қаралды 28 М.
How to Split A User Story In Just 2 Steps.
19:30
Vibhor Chandel
Рет қаралды 136 М.
How To Write Good Requirements (User Stories)
19:57
TheBATutor
Рет қаралды 81 М.
Scrum in 20 mins... (with examples)
19:36
Codex Community
Рет қаралды 250 М.
Requirement Specification vs User Stories
17:34
Continuous Delivery
Рет қаралды 75 М.
One Pack Of Pringles Contained M&M's And Coca-Cola🤪😃
0:43
BorisKateFamily
Рет қаралды 25 МЛН
PINK STEERING STEERING CAR
0:31
Levsob
Рет қаралды 18 МЛН
Тату растение 🤯
0:28
FATA MORGANA
Рет қаралды 5 МЛН
Quick Wire Twisting Tool ##❗️❗️
0:13
ToolBox Talk 20
Рет қаралды 4,3 МЛН