The relationship between budgets and requirements for software development projects is often overlooked.

If you ask anyone involved with software development 'Are the requirements important for success?' The immediate answer will be 'Yes, of course.' In spite of this conceptual understanding, projects continue to see cost over-runs and cancelations. The basic understanding that requirements are important does necessarily lead to the execution of effective requirements process.

The primary goal of the requirements process is to define the proposed software that will be develop. To accomplish this there must be a process. A process will address all the following issues:

	1)		Preparing you and your customer for the process
	2)		Running a requirement meeting
	3)		Administrating requirements
			a.	Collection
			b.	Tracking
			c.	Change control
	4)		Concluding the requirements process

These are the things you will learn when you attend the PRACTICUM process training. Don't just agree that requirements are import. Learn how to run a true requirements process for your next process so you can beat the budget pitfalls of bad requirements.