MP4PM: business case review - Schedule/Key Milestones; approval process

Hello Stephane,

i am sorry for producing this irritation. It was cause of the limited editing functions within the discussion board.
Like you can see now in the online version these are two different branches in the map (cause i did not want to create a single discussion thread only for the milestone branch).

And you are right about the approval process in general. This was meant as a specific approval process only for the deliverable here.

But i do also thinking about to take this off the map, what do you and of course the others also think about?

Regards,

Markus

My suggestion, Markus, would be to replace the approval process with the approval/escalation organizational chain. Basically, indicate who - or at least, what role - approves what, from most to least authority.

Hi Markus,

typically both the approval as well as the escalation process would be covered elsewhere. I don't think this belongs to the business case as a basis for decision making. If, for any reason, there are no other project initialization documents which would cover this, or if for certain projects there is a need to deviate from the usual process the business case could be used for this purpose for the simple and practical reason that it is typically signed off by exactly the same people who would need to know about or approve such things...
Of course people later on can use the maps and adapt them to their organizational needs and processes by just combining branches as needed, but for now I'd follow a pure content based approach...