Management

Business Analysts and Grammar Police

Poor grammar and spelling that cause a requirements model to be inaccurate, or difficult to understand and use, are serious because they negatively affect the documentation’s ability to serve its purpose. An otherwise solid, easy to understand document with some errors in grammar and spelling, is not as serious. In either case, poor grammar and spelling should be included in the offending analyst’s professional development plan, and improvement should be encouraged and expected.

The "Requirements Workbench" Concept

The idea of a “requirements workbench” is one that the guys over at Requirements.net have been consistently socializing over the past few months, and one that I have been following with interest.

Requirements.net has recently posted a Business Analyst Workbench Whitepaper and a Workbench Buyer’s Guide. To give the general gist of the workbench without stealing Req.net’s thunder, the workbench concept includes requirements management capabilities, but then goes beyond that to support the analyst through elicitation, elaboration and communication and validation activities.

Requirements Management Tool Resources

My company has been looking at requirements management solutions, which has provided me with the unique opportunity to play the “user” role for a change, and to do a little research into the attributes that make requirements management successful.

Anyway, what I’d like to do with this post is to share a few items I’ve found on the Web as well as some of my own thoughts on what might be of use to others who might be looking for a requirements management solution.