Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 6 · Rate Schedules and Pricing
What breaks
Lesson 64 of 198 · 2 min
Six cases. One. "The transaction priced at zero." No derivable rate. Work down the hierarchy — and if you had built the resource class fallback from Lesson 4, this would not have happened. Two. "The rate is wrong and I cannot see why." A more specific override exists somewhere. Lesson 5's method, applied. Three. "A backdated timecard used this year's rate." Effective dating not applied — the old rate was overwritten instead of dated. Four. "A project on last year's terms is billing at new rates." No project-level override for the in-flight contract. That is a client conversation, not a support ticket. Five. "Delivery consultants can see everyone's cost rates." A CONFIDENTIALITY INCIDENT, NOT A CONFIGURATION DEFECT. Access not restricted. Nothing is broken. Somebody can see salaries, and the fix is a conversation about who should have been able to. Six. "Rates have not been updated in two years." No…
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.