There's a simple (though not easy) way to avoid much of the requirements/scope creep that many developers assume is normal and unavoidable. "That's not what I expected" and "Users don't know what they want" indeed are repeatedly predictable outcomes of the inadequate way requirements are defined conventionally, but such problems can be avoided.

Creep mainly occurs when system/software requirements fail to meet the REAL, business requirements--usually because developers don't recognize business requirements' importance or how to discover them.

In this well-received interactive session, based on his recent book, Discovering REAL Business Requirements for Software Project Success, Robin describes powerful techniques for discovering the REAL requirements and documenting scope in ways that can dramatically reduce creep.

* REAL Business Requirements vs. Product/System/Software Requirements
* Powerful Problem Pyramid(tm)Technique to Get Requirements Right
* 7 Guidelines for Documenting Requirements and Scope that Don't Creep

NOTE: This is a 2 day intensive workshop September 28 & 29, 2010

For information and registration, please go to http://www.tassq.org/upcoming-events-course-calendar.php