There are times when key stakeholders join the project late and need to be brought up to speed. The

project plan is a good way of doing that and sometimes the only way. A good project plan is thorough

and well thought out. It is consistent throughout, eg: Don't introduce deliverables in the WBS if they are

not in the requirements list.

To create the project plan you will need to include a number of documents. A lot of the documents in a

project plan are based on templates that the organization or Project Management Office provides. The

$($T$)$ behind each requirement listed below will let you know whether a template for that section is

available.

$1.$ Provide a scope statement $($T$)$ how are you going to manage scope? Who is in charge of scope

changes? Include in your document a sample project change control form $($T$).$

$2.$ Create a requirements traceability document $($T$)$ listing ALL requirements and their source.

Explain how requirements were obtained? How will they be tracked to ensure completeness?

Create a schedule and resource list $($T$)$ show a breakdown of tasks with estimates in days or

weeks for each work package in the WBS$.$

$6.$ Create a stakeholder register $($T$)$ and communication plan $($T$).$ In the communication plan

identify the information the stakeholder will get, when they will get it$,$ how they will get it$,$ and

the objective of each communication activity.