After the Explain many times, many ways post, I’ve received a lot of feedback. In this post, I will follow-up on the most popular question: “Based on the different learning types and stakeholder needs, what business analysis methods or techniques…
Category: Shared understanding of requirements
Tip #6 – Structure the requirements, do not pile them up
Creating a shared understanding of business requirements is like picturing a building instead of a pile of bricks. You cannot achieve it without organizing requirements in a structure that makes sense. More than that: how can you, a business analyst,…
Tip #5 – Review, refine & repeat
Achieving a shared understanding of business requirements is an iterative process. Recap the main points after each requirements discussion – reconfirm agreement. Restate the problem, objectives and findings before the next meeting. If you see confused faces – recall previous…
Tip #4 – Share as you go, requirements are not a secret
Achieving a shared understanding of requirements is a process, not an event. Business requirements are just a format for capturing shared understanding of the problem and required solution. So, requirements are not a secret that needs to be kept from…
Tip #3 – Explain many times, many ways
You and I may differ in how we learn and absorb information. I like to see for myself, you want to hear things explained to you, someone else may need a group discussion to accept a new concept. Therefore, the…
Tip #2 – Consistent Terminology
Continuing the topic of getting to shared understanding of business requirement, here is the next tip: use consistent terminology. Define the terms, publish and share the #definitions in a glossary or business dictionary. Then, promote the correct terms. As a…
Tip #1 – Context Model
What you write may not be what I read. What I read may not be what I understand. And what I understand now may not be what I remember later… When you capture result of your analysis, how do you…