Top 10 mistakes ever made in project management

When it comes to projects, someone once said. "If everything goes exactly as planned, something happens somewhere massively wrong," and it is true, although the project managers have difficulty speaking it aloud, in the daily course of the project , errors occur. But the biggest question is whether this error will be something that the team members and project manager can learn from and never repeated, or that they will be constantly reduced and wrong procijenjen.Stalna struggle between customers and the demands of time and resources is what makes the project complex and repeating the process in such an environment, mistakes are the daily routine. But what are the key areas in which project managers can always try to improve and reduce errors?

Here are some suggestions:

Communication - it can never be too much. In order to know every detail of the task or problem, the project manager's responsibility to ensure that everyone involved is constantly updated on what's happening, what is their role, limits and dependence. What do you think is a vital sign of approaching disaster may occur on your project team as a minor glitch in the system. What we consider major changes to its original buyer can not seem to be the designer an easy change. To ensure you get the necessary information, one solution is to inform all staff of the project in advance what information your application, how often and in what format. Set goals and expectations - Each stakeholder has different expectations and images for the project. In order not to miss the customers' requirements, you must define the details, time and resources and budget properly so that each side can get what they expected. And of course, to make sure that your team can deliver what is promised. One of the goals of the project could be " to increase the overall level of customer satisfaction calls helpdesk to support the needs of the company ". For example, General Dynamics provides his PM's are familiar with the company need to maintain weekly meetings to discuss and debate new and ongoing projects, increasing the likelihood of choosing the best solution, while keeping projects on schedule (Heekens 2002). Banco Itamarati, a privately-owned Brazilian bank, attributed the success of your IT project to a clear vision and specific documented ciljeve.Tvrtka produces an annual net profit growth of 51% and moved from 47th to 15th place in the Brazilian banking industry. to be flexible, but learn to say no - List of participants desired can be infinite, but what is really applicable and feasible for you and your team know. Do you need to be flexible and accept changes in the project, but never accept something that will take the project over budget and are to deal with more than the allocated funds, time and effort. Consider Murphy Law -Never ignore risk management. Too many project managers are treated as an additional item, not to do-it-recurring event in the planning and control phases. Risks should be shared, evaluated and properly calculated, would not bring any surprises on the project. Start before you hear the whistle - Often project managers to start the project without a signed contract and terms agreed. This could be a bad idea that could lead to get loose or dissatisfied customer. Want to build a relationship and the client wants results quickly, so that goes against their policies and act. But sometimes a customer may change his mind and leave you in the middle of nowhere. Therefore, the project manager must be documented and at least get out on the project characteristics and needs of the client side. This is some protection, which can be skipped if you have built long term relationship with your client. nothing without the right resources and the right skills - Fit is critical, but the lack of allocated funds is still one of the top joint project management mistakes. They do not have the right people with the right skills doing the right thing for the project, can ubiti.Istraživanje conducted by IT Cortex, entitled "Reasons for the project weakened factors" was conducted among 365 IT managers from companies of various sizes and in different economic sectors shows that lack of funds is one of the main reasons for the failure of the project after the lack of support enforcement . It is interesting to note that lack of IT management and technology illiteracy at the bottom of the list, showing the transfer of technical skills super vještina.Najbolji plan or project ever could be ruined with a lack of skills. Therefore, project managers should carefully review staff skills and tasks. unreasonable deadlines - Setting deadlines that could not be achieved is a big problem. In order to impress and get project approval from the participants of the project managers often overestimate the abilities of the team. Great compromise between budget and time must be made by either the time of delivery of the project or staying within the budget could be pivotal cilj.Voditelj project must develop accurate and realistic time estimates for the project, and use this to convince the sponsor that the deadlines can not be achieved. The loss of contact with the WBS - break the structure of work is an important project, which provides a validated scale, including the phases and results. This is useful for creating a larger picture of the project requirements, and then to use this as a reference throughout. WBS should be designed in the scoping phase, completed in the planning stages, and is used as a key document control throughout the remainder of the project life cycle. always remain customer focused - When is deeply involved in the project, team members, they lose a sense of requirements kupaca.Najrelevantniji rule to follow here is that the "customer is always right even when it is not." This unique goal should be to attract and retain customer base and make it meet. One popular technique called Quality Function Deployment (QFD). QFD is a systematic procedure that places an intense focus on customer needs and translates those needs into detailed requirements. This is one of the best ways to ensure that the project requires compliance to customer needs. Another technique is called a CTQ (Critical to Quality) Tree. CTQ tree is used to decompose the broad requirements of customers in a more easily quantifiable requirements. Always use a project management tool - In today's dynamic environment, project management tool is needed for each project. One of the biggest mistakes a company can make use of new technology in a very visible and large-scale project. Having the right tool is really useful to keep projects on track, update and manage multiple projects simultaneously stakeholders time.It makes your job a lot easier and your project more flexible. For example, the feature task Seavus Project Viewer update could save a lot of time, lost documentation and monitor the progress of the project immediately.

A recent study of the Faculty of Computing and Information Technology, University of Malaya showed the critical factor in project success and failure among the top 10 reasons for failure were:. Lack of user input, unclear objectives, project and user focus and constant changes in requirements. These pretty much match the proposed error and field progress.

As a conclusion we can say that there are many other errors that can be encountered on the path of successful project management processes, but the field is constantly changing and evolving, so it will always be room for improvement and learning. Perhaps the biggest mistake of all is, if you never learn from your mistakes to prevent bigger ones. Project managers need to take the time and make a commitment to learn from experience and learning curve will begin to stack on each other process will be improve the productivity will increase.