Showing posts with label Change Management. Show all posts
Showing posts with label Change Management. Show all posts

Wednesday, 9 June 2010

Key Project Manager Practices

Managing a project can be daunting, but using the right techniques and tools will help the project manager achieve a project no matter how complex or large it might be.  There are seven practices that any project manager can put to good use to ensure the success of the project.

Define the objectives, scope and stakeholders
Firstly, understand the project objectives. Deciding the real objectives will help plan the project.  The client may have many ideas, but often it turns out that most of those ideas are not applicable to the current project.
Scope is the boundaries of the project.  Deciding what’s in or out of scope will determine the amount of work which needs performing.

Determine the stakeholders, what they expect to be delivered and enlist their support.  The stakeholders will review the objectives and scope, and either agree with them, or indicate what needs to be changed before they can give their approval.

Define the deliverables
Define what will be delivered by the project.  Decide what things, whether product or service, will be delivered.  Document them in enough detail to enable someone else to produce them correctly and effectively.
Key stakeholders must review the definition of deliverables and must agree they accurately reflect what must be delivered.

Project planning
Define what activities are required to produce the deliverables using techniques such as Work Breakdown Structures. Estimate the time and effort required for each activity, dependencies between activities and decide a realistic schedule to complete them. Involve the project team in estimating how long activities will take. Set milestones which indicate critical dates during the project. Write this into the project plan. Get the key stakeholders to review and agree to the plan.

Communication
Project plans are useless unless they’ve been communicated effectively to the project team. Every team member needs to know their responsibilities. I once worked on a project where the project manager sat in his office surrounded by huge paper schedules. The problem was, nobody on his team knew what the tasks and milestones were because he hadn’t shared the plan with them. The project hit all kinds of problems with people doing activities which they deemed important rather than doing the activities assigned by the project manager.

Tracking and reporting project progress
Once your project is underway you must monitor and compare the actual progress with the planned progress. You will need progress reports from project team members. You should record variations between the actual and planned cost, schedule and scope. You should report variations to your manager and key stakeholders and take corrective actions if variations get too large.

Change management
By managing changes, the project manager can make decisions about whether or not to incorporate the changes immediately or in the future, or to reject them. This increases the chances of project success because 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 often a reason why projects fail.

Risk management
Risks are events which can adversely affect the successful outcome of the project.  Risks will vary for each project but the main risks to a project must be identified as soon as possible. Plans must be made to avoid the risk, or, if the risk cannot be avoided, to mitigate the risk to lessen its impact if it occurs. This is known as risk management. Not managing risks effectively is a common reason why projects fail. Download these  Project Risk Management Templates to reduce risk on projects. View the sample risk management templates in PDF - Project Risk Management templates

Monday, 7 June 2010

Developing a Project Plan

Developing a Project Plan

Template Tips: Developing a Project Plan
The first activity within the Planning phase is the creation of a Project Plan.  To create a Project Plan, you should first identify the ‘Work Breakdown Structure’ (WBS) which is a hierarchical set of phases, activities and tasks to be undertaken on the project. After the WBS has been agreed, an assessment of the effort required to undertake the activities and tasks is made.

The activities and tasks are sequenced, resources are allocated and a detailed project schedule is formed. This project schedule will become the primary tool for the Project Manager to assess the progress of the project. The Project Plan should include:
  • A detailed description of the project scope
  • A list of the project milestones (descriptions and dates)
  • A list of the project phases, activities and tasks
  • Resources/effort allocation against phases, activities and tasks
  • A project schedule depicting when the tasks will be undertaken
  • A list of planning dependencies, assumptions and constraints
Project Tips: How to properly Execute a Project

The Project Execution phase is the phase within which the deliverables are physically constructed and presented to the customer for acceptance. While the project team are producing the deliverables, the Project Manager should implement the following management processes to monitor and control the activities being undertaken:
  • Time Management (recording time spent against the project)
  • Cost Management  (keeping track of project expenditure)
  • Quality Management  (assuring and controlling the quality of deliverables)
  • Change Management (managing changes to scope, deliverables and timescales)
  • Risk Management (identifying, quantifying and mitigating potential project risks)
  • Issue Management (documenting and resolving project issues)
  • Procurement Management (sourcing of products and services from external suppliers)
  • Acceptance Management (gaining customer acceptance of project deliverables)
  • Communications Management (distributing communications within the project).