Back to Basics

Home  >  Articles  > 






Back to Basics

by Andy Jordan

January 4, 2010


When I first started managing projects, I treated requirements as an input to the project--they would magically appear and tell me what the scope of my project was. It didn’t take me long to figure out that I was taking the wrong approach, that requirements gathering was actually an integral part in the execution of the project. But I am still surprised by how many organizations are unable to come up with good requirements.
In this article, I want to go back to requirements basics and examine how the requirements tie the organizational needs into the deliverables of the project--and how we then go on to validate those requirements.
From needs to deliverables--via requirements
All projects begin with a need, or maybe more accurately a set of needs--things that the organization is looking to change. The reason may be competitive, operational, financial, regulatory or any number of things, but we always start with a basic need.



Please login/register to read the entire article.





sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!



"Two roads diverged in a wood, and I... took the one less traveled by, and that has made all the difference."
- Robert Frost