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

Поделиться
HTML-код
  • Опубликовано: 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
  • ХоббиХобби

Комментарии • 51

  • @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.

  • @christopher1152
    @christopher1152 2 года назад +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  Год назад +1

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

  • @sepjoadat
    @sepjoadat Год назад +4

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

  • @Pragatkasana
    @Pragatkasana 3 месяца назад +1

    Most helpful video on this topic

  • @celiapajares9443
    @celiapajares9443 Год назад +4

    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! 👏

  • @tomhoffelder1348
    @tomhoffelder1348 10 месяцев назад +2

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

  • @ocn2301
    @ocn2301 Год назад +2

    Powerful tutorial, made it as easy as ABC

  • @butterfly9841
    @butterfly9841 Год назад +1

    Thank you for this amazing gift ❤️🙌🏽

  • @GULAMAHAMEDSBUJARUK
    @GULAMAHAMEDSBUJARUK 2 года назад +1

    Thanks for the video.😇
    Very insightful!

  • @katerynadereguzova6117
    @katerynadereguzova6117 7 месяцев назад

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

  • @meenakkshirajendran3776
    @meenakkshirajendran3776 2 года назад +1

    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 года назад +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.

  • @narayanamurthy5397
    @narayanamurthy5397 9 месяцев назад

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

  • @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.

  • @pranjalitiwari8612
    @pranjalitiwari8612 6 месяцев назад +1

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

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  5 месяцев назад +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.

  • @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

  • @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 8 месяцев назад

      Where do you get user stories and acceptance criteria from

  • @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

  • @jessicasherman5537
    @jessicasherman5537 2 года назад +1

    where do you add the acceptance criteria? thanks.

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

  • @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 Год назад

    Why wasn't Jira used

  • @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 😊

  • @fazalurrehman410
    @fazalurrehman410 Год назад +1

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

  • @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