Looking to get your opinion on Business Requirements practices.
What sort of a practice do you use when writing business requirements / functional requirement documents? Do you use Volere? Or do you use something else?
Give your opinion as I am interested to know and find out about different practices that I may not have used/heard of and what the wider audience uses :)
We typically use a form of Lean Power Workshops to gather the High Level Requirements (HLR). These allow us to define the HLR, justify it, and prioritize it using the MOSCOW method.
Once this is completed then we input the requirement into an application called JAMA (Great for Requirements, not so much for Test Plans) where we can track the requirement (approvals, change requests, and other modifications). It also provides accountability on the author and end user, which is often lacking and leads to arguments or missed requirements down the road.
Generally, as a career contractor, I use what the company is using. Business requirements are text, functions are user stories (used to use use cases), process I use BPMN, etc.
Btw, I started on a Volere project and left after a week cause Volere didn't offer enough structure to define functionality and was to open to interpretation. Could see a disaster about to happen - it did too I heard.
brought to you by enabling practitioners & organizations to achieve their goals using:
Advertising Opportunities | Contact Us