Wednesday, June 01, 2005

Suggested Categories and Measurements for Organizations Managing Projects

 
ON-TIME
  • What percent of projects has been completed on time (or within 10%)?
  • What is average overage in time as a percent?
  • What percent of active projects is on time and to-date according to earned value milestones?

ON-BUDGET

  • What percent of projects has been completed on budget (or within 10%)?
  • What is the average overage in cost as a percent?
  • What is the earned value variance?

CUSTOMER DELIVERABLES

  • Did the project meet customer expectations (general)?
  • Did the project meet specifically identified customer expectations defined at the beginning of the project? (i.e. what customer benefit was expected to justify the project)
  • Was training effective? (3 months later customers still understand project deliverable)
  • Was implementation effective? (target usage achieved in targeted timeframe)
  • Did implementation disrupt other priorities/processes more than expected?
  • Did the ongoing costs, including training, match expectations?

QUALITY PROJECT PROCESS

  • Customer felt the Project Team understood their needs and identified a good solution.
  • Roles of Project Team, Steering Team and Customers were well understood.
  • Customer meetings were held based on initial agreement (i.e. bi-weekly meetings).
  • Project status was updated based on initial customer agreement (i.e. weekly written reports).
  • Change process was well identified and managed appropriately.
  • Project Team had a "make-it-happen" attitude, and goes "over-and-above" to make the project successful with a sense of urgency.
  • Project Team creatively overcame obstacles encountered or issues raised in a way to optimize project results.
  • Problems were resolved through a disciplined, identified process.
  • Number of defects or project problems in initial and secondary testing processes.
  • Training and implementation issues were discussed and agreed to in advance.
  • Project implementation went smoothly with few defects, rewrites or project problems.

RISKS

  • Risks were identified throughout the project along with actions mitigating the risks
  • No/few "surprises" where project results were not expected
  • Number of change requests submitted
  • Number of change requests approved

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home