![]() |
||||||||||||||||||||||||
|
|
|
|||||||||||||||||||||||
|
CHI*ATLANTA : EVENTS : 2005: Lost in Translation |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Lost in Translation: When Great Product Requirements End Up as Not-so-great Products Download Dave Altman's presentation in PDF (240 KB) We have all experienced product development projects that flounder or result in the creation of a product that is heavily revised after release. Product development projects fail for many reasons. Sometimes the reason can be traced directly to inadequate product requirements. Often though, the answer lies not in the requirements themselves, but in underlying business conditions that diminish the effectiveness of the product requirements and the requirements management process as a whole. In this session we will discuss business conditions that negatively impact the requirements management process, and actions that you can take to eliminate these conditions and ensure that your organization receives the full benefit of a well-organized and rigorous requirements management. Several of the conditions that we will discuss are:
Dave Altman is the owner of RqMD, a consultancy that assists companies in identifying and correcting weaknesses in their requirements management practices. Dave is a Senior member of the Atlanta chapter of the Society of Technical Communications and has 18 years of experience in various fields, including Requirements Analysis, Information Design, Specification/Contract Development, and Technical Illustration. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||