_PRAI-Requirements; Final Touch



                       Under Development

Lately there are many discussions about what single thing leads to project success or failure. I don’t believe that there is a single thing, but I do know that there is one thing that is always in the list of the top three of both lists. REQUIREMENTS.

· When the requirements are detailed, clear, and unambiguous the requirements have a significantly positive impact on the project.

· When the requirements are generalized, unclear, and ambiguous the requirements have a significantly negative impact on the project.

So ……. It is just this simple:

· Successful Projects = detailed, clear, and unambiguous requirements

· Challenged Projects = generalized, unclear, and ambiguous requirements

There are numerous sources that identify specific language that is a sure sign of clarity and ambiguity (e.g., IEEE830, IEEE1233, PMBOK, PABOK, http://www.construx.com/Default.aspx?nid=1, http://www.requirementsnetwork.com/node/2085, http://www.slideshare.net/AllianceGS/requirements-ambiguity-testing, http://www.standishgroup.com/newsroom/chaos_2009.php, etc.). 

Well we have streamlined the process of separating positive from challenged requirements. It is an excellent indicator (dare I say predictor) of what is ahead.

The “Project Requirements Ambiguity Identifier” (_PRAI-) was designed and priced to be used. At $29 it is targeted for the PM’s, BA’s, QA’s, etc. and has the intent of helping them create better projects.

_PRAI- provides for automatic updating, at no cost, as improvements are made to the product.



Documentation
we are providing both hardcopy and video documentation on the use of _PRAI-.

	EndUser Agreement		none
	Installation		Video*
	QuickStart		Video*
	Preliminary Analysis		Video*
	Using .XLS Table		Video*

* be patient for large videos to download




Thank you so much for considering _PRAI-. Please feel free to contact us if you have any problems or suggestions (PRAI@SQM-LLC.COM). Thank you. Jon