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,…
Read More Shared Understanding Tip #6: Structure the Requirements, Do Not Pile Them Up
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…
Read More Shared Understanding Tip #5: Review, Refine & Repeat
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…
Read More Shared Understanding Tip #4: Share As You Go, Requirements Are Not a Secret
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…
Read More Shared Understanding Tip #3: Explain Many Times, Many Ways
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…
Read More Shared Understanding Tip #2: Consistent Terminology
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 the result of your analysis, how do you…
