How To Gather Requirements | Agile Methodology

Поделиться
HTML-код
  • Опубликовано: 13 июл 2024
  • This video captures and explains the various ways in which Business Analyst can gather requirements while working with Stakeholders including:
    1. Interviews
    2. JAD
    3. Interface Analysis
    4. Observation
    5. Brainstorming
    6. Surveys
    7. Review Past Documents
    Join us in our FREE Facebook group for a chance to attend live training sessions: / baind. .
    Get project-based hands-on training from Sarabjit; visit us at offers.itcareers4u.com/apply-...

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

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

    Thank you Sarabjit, if only you knew how helpful this was. Keep up the good work.

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

    Very Helpful . Thank you Sarabjit :)

  • @sagarmahendrakar3674
    @sagarmahendrakar3674 2 года назад +3

    Thank you for these videos, it will help us lot, u r doing a great job.

  • @resurrectingexcellence
    @resurrectingexcellence 9 месяцев назад +1

    Great video, thank you

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

    Thanks for this great video!

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

    Thank you, very knowledgeable session.

  • @pratss9957
    @pratss9957 5 месяцев назад +1

    It’s good to use the word Requirement elicitation rather than Requirement gathering . Great video !

  • @samanthag.6251
    @samanthag.6251 8 месяцев назад

    Very helpful. Thanks

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

    This is fantastic

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

    Very clear explanation, now the question that comes to mind (probably more on PO role) is about timing, in your experience how often should you be having requirement meetings with stakeholders or discoveries in Scrum? Thanks again

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

      I believe your question is around how often should you have backlog grooming sessions to identify and flush out user stories. From my experience - it's usually an ongoing progress to ensure users stories are in a state that can be included in Sprint planning/sprint backlog

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

    Awesome!!

  • @daviddawid123
    @daviddawid123 7 месяцев назад +2

    Where is the double like button, your explanation reinforces my understanding when doubts kick in my head..
    An example with generic concepts of systems generating a file and placing on server for another system might help new BA's.. Just a suggestion

  • @chandranigoswami5877
    @chandranigoswami5877 Год назад +5

    Can you pls arrange for a session on how to draw workflow diagram in visio? It would be really helpful.

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

      MS Visio is usually a program that will be provided to you once you start your job. But the key is to learn how to do workflow diagrams vs the tools you use. Use www.draw.io which is a free tool you can use to learn how to do workflow diagrams

  • @agirmaus-lh9zi
    @agirmaus-lh9zi Год назад +1

    Hi! Can you please answer what qualifies for a good requirement.

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

    When does Requirement Gathering session happens in Agile? As we know in Waterfall it is done post project kick-off meeting. In Agile as we first prepare Product Backlog in collaboration with stakeholders. So does a BA assist PO in creating PB (Requirement Gathering). Then these high level requirements are then elaborated during Sprint Planning/Backlog Grooming using the above techniques mentioned by you?

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

      That's a great question! Requirements gathering in Agile take place in the Backlog Grooming sessions.

  • @ashishgoyal4818
    @ashishgoyal4818 2 года назад +3

    In CRs, many times client disagree on the things that weren't discussed earlier even if we do have proper MOMs and document as proof.
    What to do in such situations when client is escalating the issue?
    Such events cause lot of difficulty to take calls with client.

    • @anonymous6924
      @anonymous6924 2 года назад +8

      After the requirement gathering, BA will send a MOM stating all the points that were discussed in the Requirement Gathering, if anything(requirement) you don't understand/ you not sure about the feasibility then add that point also in a MOM and put a remark that you will get back to them after a internal discussion. After then, gathering all the requirements, a BA will send RUD (Requirement Understanding Document) by listing below
      1. Purpose
      2. Scope
      2. Assumptions and dependencies
      3. Present functionality
      4. Proposed functionality
      5. wireframe (if required)
      6. Impact of the Existing features
      7. Impact on other modules.
      once the RUD is approved then go for a SRS where you will detail the entire flow of systems.
      Now your client can't disagree as you have already sent a RUD and got approval from them.
      Even after then the client disagrees and wanted to add/reduce some features, then simply ask them to raise a New CR since it was not in the scope. Mention the "scope and assumptions" clearly and get it approved.

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

      great response!

  • @anonymous6924
    @anonymous6924 2 года назад +3

    How do you decide a requirement is a good requirement or a bad requirement? i need a video on this, this question was asked in my interview. (FYI I'm an experienced BA)

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

      There are no bad requirements....there are requirements that require clarification to ensure you understand input/output and expected results. I would say a good requirement is one that is clear on the intended functionality. Hope this helps!

    • @ayushagarwal2961
      @ayushagarwal2961 2 года назад

      @@InDemandBAandScrumMaster Can we also say that good requirement is something which is properly elicitated and resulted in a +ve business outcome and all stakeholders approve of that set of requirement. Whereas a bad requirement is something which was not signed off and resulted in breaks let's say during UAT testings.

  • @affiongvictor-ayara5570
    @affiongvictor-ayara5570 Год назад +3

    Is there a reason you did not list requirement workshop as one of the requirement gathering techniques?

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

    I wanted to understand after we get the requirements how do we properly documents the To Be flow so that nothing from this existing flow/fields are disturbed ,
    basically how can i verify that our To Be flow will not break any existing working functionality in the system

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

      That’s a great question!!! I will create a video to provide a proper response

    • @shelbytownsend3511
      @shelbytownsend3511 Год назад

      @@InDemandBAandScrumMaster has a video been done on this topic?

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

    How to gather requirements from a SME or a client who always seems to be very busy. What would be your best tool in Eliciting the information from them. Thank you in advance.

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  2 года назад +4

      My approach would be to make it easy for them to meet with you - meet them on their schedule/timeframe....maybe over coffee or lunch or maybe when they're driving. If you make it easy for them - they will be most likely to help you.

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

      I would approach this in following ways :
      1. Reschedule accordingly to the SME time, when it's easy for him/her to meet-up.
      2. Explain why this engagement is important and the impact that brings, this might create a sense of urgency .
      3. Ask if s/he could deploy someone else to answer our ( BA ) questions.

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

    Hi… I have recently changed my domain from banking to IT and undergone salesforce certification.. but I am not getting projects since I have no experience in IT and salesforce.. how do I tackle this situation… pls advise

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

      Best to try and get some hands on experience in implementing IT systems. Check you my website for option on getting hands on experience: www.itcareers4u.com

    • @gloriagesicho6904
      @gloriagesicho6904 2 года назад

      @@InDemandBAandScrumMaster Thanks you so much for the training sessions. They are really helpful. As a BA, when moving to a new domain, what is the best approach to quickly learn the domain? For example moving from Healthcare to Finance domain. Is it important to learn the domain or as long as one can draft good requirements learning the domain comes gradually during the interactions with the stakeholders?

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

    Could you please provide some PDF or word document for the same ?

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

    I'm looking to pay a monthly fee to work on a project...where can I find these offers?...

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Год назад

      We don't have any such programs but we do provide training that includes end-to-end project. You can book a strategy session with the team using this link: offers.itcareers4u.com/apply

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

    Thank you, Do we have to create all these diagrams for Agile projects as well in BRD and FRD? Please explain everything is detail about Agile projects from beginning till the end.

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  Год назад

      That's a great question - today's live session covered business analyst documentation; here's the link: ruclips.net/video/1yAIXOMRpKM/видео.html Next week, I'll provide training on Agile documentation.

  • @kishanrajpurohit3436
    @kishanrajpurohit3436 9 месяцев назад +1

    Hi Mam, i have got more than 8 years of experience and 3 years as BA, i would like get a job in USA, could you please assist me to get a job in USA, I look forward to hearing from you on that mam.

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

      If you have the experience; shouldn't be hard to find a job. Apply at all the job boards. Are you located in the US? If you are not in the US - I'm not familiar with any of the immigration processes.

  • @AMITMISHRA-nx2jp
    @AMITMISHRA-nx2jp 2 года назад +1

    Sarabjit why your courses are so much expensive look I reside in India and in dollar it become too much expensive why can't your course be priced in the range as udemy provides

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

      Thank you for the comment - my course is more hands-on approach that builds experience and gets you ready for the role. We also have DIY course if that's more affordable and here's a 20% discount code: 20DIY Here's the link: baindemand.newzenler.com/courses/diy-90-day-fasttrack-business-analyst-scrum-master-program

  • @shaibalbose9831
    @shaibalbose9831 4 месяца назад +1

    next time - please come up with a proper sample/use case ... and explain by going thru step-by-step ... the whole purpose is to help explain with handson examples ... just talking is a waste of time

    • @InDemandBAandScrumMaster
      @InDemandBAandScrumMaster  4 месяца назад +2

      We have at least 3 case studies completed on the channel - I am sure they will help fill in the gaps

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

    Linked in mam once please give me your linked id mam.