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.
One of the most important responsibilities of a manager is to provide his or her team members opportunities for professional development and growth. While there are many ways to approach this responsibility, I’ve found that one of the simplest, low cost/high return professional development activities is something I call the “training moment.” What is it? The training moment consists of 15-30 minutes set aside during team meetings – or scheduled separately depending on team member availability and convenience – during which a team member or two may take the opportunity to demonstrate use and benefit of a tool or technique, share […]
What does IBM’s acquisition of Telelogic (Doors) mean to the future of both products? What does it mean for their users? I thought I’d share a recent article I came across that shows that IBM has made some progress in determining how they’ll leverage both products.
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.