Loading... Please wait...

Register for BLOG

Stay on top and comment on the latest TOPtm ideas, views and occasional rants - REGISTER NOW



How to define your project policies

Who’s accountable for assigning or reassigning project resources? When does the project need to conform to the agreed methodology? These are other such policy questions are answered in this useful Guide.

This Guide discusses policies in 27 project delivery areas so as to fast track your organization’s project policy definition. We provide a blank Guide to that you can devise your own policies and publish them

Our approach to recommended policy definitions is designed to help ensure their observance where it matters.

Image 1
$19.95
(excluding tax)

Single User License

Immediate Download


Preview guide


This Guide was born out of seeing confusion, angst and outright anger at what was happening on projects when no one had set the rules.

The 27 critical areas we have defined allow the business and technical managers to work together with clear accountabilities that enable all parties to produce excellent results.

Recognising that not all policies are created equal, we have built a hierarchy of four levels of compliance from ‘Mandatory’ to ‘Guideline’. This ensures policies are not devalued by being forced in areas where they are not applicable.

Accompanying this Guide is a blank version that you can customize for your own organization. There are 

  • parameters to be set
  • recommended policy settings to be agreed
  • recommended compliance levels to be agreed

Your own customized policies can then be made available throughout your organization to help all project participants know what to do and who is to do it. It sure beats arguing!

This Guide is a foundation stone for effective project operations.

How to define your project policies

  1. How to implement these policies
  2. Understanding the ‘specific values’ to be set for your policies
  3. Project set up policies
  4. Project planning policies
  5. Project delivery policies
  6. Project closure policies
  7. Technology set up policies
  8. Technology planning policies
  9. Technology delivery policies
  • Project Investment Committees/Boards - who are accountable for setting, agreeing or ratifying project policies
  • PPMOs - who are often accountable for formulating and governing project policies
  • Auditors - to understand the nature and scope of project policies that should be in place
  • Resolves the areas of most common dispute on projects
  • Makes clear the ‘rules’ from the outset - and which are mandatory and which are not
  • Allows you to adapt our suggestions for your organization
  • Pre-empts conflict and confusion, angst and arguments

Coming soon