A coupl’a weeks ago, I received an email notice from a big software company whom I’ll call “Company X” (even though they’re actually Borland). The email notified me of a Webcast that they seem to think I’ll be interested in.
Here’s the blurb:
Define Before You Manage: Why Requirements Definition is a Critical First Step
Managing your requirements is only half the battle. For management to be truly effective, taking the first step of defining complete, accurate requirements is absolutely critical. In this webcast, Forrester Senior Analyst Carey Schwaber will explain how you can build agreement around requirements right from the start, so there are no uncertainties down the road.
- Why adopting a Requirements Definition (RD) solution is necessary from a business perspective, plus current practice and shortfalls
- Best practices for choosing and implementing an RD solution
- Advantages and features of Borland DefineIT via the product demo
With solid Requirements Definition, everyone benefits. Application Development VP’s can improve the speed and accuracy of requirements capture. Business Analysts can significantly reduce validation cycles, and Quality Assurance leads can determine clear test objectives from business flows.
I give these people failing marks for effectively identifying their target market.