2012年9月18日星期二

Patrice Bergeron #37 jersey

Patrice Bergeron #37 jersey -

"An elegant solution to the wrong problem solves nothing."

- Bryce's Law

INTRODUCTION

Commercial Project Management systems (PM) have been available since the early 1970's. Patrice Bergeron #37 jersey As PC's proliferated in the workplace, so did PM software, which also brought an ease-of-use element to project management. A multitude of PM products are now available on the market, some expensive, and some very reasonably priced. However, to say all PM packages were created equally would be a gross exaggeration. Each has a specific niche they address in project management or target a specific industry.


As I described in my article, "Why Does Project Management Fail?", one of the main reasons for failure is because there is a lack of consideration for the magnitude and complexities of project management and, consequently, there is a natural inclination to attack it in piece meal. As a result of the bulletin, I have been asked as to what criteria I would use to evaluate a PM package. Consequently, I have developed the following checklist for evaluating a PM package it its pristine form. I hope it will be of benefit to you.

GENERAL REQUIREMENTS:

The Project Management system should...


  1. Support any type of project - large or small; not just those limited to a specific part of the business (e.g, IT pplications). As such, it should be flexible in application and accommodate any

    and all methods of work effort (new development, maintenance, and modification/improvements).



  2. Distinguish between Direct, Indirect, and Unavailable activities. For background information, see:

    http://www.phmainstreet.com/mba/pride/pmmeth.htm#time



  3. Promote the "Mini-Project Manager" concept. For background information, see:

    http://www.phmainstreet.com/mba/pride/pmmeth.htm#minipm



  4. Provide an integrated approach to support all activities of project management, not just some; this includes Planning, Estimating, Scheduling, Reporting, and Control.



  5. Promote and enforce in-house project management standards; e.g., use of standard methodologies, labor rates, time reporting, detection of estimate/schedule overruns/underruns, etc.



  6. Provide a universally applicable calendar and allow for the specification of a standard reporting cycle.

PLANNING SUPPORT:

The Project Management system should...


  1. Support various Work Breakdown Structures (WBS) - not just a single methodology. This includes controllable levels of WBS (number of levels of detail). Also, provides a library facility for reusable methodologies that can be automatically loaded upon request. Ideally, the WBS can be tied to specific information Patrice Bergeron #37 jersey resources (such as systems, programs, files, etc.) thereby enabling the ability to record and monitor time for a specific information resource.



  2. Support internal project Patrice Bergeron #37 jersey dependencies (work step-to-work step) and external dependencies (project-to-project).



  3. Allow for multiple projects, multiple human resources (both internal employees and external contractors), and multiple assignments for a single human resource. (A "many-to-many" relationship between projects and human resources).



  4. Provide a Skills Inventory to track skills and proficiencies.



  5. Be able to manage project priorities and backlogs of user service requests (business objectives). A "priority modeling" tool is highly desirable to study the impact of change.

ESTIMATING SUPPORT:

The Project Management system should...


  1. Provide for both Detail estimates (for a specific phase of a project) and Order-of-Magnitude (for the entire project). For background information, see:

    http://www.phmainstreet.com/mba/pride/pm20.htm#types



  2. Allow multiple versions of estimates (after all, estimates will inevitably need to be revised).



  3. Provide a means to maintain estimating guidelines and generate tentative estimates accordingly.

没有评论:

发表评论