Best Practices for Requirements Gathering

Total votes: 0

The April issue of the BDM Bulletin addresses Best Practices for Requirements Gathering. Larry Goldberg and Barbara von Halle from Knowledge Partners, Inc. offer up a six step process. Share your tips. What methodologies or best practices do you currently use?

Read the article here: http://www.bpminstitute.org/articles/article/article/six-simple-steps-fo...

Comments

Login or register below to comment on this discussion.
Ahmed Nizami
, Sr. Business Analyst, Walmart
posted 2 years 27 weeks ago
couple of thoughts... adding business value to the requirement description itself improves the quality of requirement and allows the business to prioritize the requirement much more effectively eg. The business must be able to provide feed back to its customers within 8 hours in order to achieve higher customer satisfaction score. "the user/system must meet X requirement, in order to gain Y benefit" The second most important point is being able to capture pure "Business" requirements free from solution or technology influence. This is the most common err I have seen is that business requirements are really some sort of a hybrid functional/system/business requirements. A good business architecture will depend on well written business requirements, so the business can determine how these requirements impacts their business capabilities, and can make sound decisions on business cases and projects.
Frank Millar
, Executive Director, Millar Consultants, LLC
posted 2 years 50 weeks ago
The authors have leveraged the Zachman framework (understandably) to assure thoroughness of rules architecture analysis. In the process, however, they don't seem to put much emphasis on the methods for requirements gathering. When you gather requirements for a few years it's easy to come to a conclusion that the following couple of items might also belong on any best practices list: - Assignment, including some level of accountability, of the business subject matter expert. (The business interface with an architect team regarding any one business process' rules works best for everyone if it is singular.) - Identification of the rules and attendant architectures into logically separable, stand-alone increments for agile implementation. (Gaining early/frequent increments of business value is a fundamental strategy for achieving user buy-in and satisfaction.) Frank Millar Millar Consultants, LLC
Frank Millar
, Executive Director, Millar Consultants, LLC
posted 2 years 50 weeks ago

Already a Member? Login Here:

Shopping cart

View your shopping cart.

Editorial DIrectors

Tom Dwyer
Editorial Director
BPMInstitute.org
William Ulrich
Editorial Director
BAInstitute.org
Mike Rosen
Editorial Director
SOAInstitute.org