iStock_000001636839XSmall

(I am gonna park my ITSM credentials at the door for this somewhat tongue in cheek post.) 

What’s good for the User often is not good for the Administrator.  With Peter’s help, I have compiled a list of the top ten(nish) things which may drive up aspirin sales to the EPM implementing community:

  1. The ability to turn off task scheduling on a task by task basis.
  2. Understanding (and explaining) functionality differences between Standard and Professional.
  3. Troubleshooting project security now that security can both be delegated – and controlled by the PM on a project by project basis.
  4. The fact that backwards compatibility (BCM) can be turned off – but not back on.
  5. Having to go back and change any implementations using a field called “Department” before migrating.
  6. Having to train PM’s how to administer security.
  7. Managing multiple project workspace templates. (did somebody say content types?)
  8. How many databases did they say were in the default install with all services?  19?
  9. Both 32 bit and 64 bit client operating systems – with different VBA versions!
  10. Now we have to play nice with the Exchange folks.

Of course all of these headaches are intended to support great new features…..but who actually needs features anyway?  Just give the User a brick and cut the support cost IMHO.