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

Поділитися
Вставка
  • Опубліковано 8 лют 2021
  • 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 8 місяців тому +2

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

  • @Pragatkasana
    @Pragatkasana 3 місяці тому +1

    Most helpful video on this topic

  • @swerviness
    @swerviness 9 місяців тому +1

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

  • @christopher1152
    @christopher1152 2 роки тому +3

    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  Рік тому +1

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

  • @ocn2301
    @ocn2301 Рік тому +3

    Powerful tutorial, made it as easy as ABC

  • @meenakkshirajendran3776
    @meenakkshirajendran3776 2 роки тому +1

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

  • @celiapajares9443
    @celiapajares9443 Рік тому +4

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

  • @GULAMAHAMEDSBUJARUK
    @GULAMAHAMEDSBUJARUK 2 роки тому +1

    Thanks for the video.😇
    Very insightful!

  • @butterfly9841
    @butterfly9841 Рік тому +1

    Thank you for this amazing gift ❤️🙌🏽

  • @tomhoffelder1348
    @tomhoffelder1348 10 місяців тому +2

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

  • @sepjoadat
    @sepjoadat Рік тому +3

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

  • @katerynadereguzova6117
    @katerynadereguzova6117 7 місяців тому

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

  • @Ravali_wanderingdairies
    @Ravali_wanderingdairies 2 роки тому +1

    useful thank you

  • @iamlevik
    @iamlevik 2 роки тому +7

    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.

  • @paarthepanns9085
    @paarthepanns9085 Рік тому +2

    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  Рік тому +1

      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
    @pranjalitiwari8612 5 місяців тому +1

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

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  4 місяці тому +1

      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.

  • @reemanfahaad
    @reemanfahaad Рік тому +1

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

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Рік тому +1

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

  • @trahamatrah8250
    @trahamatrah8250 2 роки тому +1

    Could you shed light on RTM in agile and waterfall?

    • @ALCRAN2010
      @ALCRAN2010 2 роки тому +1

      What is RTM?

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Рік тому +2

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

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Рік тому +2

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

  • @ganeshkurane6880
    @ganeshkurane6880 2 роки тому +1

    Can you please throw some light on "Story Points"

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  2 роки тому +1

      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

  • @endlesstranquility241
    @endlesstranquility241 Рік тому +1

    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 UA-cam channel. I do look at all comments and respond. Link to FB Group: facebook.com/groups/BAInDemand

  • @narayanamurthy5397
    @narayanamurthy5397 8 місяців тому

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

  • @jessicasherman5537
    @jessicasherman5537 2 роки тому +1

    where do you add the acceptance criteria? thanks.

  • @geethav3827
    @geethav3827 3 роки тому +1

    how are tasks added?

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  2 роки тому +1

      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

  • @user-jk6eg9zz4x
    @user-jk6eg9zz4x Рік тому +1

    i want to take clases

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Рік тому

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

  • @fazalurrehman410
    @fazalurrehman410 Рік тому +1

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

  • @Nishthac22
    @Nishthac22 Рік тому +1

    What is ba role in api integration?

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Рік тому +1

      Focus on the result of the integration from a requirements standpoint

    • @Nishthac22
      @Nishthac22 Рік тому +1

      @@InDemandBAandScrumMaster thank you 😊