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 the stakeholders until some supposed “readiness to review”. You are not writing a novel where you want to keep the plot to yourself until the mystery can be revealed. You are capturing problem analysis and root cause, process flows, conclusions drawn from the data, and models to support this understanding.
If you want quality analysis – share and validate as you go.
If you want to full cooperation from your stakeholders – do not keep them in the dark.
Share draft requirements, draft models, draft scenario matrices, draft hierarchy of themes and user stories.
Keep reviewing, updating and improving – and keep sharing.
More posts in the Shared Understanding of Requirements category.
Want to succeed in business analysis? Apply the twelve principles of the business analyst mindset. Sign up for the Why Change newsletter for more resources and to receive your free copy of the BA mindset poster.
3 comments