- This topic has 1 reply, 2 voices, and was last updated 12 years ago by
.
- Posts
Hi,
I’m confused with where in the project life cycle the project initiation document comes in. Is it after the project design stage or definition stage? Because the document includes a lot of details like project timelines and team roles and responsibilities which would (I think) only be available once the project has been designed… please help me understand this as the examiner does seem to be a fan of project management! :S
Also, project definition is before approval of the project has been achieved right? I mean, stuff like budget allocations, resources available will all only be given once the business case is given (which is all in the initiation doc) and agreed upon. So what then do people so in the project definition stage? Just decide on what the final objective should be and what possible solutions exits (but broadly speaking, no specifics as this comes in design?)?
I’m sorry if I seem to be rambling, as you can see i’m quite confused with this topic!
I think of the PID as starting life at the initiation point of the project and it should certainly refer to scope, deliverables, sponsor and some estimates of cost and benefits and a risk analysis. Effectively this is a project definition.
As the project progresses details get filled in eg who is on the team, better quantification of benefits and timings, and also detailed project design. These details van be added to the PID so that it grows into a ‘bible’ of the system.
It should be said that project management is an area that has many writers and commercial companies advocating their own methodologies and terminologies. I think what I have described is an acceptable view of how things evolve.
HTH
- You must be logged in to reply to this topic.