Tired of numbing statistics that continue to cite requirements as the root of all software project failure? Despite the proliferation of requirements management technologies, requirements problems persist. And, as application development processes increase in complexity, the requirements problem continues to grow - it costs software delivery organizations more than ever before in terms of budget, time-to-market, business value and customer goodwill. You may think you're managing your requirements, but the burning question is: What if you're managing the wrong requirements?
Requirements definition goes to the very core of application development - it is the underlying key to project success or failure, yet it is the single most neglected discipline within software development.
What are the hidden costs associated with poor requirements? It's much worse than you think.
Why traditional approaches to defining applications fail and will always fail.
How simulation and prototyping are different from what you do now and why it's worth trying.
Defining software requirements is a source of pain for most organizations - but for smart teams, it can be the area of greatest opportunity. Come on out and learn more!