...
The primary challenge I face is HOW to keep these documents alive and updated especially towards the end of the project.The connection between these documents is very sensitive, changing one part could lead to a lot of changes in many other docs, it is not only about the baseline.
My development approach, I start simple and then build it up systematically.
1. I am always concern about the scope clarity and the interpretation of the customer to it. The best possible scope statement is crucial in my approach.
2. Develop The project plan including baselines.
3. Explain the project plan to key stakeholders and discuss its key components.
3. Define roles and responsibilities.
5. Create the steps the team will take to manage variances to these plans.
One important aspect of the project plan is the communications plan. This document states such things as:
Who on the project wants which reports, how often, in what format and using what media
How issues will be escalated and when
Where project information will be stored and who can access it
What new risks have surfaced and what the risk response will include
What metrics will be used to ensure a quality product is built
What reserves have been used for which uncertainties.
Once the project plan is complete, it is important that its contents be delivered to key stakeholders. This communication should include such things as:
Review and approval of the project plan
Process for changing the contents of the plan
Next steps - executing and controlling the project plan and key stakeholder roles/responsibilities in the upcoming phases.
The project manager who takes time to create a clear project plan will follow a more direct route toward project success.
I am still trying to be more Agile in my approach.
Community Champion
