MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 2 · Security and Data Access

The roles a PPM project needs

Lesson 15 of 198 · 1 min

Seven roles, and what each is for. Project Manager — project delivery, plans, progress. Project Accountant — costing, adjustments, accounting. Project Billing Specialist — invoices, revenue, contract billing. Project Administrator — project setup and maintenance. Resource Manager — staffing and utilization, on the execution side. Team Member, or Employee — time, expenses, task work. Project Executive — portfolio-level visibility. The implementation consultant role. Broad, appropriate for setup, never for a business user. Combining roles at small clients is normal, and it creates the segregation-of-duties conflicts covered in Lesson 7. Do not pretend otherwise in either direction. COPIES DO NOT INHERIT NEW CAPABILITY AT EACH RELEASE. Register every copy. Review after upgrades. A copy made in year one is quietly missing three years of new privileges, and the symptom is a feature that "does not work for us".

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 2 · Security and Data Access

  1. 1The PPM security shape
  2. 2Project role versus job roleFree preview
  3. 3The roles a PPM project needs
  4. 4Provisioning users
  5. 5Business unit data access
  6. 6Project unit and project-level access
  7. 7Segregation of duties in project accounting
  8. 8What breaks
  9. 9Lab: build the access matrix, then build to it