You are welcome Narayan. The key takeaway I think, is that after the Create WBS process the Project Scope Statement has a higher level of scrutiny. From that point on, it is linked with the WBS and the WBS dictionary as the Scope Baseline. So, if you make a change to the Project Scope Statement you are changing the Scope Baseline and must do so through formal change control procedures.

Many Thanks for the response.

I wish it were called Scope Statement "update" when developed for the 2nd time as an o/p of the Create WBS process.

The Project Scope Statement is an output of Define Scope and an input to Create WBS. It is the same document. You are correct that it is an output of Create WBS as part of the Scope baseline and coupled with the WBS and WBS dictionary. Key points to note about the scope baseline are:

- it is the approved version of the Project scope statement, WBS, and WBS dictionary.

- and can be changed only through formal change control procedures.

One way of looking at it is that it is the same document but a more mature version.

Hello,

What is the difference between the Project Scope Statment that is an Output of the Define Scope process and the Scope Statement developed (as component of Scope Baseline) in the Create WBS process?

Thanks & Regards,

Narayan Shanbhag