MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 7 · Project Types

What breaks

Lesson 76 of 198 · 2 min

"The project is not behaving as expected." Check in this order. One. Which project type was it created from? Two. Is the behaviour enabled on that type? Three. Is there a project-level override? Four. Is the expenditure type class permitted on the type? Five. Is the type's effective date valid? Six. Is the required downstream setup built — burden schedule, contract, asset setup? Then seven cases. One. "Costs are not burdening." Burdening not enabled on the type — or no burden schedule assigned. Two. "We cannot bill this project." NOT FIXABLE. THE PROJECT MUST BE RECREATED AND COSTS MOVED. Created from a non-contract type. Three. "Forty project types with identical behaviour." CONSOLIDATION MEANS RECREATING PROJECTS. Reporting differentiation modelled as types. Four. "Supplier invoices are landing on internal projects." Expenditure type class not restricted. Lesson 8's control, not used. Five. "Costs on a capital project are not capitalizable." The default set…

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.

See the course and enrol9 free lessons

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 7 · Project Types

  1. 1What a project type governs
  2. 2Project type classes
  3. 3Designing the type listFree preview
  4. 4Creating a project type
  5. 5Burdening options
  6. 6Capitalization options
  7. 7Classifications
  8. 8Expenditure type class controls
  9. 9Billing and other options
  10. 10Proving the type works
  11. 11What breaks
  12. 12Lab: five behavioural patterns and a stakeholder to answer