Project management principles

Introduction of task management

Project management is a well planned and structured effort to achieve an objective or is the procedure of controlling, allocating, and timing available resources to achieve the desired goal of your project within an effective and expedient manner, for example, creating a new system or building a project. Task management is widely recognized as a sensible way of making certain projects meet aims and products are sent on time, within budget also to correct quality standards, while at exactly the same time controlling or maintaining the scope of the task at the correct level.

Project management includes developing a project plan, which includes defining and confirming the job goals and aims, identifying tasks and how goals will be achieved, quantifying the resources needed, and identifying budgets and timelines for completion. It also includes managing the execution of the task plan, along with functioning regular 'settings' to ensure that there surely is correct and objective information on 'performance' in accordance with the plan, and the mechanisms to put into practice recovery activities where necessary. Jobs usually follow major stages or stages (with various game titles for these), including feasibility, meaning, project planning, execution, analysis and support/maintenance


Project management has been employed since the early on civilization. Until 1900 civil engineering assignments were generally been able by creative architects and technical engineers by their selves, among those for example Christopher Wren (1632-1723), Thomas Telford (1757-1834) and Isambard Kingdom Brunel (1806-1859) It has been because the 1950s, that organizations began applying systemic project management tools and techniques to complex projects.

Henry Gantt (1861-1919), the daddy of planning and control techniques. Being a discipline, Project Management developed from diverse domains of request including construction, executive and defense. In the United States, the two forefathers of project management are Henry Gantt, called the father of planning and control techniques, who is famously recognized for his use of the Gantt graph as a job management tool, and Henri Fayol for his creation of the 5 management functions, which form the foundation for the body of knowledge related to job and program management. Both Gantt and Fayol were known as being students of Frederick Winslow Taylor's ideas of methodical management. His work is the forerunner to modern project management tools including work breakdown framework (WBS) and source of information allocation.

Principles of job management

The Success Principle

The main goal of project management is to create a successful product. Without making an effective product there is absolutely no good point in incurring the project Management over head cost. opposing to typical wisdom, there have been many Projects that contain been "Promptly and within budget" but the product has not been successful, and in the same way many which may have not been "Promptly and within budget" the product has been very successful.

The Commitment Principle

A mutually suitable guarantee between a task sponsor and a project team must are present before a viable project is accessible. A job sponsor is an educated person in place of the eventual owner of the merchandise of the task and who's responsible for providing the required resources (money, goods, services, and general way, as appropriate. ) A project team is an educated and skilled group able and willing to undertake the work of the job. A mutually satisfactory assurance is one in which there is contract on the goals and aims of the project in conditions of the product's opportunity, quality grade, time for you to completion and last cost.

The Tetrad-Tradeoff Principle

The core parameters of the job management process, namely: product opportunity, quality quality, time-to-produce and cost-to-complete must all be mutually constant. The core factors of scope, quality, time and cost are interrelated rather similar to a four-cornered shape with flexible bones. One spot can be anchored and another changed, but not without impacting on the other two.

The Major Communication Channel (or Unity-of-Command) Principle

A single channel of communication must can be found between the job sponsor and the task team leader for all decisions affecting the consequence of the job. This principle is essential for the effective and useful administration of the task Commitment. Who owns the eventual product, if displayed by several Person, must nevertheless consult with one voice. Similarly, at any moment, the project's team will need to have an individual point of responsibility, a task manager, for the task of the task. Such person will need to have the abilities, experience, dedication, dedication, power and tenacity to lead the job to success.

The Cultural Environment (or Suitability) Principle

An up to date management must provide a helpful ethnical environment to permit the Project team to produce its best work. An informed management is the one that understands the job management process.

A supportive social environment is one where the project is obviously backed by management, and plan associates are enabled to create their finest work

without pointless bureaucratic hindrance. This rule includes the necessity for management to ensure that the authority account and management style are appropriate to

both the sort of project and its own stage in the job life-cycle.

The Process Principle

Effective and effective policies and techniques must maintain place for the carry out of the task commitment. Such guidelines and techniques must cover, at a minimum, clear assignments and duties, delegation of authority, and functions for controlling the opportunity of work, including changes, maintenance of quality, and schedule and cost control.

The Life-Cycle Principle

Plan first, then do. An effective project management process depends on two activities - planning first, and then doing. Both of these sequential activities form the basis of every job life-cycle, and can be extended to suit the control requirements of each type of job in every part of project management program. The job life-cycle, characterized by a series of 'milestones' determines when the task starts off, the 'control gates' through which it must move, so when the project is finished. Appraise the viability of assignments and develop success/failing criteria


There are a few factors to consider before any genuine projects commence. The project designers must contain steps or project phases, most importantly, the original notion must be determined, therefore as feasibility research, business plan, risk diagnosis, public enquiry, agreement, business, planning, design, procurement, fulfillment, test, handover, monetary life. Project managers has the process of monitoring tasks to be guided into successful, unfortunately, there are a few projects which were not completed on time, over budget or being canceled in the process of creating it. In general, there are normal reasons that are usually found for job failures, these are a few reasons: insufficient user involvement, inappropriate planning or insufficient planning, incomplete requirements, lack of resources, incorrect estimations. According to the 1994 Standish CHAOS declaration there are top 10 10 factors found in successful projects. These factors are outlined in Desk below

