3 Ways to Write Clearer Requirements
Вставка
- Опубліковано 27 лют 2018
- One way to improve your requirements is to write clearer requirements.
• Clear requirements are less likely to be misunderstood by business stakeholders and technical implementers.
• Clear requirements require fewer review cycles to confirm and validate them.
• Clear requirements lead to insightful questions, that show your power and value as a business analyst.
But what does “clear” really mean? And, more importantly, how do I know if my requirements are clear or not?
In this video, we cover 3 ways you can ensure your requirements are clear.
JOIN THE FREE WORKSHOP: QUICK START TO SUCCESS AS A BUSINESS ANALYST:
www.bridging-the-gap.com/quick
WATCH THESE VIDEOS NEXT:
The Must-Have Skills for New Business Analysts:
• The Must-Have Business...
Requirements Elicitation - What Questions to Ask:
• Requirements Elicitati...
Summary of Video-
- Use active present tense which will help to identify responsibility of who does what.
- Use consistent terminology, which also means not to use those interchangeably with other.
- Do not combine multiples requirements.
You are very elaborate and clear about the things you speak about. Most of the times instructional videos are more theoritical arbitrary but your videos are absolutely reality driven and be implemented right away.Greatly appreciate your videos.
Thanks for this feedback! Providing practical guidance that helps business analysts take the next right step - with confidence - is what we are all about at Bridging the Gap.
Thank you! The summary at the end will be nice to have❤
Thank you Laura, for all the information. Very crisp and to the point. Keep up the good work and keep posting such videos.
You are so welcome! I'm glad you are benefiting from the videos. Keep doing great business analysis!
Thank you so much Laura for the insightful instructions. I generally follow all these in my requirements. But this is a good reminder to pause and check my requirements again
You are welcome. We can all, always improve.
Ah ha moment - number three, where you talked about combining requirements. I've done this in the past and it definitely caused confusion between me and the main stakeholder. Good video.
It's an easy mistake to make and correct. Your requirements will get so much clearer going forward. Congrats on the awareness - that's the first step.
I really enjoy learning more techniques and ways to work better as a BA from your videos thank you Laura.
You are so welcome. So glad you are finding lots of value in these videos.
It seems that a lot of content is based in a world of development, a lot of time companies want off the shelf products and don't have the resource or technical capability to develop in house. It would be good to see more content focused on these situations, I'm sure you may have this covered somewhere, I'll have to have a look!
You made clear, I made some mistakes like this in the past. Your video's are very knowledge and subject oriented.
Now is the perfect time to correct them!
Really nice video. I realize that sometimes I combine the business requirements and then flow chart becomes too complex! I ll follow your steps now!
Great awareness Bhushan!
Thank you, this is very useful information!
You are so welcome.
So helpful - thank you!!!
You are so welcome!
good valuable video with clear examples, thank you
You are so welcome! Thank you for your kind words - and all the best of luck writing clearer requirements!
Thanks Laura. This video is helpful
So glad to hear this! Writing clear requirements is such an important quality of good business analysis.
Thanks for that !
You are so welcome!
Thank you!
You are so welcome!
Thank you
You are so very welcome!
The video is very accurate and information heavy. I loved it. However, please consider using visual aids when presenting materials. For example, when reading from your notes at about 1 min 23 (27) secs, you could use a visual "First tip: active, present tense (etc,)" This video is a few years old so maybe you've incorporated this suggestion, but it's the first video I've ever seen by you. Thank you.
I'm glad you found this video helpful! We include a lot of visual examples and learning aids inside our online training programs. I've recently started adding them where possible to our free videos as well.
Can you share some examples of business rules?
Ah ha moment: referring about the same term with up to three different ways in the same specs document :O !
With the advent of Agile, DevOps and so other "new" ways to work, is becoming a Business Analyst still worth it? Will Business Analysis not simply fall away that some stage?
Business analysis is everywhere - and many BAs specialize in Agile, DevOps, or other areas of specialization while leveraging their foundational BA skills to ensure the business succeeds with these initiatives.
Should the requirement include, for this example, the actual job posting details? Job Title, Job number, job description, contact info, etc.?
If your process is dependent upon specific details being entered, then I would say yes. Or if the system for entering job posting details is very specific and each item (job title, job number, etc) has it's own field that needs to be filled out. So it's hard to say "yes or no" either way, it depends.
❤
Is there anyway for you to call me?