Posted: Sun Mar 23, 2008 10:34 pm Post subject: Plans and PID
A schedule will contain the tasks and milestones associated with the scope/deliverables of the project. These should relate directly to the Project Approach and Project Objectives.
A plan will contain the assumptions, dependencies, resource levels, risks, and constraints associated with achieving the schedule.
Sensu is right about the PID forming the basis of the launching the project. There is no need to reissue this with every update. (unless there is a signifcant change or the project is in 'exception')
Accept that the plan & schedule is fluid. They are dynamic reflecting progress and the changing influences exerted on the project. The trick is to set the target /aspirational schedule and commit to the dates you know you can commit to. But to issue with Schedule with the context and constraints within which the schedule has been produced.
There is a document you can issue along with the schedule. It is ?conditions for delivery? and it can e found at www.great-project-management.com. It contains the key value topics within which the scheulde lives
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Logos/trademarks property of their owners. Comments property of their posters. Everything else is ? 2004 P2uG: The Prince2 Forum You can syndicate our Prince3 news using backend.php or perhaps ultramode.txt. International Prince2 PM Forum.