As both an active project manager and a project management instructor, people often ask me what are the fundamental elements to successful project management. Though there has been many good books written on the subject, I often summarize what I consider to be the best practices in the middle of good project management.
Determine the scope and goals
For any project to become successful you'll need to determine what the project is supposed to attain. Suppose your boss asks you to organise a campaign to obtain the employees to donate blood. Is the purpose of this to get just as much blood contributed to-the local blood bank? Or, is it to boost the profile of the organization in the neighborhood area? Determining what the real aim is may help you to determine how you start planning and managing the project.
The project manager also needs to define the range of the project. Is the business of transport to simply take team to the blood bank within the range of the project? Or, must staff make their own way there? Determining which actions are within the scope or out of scope of the project includes a major impact on the amount of work which must be done during the project.
If you're planning to get their support and determine what every person needs to-be sent from the project an awareness of who are the stakeholders is also crucial. When you've defined the scope and goals, you'll want to get the stakeholders to review them and accept them together with agreeing who must be on-the listing of stakeholders.
Establish the deliverables
You should define what things (or items) should be provided by the end-of the project, to reach the desired outcome from the project. If your project is an marketing
Strategy for a new chocolate bar, the other of the deliverables might be the graphics for a magazine ad. So, you need to decide what real things are to be provided and document in enough detail what these things are. At the end of-the time, some-one will end up working on the project to make the deliverable, so that it needs to be clearly and unambiguously identified.
After you have identified the deliverables, you'll need to have the key stakeholders evaluate the work and cause them to agree that this accurately and unambiguously shows what they expect to be delivered from the project. Once they have agreed, you can begin to prepare the project. Maybe not defining the deliverables in enough detail or clarity is often a reason why projects go wrong.
Project planning
This is actually the time when you determine how you will achieve the required outcome of the project embodied with-in the objectives and definition of deliverables. Planning requires the project manager determines which budget, resources and people are required to complete the project. You will have to decide if you will separation your project into manageable stages, decide which products will be provided in each phase, and decide the composition of your project team. You should decide what actions are required to create each deliverable, since you have already defined the deliverables.
You can use techniques such as Work Break-down Structures (WBS) to help you to do this. You'll need to calculate the time and energy necessary to complete each task, dependencies between related activities and choose a reasonable schedule to complete the activities. If you have an opinion about protection, you will seemingly claim to learn about istanbul director. It's often advisable to involve the project team in calculating how long the activities will take given that they will be the people actually doing the work. Record all of this to the project plan document. You also have to get the key stakeholders to examine and consent to this plan.
When building the project plan, a project manager is usually under pressure to generate a plan which meets the (unrealistic) expectations of some of the stakeholders. It is essential here the project manager pops up with a realistic plan - the one which he/she thinks is realistic to accomplish. You will be doing no body a favor if you succumb to pressure and consent to provide the project in a totally unrealistic schedule.
Conversation
Even the very best made project plans are useless unless they have been communicated efficiently to-the project team. To get a second viewpoint, please consider checking out: read more. Everybody else on the group has to know exactly what is expected of them, what their duties are, and what they are in charge of. I once done a project where the project supervisor sat in his office surrounded by large color print outs of his latest ideas. The problem was, nobody on his team knew exactly what the goals and tasks were because he'd not discussed the plan with them. For sure the project hit all kinds of difficulties with people going down and doing the activities that they considered important instead of doing the activities given by the project manager.
Tracking and reporting project progress
Once your project is underway and you have an agreed plan, you'll need to constantly check the real progress of the project against the progress. To do this, you'll have to get reports of progress from the project team members who're actually carrying it out. You will have to record any variations between your planned and actual price, schedule and scope. You'll need to record any variations for your manager and key stakeholders and just take corrective measures in the event the variations get too large.
There are lots of ways that you can change the program in order to obtain the project straight back on track (change the order of tasks, assign tasks in parallel if the variation is small, or add more staff to the project or reduce the range if the variation is extremely large).
All tasks need the project manager to constantly manage three things: price, scope and plan. Then one of the other elements will inevitably have to be changed too, In the event the manager increases one of the. So, for a project that is running behind schedule to recover so it may be delivered to it's original prepared schedule, the budget may be improved by utilizing more staff (although this usually never achieves the desired consequence of decreasing the time left to complete the project), or the scope will need to be paid off. It is the juggling of those three components - called the project pie - that usually causes a project manager to tear their hair out in frustration!
Change management
All jobs change indirectly. Usually, a vital stakeholder at the center of a project will change their mind about what the project must provide. On tasks of longer period, the business environment has frequently changed since the start of the project, so assumptions made in the beginning of the project may no longer be appropriate. This usually leads to the opportunity or deliverables of the project having to be changed. If your project manager only accepted all of these changes to the project, the project would inevitably be delivered late (and perhaps would never be finished) and would inevitably go over budget.
By managing changes, the manager could make decisions about whether or not to include the changes quickly or in the future, or to refuse them. This increases the probability of project success since the project manager controls how the changes are incorporated, can allocate resources accordingly and can plan when and how the changes are made. Not managing changes effectively is usually cited as being a important reasons why projects fail.
Danger management
Challenges are any events which can adversely affect the successful results of the task. I have worked on projects where some of the risks have included: team lacking the technical skills to execute the job precisely, hardware perhaps not being shipped on time, the control room coming to risk of flooding in a major thunderstorm and many others. Risks will be different from project to project but it's important to determine the major dangers to a project when possible and to plan the activities necessary to prevent the risk, or, if the risk cannot be prevented, to at least reduce the risk so as to lessen its influence if it does occur. This is exactly what is known as risk management.
Do you manage all dangers? No, because there could be too many to manage, and not all risks have the same influence. Therefore a simple way would be to discover as much risks as you can, work out how likely each risk would be to happen on a scale of 1 to 3 (3 being the worst), estimate its effect on the project on a scale of 1 to 3 (3 being the worst), then multiply the two numbers together. The result may be the risk weighting. A higher risk weighting is one of the most serious risk. Only control the top five risks i.e. the people with the greatest risk weighting. Since they have a habit of moving up at unforeseen times constantly evaluate the risks and constantly be searching for new risks.
Perhaps not managing challenges efficiently can be frequently cited as a major reason projects fail.
Overview
Therefore, in a nutshell, these best-practices are-the main things that I'd assume all project managers to complete. They're appropriate on all tasks large or small. Project management is not rocket science. Applying guidelines on your project cannot promise that your project comes in under budget, on time and exceeds most of the objectives of the stake-holders, but applying them will certainly give you a much better potential for delivering your project successfully than if you don't use them on your project.