Project success factors

Project Success Factors % of


User Participation 15. 9%

Executive Management Support 13. 9%

Clear Assertion of Requirements 13. 0%

Proper Planning 9. 6%

Realistic Targets 8. 2%

Smaller Project Milestones 7. 7%

Competent Personnel 7. 2%

Ownership 5. 3%

Clear Perspective and Targets 2. 9%

Hard-Working, Focused Staff 2. 4%

Some factors that contributed to job will be discussed below:

- Individual Involvement

Among the key to success in a task is user participation, minus the user's involvement, it may cause of failure to the entire job. Even if the project was delivered on time, and on budget, a project has a high rate of declining if the task will not meet user's needs.

-Executive Management Support

This affects the process and progress of your Project and lack of executive type can put a project at a severe drawback.

-Clear Statement of Requirements

-Proper Planning

Proper planning is one of the main parts of creating a project, having poor planning of the project may cause a severe drawback to the project and lead to a failure.

-Realistic Expectations

Expectations of the project development result must be rational. If anticipations in creating a project aren't accurate, it may cause to failing in building the task itself.

-Smaller Task Milestones

One of the things to be needed for an entire success of a project is concluding smaller project millstones, the small details of a project should not be disregarded for this may lead to a minor failing. If these smaller milestones aren't being achieved, it could cause a major problem in the conclusion of the project.

-Competent Staff

Staff members play the biggest role in a task development, without the correct knowledge or skill of an employee member may cause a poor final result to a development of a job. Workers should be proper trained and have the proper experience before getting associated with the task that they can be handling through the job development.


-Clear Vision and Objectives

-Hard working

Every staff of person that is involved with a job development must be keen and accountable in achieving goals. Uncommitted staff members could cause a improper results in the building process

First of all Figure out what business you are in, and then head your own business. Figure out what business you are in. Ensure that your business is practical. Select projects that are best for your business. Understand the business value in assembling your project watching for changes. Be diligent in your chosen business, learning and making use of best practices. Define what is inside and outside your area of responsibility. 50% of job management is simply paying attention.

Understand the customer's requirements and put them under version control. Carefully understand and document the customer's requirements, obtain customer agreement on paper, and put requirements documents under version id and change control. Requirements management is the leading success factor for systems development assignments.

Prepare a reasonable plan.

Prepare a plan that defines the scope, agenda, cost, and methodology for an acceptable project. Involve job owners in producing plans and estimates, to ensure feasibility and buy-in. In case your plan is just barely possible at the outset, there is no need an acceptable plan. Utilize a work breakdown framework to provide coherence and completeness to minimize unplanned work.

Build a good team with clear ownership. Get good people and trust them. Establish clear ownership of well-defined tasks; ensure they have got tools and training needed; and provide timely feedback. Trail against a staffing plan. Emphasize wide open communications. Create an environment in which team dynamics can gel. Move misfits out.

Lead the team.

Track project position and give it wide awareness. Track improvement and conduct recurrent reviews. Provide huge visibility and marketing communications of team improvement, assumptions, and issues. Do methodical reviews of management and technological issues to help manage customer prospects, improve quality, and identify problems before they get out of palm. Trust your indicators. This is part of paying attention.

Use Baseline Settings.

Establish baselines for the merchandise using construction management as well as for the task using cost and routine baseline monitoring. Manage changes intentionally. Use measurements to baseline problem areas and then trail improvement quantitatively towards alternatives.

Write Important Stuff Down, Share it, and Save it. If it was not on paper, it didn't happen. Record requirements, plans, steps, and growing designs. Documenting thoughts allows these to advance and improve. Without documentation it is impossible to own baseline settings, reliable communications, or a repeatable process. Track record all important agreements and decisions, along with supporting rationale, as they could resurface later.

If it hasn't been tested, it generally does not work. If this is not absolutely true, that is definitely a good working assumption for job work. Develop test situations early to help with understanding and verification of the requirements. Use early screening to validate critical items and reduce complex risks. Tests is a profession; take it really.

Ensure Customer Satisfaction. Keep carefully the customer's real needs and requirements continuously because. Undetected changes in customer requirements or not focusing the task on the customer's business needs are sure paths to project failing. Plan early for adequate customer care products.

Be relentlessly pro-active.

Take effort and be relentlessly proactive in applying these ideas and determining and solving problems as they come up. Task problems usually worsen over time. Regularly address project hazards and confront them openly. Episode problems, and leave no rock unturned. Deal with any propensity to freeze into day-to-day tasks, just like a deer caught in the headlights.

http://www. hyperthot. com/pm_princ. htm

http://www. thelazyprojectmanager. com/

Also We Can Offer!

Other services that we offer

If you don’t see the necessary subject, paper type, or topic in our list of available services and examples, don’t worry! We have a number of other academic disciplines to suit the needs of anyone who visits this website looking for help.

How to ...

We made your life easier with putting together a big number of articles and guidelines on how to plan and write different types of assignments (Essay, Research Paper, Dissertation etc)