Defining a project

Projects exist to deliver a defined outcome, in agreed time and within cost. As a project progress the outcome may be modified , as may the constraints under which it is delivered , but such changes need to be done in a controlled and agreed manner against a clearly understood, accepted and documented baseline.

If the project's objectives are not crystal clear and have an ambiguous project scope , the project will be problematic no matter how good the rest of the project management is.

Three factors go towards defining a project ;

#Objectives : Why are you doing the project? When you have finished it what will have been achieved?

#Scope : How broad or narrow are the boundaries of the project to achieve your objectives? This sets the boundaries for the whole endeavour. A definition off the limits to the project.

#Requirements : How clear and stable the objectives and scope are. This impacts how you design and manage your project and even the style of project management.

It is essential to have a clear understanding of a projects objectives , as this sets the direction for the whole endeavour. Objectives should answer the question why the project is being done but not what or how it will be done.

A project should have at least two objectives , written in the form of short statements and sometimes in long sentences. They are best defined with input from stakeholders and the project sponsor

Do ensure that the objectives are of sufficient quality. A quality objective is clear, meaningful , concise and unambiguous.

Last but not least, review and confirm the objectives with the project sponsor and key stakeholders.