Seriously. You can’t make a perfect project. You can’t just “will” a project to success. Too many variables. But you can do all that you can do to make a project engagement successful. And the two biggest ingredients to that success that the project manager can have a great deal of control over is practicing effective and efficient communication and seeing to it that no works starts without good, detailed, complete-as-possible requirements that read well and mean something to both the customer and the project team. Today, we’re going to talk about requirements.
Requirements are the lifeblood of the project
I’ve said this time and time again. And I’m going to say it here again. Requirements are the lifeblood of the project. Bad requirements = an extremely risk situation wrought with conflicts, change orders, disputes, customer dissatisfaction, budget overruns and missed deadlines. Good, detailed requirements = far less risk, much greater chance for project success, fewer change orders because the project scope is well defined, and a much happier project client.