Posts

Showing posts from August, 2011

IMPORTANT PROJECT PLAN REVIEW DOCUMENTS.

Project Documentation to Archive There are some key project documents that should be retained so that the lessons learned can be easily passed to future projects. This documentation includes: Project Scope Statement Project Team Structure Project Plan (originally baselined and all subsequent re-baselined plans) Issue Management Logs Change Requests and Change Logs Risk Management Report Budget (originally vs. actual) Close-out Project Evaluation Close-out Project Team Evaluation Final Reports and/or Recommendations FIND MORE ON THE PROJECT COACHING

THE BEST BLOG LINK FOR PROJECT MANAGEMENT GUIDE.

CLICK ON THE LINKS PICTURE ABOVE AND GET ENJOYMENT OR CLICK BELOW THE UNCLE SULE PROJECT BLOG LINK 1 THE BEST UNCLE SULE PROJECT LINK BLOG OUTREACH

IMPORTANCE OF EVALUATION.

Many people think of evaluation as taking a snapshot of outcomes at the end of a program to prove to a funder that it worked or failed. These same people don't hold evaluation in much regard because they feel they are getting too little information too late in the day, especially if their program fell short of expectations or made no difference at all. Evaluation can, and should, however, be used as an ongoing management and learning tool to improve an organization's effectiveness. Well-run organizations and effective programs are those that can demonstrate the achievement of results. Results are derived from good management. Good management is based on good decision making. Good decision making depends on good information. Good information requires good data and careful analysis of the data. These are all critical elements of evaluation. Evaluation refers to a periodic process of gathering data and then analyzing or ordering it in such a way that the resulting information

PROJECT OBJECTIVE IS EVERTHIN TO KNOW.

1. Define Project Objectives Define the objectives of the project as they relate to the goals and objectives of the organization. Project objectives are used to establish performance goals – planned levels of accomplishment stated as measurable objectives that can be compared to actual results. Performance measures should be derived for each goal. These measures can be quantified to see if the project is meeting the department’s objectives. Project performance can then be traced directly to the Department’s goals, mission and objectives, enabling participants to correct areas that are not meeting those objectives. Project objectives can be described in two ways: • Hard Objectives – Relate to the time, cost and operational objectives (scope) of the product or process • Soft Objectives – Relate more to how the objectives are achieved, and which may include attitude, behavior, expectations and communications. Project objectives can also be seen as a set of objective statements,

GOALS OF THE PROJECT MANAGER

The 5 Goals of a Project Manager These goals are generic to all industries and all types of projects. Regardless of your level of experience in project management, set these 5 goals for every project you manage. Goal 1: To finish on time This is the oldest but trickiest goal in the book. It's the most difficult because the requirements often change during the project and the schedule was probably optimistic in the first place. To succeed, you need to manage your scope very carefully. Implement a change control process so that any changes to the scope are properly managed. Always keep your plan up to date, recording actual vs. planned progress. Identify any deviations from plan and fix them quickly. Goal 2: To finish under budget To make sure that your project costs don't spiral, you need to set a project budget at the start to compare against. Include in this budget, all of the types of project costs that will accrue, whether they are to do with people, equipment, suppli