Shared Understanding 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,…

Shared Understanding 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…

Shared Understanding 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…

Shared Understanding 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…

BA Mindset Principle #8: Take Responsibility for Shared Understanding of Business Requirements

What is the most important outcome of business analysis activities? Is it detailed and intricate process maps? Comprehensive business requirements documents? Groomed user stories? A requirements sign-off obtained within schedule? All of the above are important. But there is something else…