One of the primary inputs from the initiating phase is the creation of your requirements document. This is the most important element of your project plan apart from the schedule itself, because finely honed requirements result in a finely tuned schedule. Recall that the requirements should not change after the scope document has been signed and you' ve been authorized to proceed. The reason for this is the compounding effects that requirements additions—even small ones—spawn in the schedule. The tiny addition that you make to an already-finalized requirements document could result in a huge delay in a task s schedule.
The project' s deliverables need to be defined precisely, with clearly elucidated success metrics. In your schedule you track the deliverables, both the ones that are in progress and the ones that have finished.
Was this article helpful?