My pleasure, truly!!!!

It's my pleasure

Thank you so much!

You are very welcome - thank you for the comment

Absolutely!

Yes! Thank you!

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

Thank you so much!

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

Thank you so much!

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

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.

great response!

You are right - it should be there if it isn't already

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!

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

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.

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.

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

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

That's a great question - today's live session covered business analyst documentation; here's the link: kzfaq.info/get/bejne/Z99xfLuAsrjUe4E.html Next week, I'll provide training on Agile documentation.

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

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

Will do that going forward - thank you for the suggestion!

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

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.

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

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

www.linkedin.com/in/sarabjit-dahyia-pmp-mba-21b0196/