- highlight interdependencies
- describe the process’ goals and objective unambiguously
- document information that supports the process flow
- what is a customer? what are the attributes of a customer?
- what’s the (business) purpose of the process flow? in which variation does the process flow exist? who is interacting with it and what critera determines the success of the process flow? where are the business rules captured?
Business Requirement Engineering (BRE) is a process. If you want to put all its inputs and outputs in one place it is not a document anymore – “it is a repository!” One that serves the project every step of the way and beyond (and therefore needs to be maintained) in order to provide information that is
- clear, accuarate, complete
- useful for intended audience
- at this particular point in time
The Webcast: Inside Effective Business Requirements Documentation | IAG Consulting takes a real-life example of “how not to do it”, questions it and explains a stepwise BRE approach and its benefits (using some nice charts). The slides for this talk have been made available by modernanalyst.com and the Business Requirement template recommended can be downloaded from the IAG website.
This session is a deep dive into requirements documentation issues showing examples of good documentation practices, and samples of materials that only look good on the surface, but have significant buried problems.3 Learning Objectives
- Know what material must be present in high quality requirements documentation.
- See how documentation defects impact project performance.
- Learn how to simplify your strategy for documentation by focusing on the right information at the right time.