Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 7 · Project Types
Lab: five behavioural patterns and a stakeholder to answer
Lesson 77 of 198 · 2 min
Ninety minutes. Listen for the behaviours — the scenario is written as a list of them. Meridian runs: client engagements billed on a time-and-materials basis; a smaller number of fixed-price engagements where billing mechanics genuinely differ; internal initiatives that are not billed and should not attract supplier costs; a capital programme building out a new office fit-out and internally developed software; and pre-sales work that must be tracked but never billed and never capitalized. Every project must be reportable by practice — six practices — by region, three, and for client work by client segment: enterprise and mid-market. Contract projects burden at a standard overhead rate. Internal projects do not burden. The capital programme burdens at a different rate. AND THE PMO DIRECTOR — THE SAME ONE FROM MODULE 3 — HAS ASKED FOR A PROJECT TYPE PER PRACTICE. He asked for six project units in Module 3 and got…
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.
In this module: Module 7 · Project Types
- 1What a project type governs
- 2Project type classes
- 3Designing the type listFree preview
- 4Creating a project type
- 5Burdening options
- 6Capitalization options
- 7Classifications
- 8Expenditure type class controls
- 9Billing and other options
- 10Proving the type works
- 11What breaks
- 12Lab: five behavioural patterns and a stakeholder to answer
